Version-Release number of selected component: kf5-kactivities-5.9.0-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: exit executable: /usr/bin/kactivitymanagerd global_pid: 1818 kernel: 4.0.0-1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1555 var_log_messages: [System Logs]:\n-- Logs begin at Wed 2015-04-29 14:19:11 EDT, end at Wed 2015-04-29 19:07:11 EDT. -- Truncated backtrace: Thread no. 1 (10 frames) #12 exit at exit.c:104 #13 QXcbConnection::processXcbEvents at qxcbconnection.cpp:1249 #14 QObject::event at kernel/qobject.cpp:1245 #15 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3720 #16 QApplication::notify at kernel/qapplication.cpp:3503 #17 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:935 #18 sendEvent at kernel/qcoreapplication.h:228 #19 QCoreApplicationPrivate::sendPostedEvents at kernel/qcoreapplication.cpp:1552 #20 QCoreApplication::sendPostedEvents at kernel/qcoreapplication.cpp:1410 #21 postEventSourceDispatch at kernel/qeventdispatcher_glib.cpp:271
Created attachment 1020698 [details] File: backtrace
Created attachment 1020699 [details] File: cgroup
Created attachment 1020700 [details] File: core_backtrace
Created attachment 1020701 [details] File: dso_list
Created attachment 1020702 [details] File: environ
Created attachment 1020703 [details] File: limits
Created attachment 1020704 [details] File: maps
Created attachment 1020705 [details] File: mountinfo
Created attachment 1020706 [details] File: namespaces
Created attachment 1020707 [details] File: open_fds
Created attachment 1020708 [details] File: proc_pid_status
Another user experienced a similar problem: I do not know how this happened. reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: exit executable: /usr/bin/kactivitymanagerd global_pid: 1409 kernel: 4.0.2-300.fc22.x86_64 package: kf5-kactivities-5.10.0-1.fc22 reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: I opened a gnome-session and got this crash. This is the 4th time I get this. reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: exit executable: /usr/bin/kactivitymanagerd global_pid: 8562 kernel: 4.0.4-301.fc22.x86_64 package: kf5-kactivities-5.10.0-1.fc22 reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 500
This looks like the X11 server died and then the application crashed when some handlers were called. I would argue that when X11 crashes we cannot expect GUI applications to exit gracefully.
*** Bug 1235470 has been marked as a duplicate of this bug. ***
(In reply to Daniel Vrátil from comment #14) > This looks like the X11 server died and then the application crashed when > some handlers were called. > > I would argue that when X11 crashes we cannot expect GUI applications to > exit gracefully. The server didn't crash in my case. The gnome session was running.
(In reply to Daniel Vrátil from comment #14) > This looks like the X11 server died and then the application crashed when > some handlers were called. in my case, abrt doesn't have any records of X crashing most of my k-something crashes seem to appear after undocking, putting the laptop to sleep then waking it up again
Another user experienced a similar problem: Running Fedora KDE 23 Beta in a Virtualbox VM , with 3D display enabled , can't run KDE with 3D enabled , we still need to disable it to panels not crash and disappear reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1715 kernel: 4.2.1-300.fc23.x86_64 package: kf5-kactivities-5.14.0-1.fc23 reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: It happend yesterday and today, right after the login. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 2395 kernel: 4.2.3-300.fc23.x86_64 package: kf5-kactivities-5.15.0-1.fc23 reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Appears in ABRT's System crashes on first boot and login after install of F23 Final RC3 KDE live x86_64. There's no pop-up notification so it's not technically a release blocker. reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1322 kernel: 4.2.3-300.fc23.x86_64 package: kf5-kactivities-5.14.0-1.fc23 reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: This happened after undocking and closing / reopening the lid, when the machine failed to suspend, then it showed just black screen, I had to kill X ... reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1703 kernel: 4.2.3-300.fc23.x86_64 package: kf5-kactivities-5.15.0-1.fc23 reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I just ran an update after fresh installation of Fedora 23, as the updating process was taking place, it gave the error. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1639 kernel: 4.2.3-300.fc23.x86_64 package: kf5-kactivities-5.14.0-1.fc23 reason: kactivitymanagerd killed by SIGSEGV runlevel: unknown type: CCpp uid: 0
Another user experienced a similar problem: Did nothing special reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1644 kernel: 4.2.3-300.fc23.x86_64 package: kf5-kactivities-5.15.0-1.fc23 reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: kscreenlock_greeter has been left for zombie for a number of times since I upgraded to Fedora 23. This time I sent a SIGCHLD to its parent. The X session restarted. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 3177 kernel: 4.2.5-300.fc23.x86_64 package: kf5-kactivities-5.15.0-1.fc23 reason: kactivitymanagerd killed by SIGSEGV 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.