http://bugzilla.suse.com/show_bug.cgi?id=1148242 http://bugzilla.suse.com/show_bug.cgi?id=1148242#c1 --- Comment #1 from ravas mi ---

display-manager.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found.

Just FYI, plymouth is uninstalled on this system. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148242 http://bugzilla.suse.com/show_bug.cgi?id=1148242#c3 --- Comment #3 from ravas mi --- Created attachment 816484 --> http://bugzilla.suse.com/attachment.cgi?id=816484&action=edit full boot log for lighdm -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148242 http://bugzilla.suse.com/show_bug.cgi?id=1148242#c5 --- Comment #5 from ravas mi --- Created attachment 816486 --> http://bugzilla.suse.com/attachment.cgi?id=816486&action=edit full boot log for gdm -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148242 http://bugzilla.suse.com/show_bug.cgi?id=1148242#c7 --- Comment #7 from ravas mi --- I can log in as root and then do telinit 3 -> telinit 5 and the display manager will load. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148242 http://bugzilla.suse.com/show_bug.cgi?id=1148242#c9 --- Comment #9 from ravas mi --- I noticed that he also had "Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found." So I decided to reinstall plymouth, removed "plymouth.enable=0", and added back "splash=silent" and "quiet" to the kernel parameters. The first two boots have successfully loaded the display manager. I'll report back, if it fails, or in a few days otherwise. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148242 http://bugzilla.suse.com/show_bug.cgi?id=1148242#c11 --- Comment #11 from ravas mi --- Booting with "quiet splash=silent" removed and "plymouth.enable=0" has also been working with no problem. What is the correct way to uninstall plymouth via zypper? "zypper rm plymouth" wants to uninstall 2 packages. "zypper rm -u plymouth*" wants to uninstall 14. Is "dracut --force" equivalent to "mkinitrd" and do I need to run one of these after uninstalling? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148242 http://bugzilla.suse.com/show_bug.cgi?id=1148242#c13 --- Comment #13 from ravas mi --- I decided to try a less aggressive uninstall and used YaST2. It uninstalled plymouth and plymouth-dracut. The first two boots have loaded lightdm. I get the following from journald: Sep 03 20:51:28 systemd[1]: Starting Show Plymouth Boot Screen... Sep 03 20:51:28 systemd[1]: Received SIGRTMIN+20 from PID 341 (plymouthd). Sep 03 20:51:28 systemd[1]: Started Show Plymouth Boot Screen. Sep 03 20:51:28 systemd[1]: Started Forward Password Requests to Plymouth Directory Watch. Sep 03 20:51:29 systemd[1]: Starting Plymouth switch root service... Sep 03 20:51:29 systemd[1]: plymouth-switch-root.service: Succeeded. Sep 03 20:51:29 systemd[1]: Started Plymouth switch root service. The system sure does (or tries to do) a lot with something that is supposed to be uninstalled. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148242 http://bugzilla.suse.com/show_bug.cgi?id=1148242#c15 --- Comment #15 from ravas mi --- So following from my YaST uninstall of the two packages, I looked at the output of "lsinitrd" and found a lot of plymouth stuff still in there. I guess that's why the boot loaded lightdm without a problem. I then ran `dracut --force --omit "plymouth"`, which effectively cleaned the initramfs of all mention of plymouth. I rebooted and lightdm failed to load. So it seems like some aspect of plymouth needs to be in the initramfs -- otherwise this problem manifests. I've noticed "plymouth-quit.service" is mentioned in "display-manager.service" under "After=", "Conflicts=" and "OnFailure=" (hence the journal message). I reinstalled plymouth and lightdm loaded fine. No surprise at this point. I'm just going to leave plymouth installed and use "plymouth.enable=0", which worked fine for several days; although, I won't consider this resolved until we understand why plymouth as become a pseudo-dependecy. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148242 ravas mi changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Starting service |display manager fails to |lightdm..failed |load when plymouth is | |uninstalled -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148242 Alynx Zhou changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alynx.zhou@suse.com Assignee|bnc-team-screening@forge.pr |sb56637@gmail.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148242 http://bugzilla.suse.com/show_bug.cgi?id=1148242#c18 --- Comment #18 from ravas mi --- For reference, this is everything removed by "zypper rm -u plymouth*"

gnu-unifont-bitmap-fonts libply-boot-client4 libply-splash-core4 libply-splash-graphics4 libply4 plymouth plymouth-branding-openSUSE plymouth-dracut plymouth-plugin-label plymouth-plugin-label-ft plymouth-plugin-two-step plymouth-scripts plymouth-theme-bgrt plymouth-theme-spinner

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148242 http://bugzilla.suse.com/show_bug.cgi?id=1148242#c20 --- Comment #20 from ravas mi --- I didn't get the coredump, but the display manager still failed to load (logs are the same as the original attachments). Oh well. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148242 http://bugzilla.suse.com/show_bug.cgi?id=1148242#c22 --- Comment #22 from ravas mi --- No problems so far using the Intel HD Graphics 4600 via the motherboard's VGA connector and xf86-video-modesetting. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1148242 S. B. changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|sb56637@gmail.com |screening-team-bugs@suse.de -- You are receiving this mail because: You are on the CC list for the bug.