Bug 433036 - [Wayland] Crash when configuring Window/Application settings while in the "Workspace Behaviour" or "Window Management" sections
Summary: [Wayland] Crash when configuring Window/Application settings while in the "Wo...
Status: RESOLVED DUPLICATE of bug 435009
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2021-02-16 23:16 UTC by magiblot
Modified: 2021-04-05 15:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description magiblot 2021-02-16 23:16:21 UTC
SUMMARY

Please consider the following screen recording. In it, I open KWin's Window/Application-specific settings dialog twice and nothing strange happens. But when I do the same in the "Desktop Effects" section, systemsettings5 crashes.

https://drive.google.com/file/d/1axOpD-Q5ItrAu8VYLVxbIe9kmYs45y8i/view

STEPS TO REPRODUCE
1. Run systemsettings5 as a Wayland client in a Plasma Wayland session.
2. Go to the "Workspace Behaviour" or "Window Management" sections.
3. In the title bar, open "More Actions" > "Configure Special Window Settings".
4. Close the dialog by pressing "OK".
5. Repeat from step 3 until systemsettings5 crashes.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.20.90
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.16-arch1-1
OS Type: 64-bit

ADDITIONAL INFORMATION

I don't have Qt debug symbols around so I won't share a backtrace, but I presume you won't have much trouble reproducing this. Please let me know if that's not the case.

I am reproducing on 5.20.90, but I've heard from another user that this can also be reproduced on 5.19.

Thank you.
Comment 1 Nate Graham 2021-03-04 18:50:22 UTC
Cannot reproduce. I tried it 10 times and got no crash. If you can reproduce it consistently, we will need a backtrace with debug symbols. :)
Comment 2 magiblot 2021-03-06 00:29:22 UTC
I can still reproduce in Plasma 5.21.2, from the "Desktop Effects" view as in the screen recording in the first message.

> #0  0x0000000000000000 in ?? ()
> #1  0x00007efd1c8ab683 in QWaylandClientExtensionPrivate::handleRegistryGlobal (data=0x55919ee2c9a0, registry=0x55919d55f660, id=43, interface=..., version=1) at /usr/src/debug/qtwayland-everywhere-src-5.15.2/src/client/global/qwaylandclientextension.cpp:67
> #2  0x00007efd1c893b32 in QtWaylandClient::QWaylandDisplay::registry_global (this=<optimized out>, id=43, interface=..., version=1) at /usr/src/debug/qtwayland-everywhere-src-5.15.2/src/client/qwaylanddisplay.cpp:396
> #3  0x00007efd1c8b4dee in QtWayland::wl_registry::handle_global (data=0x55919d563300, object=<optimized out>, name=43, interface=0x55919f0be8e0 "org_kde_kwin_slide_manager", version=1) at qwayland-wayland.cpp:94
> #4  0x00007efd1a386acd in ?? () from /usr/lib/libffi.so.7
> #5  0x00007efd1a38603a in ?? () from /usr/lib/libffi.so.7
> #6  0x00007efd1c819fe4 in wl_closure_invoke (closure=0x55919f0be800, flags=1, target=<optimized out>, opcode=0, data=<optimized out>) at ../wayland-1.19.0/src/connection.c:1018
> #7  0x00007efd1c816563 in dispatch_event (display=display@entry=0x55919d563830, queue=<optimized out>, queue=<optimized out>) at ../wayland-1.19.0/src/wayland-client.c:1452
> #8  0x00007efd1c817cac in dispatch_queue (queue=0x55919d563900, display=0x55919d563830) at ../wayland-1.19.0/src/wayland-client.c:1598
> #9  wl_display_dispatch_queue_pending (display=0x55919d563830, queue=0x55919d563900) at ../wayland-1.19.0/src/wayland-client.c:1840
> #10 0x00007efd1c817d0d in wl_display_dispatch_pending (display=<optimized out>) at ../wayland-1.19.0/src/wayland-client.c:1903
> #11 0x00007efd1c89344d in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55919d5632f0) at /usr/src/debug/qtwayland-everywhere-src-5.15.2/src/client/qwaylanddisplay.cpp:221
> #12 0x00007efd1ed10dc0 in doActivate<false> (sender=0x55919d589ca0, signal_index=3, argv=argv@entry=0x7ffd3ee085c0) at kernel/qobject.cpp:3898
> #13 0x00007efd1ed09f20 in QMetaObject::activate (sender=sender@entry=0x55919d589ca0, m=m@entry=0x7efd1ef717a0 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd3ee085c0) at kernel/qobject.cpp:3946
> #14 0x00007efd1ed142f0 in QSocketNotifier::activated (this=this@entry=0x55919d589ca0, _t1=..., _t2=<optimized out>, _t3=...) at .moc/moc_qsocketnotifier.cpp:178
> #15 0x00007efd1ed14afd in QSocketNotifier::event (this=0x55919d589ca0, e=0x7ffd3ee086d0) at kernel/qsocketnotifier.cpp:302
> #16 0x00007efd1f89c752 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55919d589ca0, e=0x7ffd3ee086d0) at kernel/qapplication.cpp:3632
> #17 0x00007efd1ecd9a2a in QCoreApplication::notifyInternal2 (receiver=0x55919d589ca0, event=0x7ffd3ee086d0) at kernel/qcoreapplication.cpp:1063
> #18 0x00007efd1ed332a6 in socketNotifierSourceDispatch (source=0x55919d5aae00) at kernel/qeventdispatcher_glib.cpp:107
> #19 0x00007efd1c9a5b84 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
> #20 0x00007efd1c9f9c21 in ?? () from /usr/lib/libglib-2.0.so.0
> #21 0x00007efd1c9a43b1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
> #22 0x00007efd1ed32691 in QEventDispatcherGlib::processEvents (this=0x55919d579640, flags=...) at kernel/qeventdispatcher_glib.cpp:423
> #23 0x00007efd1ecd83ac in QEventLoop::exec (this=this@entry=0x7ffd3ee08930, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
> #24 0x00007efd1ece0844 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
> #25 0x00007efd1f1a184e in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867
> #26 0x00007efd1f89c6c6 in QApplication::exec () at kernel/qapplication.cpp:2824
> #27 0x000055919bbec960 in main (argc=<optimized out>, argv=0x7ffd3ee08a60) at /usr/src/debug/systemsettings-5.21.2/app/main.cpp:222

