Waking up from suspend-to-disk after docking the laptop (which was suspended-to-disk), which means that external devices, including an external display became attached. Concurrent plasmashell crash reported in bug 362073. Reproducible: Always -- Backtrace: Application: ksmserver (ksmserver), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 QXcbScreen::mapToNative (this=this@entry=0x0, rect=...) at qxcbscreen.cpp:267 #7 0x00007fe27acd37b3 in QXcbWindow::mapToNative (this=<optimized out>, rect=..., screen=0x0) at qxcbwindow.cpp:199 #8 0x00007fe27acd4f6b in QXcbWindow::propagateSizeHints (this=0x24c9620) at qxcbwindow.cpp:1606 #9 0x00007fe27acda06d in QXcbWindow::setGeometry (this=0x24c9620, rect=...) at qxcbwindow.cpp:709 #10 0x000000311dc1831a in ScreenLocker::X11Locker::updateGeo (this=0x25d9310) at /var/tmp/portage/kde-plasma/kscreenlocker-5.5.5/work/kscreenlocker-5.5.5/x11locker.cpp:492 #11 0x0000003d37475313 in QtPrivate::QSlotObjectBase::call (a=0x7fff69d6a400, r=0x25d9310, this=0x25c3e10) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #12 QMetaObject::activate (sender=sender@entry=0x24b9110, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff69d6a400) at kernel/qobject.cpp:3698 #13 0x0000003d37475f87 in QMetaObject::activate (sender=sender@entry=0x24b9110, m=m@entry=0x311565b280 <QDesktopWidget::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff69d6a400) at kernel/qobject.cpp:3578 #14 0x00000031151b63ce in QDesktopWidget::resized (this=this@entry=0x24b9110, _t1=0) at .moc/moc_qdesktopwidget.cpp:204 #15 0x00000031151b7a25 in QDesktopWidgetPrivate::_q_updateScreens (this=<optimized out>) at kernel/qdesktopwidget.cpp:120 #16 0x0000003d37475894 in QMetaObject::activate (sender=0x239eb40, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fff69d6a630) at kernel/qobject.cpp:3713 #17 0x0000003d37475f87 in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x3114ea19c0 <QGuiApplication::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fff69d6a630) at kernel/qobject.cpp:3578 #18 0x0000003114ae6252 in QGuiApplication::screenAdded (this=<optimized out>, _t1=0x24b7750) at .moc/moc_qguiapplication.cpp:326 #19 0x0000003114adcf7b in QPlatformIntegration::screenAdded (this=<optimized out>, ps=<optimized out>, isPrimary=<optimized out>) at kernel/qplatformintegration.cpp:459 #20 0x00007fe27acbee83 in QXcbConnection::updateScreens (this=this@entry=0x23b5100, event=event@entry=0x7fe274003780) at qxcbconnection.cpp:272 #21 0x00007fe27acc10d3 in QXcbConnection::handleXcbEvent (this=this@entry=0x23b5100, event=event@entry=0x7fe274003780) at qxcbconnection.cpp:1136 #22 0x00007fe27acc28cb in QXcbConnection::processXcbEvents (this=0x23b5100) at qxcbconnection.cpp:1502 #23 0x0000003d3747694a in QObject::event (this=0x23b5100, e=<optimized out>) at kernel/qobject.cpp:1239 #24 0x000000311515b69c in QApplicationPrivate::notify_helper (this=this@entry=0x239d690, receiver=receiver@entry=0x23b5100, e=e@entry=0x7fe274003f40) at kernel/qapplication.cpp:3716 #25 0x0000003115160b10 in QApplication::notify (this=0x239eb40, receiver=0x23b5100, e=0x7fe274003f40) at kernel/qapplication.cpp:3499 #26 0x0000003d3744d65d in QCoreApplication::notifyInternal (this=0x239eb40, receiver=0x23b5100, event=event@entry=0x7fe274003f40) at kernel/qcoreapplication.cpp:965 #27 0x0000003d37450423 in QCoreApplication::sendEvent (event=0x7fe274003f40, receiver=<optimized out>) at kernel/qcoreapplication.h:224 #28 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x239ba00) at kernel/qcoreapplication.cpp:1593 #29 0x0000003d374509e8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451 #30 0x0000003d3749afb3 in postEventSourceDispatch (s=0x23e14a0) at kernel/qeventdispatcher_glib.cpp:271 #31 0x0000003d2de49c9d in g_main_dispatch (context=0x7fe2740016f0) at /var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3154 #32 g_main_context_dispatch (context=context@entry=0x7fe2740016f0) at /var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3769 #33 0x0000003d2de49f80 in g_main_context_iterate (context=context@entry=0x7fe2740016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3840 #34 0x0000003d2de4a02c in g_main_context_iteration (context=0x7fe2740016f0, may_block=1) at /var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3901 #35 0x0000003d3749b027 in QEventDispatcherGlib::processEvents (this=0x23e9dc0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #36 0x0000003d3744c27a in QEventLoop::exec (this=this@entry=0x7fff69d6ad90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #37 0x0000003d3745364c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #38 0x0000003114ae72fc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1527 #39 0x00000031151572d5 in QApplication::exec () at kernel/qapplication.cpp:2976 #40 0x000000311e4110fe in kdemain (argc=1, argv=<optimized out>) at /var/tmp/portage/kde-plasma/plasma-workspace-5.5.5-r2/work/plasma-workspace-5.5.5/ksmserver/main.cpp:349 #41 0x0000003d2b620620 in __libc_start_main () from /lib64/libc.so.6 #42 0x0000000000400849 in _start ()
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
(In reply to Andrew Crouthamel from comment #1) > This bug has been stagnant for a long time. Could you help us out and > re-test if the bug is valid in the latest version? Re-testing is hard, so I'm fine with closing this. In case I do bump into it again, I'll just create a new bug report. (Note that I only submit backtraces if they're deemed useful by DrKonqi, so a developer for the component might still be able to do something with this.)
Thanks for the update!