FS#55960 - [sddm] 0.16.0-1 causes hang at boot

Attached to Project: Arch Linux
Opened by Nicola Mori (snack) - Thursday, 12 October 2017, 08:01 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 03 December 2017, 14:52 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Antonio Rojas (arojas)
Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 10
Private No

Details

Description:
Today's update to sddm 0.16.0-1 broke the boot process on my system. The sddm login screen does not show up, with no errors logged to console. From journalctl I get:

ott 12 09:47:17 elric sddm[424]: Setting default cursor
ott 12 09:47:17 elric sddm[424]: Running display setup script "/usr/share/sddm/scripts/Xsetup"
ott 12 09:47:17 elric sddm[424]: Display server started.
ott 12 09:47:17 elric sddm[424]: Socket server starting...
ott 12 09:47:17 elric sddm[424]: Socket server started.
ott 12 09:47:17 elric sddm[424]: Greeter starting...
ott 12 09:47:17 elric sddm[424]: Adding cookie to "/var/run/sddm/{3ccdee95-2320-47ce-9f49-921de96b78e3}"
ott 12 09:47:17 elric sddm-helper[450]: PAM unable to dlopen(/usr/lib/security/pam_elogind.so): /usr/lib/security/pam_elogind.so: cannot open shared object file: No such file or d
ott 12 09:47:17 elric sddm-helper[450]: PAM adding faulty module: /usr/lib/security/pam_elogind.so
ott 12 09:47:17 elric sddm-helper[450]: [PAM] Starting...
ott 12 09:47:17 elric sddm-helper[450]: [PAM] Authenticating...
ott 12 09:47:17 elric sddm-helper[450]: [PAM] returning.
ott 12 09:47:17 elric sddm-helper[450]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)

Reverting to sddm 0.15 fixes the problem.
This task depends upon

Closed by  Antonio Rojas (arojas)
Sunday, 03 December 2017, 14:52 GMT
Reason for closing:  Fixed
Additional comments about closing:  sddm 0.16.0-3
Comment by Nicola Mori (snack) - Thursday, 12 October 2017, 08:31 GMT
Sorry, I got confused when reading the logs. The reported log is for version 0.15 which actually works despite of errors in the log. With 0.16 there's almost nothing about sddm in journalctl:

ott 12 10:21:45 elric sddm[439]: Initializing...
ott 12 10:21:45 elric sddm[439]: Logind interface found
ott 12 10:21:45 elric sddm[439]: Starting...

but the greeter screen does not show up.
Comment by Antonio Rojas (arojas) - Thursday, 12 October 2017, 08:50 GMT
can you try with the upstream provided sddm.conf?
Comment by Konstantin Plotnikov (konstantin) - Thursday, 12 October 2017, 13:55 GMT
Seems it is this:
https://github.com/sddm/sddm/issues/905
Comment by Doug Newgard (Scimmia) - Thursday, 12 October 2017, 16:39 GMT
Sounds like a race condition. Try putting your video module in the initramfs.
Comment by Christopher (cchurchill82) - Friday, 13 October 2017, 03:25 GMT
Putting video module (i915 with intel_agp) fixed this for me, thank you
Comment by daimonion (demon) - Friday, 13 October 2017, 09:20 GMT
Putting "radeon" in the initramfs fixed this for me. :)
Comment by Antonio Rojas (arojas) - Friday, 13 October 2017, 09:34 GMT
Thanks for the feedback, please forward this information to the upstream report
Comment by Nicola Mori (snack) - Friday, 13 October 2017, 14:40 GMT
Thanks everybody, all the mail notifications were wrongly redirected to my spam folder so I lost track of this report. I don't have a github account, so if someone is willing to update the upstream report it will be appreciated. Thanks.
Comment by Christoph (egeus) - Tuesday, 17 October 2017, 18:33 GMT
Putting module i915 and intel_agp into the video modules did NOT fixed it for me. Only a downgrade to 0.15 did the trick.
Thank you!
Comment by Antonio Rojas (arojas) - Saturday, 02 December 2017, 20:13 GMT
Any improvement with 0.16.0-2?
Comment by Jon Gjengset (Jonhoo) - Saturday, 02 December 2017, 20:27 GMT
0.16.0-2 doesn't fix the issue for me, though maybe mine is slightly different? sddm *starts* just fine, but hangs and/or crashes *after* login. 0.15.0 works just fine. My logs just show a never-ending sequence of:

