FS#46302 - [sddm] unable to login due to segmentation fault

Attached to Project: Arch Linux
Opened by Andrea Amorosi (AndreaA) - Tuesday, 15 September 2015, 17:57 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 01 October 2015, 19:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 17
Private No

Details

Description:
After upgrading to sddm-0.12.0-2-x86_64, it is impossible to login due to a segmentation fault of sddm.
reverting back to sddm-0.11.0-3-x86_64 has solved the issue

Additional info:

Steps to reproduce:
This task depends upon

Closed by  Antonio Rojas (arojas)
Thursday, 01 October 2015, 19:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  sddm 0.12.0-3
Comment by Dieter Rethmeyer (Dieter) - Wednesday, 16 September 2015, 19:13 GMT
Additional info from journalctl:

Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm[329]: Initializing...
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm[329]: Starting...
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm[329]: Adding new display on vt 1 ...
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm[329]: Display server starting...
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm[329]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{7b1576b4-6e73-43f1-944
Sep 16 20:49:50 arch64-t2.rethmeyers.de colord[328]: (colord:328): Cd-WARNING **: failed to get session [pid 291]: Kein passende
Sep 16 20:49:50 arch64-t2.rethmeyers.de colord[328]: (colord:328): Cd-WARNING **: failed to get session [pid 291]: Kein passende
Sep 16 20:49:50 arch64-t2.rethmeyers.de colord[328]: (colord:328): Cd-WARNING **: failed to get session [pid 291]: Kein passende
Sep 16 20:49:50 arch64-t2.rethmeyers.de colord-sane[366]: [bjnp] create_broadcast_socket: bind socket to local address failed -
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm[329]: Running display setup script "/usr/share/sddm/scripts/Xsetup"
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm[329]: Display server started.
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm[329]: Socket server starting...
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm[329]: Socket server started.
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm[329]: Greeter starting...
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm[329]: Adding cookie to "/var/run/sddm/{7b1576b4-6e73-43f1-9448-8876e047423c}"
Sep 16 20:49:50 arch64-t2.rethmeyers.de postfix/postfix-script[412]: starting the Postfix mail system
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm-helper[406]: [PAM] Starting...
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm-helper[406]: [PAM] Authenticating...
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm-helper[406]: [PAM] returning.
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm-helper[406]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[1]: Created slice user-997.slice.
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[1]: Starting User Manager for UID 997...
Sep 16 20:49:50 arch64-t2.rethmeyers.de postfix/master[414]: daemon started -- version 3.0.2, configuration /etc/postfix
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd-logind[298]: New session c1 of user sddm.
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[415]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[1]: Started Session c1 of user sddm.
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[1]: Started Postfix Mail Transport Agent.
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[1]: Reached target Multi-User System.
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[1]: Reached target Graphical Interface.
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[415]: Reached target Sockets.
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[415]: Reached target Timers.
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[415]: Reached target Paths.
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[415]: Reached target Basic System.
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[415]: Reached target Default.
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[415]: Startup finished in 15ms.
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[1]: Started User Manager for UID 997.
Sep 16 20:49:50 arch64-t2.rethmeyers.de systemd[1]: Startup finished in 1.766s (kernel) + 4.870s (userspace) = 16.679s.
Sep 16 20:49:50 arch64-t2.rethmeyers.de kernel: sddm-helper[421]: segfault at 14 ip 000000000042965e sp 00007ffcfed9c710 error 4
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm[329]: Greeter session started successfully
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm-helper[406]: [PAM] Ended.
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm[329]: Auth: sddm-helper exited with 11
Sep 16 20:49:50 arch64-t2.rethmeyers.de sddm[329]: Greeter stopped.
Comment by Andrea Amorosi (AndreaA) - Thursday, 17 September 2015, 20:17 GMT
set 15 08:18:46 pro5av sddm[525]: Initializing...
set 15 08:18:46 pro5av sddm[525]: Starting...
set 15 08:18:46 pro5av sddm[525]: Adding new display on vt 1 ...
set 15 08:18:46 pro5av polkitd[663]: Started polkitd version 0.113
set 15 08:18:46 pro5av sddm[525]: Display server starting...
set 15 08:18:46 pro5av sddm[525]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{955f2d4e-815b-4c2d-bb4a-a5a0309057fa} -background none -noreset -displayfd 17 vt1
set 15 08:18:46 pro5av dbus[448]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
set 15 08:18:46 pro5av systemd[1]: Started WPA supplicant.
set 15 08:18:46 pro5av NetworkManager[444]: <info> wpa_supplicant running
set 15 08:18:46 pro5av NetworkManager[444]: <info> (wlan0) supports 5 scan SSIDs
set 15 08:18:46 pro5av NetworkManager[444]: <info> (wlan0): supplicant interface state: starting -> ready
set 15 08:18:46 pro5av NetworkManager[444]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
set 15 08:18:46 pro5av kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
set 15 08:18:46 pro5av polkitd[663]: Loading rules from directory /etc/polkit-1/rules.d
set 15 08:18:46 pro5av polkitd[663]: Loading rules from directory /usr/share/polkit-1/rules.d
set 15 08:18:46 pro5av polkitd[663]: Finished loading, compiling and executing 1 rules
set 15 08:18:46 pro5av dbus[448]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
set 15 08:18:46 pro5av systemd[1]: Started Authorization Manager.
set 15 08:18:46 pro5av polkitd[663]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
set 15 08:18:47 pro5av kernel: cfg80211: Calling CRDA to update world regulatory domain
set 15 08:18:47 pro5av acpid[447]: client connected from 666[0:0]
set 15 08:18:47 pro5av acpid[447]: 1 client rule loaded
set 15 08:18:49 pro5av NetworkManager[444]: <info> (wlan0): supplicant interface state: ready -> inactive
set 15 08:18:51 pro5av NetworkManager[444]: <info> startup complete
set 15 08:18:51 pro5av systemd[1]: Started Network Manager Wait Online.
set 15 08:18:51 pro5av systemd[1]: Reached target Network.
set 15 08:18:51 pro5av systemd[1]: Started Mount Samba Shares.
set 15 08:18:51 pro5av systemd[1]: Starting Postfix Mail Transport Agent...
set 15 08:18:51 pro5av systemd[1]: Starting clamav daemon...
set 15 08:18:51 pro5av systemd[1]: Starting Network Time Service...
set 15 08:18:51 pro5av ntpd[680]: ntpd 4.2.8p3@1.3265-o Wed Jul 1 15:59:39 UTC 2015 (1): Starting
set 15 08:18:51 pro5av ntpd[680]: Command line: /usr/bin/ntpd -g -u ntp:ntp
set 15 08:18:51 pro5av systemd[1]: Started Network Time Service.
set 15 08:18:51 pro5av kernel: cfg80211: Calling CRDA to update world regulatory domain
set 15 08:18:51 pro5av kernel: NVRM: Your system is not currently configured to drive a VGA console
set 15 08:18:51 pro5av kernel: NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
set 15 08:18:51 pro5av kernel: NVRM: requires the use of a text-mode VGA console. Use of other console
set 15 08:18:51 pro5av kernel: NVRM: drivers including, but not limited to, vesafb, may result in
set 15 08:18:51 pro5av kernel: NVRM: corruption and stability problems, and is not supported.
set 15 08:18:52 pro5av ntpd[681]: proto: precision = 0.768 usec (-20)
set 15 08:18:52 pro5av ntpd[681]: Listen and drop on 0 v6wildcard [::]:123
set 15 08:18:52 pro5av ntpd[681]: Listen and drop on 1 v4wildcard 0.0.0.0:123
set 15 08:18:52 pro5av ntpd[681]: Listen normally on 2 lo 127.0.0.1:123
set 15 08:18:52 pro5av ntpd[681]: Listen normally on 3 lo [::1]:123
set 15 08:18:52 pro5av ntpd[681]: Listening on routing socket on fd #20 for interface updates
set 15 08:18:53 pro5av clamd[679]: LibClamAV Warning: **************************************************
set 15 08:18:53 pro5av clamd[679]: LibClamAV Warning: *** The virus database is older than 7 days! ***
set 15 08:18:53 pro5av clamd[679]: LibClamAV Warning: *** Please update it as soon as possible. ***
set 15 08:18:53 pro5av clamd[679]: LibClamAV Warning: **************************************************
set 15 08:18:53 pro5av acpid[447]: client connected from 666[0:0]
set 15 08:18:53 pro5av acpid[447]: 1 client rule loaded
set 15 08:18:53 pro5av kernel: cfg80211: Calling CRDA to update world regulatory domain
set 15 08:18:56 pro5av postfix/postfix-script[755]: starting the Postfix mail system
set 15 08:18:56 pro5av kernel: cfg80211: Calling CRDA to update world regulatory domain
set 15 08:18:56 pro5av postfix/master[758]: daemon started -- version 3.0.2, configuration /etc/postfix
set 15 08:18:56 pro5av systemd[1]: Started Postfix Mail Transport Agent.
set 15 08:18:56 pro5av sddm[525]: Running display setup script "/usr/share/sddm/scripts/Xsetup"
set 15 08:18:57 pro5av sddm[525]: Display server started.
set 15 08:18:57 pro5av sddm[525]: Socket server starting...
set 15 08:18:57 pro5av sddm[525]: Socket server started.
set 15 08:18:57 pro5av sddm[525]: Greeter starting...
set 15 08:18:57 pro5av sddm[525]: Adding cookie to "/var/run/sddm/{955f2d4e-815b-4c2d-bb4a-a5a0309057fa}"
set 15 08:18:58 pro5av sddm-helper[772]: [PAM] Starting...
set 15 08:18:58 pro5av sddm-helper[772]: [PAM] Authenticating...
set 15 08:18:58 pro5av sddm-helper[772]: [PAM] returning.
set 15 08:18:58 pro5av sddm-helper[772]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
set 15 08:18:58 pro5av systemd[1]: Created slice user-995.slice.
set 15 08:18:58 pro5av systemd[1]: acpid.socket: Cannot add dependency job, ignoring: Unit acpid.socket failed to load: No such file or directory.
set 15 08:18:58 pro5av systemd[1]: cups.socket: Cannot add dependency job, ignoring: Unit cups.socket failed to load: No such file or directory.
set 15 08:18:58 pro5av systemd[1]: Starting User Manager for UID 995...
set 15 08:18:58 pro5av systemd-logind[437]: New session c1 of user sddm.
set 15 08:18:58 pro5av systemd[1]: Started Session c1 of user sddm.
set 15 08:18:58 pro5av systemd[775]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
set 15 08:18:58 pro5av systemd[775]: Reached target Timers.
set 15 08:18:58 pro5av systemd[775]: Reached target Paths.
set 15 08:18:58 pro5av systemd[775]: Reached target Sockets.
set 15 08:18:58 pro5av systemd[775]: Reached target Basic System.
set 15 08:18:58 pro5av systemd[775]: Reached target Default.
set 15 08:18:58 pro5av systemd[775]: Startup finished in 182ms.
set 15 08:18:58 pro5av systemd[1]: Started User Manager for UID 995.
set 15 08:18:58 pro5av kernel: sddm-helper[779]: segfault at 14 ip 000000000042965e sp 00007ffeba801090 error 4 in sddm-helper[400000+3a000]
set 15 08:18:59 pro5av kernel: cfg80211: Calling CRDA to update world regulatory domain
set 15 08:19:01 pro5av sddm[525]: Greeter session started successfully
set 15 08:19:01 pro5av sddm-helper[772]: [PAM] Ended.
set 15 08:19:01 pro5av sddm[525]: Auth: sddm-helper exited with 11
set 15 08:19:01 pro5av sddm[525]: Greeter stopped.
set 15 08:19:01 pro5av systemd-logind[437]: Removed session c1.
set 15 08:19:01 pro5av systemd[1]: Stopping User Manager for UID 995...
set 15 08:19:02 pro5av systemd-coredump[780]: Process 779 (sddm-helper) of user 0 dumped core.
set 15 08:19:03 pro5av kernel: cfg80211: Calling CRDA to update world regulatory domain
set 15 08:19:02 pro5av systemd[776]: pam_unix(systemd-user:session): session closed for user sddm
set 15 08:19:02 pro5av systemd[775]: Reached target Shutdown.
set 15 08:19:02 pro5av systemd[775]: Starting Exit the Session...
set 15 08:19:02 pro5av systemd[775]: Stopped target Default.
set 15 08:19:02 pro5av systemd[775]: Stopped target Basic System.
set 15 08:19:02 pro5av systemd[775]: Stopped target Sockets.
set 15 08:19:02 pro5av systemd[775]: Stopped target Paths.
set 15 08:19:02 pro5av systemd[775]: Stopped target Timers.
Comment by Stach Jemiola (jemiola) - Thursday, 24 September 2015, 19:28 GMT
"systemctl restart sddm" allows to start sddm.
Comment by Bruno Pagani (ArchangeGabriel) - Monday, 28 September 2015, 14:39 GMT
Got this too: sddm-helper[1282]: segfault at 14 ip 000000000042965e sp 00007ffc87758020 error 4 in sddm-helper[400000+3a000]

However, I though it started when upgrading to systemd 226, but it might not be linked.

Sometime restarting X (configured Ctrl+Alt+Suppr for that) also works to bring sddm back.
Comment by DeLord (DeLord) - Wednesday, 30 September 2015, 23:50 GMT
Hi, I am also experiencing this bug, is this upstream? If yes, any news to that? Couldn't find anything. If not, how to fix?
Comment by Hans Schwimmbeck (hans) - Thursday, 01 October 2015, 06:29 GMT
With sddm-git commit c637727 from the AUR I don't experience the segfault any more.

There are only a few commits since the 0.12 release. Most of them are obviously unrelated, so it should not be too hard to make a patch.

Comment by Antonio Rojas (arojas) - Thursday, 01 October 2015, 06:53 GMT
Please test 0.12.0-3
Comment by Admoni Rotem (rotema8) - Thursday, 01 October 2015, 18:42 GMT
With caution after several reboots during the day : fixed for me.
Comment by Hans Schwimmbeck (hans) - Thursday, 01 October 2015, 19:13 GMT
Same here.

Loading...