Bug 439249 - Crash in settings application when applying change to window decorations
Summary: Crash in settings application when applying change to window decorations
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-28 03:19 UTC by Thomas Faber
Modified: 2021-06-28 17:09 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 Thomas Faber 2021-06-28 03:19:07 UTC
Application: systemsettings5 (5.22.2)

Qt Version: 5.15.2
Frameworks Version: 5.83.0
Operating System: Linux 5.12.12-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:

Changed the Window Decorations theme from Breeze to Plastik, then clicked Apply. It looks like the change was correctly applied, though.
I just tried changing back to Breeze and it resulted in another crash. So this seems to be reproducible; however it does not happen every time.

I encountered a similar crash earlier after modifying and applying a change to the "Show selected window" setting under Window Management -> Task Switcher. This one does not seem to reproduce.

The crash can be reproduced sometimes.

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

[KCrash Handler]
#4  0x00007fe3ac455f34 in QWaylandClientExtensionPrivate::handleRegistryGlobal(void*, wl_registry*, unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5
#5  0x00007fe3ac442419 in QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5
#6  0x00007fe3ac45e7c3 in QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) () from /lib64/libQt5WaylandClient.so.5
#7  0x00007fe3a9dc1c04 in ffi_call_unix64 () from /lib64/libffi.so.6
#8  0x00007fe3a9dc1107 in ffi_call () from /lib64/libffi.so.6
#9  0x00007fe3ac3afd10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0
#10 0x00007fe3ac3b042b in dispatch_event.isra () from /lib64/libwayland-client.so.0
#11 0x00007fe3ac3b061c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0
#12 0x00007fe3ac43a7a3 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5
#13 0x00007fe3ae9ee4fd in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#14 0x00007fe3ae9f0b3a in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5
#15 0x00007fe3ae9f12d4 in QSocketNotifier::event(QEvent*) () from /lib64/libQt5Core.so.5
#16 0x00007fe3af549e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#17 0x00007fe3ae9bdf48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#18 0x00007fe3aea0b17f in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#19 0x00007fe3ac7a54cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#20 0x00007fe3ac7f94e8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0
#21 0x00007fe3ac7a2c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#22 0x00007fe3aea0a6f8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#23 0x00007fe3ae9bc9b2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#24 0x00007fe3ae9c4544 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#25 0x00005622ef3ad58c in main ()
[Inferior 1 (process 6295) detached]

Reported using DrKonqi
Comment 1 David Edmundson 2021-06-28 17:09:53 UTC

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