On 6/30/23 05:58, Fabian Vogt wrote:
Hi,
in SDDM 0.20, the protocol between the greeter and the daemon changed a bit, which means the greeter from 0.20 will not start properly if the daemon from 0.19 is still running. It's not possible to restart the daemon automatically during/after the upgrade, as this would stop all sessions.
The result is that directly after upgrading to sddm 0.20, performing a logout will end up in a black screen. So instead of logging out, just select reboot or shut down directly.
If you by accident end up at the black screen, press Ctrl-Alt-F1 to switch to a console and press Ctrl-Alt-Del to trigger a reboot. Or log in as root and run "rcxdm restart; exit" to restart the daemon.
Cheers, Fabian
On 7/7/23 15:55, Joe Salmeri wrote:
Just updated several machines to 20230705 which has SDDM 0.20.
Received the following messages during the zypper dup
/usr/bin/systemd-sysusers --replace=/usr/lib/sysusers.d/sddm.conf - /usr/lib/sysusers.d/system-user-sddm.conf:2: Conflict with earlier configuration for user 'sddm' in -:1, ignoring line.
Rebooted after DUP finished and everything appears to be working.
Does anything need to be done to resolve this ?
NOTE: that /usr/lib/sysusers.d/sddm.conf already exists
Also received this error multiple times during the DUP
/usr/lib/tmpfiles.d/suse.conf:10: Duplicate line for path "/run/lock", ignoring.
Nobody else received those messages during their zypper dup ???
-- Regards, Joe