> (gdb) frame 1
> #1  0x00007fd59ca70683 in QWaylandClientExtensionPrivate::handleRegistryGlobal (data=0x55c040570740, registry=0x55c03edff660, id=44, interface=..., version=1) at /usr/src/debug/qtwayland-everywhere-src-5.15.2/src/client/global/qwaylandclientextension.cpp:67
> 67	    if (interface == QLatin1String(extension->extensionInterface()->name) && !extension->d_func()->active) {
> (gdb) print *extension
> $1 = {<QObject> = {_vptr.QObject = 0x55919d553f50, static staticMetaObject = {d = {superdata = {direct = 0x0}, stringdata = 0x7efd1eea5720 <qt_meta_stringdata_QObject>, data = 0x7efd1eea5600 <qt_meta_data_QObject>, static_metacall = 0x7efd1ed0f4d0 <QObject::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)>, relatedMetaObjects = 0x0, extradata = 0x0}}, d_ptr = {d = 0x55919f062d20}, static staticQtMetaObject = {d = {superdata = {direct = 0x0}, stringdata = 0x7efd1eea86c0 <qt_meta_stringdata_Qt>, data = 0x7efd1eea5840 <qt_meta_data_Qt>, static_metacall = 0x0, relatedMetaObjects = 0x0, extradata = 0x0}}}, static staticMetaObject = {d = {superdata = {direct = 0x7efd1ef68740 <QObject::staticMetaObject>}, stringdata = 0x7efd1c910880 <qt_meta_stringdata_QWaylandClientExtension>, data = 0x7efd1c9107c0 <qt_meta_data_QWaylandClientExtension>, static_metacall = 0x7efd1c8b8d20 <QWaylandClientExtension::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)>, relatedMetaObjects = 0x0, extradata = 0x0}}}

The string stored in the 'interface' variable is "org_kde_kwin_slide_manager".

For some reason, I am unable to reproduce the crash when running systemsettings5 under Valgrind.

Sometimes, the issue appears to be unreproducible. Exiting and entering the Plasma Wayland session makes it reproducible again.
Comment 3 Bug Janitor Service 2021-03-21 04:33:48 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 4 Bug Janitor Service 2021-04-05 04:33:39 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!
Comment 5 magiblot 2021-04-05 08:39:38 UTC
Reopening because I provided the requested info, but we forgot to remove the NEEDSINFO status.
Comment 6 Nate Graham 2021-04-05 15:14:07 UTC
Ah, this is the same as Bug 435009. Duping to that despite being newer since there's already some investigation going on in there. If yo can still reproduce it as of today's git master, please feel free to join in the conversation over there. Thanks!

*** This bug has been marked as a duplicate of bug 435009 ***