Version-Release number of selected component: sddm-0.13.0-7.fc24 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/sddm-greeter --socket /tmp/sddm-:0-JAXmeM --theme /usr/share/sddm/themes/01-breeze-fedora crash_function: SDDM::XcbKeyboardBackend::initLedMap executable: /usr/bin/sddm-greeter global_pid: 2330 kernel: 4.5.5-300.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 993 Truncated backtrace: Thread no. 1 (4 frames) #0 SDDM::XcbKeyboardBackend::initLedMap at /usr/src/debug/sddm-0.13.0/src/greeter/XcbKeyboardBackend.cpp:122 #1 SDDM::XcbKeyboardBackend::init at /usr/src/debug/sddm-0.13.0/src/greeter/XcbKeyboardBackend.cpp:40 #2 SDDM::KeyboardModel::KeyboardModel at /usr/src/debug/sddm-0.13.0/src/greeter/KeyboardModel.cpp:31 #3 SDDM::GreeterApp::GreeterApp at /usr/src/debug/sddm-0.13.0/src/greeter/GreeterApp.cpp:115 Potential duplicate: bug 1312005
Created attachment 1247694 [details] File: backtrace
Created attachment 1247695 [details] File: cgroup
Created attachment 1247696 [details] File: core_backtrace
Created attachment 1247697 [details] File: dso_list
Created attachment 1247698 [details] File: environ
Created attachment 1247699 [details] File: exploitable
Created attachment 1247700 [details] File: limits
Created attachment 1247701 [details] File: maps
Created attachment 1247702 [details] File: mountinfo
Created attachment 1247703 [details] File: namespaces
Created attachment 1247704 [details] File: open_fds
Created attachment 1247705 [details] File: proc_pid_status
Created attachment 1247706 [details] File: var_log_messages
This bug exists since Fedora 22!
*** Bug 1244447 has been marked as a duplicate of this bug. ***
*** Bug 1312005 has been marked as a duplicate of this bug. ***
Any ideas how to reproduce this? Or ideally, please report upstream to https://github.com/sddm/sddm/issues
(In reply to Rex Dieter from comment #17) > Any ideas how to reproduce this? > > Or ideally, please report upstream to > https://github.com/sddm/sddm/issues From the old bug #1244447: Alvin 2016-05-03 13:51:43 CEST This occurs on fresh install. At first boot, monitor is blank. Likewise, restarting sddm shows a blank screen. -- It seems to be related to the known bug with the wrong default keyboard layout ("always us") due to a bug in xorg/xcb. https://bugs.freedesktop.org/show_bug.cgi?id=93701 https://github.com/sddm/sddm/issues/202
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.