Hide Forgot
Description of problem: starting kde Version-Release number of selected component: kf5-kinit-5.15.0-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: 'klauncher [kdeinit5] --fd=8' crash_function: qt_message_fatal executable: /usr/bin/kdeinit5 global_pid: 4330 kernel: 4.2.5-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 qt_message_fatal at global/qlogging.cpp:1578 #3 QMessageLogger::fatal at global/qlogging.cpp:781 #4 QXcbConnection::QXcbConnection at qxcbconnection.cpp:525 #5 QXcbIntegration::QXcbIntegration at qxcbintegration.cpp:177 #6 QXcbIntegrationPlugin::create at qxcbmain.cpp:50 #7 loadIntegration at kernel/qplatformintegrationfactory.cpp:56 #8 QPlatformIntegrationFactory::create at kernel/qplatformintegrationfactory.cpp:73 #9 init_platform at kernel/qguiapplication.cpp:1019 #10 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1176 #11 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1193 Potential duplicate: bug 1167056
Created attachment 1092721 [details] File: backtrace
Created attachment 1092722 [details] File: cgroup
Created attachment 1092723 [details] File: core_backtrace
Created attachment 1092724 [details] File: dso_list
Created attachment 1092725 [details] File: environ
Created attachment 1092726 [details] File: limits
Created attachment 1092727 [details] File: maps
Created attachment 1092728 [details] File: mountinfo
Created attachment 1092729 [details] File: namespaces
Created attachment 1092730 [details] File: open_fds
Created attachment 1092731 [details] File: proc_pid_status
*** ConfidentialBug 1315418 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Just logged in. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: 'klauncher [kdeinit5] --fd=8' crash_function: qt_message_fatal executable: /usr/bin/kdeinit5 global_pid: 13792 kernel: 4.4.6-300.fc23.x86_64 package: kf5-kinit-5.20.0-1.fc23 reason: kdeinit5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
*** ConfidentialBug 1321171 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Login plasma through sddm reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: 'klauncher [kdeinit5] --fd=8' crash_function: qt_message_fatal executable: /usr/bin/kdeinit5 global_pid: 4407 kernel: 4.4.6-300.fc23.x86_64 package: kf5-kinit-5.21.0-1.fc23 reason: kdeinit5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Left computer alone for approximately half an hour. User was logged in, but screen locked. 'Dim Screen' and 'Screen Energy Saving' was off in KDE System Settings (Power Management). reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: 'klauncher [kdeinit5] --fd=8' crash_function: qt_message_fatal executable: /usr/bin/kdeinit5 global_pid: 2229 kernel: 4.4.7-300.fc23.x86_64 package: kf5-kinit-5.21.0-1.fc23 reason: kdeinit5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1208
*** ConfidentialBug 1333011 has been marked as a duplicate of this bug. ***
Similar problem has been detected: On login (or logout?) circumstances are unclear because the actual login does not succeed completely. User is logged in, but plasmashell crashed. Logout is possible using Krunner. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: 'klauncher [kdeinit5] --fd=8' crash_function: qt_message_fatal executable: /usr/bin/kdeinit5 global_pid: 2052 kernel: 4.4.8-300.fc23.x86_64 package: kf5-kinit-5.21.0-1.fc23 reason: kdeinit5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1001
backtrace from comment #1 #3 QMessageLogger::fatal (this=this@entry=0x7ffc9fe558c0, msg=msg@entry=0x7f6c6de025b8 "QXcbConnection: Could not connect to display %s") at global/qlogging.cpp:781 Means (most likely), your X-server died. A common cause for that is video driver issues, possibly bug #1335047 (or similar)
I take it back about the *most likely* part, though it is one explanation. There are multiple causes for being unable to connect to a display (permission, maximum clients, server crash, etc...)
*** ConfidentialBug 1335659 has been marked as a duplicate of this bug. ***
*** ConfidentialBug 1337524 has been marked as a duplicate of this bug. ***
*** ConfidentialBug 1344628 has been marked as a duplicate of this bug. ***
*** ConfidentialBug 1344855 has been marked as a duplicate of this bug. ***
*** ConfidentialBug 1348082 has been marked as a duplicate of this bug. ***
Similar problem has been detected: It happened at login. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/kf5/klauncher --fd=8 crash_function: qt_message_fatal executable: /usr/libexec/kf5/klauncher global_pid: 30169 kernel: 4.7.2-101.fc23.x86_64 package: kf5-kinit-5.25.0-1.fc23 reason: klauncher killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.