Bug 439199 - System settings crashed when changing number of workspaces under wayland
Summary: System settings crashed when changing number of workspaces under wayland
Status: RESOLVED DUPLICATE of bug 437455
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.22.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-06-27 03:09 UTC by Sebastian Hörberg
Modified: 2021-06-27 22:13 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 Sebastian Hörberg 2021-06-27 03:09:51 UTC
Application: systemsettings5 (5.22.2)

Qt Version: 5.15.2
Frameworks Version: 5.83.0
Operating System: Linux 5.12.12-301.fsync.fc34.x86_64 x86_64
Windowing System: Wayland
Drkonqi Version: 5.22.2
Distribution: Fedora 34 (KDE Plasma)

-- Information about the crash:
- What I was doing when the application crashed:
Changing the number of workspaces from 1 to 4 or back again and hitting 'Apply' crashes System Settings and seem to restart the Plasma shell. However the setting gets properly updated as I can see and use the requested number of workspaces.

This crash seems to happen every time.

Tried to change:
- From single to 2 rows of 2
- From 2 rows of 2 back to single
- From single to 3 over 2 rows
- From 3 over 2 rows back to single

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f989ecd6f34 in QWaylandClientExtensionPrivate::handleRegistryGlobal(void*, wl_registry*, unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5
#5  0x00007f989ecc3419 in QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5
#6  0x00007f989ecdf7c3 in QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) () from /lib64/libQt5WaylandClient.so.5
#7  0x00007f989c642c04 in ffi_call_unix64 () from /lib64/libffi.so.6
#8  0x00007f989c642107 in ffi_call () from /lib64/libffi.so.6
#9  0x00007f989ec30d10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0
#10 0x00007f989ec3142b in dispatch_event.isra () from /lib64/libwayland-client.so.0
#11 0x00007f989ec3161c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0
#12 0x00007f989ecbb7a3 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5
#13 0x00007f98a126f4fd in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#14 0x00007f98a1271b3a in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5
#15 0x00007f98a12722d4 in QSocketNotifier::event(QEvent*) () from /lib64/libQt5Core.so.5
#16 0x00007f98a1dcae73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#17 0x00007f98a123ef48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#18 0x00007f98a128c17f in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#19 0x00007f989f0264cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#20 0x00007f989f07a4e8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0
#21 0x00007f989f023c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#22 0x00007f98a128b6f8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#23 0x00007f98a123d9b2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#24 0x00007f98a1245544 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#25 0x000055fd3a0ed58c in main ()
[Inferior 1 (process 191022) detached]

Reported using DrKonqi
Comment 1 David Edmundson 2021-06-27 22:13:43 UTC

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