[Bug]: Mouse cursor does not respect .Xresources in home dir

[hholst80]

Checklist

• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug that matches the one I want to file, without success.
• If this is an issue with a particular app, I have tried filing it in the appropriate issue tracker for the app (e.g. under https://github.com/flathub/) and determined that it is an issue with Flatpak itself.
• This issue is not a report of a security vulnerability (see here if you need to report a security issue).

Flatpak version

1.12.7

What Linux distribution are you using?

Pop!_OS

Linux distribution version

22.04

What architecture are you using?

x86_64

How to reproduce

Configure .Xresources with a higher DPI suitale for a 4K display. Observe that applications like Telegram desktop adapts to this seting. Now launch telegram in flatpak. That is a QT application. The size of the UI is correct. However, the cursor size is not correct. The mouse cursor will not be affected as it is done in native desktop applcations.

⋊> ~ cat .Xresources                                                                                                                  12:22:44
Xft.dpi: 192
⋊> ~                                                                                                                                  12:22:46

Expected Behavior

The mouse cursor should be consistent with native desktop app.

Actual Behavior

The mouse cursor is not updated when .Xresources is updated.

Additional Information

mental note. wow was that a lot of boilerplate. i bet still this wont be fixed though so it was all for nothing. that is always the case, organizations that spend a lot of time on boilerplate get very little fixed on actual user issues.

[jcleng]

Always there, for a long time

###
Operating System: NixOS 22.11
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Kernel Version: 5.15.97 (64-bit)
Graphics Platform: X11
Processors: 16 × Intel® Xeon® CPU E5-2650 v2 @ 2.60GHz
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series

###
Resolution: 3840x2160
Font DPI: 192
###
Flatpak 1.14.0

not Effects:
org.kde.Platform

Effects:
org.gnome.Platform
org.freedesktop.Platform

[LorbusChris]

There is a workaround, see e.g. flathub/im.riot.Riot@082f107

[jcleng]

today try use gnome cursors theme can a solved

# download like: https://www.gnome-look.org/p/2002505
# ~/.icons/default/index.theme
mv ./* ~/.icons/default/

#└❯ tree -L 1 /home/jcleng/.icons/default
#/home/jcleng/.icons/default
#├── cursors
#└── index.theme

[jcleng]

when app use freedesktop sdk, mount icons/ dir use Flatseal global /home/jcleng/.icons/:rw

└❯ flatpak info org.mozilla.firefox|grep SDK
 SDK： org.freedesktop.Sdk/x86_64/22.08


wget https://kgithub.com/alvatip/Sunity-cursors/releases/download/2.0/Sunity-cursors.tar.gz
tar -zxvf Sunity-cursors.tar.gz -C $HOME/.icons/
rm -rf default
mv Sunity-cursors default

[hfiguiere]

.Xresources might not be accessible because of filesystem permissions.

[rkfg]

when app use freedesktop sdk, mount icons/ dir use Flatseal global /home/jcleng/.icons/:rw

I don't even have that directory and there are some old .png icons in ~/.local/share/icons. I tried all the workarounds from #709 and nothing works. I even shared the entire home directory just to test it with flatpak --user override --filesystem=home and it changed nothing. Gnome apps (like flatseal) work fine and the cursor there is consistent with my host system. Qt apps built on org.kde.Platform and Brave on org.freedesktop.Platform (for example) use the default black cursor.

I use AwesomeWM and I load Xorg settings from ~/.Xresources with xrdb -merge ~/.Xresources.

Never mind, turned out I didn't have the cursor theme installed on the host. I had it set to Xcursor.theme: DMZ-White but didn't have dmz-cursor-theme package installed. For some reason it looked fine (I couldn't find where exactly it pulled the cursors) but broke in flatpak. After installing the package all apps now behave well (no overrides needed, I removed them all and everything still works).