Incorrect scaling in native Gnome 47 UI

[shawnyeager]

I installed via Arch AUR, running Gnome 47. In apps like Firefox, the cursors appears to render correctly, however in Gnome UI, Files/Nautilus, etc., the cursors appear to be 2x size and heavily pixelated.

[sgoudham]

Hey 👋,

That's disappointing to hear since v1.0.0 was meant to fix all the issues on GNOME. Could you provide a screen recording showing what happens when the cursor moves from Firefox to something like Files/Nautilus?

We're making use of KDE Breeze's scripts for generating the scales so it may be a problem in that script we need to fix or something else entirely.

[ARKye03]

I installed via Arch AUR, running Gnome 47. In apps like Firefox, the cursors appears to render correctly, however in Gnome UI, Files/Nautilus, etc., the cursors appear to be 2x size and heavily pixelated.

+1 I support this, on Hyprland the catppuccin-cursors-mocha pkg from AUR seems off completely, with a size of 24 it's too big, and 20 it's too small, however, I can work with 24, yet with a size of 20 it looks pixelated and incomplete(some borders of the cursor won't render they appear cut. I set the cursor via hyprctl setcursor "catppuccin-mocha-dark-cursors" 20

[sgoudham]

If you're on Hyprland, scaling is a known issue (#31) because I believe the current implementation uses PNGs in order to work around a different bug raised a while back. @kerichdev can provide more context about that.

[ARKye03]

If you're on Hyprland, scaling is a known issue (#31) because I believe the current implementation uses PNGs in order to work around a different bug raised a while back. @kerichdev can provide more context about that.

Oh, I see, yes that seems to be related to my comment above...

[Covkie]

on a fresh user with Gnome session cursor sizes are correct across all applications regardless of toolkit.

you most definitely have conflicting settings.

[shawnyeager]

Thanks, @sgoudham. I've tried to record using Gnome's built in recorder, as well as flameshot, but neither one capture the pointer, oddly enough (see below). Any ideas on how to capture?

Screencast.From.2024-10-25.09-21-37.webm

[shawnyeager]

@Covkie No other cursor set exhibits this behavior, or I might agree.

[jinliu]

This is a known GTK 4.16 bug. You can find explanation in the end of this article:

https://blogs.kde.org/2024/10/09/cursor-size-problems-in-wayland-explained/

It's triggered when you have scaling, and a cursor theme whose nominal size != image size.

It's fixed in GTK but not backported to 4.16.

If Catppuccin use a nominal size 32 instead of 24, it would work around the problem.

[Covkie]

I am on gtk 4.16.3 and dont have the wonkiness and yeah .3 has the fix? So all you need to do is update.

edit: realized this issue is for fractional scaling. can repro

[shawnyeager]

I was already running 4.16.3 on Arch, so that didn't fix it for me.