Bug 439672 - KDE System Settings crashes under Wayland on changing Task Switcher
Summary: KDE System Settings crashes under Wayland on changing Task Switcher
Status: RESOLVED DUPLICATE of bug 414834
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-07-09 11:06 UTC by Uday
Modified: 2021-08-03 17:58 UTC (History)
2 users (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 Uday 2021-07-09 11:06:41 UTC
Application: systemsettings5 (5.22.2)

Qt Version: 5.15.2
Frameworks Version: 5.83.0
Operating System: Linux 5.12.14-300.fc34.x86_64 x86_64
Windowing System: Wayland
Drkonqi Version: 5.22.2
Distribution: Fedora 34 (Workstation Edition)

-- Information about the crash:
- What I was doing when the application crashed:
Recently upgraded my system from Fedora 33 to Fedora 34. 
In KDE Desktop Environment (Wayland), when I open System Settings ->  Window Management -> Task Switcher and try changing the Task Switcher the app crashes.
Even after I tried installing a new task switcher "Scaling" and changed my current task switcher to "Scaling", the crash still occurs.

The crash can be reproduced every time.

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

[KCrash Handler]
#4  0x00007fc2d64caf34 in QWaylandClientExtensionPrivate::handleRegistryGlobal(void*, wl_registry*, unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5
#5  0x00007fc2d64b7419 in QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5
#6  0x00007fc2d64d37c3 in QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) () from /lib64/libQt5WaylandClient.so.5
#7  0x00007fc2d3e35c04 in ffi_call_unix64 () from /lib64/libffi.so.6
#8  0x00007fc2d3e35107 in ffi_call () from /lib64/libffi.so.6
#9  0x00007fc2d6424d10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0
#10 0x00007fc2d642542b in dispatch_event.isra () from /lib64/libwayland-client.so.0
#11 0x00007fc2d642561c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0
#12 0x00007fc2d64af7a3 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5
#13 0x00007fc2d8ac4ce0 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#14 0x00007fc2d8ac743a in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5
#15 0x00007fc2d8ac7c53 in QSocketNotifier::event(QEvent*) () from /lib64/libQt5Core.so.5
#16 0x00007fc2d965d423 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#17 0x00007fc2d8a91098 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#18 0x00007fc2d8ae311f in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#19 0x00007fc2d681a4cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#20 0x00007fc2d686e4e8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0
#21 0x00007fc2d6817c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#22 0x00007fc2d8ae2698 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#23 0x00007fc2d8a8fab2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#24 0x00007fc2d8a97fe4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#25 0x000056519d93958c in main ()
[Inferior 1 (process 7405) detached]

Reported using DrKonqi
Comment 1 David Edmundson 2021-07-09 11:12:37 UTC

*** This bug has been marked as a duplicate of bug 439670 ***
Comment 2 Nate Graham 2021-08-03 17:58:38 UTC

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