Flatpak Cursor Size

[ericfrance]

I’ve noticed, for many Flatpak apps, that the cursor size is very little. How to solve this problem ?

[hub]

Do you have examples of apps? Do you use an HiDPI screen?

[ericfrance]

HiDPI screen : NO, I’m using a desktop with a 23 inch screen, resolution 16801050 (16:10) (max allowed 19201080) (16:9). I tried 1920*1080 and it does not change anything.

Examples of apps where the mouse cursor is small (not the size I chose) : Most of them : Firefox, Gradio, KGeography, gPodder, Clocks, Calculator, Wire, Contacts, To Do, Thunderbird, Blink, Qbittorrent, Fondo, Avidemux, Bookworm, Pdf Tricks, Icon Library, Byte, Calibre, Gnome Maps, Celluloid

Examples of apps where the mouse cursor is the right size (the size I chose) : Gimp, Libre Office, Linphone, Gedit, Handbrake, Beaker, Teo, VLC

[Mohabdo21]

I had this issue on GNOME (Wayland), and I used this one-liner to apply my UI configuration to all installed Flatpaks:

for app in $(flatpak list --app --columns=application); do
  flatpak --user override "$app" \
    --filesystem=~/.icons/:ro \
    --filesystem=/usr/share/icons/:ro \
    --filesystem=~/.themes/:ro \
    --filesystem=/usr/share/themes/:ro \
    --filesystem=~/.fonts/:ro \
    --filesystem=/usr/share/fonts/:ro \
    --env=GTK_THEME=$(gsettings get org.gnome.desktop.interface gtk-theme | tr -d \')
done

i hope it helps

[CodedOre]

Just my two cents, but a few things to mention:

First, you can issue global overrides by omitting the app id, so the loop is unnecessary.

Next, ~/.themes, ~/.icons and ~/.fonts are deprecated for a while now. These folders should be in the XDG_DATA_HOME, which under most systems is under ~/.local/share.
So, the proper folders would be ~/.local/share/themes, ~/.local/share/icons and ~/.local/share/fonts. Also, in the Flatpak override, you should reference to XDG_DATA_HOME with xdg-data.

Also, the GTK_THEME environment variable is meant for debugging purposes. Using this in this way just asks for some apps breaking visually.

Lastly, and this may just be my opinion, but rather to add random overrides as an temporary fix I think it makes more sense to look into why this is happening, and to resolve the issue itself.
This is ignoring the fact that the original post is 5 years old by now, so it could very well be resolved already.