4 ms·

Things that I can't get to work on Wayland: * Getting the display scale just right. I have a 3k by 2k laptop screen. 1x is too small and 2x is too big. * Gett

Things that I can't get to work on Wayland: * Getting the display scale just right. I have a 3k by 2k laptop screen. 1x is too small and 2x is too big. * Getting the mouse cursor to be drawn at a consistent size. Now the size varies when you move it across windows which is unacceptable. Am I missing something? Both of these seem like basic issues that someone must have figured out a solution to.

Schnouki 3y ago
I use 1.5x on my Framework 13 laptop (2256x1504) and it works perfectly :) Way better than Xorg, especially when using multiple displays with different scales or fractional scales. For the mouse cursor, I had the same issue with Xwayland windows until I explicitly setup a cursor theme. Now that works too... and I suspect it was also because of that display scale thing.
- andrewmackrodt 3y ago
  Are you using any electron based apps? I find them to be much blurrier when using fractional scaling versus Xorg so I'm running my monitors at native rather than my preferred scale of 125% (2K 16" and 4K 27" displays). IIRC, vs code supported some extra arguments (--enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland) but this didn't work universally across electron applications and caused very noticeable input lag in others such as Discord.
  - TheCycoONE 3y ago
    Yes xwayland just renders the application in the original size and scales it leading to a very blurry experience. Using only native apps avoids it so I find it a little hard to knock wayland instead of say electron or X. This is the issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1318 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1318
galkk 3y ago
Wayland is supposed to have fractional scaling now. I think wdisplays lets you configure it. #1 was was never solved by X11 properly, and I'm forced either have large fonts on 27" 2K and ok fonts on 4K 32" or ok fonts on 27" and small on 32", because I'm limited by one Xft.dpi
- thtas 3y ago
  I found fractional scaling to be way better handled under X11. If you fractional scale under wayland you get terrible blurriness everywhere as if they're upscaling instead of downscaling.
  - zdragnar 3y ago
    I've had the opposite experience, but I've really only used swaywm in Wayland, so maybe it is an issue specific to a DE?
    - mksybr 3y ago
      with i3 i use an xrandr oneline to set the fractional scaling and it works great. xrandr --output DP-2 --scale 0.6x0.6
      - maxdamantus 3y ago
        This will still result in bluriness, since it is scaling the already rasterised image, instead of informing the application to render at a different pixel resolution. X11/Xorg has long supported proper per-display fractional scaling, since the usual resolution in 96 DPI, which can easily be multiplied by 1/0.6 and set per-display using `xrandr --dpi 160/DP-2`. It is still however up to frameworks (Gtk, Qt) to detect and implement this. I've seen Qt applications handle this automatically, but not Gtk. My last Wayland-related post on HN [0] was about how it handled this worse than X11 due to lack of proper fractional scaling. AAIU, this has since been added to the protocol, but based on sibling posts, it sounds like framework support is still in the same state as in X11 (ie, works in Qt, not in Gtk). [0] https://news.ycombinator.com/item?id=32021261 https://news.ycombinator.com/item?id=32021261
Kudos 3y ago
Search for "fractional scaling" with the name of your DE and you should get the answers you need.
dheera 3y ago
I can't get input methods working on Wayland in Chrome. I need to use the fallback X11 mode in Chrome. It's been an issue for months.
MindSpunk 3y ago
I'm guessing you're using GNOME? Gnome doesn't support proper fractional scaling currently because GTK's current API only supports an integer scaling factor. There's an experimental feature that fakes it with 2x scale to GTK and downscales in the compositor.
SAI_Peregrinus 3y ago
Gnome (or rather GTK) is currently lagging on fractional scaling support, KDE Plasma seems to get it correct. For mouse cursors changing size, I fixed that on my system by ensuring the XDG desktop portal for KDE was enabled. Not sure that was the real fix, but it seemed to let KDE handle cursor rendering even over GTK windows.

Schnouki 3y ago

I use 1.5x on my Framework 13 laptop (2256x1504) and it works perfectly :) Way better than Xorg, especially when using multiple displays with different scales or fractional scales. For the mouse cursor, I had the same issue with Xwayland windows until I explicitly setup a cursor theme. Now that works too... and I suspect it was also because of that display scale thing.

andrewmackrodt 3y ago
Are you using any electron based apps? I find them to be much blurrier when using fractional scaling versus Xorg so I'm running my monitors at native rather than my preferred scale of 125% (2K 16" and 4K 27" displays). IIRC, vs code supported some extra arguments (--enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland) but this didn't work universally across electron applications and caused very noticeable input lag in others such as Discord.
- TheCycoONE 3y ago
  Yes xwayland just renders the application in the original size and scales it leading to a very blurry experience. Using only native apps avoids it so I find it a little hard to knock wayland instead of say electron or X. This is the issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1318 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1318

galkk 3y ago

Wayland is supposed to have fractional scaling now. I think wdisplays lets you configure it. #1 was was never solved by X11 properly, and I'm forced either have large fonts on 27" 2K and ok fonts on 4K 32" or ok fonts on 27" and small on 32", because I'm limited by one Xft.dpi

thtas 3y ago
I found fractional scaling to be way better handled under X11. If you fractional scale under wayland you get terrible blurriness everywhere as if they're upscaling instead of downscaling.
- zdragnar 3y ago
  I've had the opposite experience, but I've really only used swaywm in Wayland, so maybe it is an issue specific to a DE?
  - mksybr 3y ago
    with i3 i use an xrandr oneline to set the fractional scaling and it works great. xrandr --output DP-2 --scale 0.6x0.6
    - maxdamantus 3y ago
      This will still result in bluriness, since it is scaling the already rasterised image, instead of informing the application to render at a different pixel resolution. X11/Xorg has long supported proper per-display fractional scaling, since the usual resolution in 96 DPI, which can easily be multiplied by 1/0.6 and set per-display using `xrandr --dpi 160/DP-2`. It is still however up to frameworks (Gtk, Qt) to detect and implement this. I've seen Qt applications handle this automatically, but not Gtk. My last Wayland-related post on HN [0] was about how it handled this worse than X11 due to lack of proper fractional scaling. AAIU, this has since been added to the protocol, but based on sibling posts, it sounds like framework support is still in the same state as in X11 (ie, works in Qt, not in Gtk). [0] https://news.ycombinator.com/item?id=32021261 https://news.ycombinator.com/item?id=32021261

Kudos 3y ago

Search for "fractional scaling" with the name of your DE and you should get the answers you need.

dheera 3y ago

I can't get input methods working on Wayland in Chrome. I need to use the fallback X11 mode in Chrome. It's been an issue for months.

MindSpunk 3y ago

I'm guessing you're using GNOME? Gnome doesn't support proper fractional scaling currently because GTK's current API only supports an integer scaling factor. There's an experimental feature that fakes it with 2x scale to GTK and downscales in the compositor.

SAI_Peregrinus 3y ago

Gnome (or rather GTK) is currently lagging on fractional scaling support, KDE Plasma seems to get it correct. For mouse cursors changing size, I fixed that on my system by ensuring the XDG desktop portal for KDE was enabled. Not sure that was the real fix, but it seemed to let KDE handle cursor rendering even over GTK windows.