Bug 389303 - Wayland - session crashes when enable AND move output in KScreen
Summary: Wayland - session crashes when enable AND move output in KScreen
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.11.95
Platform: Neon Linux
: NOR crash
Target Milestone: 1.0
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-22 04:03 UTC by Kamil Piwowarski
Modified: 2020-12-29 04:34 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
mgraesslin: Wayland+
mgraesslin: X11-


Attachments
Screenshot - disabled output (979.11 KB, image/png)
2018-01-22 04:05 UTC, Kamil Piwowarski
Details
Screenshot - before click Apply (979.76 KB, image/png)
2018-01-22 04:06 UTC, Kamil Piwowarski
Details
plasmashell-20180131-004131.kcrash.txt (14.50 KB, text/plain)
2018-01-30 23:54 UTC, Kamil Piwowarski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kamil Piwowarski 2018-01-22 04:03:33 UTC
Tested using neon-devedition-gitunstable-20180121-0806-amd64.iso

1. Open KScreen and disable one output.
2. Apply
3. Enable output and place it where you want (if you dont't place and only enable it works)
4. Apply
5. All outputs are working for ~1 sec and then whole session crashes
Comment 1 Kamil Piwowarski 2018-01-22 04:05:29 UTC
Created attachment 110038 [details]
Screenshot - disabled output
Comment 2 Kamil Piwowarski 2018-01-22 04:06:40 UTC
Created attachment 110039 [details]
Screenshot - before click Apply
Comment 3 Martin Flöser 2018-01-24 18:39:01 UTC
I just tried to reproduce, but failed.

Could you please try attaching gdb to kwin in order to get a backtrace?
Comment 4 Kamil Piwowarski 2018-01-30 23:53:41 UTC
I am sorry for misleading, this is not kwin fail but plasmashell. Sometimes additionaly kdeinit, policykit-kde-agent-1 and some other services crashes.
Comment 5 Kamil Piwowarski 2018-01-30 23:54:02 UTC
Created attachment 110244 [details]
plasmashell-20180131-004131.kcrash.txt
Comment 6 David Edmundson 2018-01-30 23:57:19 UTC
Please state Qt version
Comment 7 Kamil Piwowarski 2018-01-31 00:04:26 UTC
Qt 5.9.3 (running fresh installed neon-devedition-gitstable-20180130-0526-amd64)
Comment 8 Marco Martin 2018-02-02 10:53:44 UTC
pasting backtrace inline
may even be something in qtwayland as the crash is into qscreen internals?

Thread 1 (Thread 0x7fa2d9ff48c0 (LWP 3424)):
[KCrash Handler]
#6  QScreen::availableGeometry (this=0x0) at kernel/qscreen.cpp:391
#7  0x00007fa2d482167c in QScreen::availableVirtualGeometry (this=this@entry=0x1220f20) at kernel/qscreen.cpp:476
#8  0x00007fa2d7c20d65 in QQuickScreenInfo::setWrappedScreen (this=this@entry=0x1993970, screen=0x120fe40) at items/qquickscreen.cpp:342
#9  0x00007fa2d7c212e5 in QQuickScreenAttached::screenChanged (this=0x1993970, screen=<optimized out>) at items/qquickscreen.cpp:439
#10 0x00007fa2d3fa8279 in QMetaObject::activate (sender=sender@entry=0x14fc990, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe2bbd1690) at kernel/qobject.cpp:3766
#11 0x00007fa2d3fa8b87 in QMetaObject::activate (sender=sender@entry=0x14fc990, m=m@entry=0x7fa2d4dfc440 <QWindow::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe2bbd1690) at kernel/qobject.cpp:3628
#12 0x00007fa2d47fab9f in QWindow::screenChanged (this=this@entry=0x14fc990, _t1=_t1@entry=0x120fe40) at .moc/moc_qwindow.cpp:658
#13 0x00007fa2d47fb343 in QWindowPrivate::emitScreenChangedRecursion (this=this@entry=0x159c5e0, newScreen=newScreen@entry=0x120fe40) at kernel/qwindow.cpp:400
#14 0x00007fa2d48029ae in QWindowPrivate::setTopLevelScreen (this=0x159c5e0, newScreen=0x120fe40, recreate=recreate@entry=false) at kernel/qwindow.cpp:424
#15 0x00007fa2d47f3b79 in QGuiApplicationPrivate::processWindowScreenChangedEvent (wse=0x19d00f0) at kernel/qguiapplication.cpp:2203
#16 0x00007fa2d47f8805 in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x19d00f0) at kernel/qguiapplication.cpp:1760
#17 0x00007fa2d47d281b in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:939
#18 0x00007fa2c5685570 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#19 0x00007fa2ce56d197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fa2ce56d3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fa2ce56d49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007fa2d3fd16af in QEventDispatcherGlib::processEvents (this=0x127e490, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#23 0x00007fa2c564eb94 in QtWaylandClient::QWaylandDisplay::forceRoundTrip (this=this@entry=0x12031e0) at qwaylanddisplay.cpp:364
#24 0x00007fa2c564f3ee in QtWaylandClient::QWaylandDisplay::registry_global (this=0x12031e0, id=37, interface=..., version=2) at qwaylanddisplay.cpp:251
#25 0x00007fa2c567447e in QtWayland::wl_registry::handle_global (data=0x12031f0, object=<optimized out>, name=37, interface=0x7fa218081500 "wl_output", version=2) at qwayland-wayland.cpp:74
#26 0x00007fa2ce118e40 in ffi_call_unix64 () at ../src/x86/unix64.S:76
#27 0x00007fa2ce1188ab in ffi_call (cif=cif@entry=0x7ffe2bbd1c50, fn=<optimized out>, rvalue=rvalue@entry=0x0, avalue=avalue@entry=0x7ffe2bbd1d20) at ../src/x86/ffi64.c:525
#28 0x00007fa2d28059de in wl_closure_invoke (closure=closure@entry=0x7fa218081420, flags=flags@entry=1, target=target@entry=0x11ff980, opcode=opcode@entry=0, data=0x12031f0) at ../src/connection.c:935
#29 0x00007fa2d2802650 in dispatch_event (display=display@entry=0x11f12d0, queue=0x11f1398) at ../src/wayland-client.c:1310
#30 0x00007fa2d28038ac in dispatch_queue (queue=0x11f1398, display=0x11f12d0) at ../src/wayland-client.c:1456
#31 wl_display_dispatch_queue_pending (display=0x11f12d0, queue=0x11f1398) at ../src/wayland-client.c:1698
#32 0x00007fa2d28038fc in wl_display_dispatch_pending (display=<optimized out>) at ../src/wayland-client.c:1761
#33 0x00007fa2c564e962 in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x12031e0) at qwaylanddisplay.cpp:190
#34 0x00007fa2d3fa8279 in QMetaObject::activate (sender=sender@entry=0x127e490, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3766
#35 0x00007fa2d3fa8b87 in QMetaObject::activate (sender=sender@entry=0x127e490, m=m@entry=0x7fa2d4432420 <QAbstractEventDispatcher::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3628
#36 0x00007fa2d3f78173 in QAbstractEventDispatcher::awake (this=this@entry=0x127e490) at .moc/moc_qabstracteventdispatcher.cpp:144
#37 0x00007fa2d3fd16ee in QEventDispatcherGlib::processEvents (this=0x127e490, flags=...) at kernel/qeventdispatcher_glib.cpp:430
#38 0x00007fa2d3f79e2a in QEventLoop::exec (this=this@entry=0x7ffe2bbd2080, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#39 0x00007fa2d3f82d64 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1291
#40 0x000000000041cd99 in main (argc=1, argv=<optimized out>) at /workspace/build/shell/main.cpp:166
Comment 9 Justin Zobel 2020-11-29 21:09:12 UTC
Thanks for the report, Kamil.

I've been using Wayland on my laptop and have an external monitor connected. I've not experienced these crashes.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 10 Bug Janitor Service 2020-12-14 04:33:58 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 11 Bug Janitor Service 2020-12-29 04:34:31 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!