Dec 02 15:23:15 x1c3 sddm[671]: Adding new display on vt 1 ...
Dec 02 15:23:15 x1c3 sddm[671]: Loading theme configuration from ""
Dec 02 15:23:15 x1c3 sddm[671]: Display server starting...
Dec 02 15:23:15 x1c3 sddm[671]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{5860f1b3-ec6a-488b-9ef3-c798dfee6931} -background none -noreset -displayfd 26 -seat seat0 vt1
Dec 02 15:23:15 x1c3 sddm-helper[1642]: [PAM] Starting...
Dec 02 15:23:15 x1c3 sddm-helper[1642]: [PAM] Authenticating...
Dec 02 15:23:15 x1c3 sddm-helper[1642]: [PAM] returning.
Dec 02 15:23:16 x1c3 sddm[671]: Setting default cursor
Dec 02 15:23:16 x1c3 sddm[671]: Running display setup script "/usr/share/sddm/scripts/Xsetup"
Dec 02 15:23:16 x1c3 sddm[671]: Display server started.
Dec 02 15:23:16 x1c3 sddm[671]: Socket server starting...
Dec 02 15:23:16 x1c3 sddm[671]: Socket server started.
Dec 02 15:23:16 x1c3 sddm[671]: Loading theme configuration from "/usr/share/sddm/themes/maldives-light/theme.conf"
Dec 02 15:23:16 x1c3 sddm[671]: Greeter starting...
Dec 02 15:23:16 x1c3 sddm[671]: Adding cookie to "/var/run/sddm/{5860f1b3-ec6a-488b-9ef3-c798dfee6931}"
Dec 02 15:23:16 x1c3 sddm[671]: /usr/bin/xauth: (stdin):1: bad "remove" command line
Dec 02 15:23:16 x1c3 sddm[671]: /usr/bin/xauth: (stdin):2: bad "add" command line
Dec 02 15:23:16 x1c3 sddm[671]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Dec 02 15:23:16 x1c3 sddm[671]: Display server stopped.
Dec 02 15:23:16 x1c3 sddm[671]: Running display stop script "/usr/share/sddm/scripts/Xstop"
Dec 02 15:23:16 x1c3 sddm[671]: Socket server stopping...
Dec 02 15:23:16 x1c3 sddm[671]: Socket server stopped.
Dec 02 15:23:16 x1c3 sddm[671]: Removing display "" ...
Comment by Antonio Rojas (arojas) - Saturday, 02 December 2017, 20:32 GMT
@Jonhoo If sddm starts, then it is unrelated to this issue
Comment by Jon Gjengset (Jonhoo) - Saturday, 02 December 2017, 20:34 GMT
@arojas: I'm not so sure. It starts *the first time*, then crashes for some (probably unrelated) reason, but then it hangs completely when trying to restart.
Comment by Antonio Rojas (arojas) - Saturday, 02 December 2017, 20:36 GMT
@Jonhoo that makes it even more clear that it is not related to this issue, which is that sddm starts before the video is up.
Comment by Jon Gjengset (Jonhoo) - Saturday, 02 December 2017, 20:37 GMT
@arojas: ah, interesting, I guess I misread the issue. This must be something else then. I wonder if it'll start hitting more people when the fix to this lands...
Comment by Damjan Georgievski (damjan) - Sunday, 03 December 2017, 10:02 GMT
anyone tried the patch at https://github.com/sddm/sddm/issues/905#issuecomment-344165648

https://github.com/sddm/sddm/commit/ba9ab1ddf2c6ebef1fbc95fca75f196d5cfce598

?
Comment by Nicola Mori (snack) - Sunday, 03 December 2017, 10:12 GMT
@arojas no improvement with 0.16.0-2 here. Still requires "radeon" in MODULES in mkinitcpio.conf, otherwise sddm does not start.
Comment by Antonio Rojas (arojas) - Sunday, 03 December 2017, 10:29 GMT
I've backported the aforementioned patch to 0.16.0-3, please test
Comment by Michel (xantares) - Sunday, 03 December 2017, 10:39 GMT
0.16.0-2 fixed the problem for me (intel driver), thanks
Comment by Nicola Mori (snack) - Sunday, 03 December 2017, 11:43 GMT
@arojas I built and tested 0.16.0-3 and it seems that it fixed my problem. Now sddm starts event without placing the radeon module in MODULES. I still get an error:

dic 03 12:39:09 elric kernel: Console: switching to colour frame buffer device 160x50
dic 03 12:39:09 elric kernel: radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
dic 03 12:39:09 elric kernel: kfd kfd: DID 95c4 is missing in supported_devices
dic 03 12:39:09 elric kernel: kfd kfd: kgd2kfd_probe failed
dic 03 12:39:09 elric kernel: [drm] Initialized radeon 2.50.0 20080528 for 0000:01:00.0 on minor 0

but it seems that it does not impair the boot process.

Loading...