Please reboot after upgrading to SDDM 0.20 (Snapshot 20230630+)
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
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. 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
-- Regards, Joe
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
On 13.07.2023 01:49, Joe Salmeri wrote:
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 ???
On 7/13/23 00:00, Andrei Borzenkov wrote:
On 13.07.2023 01:49, Joe Salmeri wrote:
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 ???
Hi Andrei, Thanks, that address the /run/lock messages but it does not seem mention the sddm messages that I explained here: 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 -- Regards, Joe
Am 13.07.23 um 00:49 schrieb Joe Salmeri:
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 ???
I had the message about /usr/lib/sysusers.d as well but figured it was harmless. Apparently the package was previously shipping system-user-sddm.conf, and now ships sddm.conf, and during the update, both files coexisted for a brief time. (Or a longer time, if you're using ZYPP_SINGLE_RPMTRANS=1 like me.) Since it's functionally just moving the file (the "GECOS" column changed, but that's just sugar as far as I know), ignoring one of the lines should be fine. Not sure if this is always going to work out though, so maybe filing a bug isn't the worst idea. Best regards, Aaron
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
I have 2 monitors on my system. The left monitor is set at the primary. After updating to 20230705 with SDDM 0.20 the cursor is on the secondary ( right ) monitor for me to login instead of being on the primary ( left ) monitor. -- Regards, Joe
participants (4)
-
Aaron Puchert -
Andrei Borzenkov -
Fabian Vogt -
Joe Salmeri