Bug 354934 - crash after connecting external screen
Summary: crash after connecting external screen
Status: RESOLVED WORKSFORME
Alias: None
Product: ksmserver
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-06 09:29 UTC by Marc Schiffbauer
Modified: 2018-12-01 03:49 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
ksmserver-20151224-151328.kcrash (5.82 KB, text/plain)
2015-12-24 15:18 UTC, Andreas Sturmlechner
Details
Stacktrace with ScreenLocker entry (3.89 KB, text/plain)
2015-12-30 20:50 UTC, Kelvie Wong
Details
stack trace segmentation fault (4.37 KB, text/plain)
2016-04-18 11:51 UTC, David Menday
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Schiffbauer 2015-11-06 09:29:23 UTC
This crash happened after connecting external screen

kde-frameworks 5.15.0
qt 5.5.1

Application: kdeinit5 (kdeinit5), 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  0x00007f0f817997b3 in QXcbWindow::mapToNative (this=<optimized out>, rect=..., screen=0x0) at qxcbwindow.cpp:199
#8  0x00007f0f8179af6b in QXcbWindow::propagateSizeHints (this=0x141f730) at qxcbwindow.cpp:1606
#9  0x00007f0f817a006d in QXcbWindow::setGeometry (this=0x141f730, rect=...) at qxcbwindow.cpp:709
#10 0x00007f0f94096ba2 in QWidgetPrivate::setGeometry_sys (this=this@entry=0x1711f00, x=0, y=0, w=2560, h=<optimized out>, isMove=<optimized out>, isMove@entry=true) at kernel/qwidget.cpp:7168
#11 0x00007f0f94097770 in QWidget::setGeometry (this=0x14b6e20, r=...) at kernel/qwidget.cpp:7094
#12 0x00007f0f95559894 in QMetaObject::activate (sender=sender@entry=0x1438fb0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdc12c1730) at kernel/qobject.cpp:3713
#13 0x00007f0f95559f87 in QMetaObject::activate (sender=sender@entry=0x1438fb0, m=m@entry=0x7f0f9455b240 <QDesktopWidget::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdc12c1730) at kernel/qobject.cpp:3578
#14 0x00007f0f940b63ae in QDesktopWidget::resized (this=this@entry=0x1438fb0, _t1=0) at .moc/moc_qdesktopwidget.cpp:204
#15 0x00007f0f940b7a05 in QDesktopWidgetPrivate::_q_updateScreens (this=<optimized out>) at kernel/qdesktopwidget.cpp:120
#16 0x00007f0f95559894 in QMetaObject::activate (sender=0x12c6290, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffdc12c1960) at kernel/qobject.cpp:3713
#17 0x00007f0f95559f87 in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7f0f95c10d00 <QGuiApplication::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffdc12c1960) at kernel/qobject.cpp:3578
#18 0x00007f0f95855462 in QGuiApplication::screenAdded (this=<optimized out>, _t1=0x13a5620) at .moc/moc_qguiapplication.cpp:326
#19 0x00007f0f9584c18b in QPlatformIntegration::screenAdded (this=<optimized out>, ps=<optimized out>, isPrimary=<optimized out>) at kernel/qplatformintegration.cpp:459
#20 0x00007f0f81784e83 in QXcbConnection::updateScreens (this=this@entry=0x1337160, event=event@entry=0x194df00) at qxcbconnection.cpp:272
#21 0x00007f0f817870d3 in QXcbConnection::handleXcbEvent (this=this@entry=0x1337160, event=event@entry=0x194df00) at qxcbconnection.cpp:1136
#22 0x00007f0f817888cb in QXcbConnection::processXcbEvents (this=0x1337160) at qxcbconnection.cpp:1502
#23 0x00007f0f9555a94a in QObject::event (this=0x1337160, e=<optimized out>) at kernel/qobject.cpp:1239
#24 0x00007f0f9405b69c in QApplicationPrivate::notify_helper (this=this@entry=0x131ef20, receiver=receiver@entry=0x1337160, e=e@entry=0x7f0f78003fc0) at kernel/qapplication.cpp:3716
#25 0x00007f0f94060b10 in QApplication::notify (this=0x12c6290, receiver=0x1337160, e=0x7f0f78003fc0) at kernel/qapplication.cpp:3499
#26 0x00007f0f9553165d in QCoreApplication::notifyInternal (this=0x12c6290, receiver=0x1337160, event=event@entry=0x7f0f78003fc0) at kernel/qcoreapplication.cpp:965
#27 0x00007f0f95534423 in QCoreApplication::sendEvent (event=0x7f0f78003fc0, receiver=<optimized out>) at kernel/qcoreapplication.h:224
#28 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1252930) at kernel/qcoreapplication.cpp:1593
#29 0x00007f0f955349e8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451
#30 0x00007f0f9557efb3 in postEventSourceDispatch (s=0x136d4b0) at kernel/qeventdispatcher_glib.cpp:271
#31 0x00007f0f920ae8ed in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#32 0x00007f0f920aebd0 in ?? () from /usr/lib64/libglib-2.0.so.0
#33 0x00007f0f920aec7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#34 0x00007f0f9557f027 in QEventDispatcherGlib::processEvents (this=0x136d530, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#35 0x00007f0f9553027a in QEventLoop::exec (this=this@entry=0x7ffdc12c20c0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#36 0x00007f0f9553764c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229
#37 0x00007f0f83950b69 in kdemain () from /usr/lib64/libkdeinit5_ksmserver.so
#38 0x0000000000408540 in ?? ()
#39 0x0000000000409d79 in ?? ()
#40 0x000000000040a320 in ?? ()
#41 0x0000000000405044 in main ()

