When editing settings, configuration is saved only the first time I hit "Apply". Further changes are discarded, applying the configuration has no effect. Reproducible: Always Steps to Reproduce: 0. Open lightdm-kde configuration 1. Select the classic theme. 2. Change the welcome message to some garbage. 3. Hit "Apply" and confirm the PolicyKit dialogue. 4. Change the welcome message again. 5. Hit Apply again. 6. Close configuration. 7. Check the content of /etc/lightdm/lightdm-kde-greeter.conf Actual Results: The garbage message is still in the config. Expected Results: It should have saved the new message when I hit "Apply" the 2nd time. This also happens in current master.
I can't reproduce this. I don't get a policykit prompt the second time, but it is still saved.
I just tried it again with 0.3.0 - the bug is still present and reproducible here (Debian testing amd64). It should be reopened. Please let me know if and how I can help debugging.
Re-opened. Run "kcmshell4 lightdm" from a terminal and paste any output.
Here you go: $ kcmshell4 lightdm true loading sessions adding session "lightdm-xsession" adding session "kde-plasma" adding session "razor" loading themes ("/usr/share/kde4/apps/lightdm-kde-greeter/themes/") "/usr/share/kde4/apps/lightdm-kde-greeter/themes/classic/theme.rc" "adding theme" "Classic" "/usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/theme.rc" "adding theme" "User Bar" changed changed changed changed changed changed false <after 1st apply> changed changed I inserted the <after 1st apply> mark after hitting "Apply", entering the password and hitting enter. So, the "false" is from the first time the config file is saved, while the "changed" is from when I edited the welcome message again.
We no longer use lightDM, having moved to SDDM several years ago. As such, this bug report is no longer applicable. Bugs reports for the new SDDM-based login screen should be filed to one of two places: 1. Visual/UI bugs with the login screen UI itself, or feature requests: plasmashell | Theme - Breeze 2. Bugs with the login/user switching process: https://github.com/sddm/sddm/issues