Version-Release number of selected component: plasma-workspace-5.3.0-3.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/libexec/drkonqi -platform xcb -display :0 --appname kdeinit5 --kdeinit --apppath /usr/bin --signal 11 --pid 2038 --startupid 0 --restarted crash_function: qt_message_fatal executable: /usr/libexec/drkonqi global_pid: 5096 kernel: 4.0.1-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 qt_message_fatal at global/qlogging.cpp:1415 #3 QMessageLogger::fatal at global/qlogging.cpp:636 #4 QXcbConnection::QXcbConnection at qxcbconnection.cpp:355 #5 QXcbIntegration::QXcbIntegration at qxcbintegration.cpp:174 #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:1010 #10 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1165 #11 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1182
Created attachment 1023763 [details] File: backtrace
Created attachment 1023764 [details] File: cgroup
Created attachment 1023765 [details] File: core_backtrace
Created attachment 1023766 [details] File: dso_list
Created attachment 1023767 [details] File: environ
Created attachment 1023768 [details] File: limits
Created attachment 1023769 [details] File: maps
Created attachment 1023770 [details] File: mountinfo
Created attachment 1023771 [details] File: namespaces
Created attachment 1023772 [details] File: open_fds
Created attachment 1023773 [details] File: proc_pid_status
Created attachment 1023774 [details] File: var_log_messages
*** Bug 1239221 has been marked as a duplicate of this bug. ***
*** Bug 1236181 has been marked as a duplicate of this bug. ***
Same problem as bug #1154637 - application fails to connect to the X server on startup.
Another user experienced a similar problem: Plasma crashed after I logged in at the GDM prompt, so I sshed into my PC and ran "DISPLAY=:1 strace plasmashell". This is because I have been having ongoing problems with plasma crashing. reporter: libreport-2.6.1 backtrace_rating: 4 cmdline: plasmashell crash_function: QMessageLogger::fatal(char const*, ...) const executable: /usr/bin/plasmashell global_pid: 5806 kernel: 4.0.8-300.fc22.x86_64 package: plasma-workspace-5.3.2-2.fc22 reason: plasmashell killed by SIGABRT runlevel: N 5 type: CCpp uid: 17592
Another user experienced a similar problem: Crash occured when I was attempting to set my second screen (DVI-I-0) in portrait mode. Main screen is DVI-I-1. Actions taken: 1) started Systeeminstellingen => Instellingen van het scherm (Sorry, I am working on DUTCH system) 2) Disconnect DVI-I-0 from DVI-I-1 to enable rotating 3) Rotated DVI-I-1 90 degrees to the right 4) Commit the change 5) A crash will follow. Expected behavior: Screen DVI-I-0 will show data in portrait-mode. Further info: Screen DVI-I-1: MD 20888 (1920 x 1080) Screen DVI-I-0: MD 20263 (1680 x 1050) Both screens work fine in landscape, but I have work to do that is easier to do when screen DVI-I-0 is in portrait-mode. reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/ksmserver crash_function: qt_message_fatal executable: /usr/bin/ksmserver global_pid: 13719 kernel: 4.1.3-200.fc22.x86_64+debug package: plasma-workspace-5.3.2-2.fc22 reason: ksmserver killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Left computer unattended, when I came back I couldn't do anything on the desktop reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/kscreenlocker_greet --graceTime 5068 --ksldfd 35 crash_function: qt_message_fatal executable: /usr/libexec/kscreenlocker_greet global_pid: 19714 kernel: 4.1.3-201.fc22.x86_64 package: plasma-workspace-5.3.2-2.fc22 reason: kscreenlocker_greet killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Leave the system inactive for a while (like 5m), the screenlocker should turn on. However, I see no screenlock, and the screen is not clickable. When trying from another tty to restart e.g. kwin, plasma or whatever, I get an X message: Maximum number of clients reached. In journalctl I get millions of messages such as: sep 30 14:55:53 mimi abrt-hook-ccpp[29109]: Not saving repeating crash in '/usr/libexec/kscreenlocker_greet' sep 30 14:55:53 mimi audit[29108]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=29108 comm="kscreenlocker Looks like the screenlocker is continuously crashing and starting. reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/kscreenlocker_greet --graceTime 4738 --ksldfd 29 crash_function: qt_message_fatal executable: /usr/libexec/kscreenlocker_greet global_pid: 11607 kernel: 4.2.1-300.fc23.x86_64 package: plasma-workspace-5.4.1-4.fc23 reason: kscreenlocker_greet killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This is definitely not a duplicate. Me and Paulo Fessel have the same problem though
Another user experienced a similar problem: During logout. reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/drkonqi -platform xcb -display :50 --appname kdeinit5 --kdeinit --apppath /usr/bin --signal 4 --pid 19017 --startupid 0 --restarted crash_function: qt_message_fatal executable: /usr/libexec/drkonqi global_pid: 30802 kernel: 4.1.7-200.fc22.x86_64 package: plasma-workspace-5.4.1-3.fc22 reason: drkonqi killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: starting kde reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/drkonqi -platform xcb -display :1 --appname kdeinit5 --kdeinit --apppath /usr/bin --signal 11 --pid 3768 --startupid 0 --restarted crash_function: qt_message_fatal executable: /usr/libexec/drkonqi global_pid: 4322 kernel: 4.2.5-300.fc23.x86_64 package: plasma-workspace-drkonqi-5.4.3-1.fc23 reason: drkonqi killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: .. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/drkonqi -platform xcb -display :0 --appname kwin_x11 --apppath /usr/bin --signal 11 --pid 2011 --appversion 5.4.3 --programname KWin --bugaddress submit.org --startupid 0 crash_function: qt_message_fatal executable: /usr/libexec/drkonqi global_pid: 3658 kernel: 4.2.6-301.fc23.x86_64 package: plasma-workspace-drkonqi-5.4.3-3.fc23 reason: drkonqi killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: desktop froze - plasmashell was killed to make desktop responsive again reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: plasmashell crash_function: qt_message_fatal executable: /usr/bin/plasmashell global_pid: 2972 kernel: 4.2.6-300.fc23.x86_64 package: plasma-workspace-5.4.3-3.fc23 reason: plasmashell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: logged into computer, had the terminal open (Konsole) running dnf, after walking away while dnf was downloading an application, 20 minutes later the desktop was frozen and unresponsive. I could ssh into the system, but it refused to reboot. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: plasmashell crash_function: qt_message_fatal executable: /usr/bin/plasmashell global_pid: 678 kernel: 4.2.6-301.fc23.x86_64 package: plasma-workspace-5.5.0-2.fc23 reason: plasmashell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: .. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kcminit mouse crash_function: qt_message_fatal executable: /usr/bin/kcminit global_pid: 28610 kernel: 4.2.8-300.fc23.x86_64 package: plasma-workspace-5.5.0-4.fc23 reason: kcminit killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Loaded kde via startkde & (under VNC) reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/drkonqi -platform xcb -display :1 --appname ksmserver --apppath /usr/bin --signal 11 --pid 27633 --startupid 0 --restarted crash_function: qt_message_fatal executable: /usr/libexec/drkonqi global_pid: 28110 kernel: 4.2.8-300.fc23.x86_64 package: plasma-workspace-drkonqi-5.5.1-1.fc23 reason: drkonqi killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Loaded KDE via startkde & in VNC xstartup reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/ksmserver crash_function: qt_message_fatal executable: /usr/bin/ksmserver global_pid: 28109 kernel: 4.2.8-300.fc23.x86_64 package: plasma-workspace-5.5.1-1.fc23 reason: ksmserver killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: It happened at login. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/drkonqi -platform xcb -display :0 --appname kglobalaccel5 --apppath /usr/bin --signal 11 --pid 9007 --appversion 0.2 --programname 'KDE Global Shortcuts Service' --bugaddress submit.org --startupid 0 --restarted crash_function: qt_message_fatal executable: /usr/libexec/drkonqi global_pid: 12373 kernel: 4.2.8-200.fc22.x86_64 package: plasma-workspace-drkonqi-5.5.0-4.fc22 reason: drkonqi killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Upgrade to 5.5.1 by enabling updates-testing. It is much more stable and almost ready for daily work and not just tech preview.
Got a plasma-workspace crash with 5.5.5.3.fc23.x86_64. The Problem Reporting bug references this bugzilla.
Similar problem has been detected: Just logged in. This was crash #2 / 4 after startup. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/drkonqi -platform xcb -display :0 --appname ksmserver --apppath /usr/bin --signal 11 --pid 7663 --startupid 0 --restarted crash_function: qt_message_fatal executable: /usr/libexec/drkonqi global_pid: 13197 kernel: 4.4.6-300.fc23.x86_64 package: plasma-workspace-drkonqi-5.5.5-4.fc23 reason: drkonqi killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Just logged in. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/xembedsniproxy crash_function: qt_message_fatal executable: /usr/bin/xembedsniproxy global_pid: 13261 kernel: 4.4.6-300.fc23.x86_64 package: plasma-workspace-5.5.5-4.fc23 reason: xembedsniproxy killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I have shutted dow the external monitor and let it for several hours... but I'm not sure if this is the cause. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: plasmashell crash_function: qt_message_fatal executable: /usr/bin/plasmashell global_pid: 10561 kernel: 4.4.6-300.fc23.x86_64 package: plasma-workspace-5.5.5-4.fc23 reason: plasmashell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Login Plasma with sddm. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/drkonqi -platform xcb -display :0 --appname kdeinit5 --kdeinit --apppath /usr/bin --signal 11 --pid 1417 --startupid 0 --restarted crash_function: qt_message_fatal executable: /usr/libexec/drkonqi global_pid: 4404 kernel: 4.4.6-300.fc23.x86_64 package: plasma-workspace-drkonqi-5.5.5-5.fc23 reason: drkonqi killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Crash out of the blue. User was logged in and working. (Probably only using ssh and KRDC with xfreerdp.) reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/drkonqi -platform xcb -display :0 --appname kdeinit5 --kdeinit --apppath /usr/bin --signal 11 --pid 2928 --startupid 0 --restarted crash_function: qt_message_fatal executable: /usr/libexec/drkonqi global_pid: 3634 kernel: 4.4.7-300.fc23.x86_64 package: plasma-workspace-drkonqi-5.5.5-5.fc23 reason: drkonqi killed by SIGABRT runlevel: N 5 type: CCpp uid: 1208
Similar problem has been detected: Computer locked after begin AFK. Lock screen is visible. No keyboard input or mouse input is accepted anymore. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/ksmserver crash_function: qt_message_fatal executable: /usr/bin/ksmserver global_pid: 2975 kernel: 4.4.7-300.fc23.x86_64 package: plasma-workspace-5.5.5-5.fc23 reason: ksmserver killed by SIGABRT runlevel: N 5 type: CCpp uid: 1208
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: /usr/libexec/drkonqi -platform xcb -display :0 --appname kdeinit5 --kdeinit --apppath /usr/bin --signal 11 --pid 1483 --startupid 0 --restarted crash_function: qt_message_fatal executable: /usr/libexec/drkonqi global_pid: 2019 kernel: 4.4.8-300.fc23.x86_64 package: plasma-workspace-drkonqi-5.6.3-2.fc23 reason: drkonqi killed by SIGABRT runlevel: N 5 type: CCpp uid: 1001
from comment #1 backtrace: #3 QMessageLogger::fatal (this=this@entry=0x7ffe19462b20, msg=msg@entry=0x7f4b14e97b28 "QXcbConnection: Could not connect to display %s") at global/qlogging.cpp:636 Though there is no single explanation for "could not connect to display", unfortunately.
Similar problem has been detected: While logging in. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/drkonqi -platform xcb -display :0 --appname kdeinit5 --kdeinit --apppath /usr/bin --signal 11 --pid 19983 --startupid 0 crash_function: qt_message_fatal executable: /usr/libexec/drkonqi global_pid: 12120 kernel: 4.4.9-200.fc22.x86_64 package: plasma-workspace-drkonqi-5.5.5-2.fc22 reason: drkonqi killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
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.