Usability with HiDPI #60

New issue

Open

opened 2022-01-10 22:25:55 +01:00 by simon · 0 comments

simon commented

2022-01-10 22:25:55 +01:00

Owner

Fortunately, many things work out of the box. Most things that don’t are related to wayland or rather the lack of support thereof.

A more or less complete list of things that do not work that well:

Almost all Linux-native games (no wayland support in their SDL version)
All wine games (no wayland support in wine)
Unexplainably high memory usage (no process seems to use it?)
- /proc/meminfo with all high-footprint applications (including sway) terminated, at this point around 9GiB were used (not available), though it should have been less than 1GiB.
- This does not happen directly after start, but it accumulates over time but then seems to stay constant
- This probably is not necessarily due to hidpi/4k screen but rather because of qutebrowser running under wayland (higher resolutions amplify the memory usage)
- Current workaround: If the memory usage gets too high, close qutebrowser, run nix run nixpkgs#stress -- -m 16 --vm-bytes 1024M -t 10s, open qutebrowser again
- Seems to have gotten way less intense after upgrade to 22.05
~~Low-res icons in claws-mail (can Adwaita be used?)~~ (I now use aerc)
dolphin (does not respect QT_QPA_PLATFORM)
yuzu (hardcodes qt platforms xcb or wayland (not wayland-egl!); opengl backend crashes, vulkan produces transparent surface)
qutebrowser has hard to locate memory leaks when running wayland-native (see above)
GIMP (uses GTK2)
jameica/hibiscus (properly scales, but icons are huge and UI is almost unusable)

General Workarounds

Set scale to 1 temporarily while using a game, starting steam with GDK_SCALE=2 steam-sandbox to make it readable

Fortunately, many things work out of the box. Most things that don’t are related to wayland or rather the lack of support thereof. A more or less complete list of things that do not work that well: * Almost all Linux-native games (no wayland support in their SDL version) * All wine games (no wayland support in wine) * Unexplainably high memory usage (no process seems to use it?) + [/proc/meminfo with all high-footprint applications (including sway) terminated](https://gist.github.com/sbruder/84ad03459cdcd73705ff625a0f7e2332), at this point around 9GiB were used (not available), though it should have been less than 1GiB. + This does not happen directly after start, but it accumulates over time but then seems to stay constant + This probably is not necessarily due to hidpi/4k screen but rather because of qutebrowser running under wayland (higher resolutions amplify the memory usage) + Current workaround: If the memory usage gets too high, close qutebrowser, run `nix run nixpkgs#stress -- -m 16 --vm-bytes 1024M -t 10s`, open qutebrowser again + Seems to have gotten way less intense after upgrade to 22.05 * ~~Low-res icons in claws-mail (can Adwaita be used?)~~ (I now use aerc) * dolphin (does not respect `QT_QPA_PLATFORM`) * yuzu (hardcodes qt platforms `xcb` or `wayland` (not `wayland-egl`!); opengl backend crashes, vulkan produces transparent surface) * qutebrowser has hard to locate memory leaks when running wayland-native (see above) * GIMP (uses GTK2) * jameica/hibiscus (properly scales, but icons are huge and UI is almost unusable) ### General Workarounds * Set scale to 1 temporarily while using a game, starting steam with `GDK_SCALE=2 steam-sandbox` to make it readable