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.
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
Try the following to delete the config files:
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.
SYNOPSIS
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.
/usr/lib/sddm/sddm.conf.d
System configuration directory
/etc/sddm.conf.d
Local configuration directory
/etc/sddm.conf
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.