http://bugzilla.opensuse.org/show_bug.cgi?id=1110364 Bug ID: 1110364 Summary: Systemd Display Manager service 20 sec start on non-UEFI system - various scripts bypass the systemd mechanism Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: bugrprt21882@online.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- An alternative analysis to that described in Bug 1110199. The SUSE/openSUSE script '/usr/lib/X11/display-manager' ignores the systemd unit file mechanism -- the calls "/usr/bin/plymouth quit" and "plymouth --wait" conflict with the systemd "Plymouth quit" and "Plymouth quit wait" services. Given the "After=" dependencies in other systemd unit files, I suggest that, the following be done: * Recognise that, the system is being initialised by systemd and retain the current script behaviour for the case that, the system is **not** using systemd for the system initialisation. It's actually quite simple: "ps -q 1 -o comm=" returns a string that may or may not be "systemd". This leads to the following suggested changes: # /usr/lib/X11/displaymanagers/sddm # Modify: sddm_start_proc () { + pid1name=$(ps -q 1 -o comm=) + if [ 'systemd' != $pid1name ]; then if [ -x /usr/bin/plymouth ]; then /usr/bin/plymouth quit fi + fi return 0 } # # /usr/lib/X11/display-manager # Modify: plymouth_quit() { + pid1name=$(ps -q 1 -o comm=) + if [ 'systemd' != $pid1name ]; then if [ -x /usr/bin/plymouth ]; then plymouth quit plymouth --wait fi + fi } # # /usr/lib/systemd/system/display-manager.service # Remove the Plymouth quit service conflict: - Conflicts=getty@tty7.service plymouth-quit.service - Conflicts=getty@tty7.service plymouth-quit.service plymouth-quit-wait.service + Conflicts=getty@tty7.service # # /usr/lib/systemd/system/sddm.service # Remove the Plymouth quit call: - ExecStartPre=-/usr/bin/plymouth quit --retain-splash # -- You are receiving this mail because: You are on the CC list for the bug.