Quote Originally Posted by dcurtisfra View Post
With respect to the Plymouth "quit wait" issue, assuming that Plymouth is enabled, these two Bug Reports are currently being worked: <https://bugzilla.opensuse.org/show_bug.cgi?id=1110199> and <https://bugzilla.opensuse.org/show_bug.cgi?id=1110364>.
  • With Plymouth enabled, my current "work around" is to add a "plymouth-quit-wait.service" Conflict to '/usr/lib/systemd/system/display-manager.service' -- yes, yes, the file is by default write protected but, as "root" the vi command "w!" deals with this situation …
If I read your bug report and suggestion above correctly, would the workaround be just adding "-wait" to an existing "plymouth-quit.service" conflict? Or is it added as an additional conflict? I found this in my /usr/lib/systemd/system/display-manager.service:
Description=X Display Manager
Conflicts=getty@tty7.service plymouth-quit.service
After=ypbind.service gpm.service time-sync.target winbind.service acpid.service
Wants=remote-fs.target dbus.socket systemd-user-sessions.service systemd-logind.service
After=remote-fs.target dbus.socket systemd-user-sessions.service systemd-logind.service getty@tty7.service plymouth-quit.service