Summary: | Excessive Cursor Size in GTK4 Applications on KDE Plasma 6 Under Wayland with Scaling Above 100% | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | reiokorn |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | ad.liu.jin, cwo.kde, dobrovvvvvvvv, jgqehj55, sbarnard86 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
reiokorn
2024-09-24 12:18:35 UTC
Thank you for the detailed bug report! Unfortunately, gtk does not support the cursor-shape-v1 Wayland protocol yet, which should solve this. For more information see this gtk issue and the links there: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/6212 There are some hacks that you can try, for example here: https://www.reddit.com/r/kde/comments/133dkad/gtk_mouse_scaling_on_wayland/ It may also help to use a cursor theme with a lot of sizes available, in case you're using something other than breeze. *** This bug has been marked as a duplicate of bug 451158 *** This is actually a GTK4 bug/regression. It's triggered when you have global scaling AND a cursor theme with "nominal size" (the size you choose in the Cursor Theme KCM) different from image sizes. E.g. if you run `xcursor-viewer /usr/share/icons/breeze_cursors/cursors/`, you'll see info like "Nominal size: 24. Image size: 32x32.". But for `xcursor-viewer /usr/share/icons/Adwaita/cursors/`, it will be "Nominal size: 24. Image size: 24x24.". So it can be worked around by using a cursor theme like Adwaita. I've already submitted the fix, but it hasn't been merged yet: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/7722 So I'll change this to UPSTREAM, as this doesn't really require `wayland/cursor-shape-v1` to fix. And it worked in GTK 4.14. It's a recent regression in their code. *** Bug 495951 has been marked as a duplicate of this bug. *** *** Bug 495965 has been marked as a duplicate of this bug. *** *** Bug 496856 has been marked as a duplicate of this bug. *** |