Hello,
I’m currently using Kripton theme for my desktop. Everything is working fine until I restart my pc, then the ‘Legacy Applications’ is set to null. This makes many applications appear in default theme instead of Kripton. I tried to set the theme to Kripton again but it still happens when I turn off the pc.
hmm - the theme is set/applied when the user is logged in
into the session
so:
the $HOME directory not being available at that point
does not sound plausible
as the user is … using that very $HOME directory
but I made my point in my first post - the theme might not be working for the current Gnome environment …
and we have not had any feedback since
I have seen strange things from Gnome, imho its the most convoluted linux desktop. In the past I had a similar situation with themes.
As far as placing a theme in /usr/share/themes instead of ~./.themes, it makes little difference. All its doing is adding color. But perhaps /usr/local/share/themes would be a better place.
But getting back to the Kripton theme. Its not incompatible. Otherwise they couldnt load it in the first place, only to loose the setting on reboot.
To make sure I booted into my Gnome partition, updated it, and put Kripton v40 in ~./.themes. Enabled it as the legacy them in Appearance, and rebooted several times. The theme just worked.
I’m facing the same issue, but with Tokyonight-Moon-BL. As suggested, I moved my themes from ~/.themes to /usr/share/themes, but this didn’t fix the issue though.
EDIT: I’ve also tried with Nordic theme, and the same issue happens. I tried setting the theme with
gsettings set org.gnome.desktop.interface gtk-theme Nordic-v40
gsettings set org.gnome.desktop.wm.preferences theme Nordic-v40
but the theme just won’t stick. If I restart gnome-shell with ALT+F2 and typing ‘r’, the same issue occurs. Only themes that actually stay after restarting gnome-shell are the ones that come with Manjaro.
I was having the same issue, but I noticed it was related to an extension called (Legacy (GTK3) Theme Scheme Auto Switcher), once I disabled this extension the issue disappeared.