[SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

Aitch · 2015-11-07 13:59:27

I did a fairly massive system upgrade last night and my boot sequence has been hanging with messages about sddm.service today. Included in the upgrade was sddm 0.12.0-4 -> 0.12.0-5.

So I disabled the sddm.service and KDE & Plasma are working when I boot to the cl prompt then login as my user. Starting the sddm.service again crashes xorg.

I couldn't find any posts or bug reports about this so wondered if anyone else was having this problem?

Update: I have downgraded to sddm 0.12.0-4 again and confirmed that all works as before

Last edited by Aitch (2016-03-05 18:14:54)

twelveeighty · 2015-11-07 14:22:09

My sddm is at 0.13.0-1. Try updating the whole system again with -Syu. Maybe your problem was addressed in the latest update?

Last edited by twelveeighty (2015-11-07 14:23:34)

Aitch · 2015-11-07 14:28:42

Thanks, that version has just hit my mirror. I'll give it try.

Update: Nope. Same boot issue with 0.13.0-1

Last edited by Aitch (2015-11-07 14:38:59)

twelveeighty · 2015-11-07 15:25:53

What is journalctl reporting on that service? Please post the exact error message you're getting.

Aitch · 2015-11-07 16:51:30

Problem is the boot hangs if I have sddm.service enabled with anything newer than 0.12.0-4. I get something like:

[FAILED] Failed to start Simple Desktop Display Manager
See 'systemctl status sddm.service' for details.
[TIME] Timed out waiting for device sys-subsystem-?????
-
-
[OK] Reached target Graphical Interface.

& that's as far as it gets.

Aitch · 2015-11-08 11:08:01

OK. Now I have a little more time to read the systemd wiki page & learn about journalctl. Looks like it is failing round core-dump with seqfault problems.

# systemctl --failed gives:

 sddm.service - Simple Desktop Display Manager
   Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Sun 2015-11-08 11:30:24 CET; 8min ago
     Docs: man:sddm(1)
           man:sddm.conf(5)
  Process: 357 ExecStart=/usr/bin/sddm (code=dumped, signal=SEGV)
 Main PID: 357 (code=dumped, signal=SEGV)

Nov 08 11:30:24 T_3400 systemd[1]: sddm.service: Unit entered failed state.
Nov 08 11:30:24 T_3400 systemd[1]: sddm.service: Failed with result 'core-dump'.
Nov 08 11:30:24 T_3400 systemd-coredump[358]: Process 357 (sddm) of user 0 dumped core.
Nov 08 11:30:24 T_3400 systemd[1]: sddm.service: Service hold-off time over, scheduling restart.
Nov 08 11:30:24 T_3400 systemd[1]: Stopped Simple Desktop Display Manager.
Nov 08 11:30:24 T_3400 systemd[1]: sddm.service: Start request repeated too quickly.
Nov 08 11:30:24 T_3400 systemd[1]: Failed to start Simple Desktop Display Manager.
Nov 08 11:30:24 T_3400 systemd[1]: sddm.service: Unit entered failed state.
Nov 08 11:30:24 T_3400 systemd[1]: sddm.service: Failed with result 'start-limit'.

# journalctl | grep "sddm" gives:

Nov 08 11:29:55 T_3400 sddm[308]: Adding new display on vt 1 ...
Nov 08 11:29:55 T_3400 sddm[308]: Display server starting...
Nov 08 11:29:55 T_3400 sddm[308]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{9cc58145-60c9-4444-817d-3150966045fb} -background none -noreset -display$
Nov 08 11:29:56 T_3400 sddm[308]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Nov 08 11:29:56 T_3400 sddm[308]: Display server started.
Nov 08 11:29:56 T_3400 sddm[308]: Socket server starting...
Nov 08 11:29:56 T_3400 sddm[308]: Socket server started.
Nov 08 11:29:56 T_3400 sddm[308]: Greeter starting...
Nov 08 11:29:56 T_3400 sddm[308]: Adding cookie to "/var/run/sddm/{9cc58145-60c9-4444-817d-3150966045fb}"
Nov 08 11:29:56 T_3400 sddm[308]: Signal received: SIGTERM
Nov 08 11:29:56 T_3400 sddm[308]: Socket server stopping...
Nov 08 11:29:56 T_3400 sddm[308]: Socket server stopped.
Nov 08 11:29:56 T_3400 kernel: sddm-helper[5635]: segfault at 27b993a ip 00007f4b7efe45cd sp 00007ffe2fa96e50 error 4 in libQt5Core.so.5.5.1[7f4b7ee8c000+4d9000]
Nov 08 11:29:56 T_3400 sddm[308]: Display server stopping...
Nov 08 11:29:56 T_3400 systemd-coredump[5637]: Process 5635 (sddm-helper) of user 0 dumped core.
Nov 08 11:30:00 T_3400 sddm[308]: Display server stopped.
Nov 08 11:30:00 T_3400 sddm[308]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Nov 08 11:30:00 T_3400 sddm[308]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Nov 08 11:30:22 T_3400 kernel: sddm[291]: segfault at 219617a ip 00007fb0c2b435cd sp 00007ffeb68982c0 error 4 in libQt5Core.so.5.5.1[7fb0c29eb000+4d9000]
Nov 08 11:30:22 T_3400 systemd[1]: sddm.service: Main process exited, code=dumped, status=11/SEGV
Nov 08 11:30:22 T_3400 systemd[1]: sddm.service: Unit entered failed state.
Nov 08 11:30:22 T_3400 systemd[1]: sddm.service: Failed with result 'core-dump'.
Nov 08 11:30:22 T_3400 systemd-coredump[308]: Process 291 (sddm) of user 0 dumped core.
Nov 08 11:30:23 T_3400 kernel: sddm[342]: segfault at 325417a ip 00007f7678d815cd sp 00007ffde16adc10 error 4 in libQt5Core.so.5.5.1[7f7678c29000+4d9000]
Nov 08 11:30:22 T_3400 systemd[1]: sddm.service: Service hold-off time over, scheduling restart.
Nov 08 11:30:23 T_3400 systemd[1]: sddm.service: Main process exited, code=dumped, status=11/SEGV
Nov 08 11:30:23 T_3400 systemd[1]: sddm.service: Unit entered failed state.
Nov 08 11:30:23 T_3400 systemd[1]: sddm.service: Failed with result 'core-dump'.
Nov 08 11:30:23 T_3400 systemd-coredump[343]: Process 342 (sddm) of user 0 dumped core.
Nov 08 11:30:23 T_3400 systemd[1]: sddm.service: Service hold-off time over, scheduling restart.
Nov 08 11:30:23 T_3400 kernel: sddm[347]: segfault at 2a0a17a ip 00007f36ab4545cd sp 00007ffe8eb8bb90 error 4 in libQt5Core.so.5.5.1[7f36ab2fc000+4d9000]
Nov 08 11:30:23 T_3400 systemd[1]: sddm.service: Main process exited, code=dumped, status=11/SEGV
Nov 08 11:30:23 T_3400 systemd[1]: sddm.service: Unit entered failed state.
Nov 08 11:30:23 T_3400 systemd[1]: sddm.service: Failed with result 'core-dump'.
Nov 08 11:30:23 T_3400 systemd-coredump[348]: Process 347 (sddm) of user 0 dumped core.
Nov 08 11:30:23 T_3400 systemd[1]: sddm.service: Service hold-off time over, scheduling restart.
Nov 08 11:30:23 T_3400 kernel: sddm[354]: segfault at 408a17a ip 00007fb6040345cd sp 00007ffecfcad480 error 4 in libQt5Core.so.5.5.1[7fb603edc000+4d9000]
Nov 08 11:30:23 T_3400 systemd[1]: sddm.service: Main process exited, code=dumped, status=11/SEGV
Nov 08 11:30:23 T_3400 systemd[1]: sddm.service: Unit entered failed state.
Nov 08 11:30:23 T_3400 systemd[1]: sddm.service: Failed with result 'core-dump'.
Nov 08 11:30:23 T_3400 systemd-coredump[355]: Process 354 (sddm) of user 0 dumped core.
Nov 08 11:30:24 T_3400 systemd[1]: sddm.service: Service hold-off time over, scheduling restart.
Nov 08 11:30:24 T_3400 kernel: sddm[357]: segfault at 2a9217a ip 00007f9c0a66b5cd sp 00007ffe46f23680 error 4 in libQt5Core.so.5.5.1[7f9c0a513000+4d9000]
Nov 08 11:30:24 T_3400 systemd[1]: sddm.service: Main process exited, code=dumped, status=11/SEGV
Nov 08 11:30:24 T_3400 systemd[1]: sddm.service: Unit entered failed state.
Nov 08 11:30:24 T_3400 systemd[1]: sddm.service: Failed with result 'core-dump'.
Nov 08 11:30:24 T_3400 systemd-coredump[358]: Process 357 (sddm) of user 0 dumped core.
Nov 08 11:30:24 T_3400 systemd[1]: sddm.service: Service hold-off time over, scheduling restart.
Nov 08 11:30:24 T_3400 systemd[1]: sddm.service: Start request repeated too quickly.
Nov 08 11:30:24 T_3400 systemd[1]: sddm.service: Unit entered failed state.
Nov 08 11:30:24 T_3400 systemd[1]: sddm.service: Failed with result 'start-limit'.
Nov 08 11:36:40 T_3400 sudo[526]:        h : TTY=tty2 ; PWD=/home/h ; USER=root ; COMMAND=/usr/bin/systemctl status sddm.service
Nov 08 11:38:33 T_3400 sudo[528]:        h : TTY=tty2 ; PWD=/home/h ; USER=root ; COMMAND=/usr/bin/systemctl status sddm.service

Scimmia · 2015-11-08 15:56:50

What's your xorg log look like?

twelveeighty · 2015-11-08 17:17:31

Aitch wrote:

Nov 08 11:29:56 T_3400 kernel: sddm-helper[5635]: segfault at 27b993a ip 00007f4b7efe45cd sp 00007ffe2fa96e50 error 4 in libQt5Core.so.5.5.1[7f4b7ee8c000+4d9000]

I wonder if you are getting this error as reported for sddm: https://github.com/sddm/sddm/issues/518, which points to a bug in qt5-base (check https://bugs.debian.org/cgi-bin/bugrepo … ug=802811), but it's not reported here on Arch, as far as I know.

Are you 100% sure you are not doing partial updates?

Aitch · 2015-11-08 18:26:36

Looks like you are on the right track twelveeighty. Both xorg and qt5 got updated on the same session that sddm did.

After reading the links you provided I tried downgrading qt5-x11extras (which I took as Arch's equivalent to Debian's libqt5x11extras5 mentioned in the bug report), but this didn't help. I can try downgrading the qt5 packages to see if I can isolate the problem.

I always do a full Syu so, unless my pacman db is corrupted, partial updates shouldn't be an issue.

hcartiaux · 2015-11-10 09:45:54

Same issue with sddm 0.13.0-1, I've downgraded to 0.12.0-5 and it works for me.
With 0.13.0-1, I get this error:

Nov 10 10:29:39 hc-e7440 kernel: sddm[18851]: segfault at 4643a6c ip 00007f90377d05cd sp 00007fffc75c59d0 error 4 in libQt5Core.so.5.5.1[7f9037678000+4d9000]

Guidobelix · 2015-11-10 12:24:59

hcartiaux wrote:

Same issue with sddm 0.13.0-1, I've downgraded to 0.12.0-5 and it works for me.
With 0.13.0-1, I get this error:
Nov 10 10:29:39 hc-e7440 kernel: sddm[18851]: segfault at 4643a6c ip 00007f90377d05cd sp 00007fffc75c59d0 error 4 in libQt5Core.so.5.5.1[7f9037678000+4d9000]

Same error message here with sddm 0.13.0-1. Going back to 0.12.0-5 fixes the issue.

micsnare · 2015-11-13 17:27:06

Guidobelix wrote:

hcartiaux wrote:
Same issue with sddm 0.13.0-1, I've downgraded to 0.12.0-5 and it works for me.
With 0.13.0-1, I get this error:
Nov 10 10:29:39 hc-e7440 kernel: sddm[18851]: segfault at 4643a6c ip 00007f90377d05cd sp 00007fffc75c59d0 error 4 in libQt5Core.so.5.5.1[7f9037678000+4d9000]
Same error message here with sddm 0.13.0-1. Going back to 0.12.0-5 fixes the issue.

Hi,
I'm having the same problem you described. Could you please explain how you downgraded to 0.12.0-5 ??
Thank you!!

Aitch · 2015-11-13 19:22:11

micsnare wrote:

Hi,
I'm having the same problem you described. Could you please explain how you downgraded to 0.12.0-5 ??
Thank you!!

Go to the pacman cache:

$ cd /var/cache/pacman/pkg/

Find the package and version you want to install then run:

$ sudo pacman -U sddm-0.12.0-5-x86_64.pkg.tar.xz

hcartiaux · 2015-11-16 17:16:46

I've downloaded the old version from the Arch Linux Archive:

https://wiki.archlinux.org/index.php/Arch_Linux_Archive

nomasteryoda · 2015-12-02 12:58:50

I have the same error and rolled back to the .12 version. I set sddm to ignore in pacman.conf too and manually check for any version update once I'm done with my normal pacman -Syu.

edit:
The bug reported over on sddm git (https://github.com/sddm/sddm/issues/518) was closed per issue actually arising from the qt5-x11extras package update. Booting to any GUI login is pretty high on my issue list and I do not see rolling back any qt5 packages as a viable option; Pinning sddm version appears to be the only solution at this point - or replacing with gdm (bleh!).

Last edited by nomasteryoda (2015-12-02 13:08:34)

Aitch · 2015-12-10 22:39:41

There is now a new version of qt5-x11extras (5.5.1-5) so I tried upgrading sddm again but the result was the same. Has anyone found a bug report for this in qt5?

Aitch · 2016-03-05 18:21:11

In case anyone is still having this problem I am updating this issue to solved.

Latest Plasma update 5.5.5-1 & qt5-x11extras 5.5.1-9 has sddm 0.13.0-2 working perfectly for me (at last).

Arch Linux

#1 2015-11-07 13:59:27

[SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#2 2015-11-07 14:22:09

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#3 2015-11-07 14:28:42

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#4 2015-11-07 15:25:53

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#5 2015-11-07 16:51:30

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#6 2015-11-08 11:08:01

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#7 2015-11-08 15:56:50

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#8 2015-11-08 17:17:31

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#9 2015-11-08 18:26:36

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#10 2015-11-10 09:45:54

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#11 2015-11-10 12:24:59

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#12 2015-11-13 17:27:06

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#13 2015-11-13 19:22:11

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#14 2015-11-16 17:16:46

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#15 2015-12-02 12:58:50

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#16 2015-12-10 22:39:41

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

#17 2016-03-05 18:21:11

Re: [SOLVED] sddm 0.12.0-5 upgrade breaks boot sequence

Board footer