Description of problem:
Happens regularly when resuming from suspend to RAM. When the machine resumes, the session has been killed and it's thrown back to the login screen. Logging back in usually has an error displayed "Could not start ksmserver. Check your installation".
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 QXcbConnection::internAtom at qxcbconnection.h:409
#1 QXcbNativeInterface::atspiBus at qxcbnativeinterface.cpp:469
#2 QXcbNativeInterface::nativeResourceForIntegration at qxcbnativeinterface.cpp:174
#3 DBusConnection::getAddressFromXCB at dbusconnection.cpp:96
#4 DBusConnection::DBusConnection at dbusconnection.cpp:82
#5 QSpiAccessibleBridge::QSpiAccessibleBridge at bridge.cpp:66
#6 QXcbIntegration::accessibility at qxcbintegration.cpp:398
#7 platformAccessibility at accessible/qaccessible.cpp:488
#8 QAccessible::setRootObject at accessible/qaccessible.cpp:830
#9 QGuiApplication::exec at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:116
Potential duplicate: bug 1426783
Created attachment 1434849 [details]
Created attachment 1434850 [details]
Created attachment 1434851 [details]
Created attachment 1434852 [details]
Created attachment 1434853 [details]
Created attachment 1434854 [details]
Created attachment 1434855 [details]
Created attachment 1434856 [details]
Created attachment 1434857 [details]
Created attachment 1434858 [details]
Created attachment 1434859 [details]
Created attachment 1434860 [details]
Created attachment 1434861 [details]
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.
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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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
Thank you for reporting this bug and we are sorry it could not be fixed.