Version-Release number of selected component: sddm-0.10.0-4.fc22 Additional info: reporter: libreport-2.6.0 backtrace_rating: 4 cmdline: /usr/bin/sddm-greeter --socket /tmp/sddm-:0-gdePwh --theme /usr/share/sddm/themes/fedora crash_function: SDDM::XcbKeyboardBackend::initLedMap executable: /usr/bin/sddm-greeter global_pid: 4072 kernel: 4.0.8-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 990 Truncated backtrace: Thread no. 1 (4 frames) #0 SDDM::XcbKeyboardBackend::initLedMap at /usr/src/debug/sddm-0.10.0/src/greeter/KeyboardModel.cpp:231 #1 SDDM::XcbKeyboardBackend::init at /usr/src/debug/sddm-0.10.0/src/greeter/KeyboardModel.cpp:149 #2 SDDM::KeyboardModel::KeyboardModel at /usr/src/debug/sddm-0.10.0/src/greeter/KeyboardModel.cpp:449 #3 SDDM::GreeterApp::GreeterApp at /usr/src/debug/sddm-0.10.0/src/greeter/GreeterApp.cpp:116
Created attachment 1053443 [details] File: backtrace
Created attachment 1053444 [details] File: cgroup
Created attachment 1053445 [details] File: core_backtrace
Created attachment 1053446 [details] File: dso_list
Created attachment 1053447 [details] File: environ
Created attachment 1053448 [details] File: limits
Created attachment 1053449 [details] File: maps
Created attachment 1053450 [details] File: mountinfo
Created attachment 1053451 [details] File: namespaces
Created attachment 1053452 [details] File: open_fds
Created attachment 1053453 [details] File: proc_pid_status
Created attachment 1053454 [details] File: var_log_messages
This occurs on fresh install. At first boot, monitor is blank. Likewise, restarting sddm shows a blank screen.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.
*** This bug has been marked as a duplicate of bug 1419268 ***