Unable to change SDDM theme with dr460nized

Decided to try the dr460nized version of Garuda a couple of days ago, since I wanted to try the nvidia-tkg ISO and fix some things I messed up in my previous install, and I'm loving it, but there's this one thing that is bugging me, and I'm not sure if it is by accident or by design.

The only thing I don't like in the stock theme is the Sweet SDDM theme and wanted to change it, but every time I make the change in the settings, it never actually changes the theme, if I close and open the authentication screen menu it always is set to the Sweet theme. If I uninstall the garuda-dr460nized package everything works fine, but then I'd have to manually reinstall everything related to the theme.

Are you sure you log-out and not scrren-lock?

cat /etc/sddm.conf
cat /etc/sddm.conf.d/*.conf

This is kind of funny since the SDDM theme never applied for me, instead Breeze was used even though the exact sddm config that KDE creates when applying the theme is shipped :roll_eyes:
Try the following to delete the config files:

sudo rm /etc/sddm.conf.d/kde_settings.conf
sudo rm /etc/sddm.conf.d/sddm.conf

And set the theme afterwards using the SDDM-kcm


I found that weird as well, because I remember when I first booted into the system after I installed it, Breeze was the sddm theme, and every time after that it was Sweet.

But it works now, thanks for the help. :blush:


I also have these settings (.d/*.conf) but my theme is changed with system settings in /etc/sddm.conf. Really funny, if not scary... :scream:

1 Like

The thing is I dont see the logic behind this - for some it works for others it doesnt :sweat_smile:
Glad to see you its working now though @joojmachine :smiley:


From man sddm.conf:

Configuration loads all files in the configuration directories followed by the configuration file in the order listed below with the latter having highest precedence. Changes should be made to the local configurations.

              System configuration directory

              Local configuration directory

              Local configuration file for compatibility

I think the logic is that distro/vendor should not provide an /etc/sddm.conf, using /etc/sddm.conf.d for default distro values.
Then, the local admin, using KDE GUI Sddm kcm, will apply changes to /etc/sddm.conf, which are parsed last, overriding specific settings.
It seems KDE GUI (sddm) writes all available/controllable settings in /etc/sddm.conf to override previous ones that overlap.