You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Distribution (version): (Doesn't matter in this case)
Desktop environment: GNOME
Installing method: Papirus Installer
App name (version): Refine, used to change the icons
The GTK section for the Papirus Installer installs the icons in $HOME/.icons, which is a legacy path for GNOME, and Refine will not pick up Papirus icons in the settings. Using the KDE section however, the icons do show up, as the icons are in $HOME/.local/share/icons instead, which Refine picks up fine.
In my opinion, I think the GTK section could be misleading if one is using GNOME and Refine, instead of GNOME and GNOME Tweaks, and as Refine is going to be a modern replacement for GNOME Tweaks for many, I think the KDE section can be recommended for both GNOME and KDE, and the GTK section can still be there, but for GTK-based desktop environments.
The text was updated successfully, but these errors were encountered:
I agree that a Papirus install in a user's home directory should probably go in XDG_DATA_HOME/icons, though. ~/.icons is not deprecated yet, but using it for housing anything other the user's own personal icons seems bad.
The GTK section for the Papirus Installer installs the icons in $HOME/.icons, which is a legacy path for GNOME, and Refine will not pick up Papirus icons in the settings. Using the KDE section however, the icons do show up, as the icons are in $HOME/.local/share/icons instead, which Refine picks up fine.
In my opinion, I think the GTK section could be misleading if one is using GNOME and Refine, instead of GNOME and GNOME Tweaks, and as Refine is going to be a modern replacement for GNOME Tweaks for many, I think the KDE section can be recommended for both GNOME and KDE, and the GTK section can still be there, but for GTK-based desktop environments.
The text was updated successfully, but these errors were encountered: