Description of problem: I've tried to log in to a standard Plasma Session on the current Rawhide Version-Release number of selected component: kf5-kactivities-5.16.0-1.fc24 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 853 kernel: 4.4.0-0.rc1.git2.1.fc24.x86_64 runlevel: unknown type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #11 QXcbConnection::processXcbEvents at qxcbconnection.cpp:1470 #12 QObject::event at kernel/qobject.cpp:1239 #13 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3716 #14 QApplication::notify at kernel/qapplication.cpp:3499 #15 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:965 #16 QCoreApplication::sendEvent at kernel/qcoreapplication.h:224 #17 QCoreApplicationPrivate::sendPostedEvents at kernel/qcoreapplication.cpp:1593 #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 1283185
Created attachment 1097325 [details] File: backtrace
Created attachment 1097326 [details] File: cgroup
Created attachment 1097327 [details] File: core_backtrace
Created attachment 1097328 [details] File: dso_list
Created attachment 1097329 [details] File: environ
Created attachment 1097330 [details] File: exploitable
Created attachment 1097331 [details] File: limits
Created attachment 1097332 [details] File: maps
Created attachment 1097333 [details] File: mountinfo
Created attachment 1097335 [details] File: namespaces
Created attachment 1097336 [details] File: open_fds
Created attachment 1097337 [details] File: proc_pid_status
Created attachment 1097338 [details] File: var_log_messages
Another user experienced a similar problem: Crash likely happened the moment I logged into KDE. The K-gears appear for about 30 seconds, fade to black and then nothing. I have to manually kill and start a new plasmashell instance to get anything useful on the desktop. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1793 kernel: 4.4.0-0.rc5.git3.1.fc24.x86_64 package: kf5-kactivities-5.17.0-1.fc24 reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
*** Bug 1317033 has been marked as a duplicate of this bug. ***
this crash line reference is a qWarning "The X11 connection broke (error_code), Did the X11 server die?" which is wrapped under int connection_error = xcb_connection_has_error(xcb_connection()); if (connection_error) qWarning(...) exit(1); } So... wierd?
The backtrace looks quite different to the abrt trace: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f58640a9731 in QSqlDatabase::close (this=this@entry=0x55c00b82f688) at kernel/qsqldatabase.cpp:871 871 d->driver->close(); ... #10 0x00007f5878dea1a5 in __GI_exit (status=status@entry=1) at exit.c:104 No locals. #11 0x00007f5868f3470e in QXcbConnection::processXcbEvents (this=0x55c00b5875a0) at qxcbconnection.cpp:1470 connection_error = <optimized out> eventqueue = <optimized out> This looks similar to the report below where a crash happened during exit(): https://bugreports.qt.io/browse/QTBUG-35977
Is this a duplicate of: Bug 1233653 - [abrt] kf5-kactivities: QSqlDatabase::close()(): kactivitymanagerd killed by SIGSEGV
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.