Arch Linux

jeffro-tull

Member

Registered: 2008-09-25

Posts: 17

[SITUATION RESOLVED ITSELF] glibc, qt5, and/or sddm issues

I've been having some issues ever since glibc got updated from 2.22-4 to 2.23-1. I have Plasma 5 installed as my only GUI, and use sddm to log in. Since the glibc update, sddm won't start. When it won't start, running /usr/bin/startkde doesn't do any good either.

When sddm didn't come up, I checked dmesg:

[jeffro@jeffro-e420 ~]$ dmesg | grep sddm
[   17.088262] sddm[371]: segfault at 1e8384e ip 00007f4e3289b61d sp 00007ffddeb8abc0 error 4 in libQt5Core.so.5.5.1[7f4e32759000+4c3000]
[   17.884597] sddm[398]: segfault at 461b84e ip 00007ff973ddb61d sp 00007ffcca553540 error 4 in libQt5Core.so.5.5.1[7ff973c99000+4c3000]
[   18.443860] sddm[412]: segfault at 2fc184e ip 00007fb57b29861d sp 00007ffd35fa5570 error 4 in libQt5Core.so.5.5.1[7fb57b156000+4c3000]
[   18.667562] sddm[420]: segfault at 30bf84e ip 00007f02d10f161d sp 00007fff439132b0 error 4 in libQt5Core.so.5.5.1[7f02d0faf000+4c3000]
[   19.174922] sddm[430]: segfault at 1c2f84e ip 00007f87e002661d sp 00007ffea8aea810 error 4 in libQt5Core.so.5.5.1[7f87dfee4000+4c3000]

Then I checked systemctl:

[jeffro@jeffro-e420 ~]$ systemctl status sddm 
● sddm.service - Simple Desktop Display Manager
   Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset: disabled)
   Active: inactive (dead) (Result: core-dump) since Sun 2016-03-06 18:33:53 EST; 4min 21s ago
     Docs: man:sddm(1)
           man:sddm.conf(5)
  Process: 430 ExecStart=/usr/bin/sddm (code=dumped, signal=SEGV)
 Main PID: 430 (code=dumped, signal=SEGV)

Mar 06 18:33:52 jeffro-e420 systemd[1]: Started Simple Desktop Display Manager.
Mar 06 18:33:52 jeffro-e420 systemd[1]: sddm.service: Main process exited, code=dumped, status=11/SEGV
Mar 06 18:33:52 jeffro-e420 systemd[1]: sddm.service: Unit entered failed state.
Mar 06 18:33:52 jeffro-e420 systemd[1]: sddm.service: Failed with result 'core-dump'.
Mar 06 18:33:53 jeffro-e420 systemd[1]: sddm.service: Service hold-off time over, scheduling restart.
Mar 06 18:33:53 jeffro-e420 systemd[1]: Stopped Simple Desktop Display Manager.
Mar 06 18:33:53 jeffro-e420 systemd[1]: sddm.service: Start request repeated too quickly.
Mar 06 18:33:53 jeffro-e420 systemd[1]: Failed to start Simple Desktop Display Manager.

...and journalctl:

[jeffro@jeffro-e420 ~]$ journalctl -xn 
-- Logs begin at Fri 2015-10-16 17:55:17 EDT, end at Sun 2016-03-06 18:41:13 EST. --
Mar 06 18:41:12 jeffro-e420 systemd[1]: Started Simple Desktop Display Manager.
-- Subject: Unit sddm.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit sddm.service has finished starting up.
-- 
-- The start-up result is done.
Mar 06 18:41:12 jeffro-e420 systemd[1]: Started Process Core Dump (PID 546/UID 0).
-- Subject: Unit systemd-coredump@9-546-0.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-coredump@9-546-0.service has finished starting up.
-- 
-- The start-up result is done.
Mar 06 18:41:13 jeffro-e420 systemd[1]: sddm.service: Main process exited, code=dumped, status=11/SEGV
Mar 06 18:41:13 jeffro-e420 systemd[1]: sddm.service: Unit entered failed state.
Mar 06 18:41:13 jeffro-e420 systemd[1]: sddm.service: Failed with result 'core-dump'.
Mar 06 18:41:13 jeffro-e420 systemd-coredump[547]: Process 544 (sddm) of user 0 dumped core.
                                                   
                                                   Stack trace of thread 544:
                                                   #0  0x00007f0a7fbe161d _ZNK10QStringRef7trimmedEv (libQt5Core.so.5)
                                                   #1  0x0000000000428b28 _ZrsR11QTextStreamR11QStringList (sddm)
                                                   #2  0x000000000042535a _ZN4SDDM11ConfigEntryI11QStringListE8setValueERK7QString (sddm)
                                                   #3  0x000000000042a18d _ZN4SDDM10ConfigBase4loadEv (sddm)
                                                   #4  0x0000000000423bd7 _ZN4SDDM10MainConfigC1Ev (sddm)
                                                   #5  0x000000000041a410 n/a (sddm)
                                                   #6  0x000000000045623d __libc_csu_init (sddm)
                                                   #7  0x00007f0a7f18669f __libc_start_main (libc.so.6)
                                                   #8  0x000000000041aa69 _start (sddm)
