Patch for GTK 4.16 for incorrect cursor size on KDE

There is a GTK 4.16 bug where there would be a huge cursor. GTK has merged fixes but for main branch meaning, it’ll be fixed with GTK 4.18

TLDR: Cursor is pixelated and too large on GTK4 apps

Relevant threads:

I the meantime, would it be possible to apply wayland: Bring back the pointer viewporter (!7760) · Merge requests · GNOME / gtk · GitLab over the GTK 4.16 (currently unstable branch)?

I cannot reproduce the issue on three machines. All are running GNOME, two with Wayland sessions. :man_shrugging:

If you did not already know, Manjaro is based on Arch. Most packages including gtk4 are synced directly from Arch.

If you can reproduce the issue on Arch, feel free to submit a gtk4 bug report. However, I doubt Arch will add the MR as a patch–especially if they can’t reproduce it.

Then we’ll have to wait. It’s possible upstream will tag it before GNOME 47.1 in a few weeks. We’ll see.

1 Like

Its only in the title, but OP seems to be referring to KDE only.

I can reproduce this on a Plasma system with one of the only gtk4 apps I have/tried.

gtk4bug

Ah, my bad apparently this is only on KDE. I do not have GNOME to test it unfortunately :confused:

Nope. I can reproduce it on Gnome and Sway with only GTK4 Applications on Wayland. Actually, when I switch the cursor theme to Adwaita (default), it scales correctly. So xcursor-breeze actually results in:

(gnome-system-monitor:7764): Gdk-WARNING **: 10:57:51.343: ../gtk/gdk/wayland/gdkcursor-wayland.c:210 cursor image size (64) not an integer multiple of theme size (24)

So in my understanding it is the theme that needs to be updated, to be compatible with wayland. The cursor size here is 64px and the default size is set to 24px at dconf. So the image size is 64px and wayland requires here the half. So set it to 32px and it looks good. No more warnings.

dconf read /org/gnome/desktop/interface/cursor-size
dconf write /org/gnome/desktop/interface/cursor-size 32
1 Like

Yes, one of the solutions for breeze is to regenerate it with nominal-size set to 32
Or set it via dconf, thanks!

By the way, the fix is included in 4.16.3, so we’ll see it a little sooner than we might have thought.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.