[Bug 1030606] New: Restart of sddm only works after killing sddm process / sddm service does not show as running
http://bugzilla.opensuse.org/show_bug.cgi?id=1030606 Bug ID: 1030606 Summary: Restart of sddm only works after killing sddm process / sddm service does not show as running Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: okurz@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- ## observation On an openSUSE Leap 42.2 (x86_64) with sddm 0.13.0-8.1 when reaching sddm login, selecting text terminal, logging in, `systemctl status sddm` reports sddm to be inactive. Also, restarting the service will try to start another service and make the system unusable because the display manager constantly tries to restart itself. ## steps to reproduce * boot system with sddm enabled * wait for sddm ready * switch to text terminal and login * call `systemctl restart sddm` * observe error ## expected result * systemctl status sddm should show the service running when the process is running * systemctl restart sddm should ensure the system is restarted and ready for login afterwards ## workaround Killing sddm processes and restarting service works -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1030606
http://bugzilla.opensuse.org/show_bug.cgi?id=1030606#c2
Wolfgang Bauer
On an openSUSE Leap 42.2 (x86_64) with sddm 0.13.0-8.1 when reaching sddm login, selecting text terminal, logging in, `systemctl status sddm` reports sddm to be inactive.
In openSUSE we use a generic display-manager.service that starts the DM specified in /etc/sysconfig/displaymanager. So it is normal and to be expected that sddm.service is inactive. Unless you enabled it manually via "systemctl enable sddm.service". I suppose that's what you mean with "boot system with sddm enabled", do you? But IIRC, you need to disable display-manager.service before for this to work. "systemctl enable sddm.service" will change the link /etc/systemd/system/display-manager.service to point to sddm.service instead, but there may still be a xdm.service too (that points to the real display-manager.service and cause display-manager.service to be started). Maybe that's the problem you experienced? What's the exact output of "systemctl status sddm.service" and "systemctl status display-manager.service"? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com