I’m new as far as snaps go, although I feel like this is a symptom of sandboxing.ĮDIT: A key note is that I’m running on X11 - Could this be the case where the XSETTINGS isn’t set up properly to get the default cursor? The long-term solution is for someone to reach out to the KDE Neon team and see what needs to be done for them to go all-in on the kde-neon extension. All the KDE snaps are open source, so a community member should be able to go through all the snaps and add gtk-common-themes support. The short-term solution is for somebody to take a look at the custom neon tooling and docs, and fix it so they also use the icon themes snap. The KDE Neon team, however, mostly still uses custom tooling which doesn’t automatically add the gtk-common-themes snap. That extension adds support for the icon themes (I added this myself).
However, they might be more comfortable with only adding the gtk-common-themes snap. Spotify should probably upgrade to the gnome-3-28 extension.However, many apps still use the older desktop helpers, which require you to manually add support for gtk-common-themes.
GTK apps and all other apps (except 32-bit apps, GTK+ 2 apps and Qt apps) should use the gnome-3-28 extension. The easiest method is to use the gnome-3-28 extension. For cursors specifically, it should include the following line: content snap-name:icon-themes gtk-common-themes:icon-themes` You can see whether a snap uses gtk-common-themes by running snap connections snap-name after it is installed. Depending on what kind of snap it is, this is easier or harder to do. Without those cursor themes, the cursor will fallback to the ugly pixelated X11 one. Application snaps like spotify should connect to gtk-common-themes so they have access to all the common cursor themes. The issue is that these snaps do not use the icon themes from gtk-common-themes.
0 kommentar(er)
