+++ This bug was initially created as a clone of Bug #1347859 +++ Version-Release number of selected component: kactivitymanagerd-5.6.5-1.fc25 Additional info: reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 859 kernel: 4.7.0-0.rc3.git1.1.fc25.x86_64 pkg_vendor: Fedora Project reproducible: Not sure how to reproduce the problem runlevel: unknown type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #11 QXcbConnection::processXcbEvents at qxcbconnection.cpp:1687 #12 QObject::event at kernel/qobject.cpp:1256 #13 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3804 #14 QApplication::notify at kernel/qapplication.cpp:3561 #15 QCoreApplication::notifyInternal2 at kernel/qcoreapplication.cpp:1015 #16 QCoreApplication::sendEvent at kernel/qcoreapplication.h:225 #17 QCoreApplicationPrivate::sendPostedEvents at kernel/qcoreapplication.cpp:1650 #18 QEventDispatcherUNIX::processEvents at kernel/qeventdispatcher_unix.cpp:579 #19 QUnixEventDispatcherQPA::processEvents at eventdispatchers/qunixeventdispatcher.cpp:62 #20 QEventLoop::exec at kernel/qeventloop.cpp:204 Potential duplicate: bug 1329330 --- Additional comment from on 2016-06-17 17:04:14 EDT --- --- Additional comment from on 2016-06-17 17:04:15 EDT --- --- Additional comment from on 2016-06-17 17:04:16 EDT --- --- Additional comment from on 2016-06-17 17:04:17 EDT --- --- Additional comment from on 2016-06-17 17:04:18 EDT --- --- Additional comment from on 2016-06-17 17:04:19 EDT --- --- Additional comment from on 2016-06-17 17:04:20 EDT --- --- Additional comment from on 2016-06-17 17:04:21 EDT --- --- Additional comment from on 2016-06-17 17:04:22 EDT --- --- Additional comment from on 2016-06-17 17:04:23 EDT --- --- Additional comment from on 2016-06-17 17:04:24 EDT --- --- Additional comment from on 2016-06-17 17:04:25 EDT --- --- Additional comment from on 2016-06-17 17:04:26 EDT --- --- Additional comment from Jan Kurik on 2016-07-26 00:42:31 EDT --- This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'. --- Additional comment from pavel raur on 2016-09-12 05:38:01 EDT --- Similar problem has been detected: Happened when i loged back on switched user. reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 2184 kernel: 4.8.0-0.rc5.git1.1.fc25.x86_64 package: kactivitymanagerd-5.7.4-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001 --- Additional comment from Mustafa Muhammad on 2016-10-10 03:35:01 EDT --- Similar problem has been detected: Just logged into wayland session reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1738 kernel: 4.8.1-1.fc25.x86_64 package: kactivitymanagerd-5.8.0-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from Giulio 'juliuxpigface' on 2016-10-18 17:08:46 EDT --- Similar problem has been detected: I don't know when did this pop up, sorry, reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1550 kernel: 4.8.1-1.fc25.x86_64 package: kactivitymanagerd-5.8.1-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from Radim Hopp on 2016-11-10 08:50:14 EST --- I'm experiencing this bug at least twice a day. It seems completely random (maybe one common thing - I think it happens when CPU is in high use for some time, but I'm not able to confirm this theory) Every time, the screen freezes for 1-2 seconds and whole X session crashes (black screen on all my 3 displays). Sometimes I'm able to switch to text console (CTRL+ALT+F2), sometimes I'm not. When I look into abrt, drkonqi crashes right after kactivitymanagerd. --- Additional comment from Alvin on 2016-11-24 05:05:22 EST --- I got it on log on. The KDE logo and my mouse pointer appear and stay on the screen. I had to restart SDDM in order to log in. --- Additional comment from Mustafa Muhammad on 2016-11-29 03:57:42 EST --- Similar problem has been detected: Just logged into Plasma Wayland session reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1560 kernel: 4.8.10-300.fc25.x86_64 package: kactivitymanagerd-5.8.4-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from Simon on 2016-12-14 06:15:42 EST --- I just updated F25 this morning, new kerenel, kdelibs etc. but I'm still getting loads of kwin_X11 warnings in journald.log: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 57771, resource id: 0, major code: 14 (GetGeometry), minor code: 0 these are preceded by: plasmashell: file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:100: TypeError: Cannot read property of null and: QXcbConnection: XCB error: 2 (BadValue), sequence: 24881, resource id: 100663419, major code: 141 (Unknown), minor code: 3 F25 has got more stable for me with the updates so far applied, (plasma hasn't frozen yet today but I'm about to open a few more programs) but can anyone advise me how to correct these errors. I have seen some older posts on the net about the bug suggesting it should be fixed by now so I'm wondering if I'm mis-configured somehow? --- Additional comment from Simon on 2016-12-14 07:38:57 EST --- update: I cannot now click to switch between the open programs on the taskbar, they don't respond to the mouse, and there is a frozen image of thunderbird that overlays all the other programs if I alt+tab between them. This happens in every session after a few programs are opened and there are no error or warning messages in journald.log or Xorg.log. The only warning are posted above. --- Additional comment from Thom Carlin on 2016-12-14 07:54:04 EST --- Thanks to Simon's hints, journalctl -xe revealed man QXcbConnection: XCB error: 2 (BadValue), sequence: <number>, resource id: <number>, major code: 141 (Unknown), minor code: 3 --- Additional comment from Thom Carlin on 2016-12-14 07:56:32 EST --- ...which led to finding at https://forum.kde.org/viewtopic.php?f=66&t=133169 the command: qdbus org.kde.KWin /KWin supportInformation --- Additional comment from Simon on 2016-12-14 13:27:15 EST --- Thanks for your post Thom I ran kwin supportinformation from a wayland gnome session (because plasma is freezing consistently) and got: kwin: unable to claim manager selection, another wm running? (try using --replace so I ran it with --replace and it crashed the session. Tried it in a plasma session but only got the the card info (Nvidia G98, nouveau etc) and the same error messages as above. So I don't think it can get past the errors. I can't paste the output because plasma crashes when you run it but it provides no more info that the logs I posted 11:15:42 GMT, less really. It's puzzling because plasma seems to have got more unstable since I updated this a.m. --- Additional comment from Thom Carlin on 2016-12-14 16:02:33 EST --- For my system, major code: 141 seems to be Composite. Daniel, is there anything we can do to provide useful additional information? --- Additional comment from Alvin on 2016-12-15 03:16:01 EST --- Similar problem has been detected: User logs in. KDE logo is visible and stays on screen. reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1672 kernel: 4.8.13-300.fc25.x86_64 package: kactivitymanagerd-5.8.4-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1218 --- Additional comment from LarryO on 2016-12-15 06:12:06 EST --- I have also had the issue a few times with the KDE logo "freezing" after authentication but don't know whether or not it's directly related to the symptom that this report is focused on. I assumed that the KDE logo "freeze" after auth was related to https://bugzilla.redhat.com/show_bug.cgi?id=1399396. --- Additional comment from Simon on 2016-12-20 08:54:24 EST --- I'm still having problems with plasma desktop freezing despite installing all updates. Here's an assortment of error messages from journalctl.log today (some of them may be from gnome sessions: kdeinit5: Fatal IO error: client killed kglobalaccel5: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. kiod5: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. QThread: Destroyed while thread is still running The X11 connection broke: I/O error (code 1) could not connect to wayland server Fatal server error: org.gnome.Shell.desktop (EE) Couldn't add screen systemd-coredump Process 19785 (kactivitymanage) of user 1000 dumped core. sddm The configured theme "01-breeze-fedora" doesn't exist, using the embedded theme instead sddm QProcess: Destroyed while process ("/usr/libexec/sddm-helper") is still running. audit USER_AUTH pid=6449 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success' audit CRED_ACQ pid=6449 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success' kdeinit5 kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/remotedirnotify.so" (LOADS like that) kdeinit5 EDID ICC Profile already exists "/home/simon/.local/share/icc/edid-8419218953dd271ab2495926a894c5f6.icc" ksmserver Qt: Session management error: networkIdsList argument is NULL In red: spice-vdagent Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 kdeinit5 kf5.kded: could not find kded module with id "kolorserver" kdeinit5 kf5.kded: attempted to load an invalid module. 20/12/2016 07:46 kwin_x11 QXcbConnection: XCB error: 3 (BadWindow), sequence: 830, resource id: 60817412, major code: 18 (ChangeProperty), minor code: 0 kwin_x11 QXcbConnection: XCB error: 3 (BadWindow), sequence: 830, resource id: 60817412, major code: 18 (ChangeProperty), minor code: 0 kwin_x11 libkwinglutils: Update of color profiles failed (Red) plasmashell Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) 20/12/2016 07:46 kdeinit5 networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "S390Subchannels" LOADS audit SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@1-7713-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' kdeinit5 kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/device_automounter.so" Lots RED kernel nouveau 0000:02:00.0: fifo: CACHE_ERROR - ch 7 [kwin_x11[7882]] subc 0 mthd 0060 data beef0201 followed by: kwin_x11 QXcbConnection: XCB error: 3 (BadWindow), sequence: 9845, resource id: 48234586, major code: 18 (ChangeProperty), minor code: 0 --- Additional comment from Michal Smolak on 2016-12-21 23:38:54 EST --- --- Additional comment from Simon on 2016-12-25 06:00:54 EST --- Merry Christmas everyone. I checked that and got: You are not authorized to access bug #1407004. So I assume people are hard at work to fix this, thanks guys. Apologies if I am not posting this the right way It's in case the info helps. Any advice welcome but plasma froze at login after installing the new kernel & rebooting but loaded OK when I logged out and back in and hasn't frozen since but I'm still getting (selection from from journalctl.log): plasmashell QXcbConnection: XCB error: 2 (BadValue), sequence: 34255, resource id: 121634850, major code: 141 (Unknown), minor code: 3 (quite a lot) kwin_x11 QXcbConnection: XCB error: 3 (BadWindow), sequence: 49143, resource id: 18916715, major code: 20 (GetProperty), minor code: 0 (Lots like this) kscreenlocker_greet QObject: Cannot create children for a parent that is in a different thread. (Parent is ScreenLocker::UnlockApp(0x7ffd20b33aa0), parent's thread is QThread(0x563364456080), current thread is QThread(0x5633645097d0) apper QCommandLineParser: option not defined: "install-mime-type" apper Invalid pixmap specified. apper No frame loaded and from apper: SearchGroups not supported by backend dolphin QPixmap::scaled: Pixmap is a null pixmap (Lots) 25/12/2016 10:50 cockpit-ws received unsupported HTTP method (And when I tried http://localhost:9090 I just got a page saying: Server: Then reloaded the page and it works fine. I'm also getting: systemd timedatex.service: Two services allocated for the same bus name org.freedesktop.timedate1, refusing operation. but I might be able to figure out what to disable to solve that best wishes --- Additional comment from Mustafa Muhammad on 2017-01-03 00:38:00 EST --- Similar problem has been detected: Just logged into Plasma Wayland session 5.8.5 reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 2346 kernel: 4.8.15-300.fc25.x86_64 package: kactivitymanagerd-5.8.5-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from Simon on 2017-01-04 03:33:12 EST --- 04/01/2017 08:25 kwin_x11 QXcbConnection: XCB error: 3 (BadWindow), sequence: 40950, resource id: 102760465, major code: 18 (ChangeProperty), minor code: 0 kwin_x11 QXcbConnection: XCB error: 3 (BadWindow), sequence: 40978, resource id: 29360185, major code: 2 (ChangeWindowAttributes), minor code: 0 Plasmashell QXcbConnection: XCB error: 2 (BadValue), sequence: 30342, resource id: 4194427, major code: 141 (Unknown), minor code: 3 audit SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' plasmashell QXcbConnection: XCB error: 2 (BadValue), sequence: 31010, resource id: 4250642, major code: 141 (Unknown), minor code: 3 04/01/2017 08:31 plasmashell QXcbConnection: XCB error: 2 (BadValue), sequence: 32964, resource id: 4256937, major code: 141 (Unknown), minor code: 3 --- Additional comment from Simon on 2017-01-10 05:50:35 EST --- All updates applied, still getting: kwin_x11 QXcbConnection: XCB error: 3 (BadWindow), sequence: 10993, resource id: 98566157, major code: 18 (ChangeProperty), minor code: 0 plasmashell file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/KickoffItem.qml:218:19: Unable to assign [undefined] to QString multiple messages like those in kystemlog and managing periodic loss of access to start menu with ctrl-alt-f2 & ctrl-alt-f1 --- Additional comment from Emanoel on 2017-01-13 08:28:34 EST --- --- Additional comment from RobbieTheK on 2017-01-20 10:15:45 EST --- --- Additional comment from Evgeny on 2017-01-21 08:14:03 EST --- --- Additional comment from Gerasim on 2017-02-18 07:51:25 EST --- --- Additional comment from Gerasim on 2017-02-20 11:12:42 EST --- --- Additional comment from on 2017-07-13 08:18:30 EDT --- Similar problem has been detected: I was just logging into kde. seems to occur every 5 to 10 login. perhaps related to package updates. reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1453 kernel: 4.11.8-200.fc25.x86_64 package: kactivitymanagerd-5.9.5-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1004 --- Additional comment from Vedran Miletić on 2017-11-05 14:30:05 EST --- --- Additional comment from Ryan on 2017-11-15 09:54:51 EST --- Similar problem has been detected: Log into Fedora 27 Kactivitymanagerd 'quit unexpectedly' reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=644e60f7add9421b9b1178beffb15a3f;i=291b;b=ef8a38e50996408f89669bb5d96a38a5;m=23760801;t=55e066d312a90;x=16a6322699bc9b60 kernel: 4.13.12-300.fc27.x86_64 package: kactivitymanagerd-5.10.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from Fedora End Of Life on 2017-11-16 09:48:20 EST --- This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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. --- Additional comment from LarryO on 2017-12-06 14:53:12 EST --- Similar problem has been detected: Tried to save PDF viewed in Firefox. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=181e2f8c93c84b0c84c5f33178f5f4ca;i=2264f;b=a71c316667c44f93bd2c13e59ae3b1e8;m=23a07da7f2;t=55fb0edf9fc70;x=9ff8b016f144b2ab kernel: 4.13.16-302.fc27.x86_64 package: kactivitymanagerd-5.10.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from Mustafa Muhammad on 2017-12-09 09:30:27 EST --- Similar problem has been detected: Just logging into my account reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=1121ba72d480460d9d79c9392745497b;i=1a811;b=84d9e8302cf342b5809125c26439c81f;m=105e4080;t=55fe8f40eb524;x=d99add1c42a79065 kernel: 4.13.16-302.fc27.x86_64 package: kactivitymanagerd-5.11.3-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from Fedora End Of Life on 2017-12-12 05:38:20 EST --- Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. --- Additional comment from Garry T. Williams on 2017-12-16 19:12:19 EST --- Similar problem has been detected: Log out of desktop and log back in. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=07872308c4734d8fb665dbcca7ae44e0;i=8602c;b=2d9a8420e10a4852ad4de220d2e3ebd9;m=1133570ab6;t=5607e0071e33c;x=ee80221d388cfcde kernel: 4.14.6-300.fc27.x86_64 package: kactivitymanagerd-5.11.4-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from Garry T. Williams on 2017-12-16 19:30:46 EST --- Please re-open this bug. It's not gone even with f27. --- Additional comment from on 2017-12-26 14:47:20 EST --- Similar problem has been detected: user login after reboot (new kernel) reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=fed5ea54a50d4f6d978002ee4583b119;i=1ad49a;b=0a16646224c749f0b605aad21c1973c9;m=ba30d447d;t=5614032c76b99;x=a9fe5139a843e0a kernel: 4.14.7-300.fc27.x86_64 package: kactivitymanagerd-5.11.3-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from Roland Pallai on 2017-12-27 10:25:26 EST --- Similar problem has been detected: I just logged out with some open windows on five activities. Next time the restored windows were assigned to one activity. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=04843fc7261049828bbc432a4bdbf3af;i=155d85f;b=f1f39b8d99384a64bd4053a25dd262a4;m=37a82bc718;t=56153a5f21ab0;x=42579e96498acfad kernel: 4.14.7-300.fc27.x86_64 package: kactivitymanagerd-5.11.3-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from Eugene Mah on 2017-12-31 06:49:07 EST --- Similar problem has been detected: Unsure what happened. Logged into my computer and found the crash report in ABRT reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=4b7f86b16e7d422380c0cd35b872e91a;i=54c2b;b=07532f4802874ba485c4253a6d434217;m=20ea50f084;t=561a11b716a99;x=d1869be4beb7f5f9 kernel: 4.14.8-300.fc27.x86_64 package: kactivitymanagerd-5.11.4-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from on 2018-01-07 16:55:50 EST --- Similar problem has been detected: login afer new kernel reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=fed5ea54a50d4f6d978002ee4583b119;i=1d498c;b=f15d9ab2d6d848a5997e0040f0cc79f4;m=117a5f5f16;t=5623666b4f61c;x=de0e98857b4fc5 kernel: 4.14.8-300.fc27.x86_64 package: kactivitymanagerd-5.11.4-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from H.-P. Sorge on 2018-01-10 14:09:21 EST --- Similar problem has been detected: I changed langua setting from de to us. The logout / login. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=ce382a0d1c8341f2b4f96eadebb633dd;i=49cb50;b=8c6f1922e11248a3aa57e54f050ef3ca;m=1ff57e0ec7;t=562709f4dd1e6;x=d4822253fcaa9294 kernel: 4.14.11-300.fc27.x86_64 package: kactivitymanagerd-5.11.4-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 2001 --- Additional comment from Garry T. Williams on 2018-01-17 11:43:05 EST --- Similar problem has been detected: I logged out and ogged back into the KDE desktop. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=52e055f5d22b4c328ab921729ec212ae;i=6cee;b=346007d197ac438183dee0161fae5d26;m=678041503d;t=562fb71fc917e;x=dc7a44a42e1ff14 kernel: 4.14.13-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from D. Stimits on 2018-01-19 15:29:51 EST --- Similar problem has been detected: This occurs each logout/login. I do not know if this occurs during the logout, or if this occurs during the login. This crash occurs in combination with dnfdragora crashing (https://bugzilla.redhat.com/show_bug.cgi?id=1518544). The system is always updated, and the problem remains after several updates. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=5a4c4fb700a04793b534ae20f2b941b7;i=4520e;b=519b4b07b6304dec8946cd834d7228a4;m=1af3ee92;t=56326a15a4179;x=db3c161dedca8886 kernel: 4.14.13-300.fc27.x86_64 package: kactivitymanagerd-5.11.4-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from D. Stimits on 2018-01-19 15:31:32 EST --- This bug is still present in Fedora 27. Can this be re-opened? --- Additional comment from Jacek Radzikowski on 2018-01-20 13:20:07 EST --- Similar problem has been detected: Switching between desktops. The crash seems to occur when KDE console and Atom editor are running, and switching between desktops containing them. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=93aadadf3cd24e548556e8048450a566;i=26cb7;b=24d7cdb62c6e447db0b4a999759458d0;m=14527263da;t=56339194879cd;x=2607d2b93a4a52ce kernel: 4.14.13-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 --- Additional comment from rossano on 2018-01-21 05:30:18 EST --- Similar problem has been detected: Dopo un crash, al riavvio ho ottenuto la segnalazione di questo errore reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=c820ab48dd164cb6b32d4fd1644858de;i=81a;b=c0e09a2fdc8c4a56a6ff301d45eda8d9;m=21412d09;t=563464d833221;x=748be7fa5315f41d kernel: 4.14.13-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1003 --- Additional comment from Alvin on 2018-01-22 11:25:26 EST --- Similar problem has been detected: abrt notices this often after logging in reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=b678c361307d41ab87c42cd6180c86f4;i=b83d;b=2b0cd7f49b0b4cf6920263d27de74534;m=55538fcef;t=5635fcd7128a9;x=41fe109e43ebbd3 kernel: 4.14.13-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 39000001 --- Additional comment from Vasyuk Vladimir on 2018-01-22 14:30:28 EST --- Similar problem has been detected: I've just got information about the problem reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=fd974f88af9d4f7097836933219f7d56;i=3a0a;b=6fa83935499340789a86cb1fb88462b8;m=ff7736ad;t=561f320846915;x=687abae85284c25d kernel: 4.14.11-300.fc27.x86_64 package: kactivitymanagerd-5.11.4-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1537345 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I signed in to KDE Plasma reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=d7542d1d9a4040a591f228ed04ca9b57;i=2a37b3;b=27904925343d4875abe88b32da6d0beb;m=4aa5c4c5;t=5637380814bd1;x=81c0dfbf9f42fe6c kernel: 4.14.13-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: after trying kde-plasma I logged into xfce4 again, when kactivitymanagerd crashed. why did it try to start up after all? reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=dbd28263a3d54c78a1d672869c619a1c;i=179a8;b=30e47af7ba59492bacedf68d58a2efbf;m=2d0dca3d;t=56380990d1864;x=95786aaa3fa29c52 kernel: 4.14.13-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
(In reply to Clemens Eisserer from comment #3) > Similar problem has been detected: > > after trying kde-plasma I logged into xfce4 again, when kactivitymanagerd > crashed. > why did it try to start up after all? ... In my case I've briefly seen a crash during logout, but since the desktop is closing I could never do anything about it until logging back in. I believe your crash was during logout from KDE, but the crash report tool told you about it during login because it isn't running (or is in the process of stopping) at the moment of crash.
could be, I once logged out of a broken session - next time the dialog appeared.
(In reply to Clemens Eisserer from comment #5) > could be, I once logged out of a broken session - next time the dialog > appeared. I just verified this. What I did was start gnome-abrt, clear all warnings, and verify "/var/spool/abrt/" was empty. Then I logged out. I looked at "/var/spool/abrt/" and there are the crash reports. So exiting KDE is a reliable trigger. Reports visible on start-up are just delayed visibility of an event which already occurred.
*** Bug 1541909 has been marked as a duplicate of this bug. ***
*** Bug 1542637 has been marked as a duplicate of this bug. ***
*** Bug 1544018 has been marked as a duplicate of this bug. ***
*** Bug 1544110 has been marked as a duplicate of this bug. ***
*** Bug 1544156 has been marked as a duplicate of this bug. ***
*** Bug 1544262 has been marked as a duplicate of this bug. ***
*** Bug 1544292 has been marked as a duplicate of this bug. ***
Similar problem has been detected: started the system when I was notified of this crash reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=e5f649b5941f438298f85a602100c562;i=868;b=cd0178b54b1d41f186c6eff7bb4bc928;m=27901b6;t=5651d50b2c059;x=2603b7307e88b94 kernel: 4.14.18-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: 5 3 type: CCpp uid: 1000
Similar problem has been detected: brefore shutdown I switcht to runlevel 3, at the next boot I got this crash reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=e5f649b5941f438298f85a602100c562;i=1203;b=550fe5fcc1774ebebe2e6518e6a22a06;m=1fe76474;t=5651d81bd4ce7;x=33153e99eb8d2ce2 kernel: 4.14.18-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: 5 3 type: CCpp uid: 1000
I have noticed a number of applications are momentarily listed as crashed during logout if the applications have not been manually closed. A big example is konsole. What I see is a pattern that logging out is for whatever reason causing crashes instead of normal shutdown of applications. I believe someone will need to trace how exiting a session for logout deals with running applications. Normally there will be no note until logging back in...in cases where the crash is actually visible during logout the crash app ends too quickly to see the details until logging back in.
*** Bug 1546199 has been marked as a duplicate of this bug. ***
*** Bug 1548186 has been marked as a duplicate of this bug. ***
Similar problem has been detected: kactivitymanagerd crashed after update kernel 4.15.4, reboot and login session reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=ca8ca2ba7181409889635ea09baca302;i=14092;b=178a8fb5b1fe4b17b3ff719198b8cfb5;m=3304c897;t=565ec06682c67;x=91380f02c728c841 kernel: 4.15.3-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1549962 has been marked as a duplicate of this bug. ***
*** Bug 1550563 has been marked as a duplicate of this bug. ***
Similar problem has been detected: typical kde crash reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=e5f649b5941f438298f85a602100c562;i=359cd;b=81688820ea7a4ee088f35633a0207ca5;m=2d0dd1e;t=5662aff4bdff0;x=404a3a2f4249f9e7 kernel: 4.15.4-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1551184 has been marked as a duplicate of this bug. ***
*** Bug 1551694 has been marked as a duplicate of this bug. ***
*** Bug 1553298 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.