Version-Release number of selected component: kf5-kglobalaccel-5.8.0-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 kernel: 3.19.2-201.fc21.i686+PAE runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at Wed 2014-11-26 15:50:12 EAT, end at Wed 2015-04-01 11:51:49 EAT. -- Truncated backtrace: Thread no. 1 (10 frames) #3 qt_message_fatal at global/qlogging.cpp:1414 #4 QMessageLogger::fatal at global/qlogging.cpp:639 #5 QXcbConnection::QXcbConnection at qxcbconnection.cpp:346 #6 QXcbIntegration::QXcbIntegration at qxcbintegration.cpp:155 #7 QXcbIntegrationPlugin::create at qxcbmain.cpp:50 #8 loadIntegration at kernel/qplatformintegrationfactory.cpp:56 #9 QPlatformIntegrationFactory::create at kernel/qplatformintegrationfactory.cpp:73 #10 init_platform at kernel/qguiapplication.cpp:1011 #11 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1166 #12 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1183
Created attachment 1013714 [details] File: backtrace
Created attachment 1013715 [details] File: cgroup
Created attachment 1013716 [details] File: core_backtrace
Created attachment 1013717 [details] File: dso_list
Created attachment 1013718 [details] File: environ
Created attachment 1013719 [details] File: limits
Created attachment 1013720 [details] File: maps
Created attachment 1013721 [details] File: open_fds
Created attachment 1013722 [details] File: proc_pid_status
*** Bug 1229360 has been marked as a duplicate of this bug. ***
*** Bug 1267968 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: After logging out, I recieve this messgae. Actually, it happens after I changed Fedora 22 KDE theme to Fedora 23. The background is black. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 global_pid: 4341 kernel: 4.2.3-300.fc23.x86_64 package: kf5-kglobalaccel-5.14.0-1.fc23 reason: kglobalaccel5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.
Another user experienced a similar problem: When moving a window (Firefox) along the top edge quickly from one monitor to another. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 global_pid: 12372 kernel: 4.2.8-200.fc22.x86_64 package: kf5-kglobalaccel-5.17.0-1.fc22 reason: kglobalaccel5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I was using an openoffice spreadsheet when I noticed a slow down in performance reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 global_pid: 3650 kernel: 4.3.3-301.fc23.x86_64 package: kf5-kglobalaccel-5.18.0-1.fc23 reason: kglobalaccel5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
I've just got redirected here while processing crashes in abrt-gui ... it obivously failed to update the version, ouch
Similar problem has been detected: KDE locked because of usual timeout. Lock screen is visible, but keyboard and mouse input are no longer accepted. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 global_pid: 2195 kernel: 4.4.7-300.fc23.x86_64 package: kf5-kglobalaccel-5.21.0-1.fc23 reason: kglobalaccel5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1208
*** Bug 1294647 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Conditions same as in https://bugzilla.redhat.com/show_bug.cgi?id=1323110#c15, except that this one has occurred half the number of times. reporter: libreport-2.7.0 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 global_pid: 1960 kernel: 4.5.4-300.fc24.x86_64 package: kf5-kglobalaccel-5.21.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: kglobalaccel5 killed by SIGABRT reproducible: The problem is reproducible runlevel: N 5 type: CCpp uid: 1000
May be related to bug #1337526.
Similar problem has been detected: Just logged in with autologin enabled. reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 global_pid: 1386 kernel: 4.6.3-300.fc24.x86_64 package: kf5-kglobalaccel-5.23.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: kglobalaccel5 killed by SIGABRT reproducible: Not sure how to reproduce the problem runlevel: unknown type: CCpp uid: 1001
Similar problem has been detected: start up , with clean caches reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 global_pid: 5699 kernel: 4.6.4-201.fc23.x86_64 package: kf5-kglobalaccel-5.24.0-1.fc23 reason: kglobalaccel5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 500
I mean start up, (*)without clean caches , after run [1] seems that helps on this kglobalaccel5 crash , that is what I call to "clean caches" , also seems to me connected on updates of kde ... [1] rm -rf /var/tmp/kdecache-sergio /run/user/500/ksocket-sergio/ /tmp/kde-sergio
Similar problem has been detected: It happened at login reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 global_pid: 30109 kernel: 4.7.2-101.fc23.x86_64 package: kf5-kglobalaccel-5.25.0-1.fc23 reason: kglobalaccel5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: logged in and immediately logged out reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 global_pid: 3061 kernel: 4.8.6-201.fc24.x86_64 package: kf5-kglobalaccel-5.27.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: kglobalaccel5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Desktop just froze. No obvious cause. Some firefox tabs kept workign though. It was mainyl the KDE panel that stopped working. reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 global_pid: 14559 kernel: 4.8.6-201.fc24.x86_64 package: kf5-kglobalaccel-5.27.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: kglobalaccel5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1001
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.
Similar problem has been detected: as usaul on startup reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 global_pid: 2393 kernel: 4.8.14-100.fc23.x86_64 package: kf5-kglobalaccel-5.27.0-1.fc23 reason: kglobalaccel5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 500
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.
Similar problem has been detected: login at kdm. kwin starts fine, kglobalaccel5 crash reported in popup. reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 global_pid: 3161 kernel: 4.9.13-100.fc24.x86_64 package: kf5-kglobalaccel-5.31.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: kglobalaccel5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: It happened at login. reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 global_pid: 4237 kernel: 4.9.13-100.fc24.x86_64 package: kf5-kglobalaccel-5.31.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: kglobalaccel5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: How did this problem happen? I logged in using the gui; subsequently I logged out. That was enough for a crash. What I observed, was that the session, gui-wise, is not terminated in an orderly manner. An example is the appearance of an icon in the systray, telling me: "Plasma closed UNEXPECTEDLY". Yes, I noticed that. Clicking that icon, triggers a small window, in which "stack trace" is shown (for a very, very short moment). The crash appears to be in NotificationsApplet::onScreenChanges(), apparently present in the file: /usr/lib64/qt5/plugins/plasma/applets/plasma_applet_notifications.so ATTENTION: this problem started to happen after an upgrade, in which plasma-workspace-libs was upgraded from version 5.6.4 to 5.8.6 (Rex Dieter?). Downgrading makes the problem disappear. reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/kglobalaccel5 crash_function: qt_message_fatal executable: /usr/bin/kglobalaccel5 global_pid: 4051 kernel: 4.9.13-101.fc24.x86_64 package: kf5-kglobalaccel-5.32.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: kglobalaccel5 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1010
same here: my experience says this doesn't happen in new user, just happens with old settings that for some reason are no longer understood.
(In reply to Sergio Monteiro Basto from comment #36) > same here: my experience says this doesn't happen in new user, just happens > with old settings that for some reason are no longer understood. Same here? Do you refer to my experience? In my case the crash ALSO happened in case of a brand new user (which I created in order to "research" this crash). (btw, as far as I can tell, kglobalaccel5 is killed as a consequence of another crash (plasmashell) ... but I am no KDE expert. See https://bugzilla.redhat.com/show_bug.cgi?id=1434870 Another entry in bugzilla that I made to report my crash. --