-- Subject: Process 544 (sddm) dumped core
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 544 (sddm) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Mar 06 18:41:13 jeffro-e420 systemd[1]: sddm.service: Service hold-off time over, scheduling restart.
Mar 06 18:41:13 jeffro-e420 systemd[1]: Stopped Simple Desktop Display Manager.
-- Subject: Unit sddm.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit sddm.service has finished shutting down.
Mar 06 18:41:13 jeffro-e420 systemd[1]: sddm.service: Start request repeated too quickly.
Mar 06 18:41:13 jeffro-e420 systemd[1]: Failed to start Simple Desktop Display Manager.
-- Subject: Unit sddm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit sddm.service has failed.
-- 
-- The result is failed.

[jeffro@jeffro-e420 ~]$ journalctl /usr/bin/sddm
Mar 06 18:33:16 jeffro-e420 sddm[373]: Authentication error: "Process crashed"
Mar 06 18:33:16 jeffro-e420 sddm[373]: Auth: sddm-helper crashed (exit code 15)
Mar 06 18:33:16 jeffro-e420 sddm[373]: Authentication error: "Process crashed"
Mar 06 18:33:16 jeffro-e420 sddm[373]: Auth: sddm-helper exited with 15
Mar 06 18:33:16 jeffro-e420 sddm[373]: Socket server stopping...
Mar 06 18:33:16 jeffro-e420 sddm[373]: Socket server stopped.
Mar 06 18:33:16 jeffro-e420 sddm[373]: Display server stopping...
Mar 06 18:33:16 jeffro-e420 sddm[373]: Display server stopped.
Mar 06 18:33:16 jeffro-e420 sddm[373]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Mar 06 18:33:16 jeffro-e420 sddm[373]: Removing display ":0" ...
Mar 06 18:33:16 jeffro-e420 sddm[373]: Adding new display on vt 1 ...
Mar 06 18:33:16 jeffro-e420 sddm[373]: Display server starting...
Mar 06 18:33:16 jeffro-e420 sddm[373]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{b7d10857-4e5c-4ec2-997b-9772d1d9ba13} -background none -noreset -displayfd 18 vt1

This has been going on for about a week now. I was hopeful last night when a who bunch of qt5 packages got upgraded, but no luck. I end up having to downgrade glibc and a few dependencies (binutils, gcc-libs, gcc) to get my display manager to work. Any ideas?

Last edited by jeffro-tull (2016-03-08 23:42:09)

loafer

Member

From: the pub

Registered: 2009-04-14

Posts: 1,772

Re: [SITUATION RESOLVED ITSELF] glibc, qt5, and/or sddm issues

Is you system entirely up-to-date?  Which theme are you using?

---

All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.

jeffro-tull

Member

Registered: 2008-09-25

Posts: 17

Re: [SITUATION RESOLVED ITSELF] glibc, qt5, and/or sddm issues

My system is up to date with the following exceptions:

[jeffro@jeffro-e420 pkg]$ sudo pacman -U glibc-2.22-4-x86_64.pkg.tar.xz binutils-2.25.1-3-x86_64.pkg.tar.xz gcc-libs-multilib-5.3.0-4-x86_64.pkg.tar.xz lib32-gcc-libs-5.3.0-4-x86_64.pkg.tar.xz gcc-multilib-5.3.0-4-x86_64.pkg.tar.xz

Those I end up reverting to get sddm to work. I have the "Maui" theme set for sddm.

jeffro-tull

Member

Registered: 2008-09-25

Posts: 17

Re: [SITUATION RESOLVED ITSELF] glibc, qt5, and/or sddm issues

So, the situation resolved itself?

I had to boot into Windows, and when I booted back into Arch I had the sddm/qt core dump even with the old versions of glibc, binutils, and the like. In a bout of "what's the worst that could happen?" I did a pacman -Syyu, rebooted, and now it's behaving itself. Strange.