Andrey Viktorov

@gbenedict had same problem on dokku with heroku-buildpack-ruby and heroku-buildpack-apt, worked for me, thanks!

Tested your Apr 13 sct-10 flatpak [from here](https://github.com/rankynbass/XIVLauncher.Core/releases/tag/steamtool-1) with flatpak-ed Steam, didn't noticed any obvious issues. When game is closed Steam now correctly handles that, so probably that'll be a...

A little bit more of a context: I've considered just enabling development mode in production deployment and configuring redirect url exactly as I wanted, but I'm unsure of other implications...

A front-end message about caveats and lots of warnings in docs can be useful, just like now there is a message when using http url without development mode enabled

Just updated to 1.6b, issue is still present:  After I select that blurry text, it becomes normal, until window loses focus. EndeavourOS, 4K screen with 150% scaling, installed via...

> EndeavourOS, 4K screen with 150% scaling, installed via AUR Issue persists on the different machine (laptop) with the same OS and the same display settings

> What I suspect is happening here is that the compositor is synthesizing its own window for fractional scaling, and that isn't picking up the correct information. When moving wezterm...

I've bisected it down to this commit: ``` d1684d38e83d31dcd28dfc7dcc36ac4ba9eb582c is the first bad commit commit d1684d38e83d31dcd28dfc7dcc36ac4ba9eb582c (HEAD) Author: MaeIsBad Date: Sat Feb 8 21:33:12 2025 +0100 Fix crash on hidpi...

Here's the full log: WAYLAND_DEBUG=1 wezterm-gui -n ``` [2999862.490] -> wl_display#1.get_registry(new id wl_registry#2) [2999862.502] -> wl_display#1.sync(new id wl_callback#3) [2999865.057] {Display Queue} wl_display#1.delete_id(3) [2999865.068] wl_registry#2.global(1, "wl_compositor", 6) [2999865.079] wl_registry#2.global(3, "zwp_tablet_manager_v2", 1)...

For me problem also occurs on NVIDIA with 150% scaled 4K display. Just updated to the latest wezterm git version on my laptop with Intel iGPU, and issue is not...