Reproducible: Always
Comment 1 Andreas Sturmlechner 2015-12-24 12:01:05 UTC
Since upgrade to plasma-5.5.1, same for 5.5.2, this same crash is now happening all the time after unlocking from screen standby. It is happening on a ThinkPad with dockingstation, lid closed, and a Displayport-connected external screen.
Comment 2 Andreas Sturmlechner 2015-12-24 15:18:50 UTC
Created attachment 96291 [details]
ksmserver-20151224-151328.kcrash

...and here's my backtrace. Reproducible each time by just switching off and on the external DP screen while kscreenlocker is active. Can't reproduce it with LVDS only (no external screen attached).
Comment 3 Kelvie Wong 2015-12-30 20:50:25 UTC
Created attachment 96370 [details]
Stacktrace with ScreenLocker entry

I have this problem as well -- I use nightly build PPAs; this happens with almost exactly the same setup

External monitor (I typically set my desktop to only display on the external display) over displayport.

Trivially reproducable (on a Dell laptop) by locking the screen whilst using the external display, and turning off the external monitor (which is the primary desktop).

Attaching a stacktrace as well.
Comment 4 Kelvie Wong 2015-12-30 20:51:20 UTC
This is on qt 5.5.1, and kde 5.17 (built on the 27th of dec, from the ubuntu unstable ci ppa)
Comment 5 David Menday 2016-04-18 11:51:32 UTC
Created attachment 98443 [details]
stack trace segmentation fault

Currently I cannot keep plasma working for more than one day.
My suspicion is that the Monitor/Display gets powered down after a work day being unused.
Then when I turn the monitor on again something is different from just turning the monitor off and on again (which ksmserver survives).

Gentoo,  kde-plasma/plasma-meta-5.5.5
Comment 6 Marco Leise 2016-04-21 18:35:26 UTC
Same here. ksmserver crash on Gentoo amd64 with Qt 5.5.1 and Plasma 5.6.2. Is this the same bug as the other crashes when plugging/unplugging monitors that was supposedly fixed in Qt 5.5.x or a KDE issue?
Comment 7 Andrew Crouthamel 2018-11-01 13:40:38 UTC
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!
Comment 8 Bug Janitor Service 2018-11-16 11:35:42 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2018-12-01 03:49:49 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!