Description of problem: 0. Autologin configured 1. Logout from session Version-Release number of selected component: sddm-0.2.0-0.16.20130914git50ca5b20.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/sddm crash_function: __memcpy_sse2_unaligned executable: /usr/bin/sddm kernel: 3.11.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 __memcpy_sse2_unaligned at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:122 #1 memcpy at /usr/include/bits/string3.h:51 #2 node_copy at /usr/include/QtCore/qlist.h:423 #3 QList<SDDM::DisplayManagerSession*>::detach_helper at /usr/include/QtCore/qlist.h:711 #4 detach_helper at /usr/include/QtCore/qlist.h:725 #5 detach at /usr/include/QtCore/qlist.h:139 #6 begin at /usr/include/QtCore/qlist.h:267 #7 SDDM::DisplayManager::RemoveSession at /usr/src/debug/sddm-50ca5b20354b6d338ce8836a613af19cedb1dca2/src/daemon/DisplayManager.cpp:116 #8 SDDM::Authenticator::finished at /usr/src/debug/sddm-50ca5b20354b6d338ce8836a613af19cedb1dca2/src/daemon/Authenticator.cpp:405 #9 QMetaObject::activate at kernel/qobject.cpp:3547
Created attachment 825238 [details] File: backtrace
Created attachment 825239 [details] File: cgroup
Created attachment 825240 [details] File: core_backtrace
Created attachment 825241 [details] File: dso_list
Created attachment 825242 [details] File: environ
Created attachment 825243 [details] File: exploitable
Created attachment 825244 [details] File: limits
Created attachment 825245 [details] File: maps
Created attachment 825246 [details] File: open_fds
Created attachment 825247 [details] File: proc_pid_status
Created attachment 825248 [details] File: var_log_messages
This bug is extremely annoying when you have LastUser set in /etc/sddm.conf. I am not able to logout because after sddm restart I am logged in again and again. Please fix asap.
> This bug is extremely annoying when you have LastUser set in /etc/sddm.conf. s/LastUser/AutoUser/ of course. The option to auto-login. My mistake.
Already looking into this a while now
sddm-0.2.0-0.21.20131125git7a008602.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/sddm-0.2.0-0.21.20131125git7a008602.fc20
Package sddm-0.2.0-0.22.20131125git7a008602.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing sddm-0.2.0-0.22.20131125git7a008602.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-22158/sddm-0.2.0-0.22.20131125git7a008602.fc20 then log in and leave karma (feedback).
sddm-0.2.0-0.29.20140623gitdb1d7381.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/sddm-0.2.0-0.29.20140623gitdb1d7381.fc20
sddm-0.2.0-0.29.20140623gitdb1d7381.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/sddm-0.2.0-0.29.20140623gitdb1d7381.fc19
sddm-0.2.0-0.31.20140627gitf49c2c79.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
sddm-0.9.0-1.20141007git6a28c29b.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/sddm-0.9.0-1.20141007git6a28c29b.fc19