Bug 1114248

Summary: display-manager.service timeouts with Xorg
Product: [openSUSE] openSUSE Distribution Reporter: Sebastian Wagner <sebix+novell.com>
Component: X.OrgAssignee: Michal Srb <msrb>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <xorg-maintainer-bugs>
Severity: Normal    
Priority: P5 - None CC: msrb, sebix+novell.com
Version: Leap 15.0   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: systemctl status display-manager.service
Xorg log of a successful start

Description Sebastian Wagner 2018-10-31 21:10:29 UTC
Created attachment 788091 [details]
systemctl status display-manager.service

At nearly every boot of one of my 15.0 systems (upgraded from 42.3) the display manager service does not start. It timeouts after 2 minutes and then I have to manually start it, which works fine. The Xorg log does not contain anything for this Xorg start, just the successful (manual) one before.

Attached is the status of the service.
Comment 1 Sebastian Wagner 2018-10-31 21:11:38 UTC
Created attachment 788092 [details]
Xorg log of a successful start
Comment 2 Michal Srb 2018-11-01 07:49:04 UTC
This could be related to bug #1110199 - plymouth can take any amount of time (even indefinite) after it is told to quit. The display-manager will wait for plymouth to quit before starting the X server.

Do you use plymouth? Could you try to boot without any "splash" parameter on the kernel command line?

If that doesn't change anything, could you try if different display manager makes a difference. Right now it seems that you are using lightdm.
Comment 3 Sebastian Wagner 2018-11-13 19:52:44 UTC
Yes! I use plymouth and booting without splash does work.

Should the current version of plymouth fix this issue? Because I have the most current version installed: 0.9.3+git20181016.a588b3f-lp150.3.3.1
Comment 4 Stefan Dirsch 2018-11-13 21:47:59 UTC
(In reply to Sebastian Wagner from comment #3)
> Yes! I use plymouth and booting without splash does work.
> 
> Should the current version of plymouth fix this issue? Because I have the
> most current version installed: 0.9.3+git20181016.a588b3f-lp150.3.3.1

This one is obviously older than the patch Michal created with
https://bugzilla.opensuse.org/show_bug.cgi?id=1110199#c41

and you would need plymouth from Tumbleweed. Unfortunately it will take ages until a fixed plymouth for Leap 15 will be available.:-(
Comment 5 Michal Srb 2018-11-15 08:37:21 UTC
The fixed plymouth is on its way to future Leap update, now all we can do is wait.

In the meantime you can keep plymouth disabled as a workaround. In case you really want to have splash now, you can build yourself the version 0.9.4 from https://build.opensuse.org/package/show/Base:System/plymouth
Comment 6 Michal Srb 2018-11-15 08:38:24 UTC

*** This bug has been marked as a duplicate of bug 1110199 ***