Control: tag -1 + moreinfo ¡Hola Johannes!
El 2016-10-26 a las 18:03 +0200, Johannes Zarl-Zierl escribió:
Package: sddm Version: 0.13.0-1 Severity: normal
--- Please enter the report below this line. --- On my system, sddm crashes when I open a second login session, thus closing/ killing my original session and active programs.
Steps to reproduce:1. Start a plasma session as user A 2. Lock screen 3. Choose "Start new session" on screen lock -> The sddm login session is shown 4. Start a session as user B 5. At this point "ps -flu A" shows that the first session is already dead
I regularly use a second session to test random stuff, so I don't think that this is a general issue.
I'd rather suspect that the X for the user A is dying when starting a second X. This can happen for some video drivers. Surely sddm could behave more gratefully in this case, instead of segfaulting, though.
To test my hypothesis I would need you to try starting a second session using a different display manager. If this fails in a similar way, then probably the video driver that you are using is the culprit, if not, something else is causing sddm to segfault and we would need some extra debugging information.
About the extra debugging information, we would need a core file of the segfault, one of the simpler ways to obtain the coredump of a daemon is to simply install systemd-coredump, this should capture the coredumps and put them under /var/lib/systemd/coredump (more about systemd-coredump in https://www.freedesktop.org/software/systemd/man/systemd-coredump.html)
This is, of course, only one of many ways to obtain the coredump. You could also stop the sddm service, and start the /usr/bin/sddmcommand as root from a vt, after setting ulimit -c unlimited (make sure that nothing has mangled the kernel.core_pattern value in this case).
The interesting snippet from journalctl:
Okt 25 23:22:27 mani sddm[4650]: Adding new display on vt 8 ... Okt 25 23:22:27 mani sddm[4650]: Display server starting... Okt 25 23:22:27 mani sddm[4650]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{b0c48caa-23a6-4e2c-9061-51f0f945afa8} -background none -noreset -displayfd 19 vt8 Okt 25 23:22:28 mani sddm[4650]: Running display setup script "/usr/share/sddm/scripts/Xsetup" Okt 25 23:22:28 mani sddm[4650]: Display server started. Okt 25 23:22:28 mani sddm[4650]: Socket server starting... Okt 25 23:22:28 mani sddm[4650]: Socket server started. Okt 25 23:22:28 mani sddm[4650]: Greeter starting... Okt 25 23:22:28 mani sddm[4650]: Adding cookie to "/var/run/sddm/{b0c48caa-23a6-4e2c-9061-51f0f945afa8}" Okt 25 23:22:28 mani sddm[4650]: /usr/bin/xauth: (stdin):1: bad "remove" command line Okt 25 23:22:28 mani kernel: sddm[4650]: segfault at 0 ip 00007fe10bfceb63 sp 00007ffe7a5fb120 error 4 in libQt5Core.so.5.6.1[7fe10bd16000+4c6000]Okt 25 23:22:28 mani sddm[4650]: /usr/bin/xauth: (stdin):2: bad "add" command line
I'm confused by this xauth errors, this might mean that the second X couldn't be started, and later sddm segfaults as it's expecting a running X.
When it segfaults, it takes the X of the user A with it, and the greeter that you see is shown because systemd restarted sddm after it died.
A confirmation of this might be a bit bellow in the journald log.
Okt 25 23:22:28 mani sddm[4650]: Display server stopped. Okt 25 23:22:28 mani sddm[4650]: Running display stop script "/usr/share/sddm/scripts/Xstop" Okt 25 23:22:28 mani sddm[4650]: Socket server stopping... Okt 25 23:22:28 mani sddm[4650]: Socket server stopped. Okt 25 23:22:28 mani sddm[4650]: Removing display "" ... Okt 25 23:22:28 mani sddm[4650]: QProcess: Destroyed while process ("/usr/lib/x86_64-linux-gnu/sddm/sddm-helper") is still running. Okt 25 23:22:28 mani systemd[1]: sddm.service: Main process exited, code=killed, status=11/SEGV Okt 25 23:22:28 mani org.kde.kpasswdserver[5397]: The X11 connection broke (error 1). Did the X11 server die? Okt 25 23:22:28 mani org.kde.KScreen[5397]: The X11 connection broke (error 1). Did the X11 server die? Okt 25 23:22:28 mani polkitd(authority=local)[658]: Unregistered Authentication Agent for unix-session:19 (system bus name :1.158, object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_AT.UTF-8) (disconnected from bus) Okt 25 23:22:28 mani org.a11y.Bus[5397]: Activating service name='org.a11y.atspi.Registry' Okt 25 23:22:28 mani org.kde.kglobalaccel[5397]: The X11 connection broke (error 1). Did the X11 server die? Okt 25 23:22:28 mani sddm[4650]: kwalletd5: Checking for pam module Okt 25 23:22:28 mani sddm[4650]: kwalletd5: Got pam-login param Okt 25 23:22:28 mani sddm[4650]: kwalletd5: Waiting for hash on 15- Okt 25 23:22:28 mani sddm[4650]: kwalletd5: waitingForEnvironment on: 18 Okt 25 23:22:28 mani sddm[4650]: kwalletd5: client connected Okt 25 23:22:28 mani sddm[4650]: kwalletd5: client disconnected
Happy hacking, -- "EIEIO Go home and have a glass of warm, dairy-fresh milk" -- The GNU C Library Reference Manual, Chapter 2.2, Error Codes Saludos /\/\ /\ >< `/
signature.asc
Description: PGP signature
