Bug 433098

Summary: Segmentation fault when fiddling with compositor settings.
Product: [Plasma] kwin Reporter: Andy Great <andythe_great>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: nate
Priority: NOR    
Version: 5.21.0   
Target Milestone: ---   
Platform: Other   
OS: Other   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: crash information

Description Andy Great 2021-02-17 17:57:07 UTC
Created attachment 135777 [details]
crash information

SUMMARY
I login to full wayland session on openSUSE Tumbleweed KDE with latest update. I was changing the Latency setting, when I press apply it crash. I could not reproduce it but I got the crash information. I hope it is useful in some way.

Operating System: openSUSE Tumbleweed 20210215
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.16-1-default
OS Type: 64-bit
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4000
Comment 1 Nate Graham 2021-02-17 19:10:33 UTC
Application: System Settings (systemsettings5), signal: Segmentation fault

[KCrash Handler]
#4  0x000055e525e9e140 in ?? ()
#5  0x00007faa1765b893 in QWaylandClientExtensionPrivate::handleRegistryGlobal (data=0x55e525c6a860, registry=0x55e5195961d0, id=51, interface=..., version=1) at global/qwaylandclientextension.cpp:67
#6  0x00007faa176444b2 in QtWaylandClient::QWaylandDisplay::registry_global (this=<optimized out>, id=51, interface=..., version=1) at qwaylanddisplay.cpp:396
#7  0x00007faa17664c56 in QtWayland::wl_registry::handle_global (data=0x55e5195920c0, object=<optimized out>, name=51, interface=0x55e51a0a1d60 "org_kde_kwin_blur_manager", version=1) at qwayland-wayland.cpp:94
#8  0x00007faa16c6c42d in ffi_call_unix64 () at ../src/x86/unix64.S:106
#9  0x00007faa16c684f9 in ffi_call_int (cif=<optimized out>, fn=<optimized out>, rvalue=<optimized out>, avalue=<optimized out>, closure=<optimized out>) at ../src/x86/ffi64.c:669
#10 0x00007faa175ba8fe in wl_closure_invoke (closure=closure@entry=0x55e51a0a1c80, target=<optimized out>, target@entry=0x55e5195961d0, opcode=opcode@entry=0, data=<optimized out>, flags=<optimized out>) at src/connection.c:1018
#11 0x00007faa175bafcb in dispatch_event (display=0x55e519596080, queue=<optimized out>, queue=<optimized out>) at src/wayland-client.c:1452
#12 0x00007faa175bb19c in dispatch_queue (queue=0x55e519596150, display=0x55e519596080) at src/wayland-client.c:1598
#13 wl_display_dispatch_queue_pending (display=0x55e519596080, queue=0x55e519596150) at src/wayland-client.c:1840
#14 0x00007faa175bb1ec in wl_display_dispatch_pending (display=<optimized out>) at src/wayland-client.c:1903
#15 0x00007faa17643c2b in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55e5195920b0) at qwaylanddisplay.cpp:221
#16 0x00007faa19baa980 in doActivate<false> (sender=0x55e5195d3e00, signal_index=4, argv=0x7ffebb18eaa0, argv@entry=0x0) at kernel/qobject.cpp:3898
#17 0x00007faa19ba3c60 in QMetaObject::activate (sender=sender@entry=0x55e5195d3e00, m=m@entry=0x7faa19e580e0 <QAbstractEventDispatcher::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946
#18 0x00007faa19b70ec3 in QAbstractEventDispatcher::awake (this=this@entry=0x55e5195d3e00) at .moc/moc_qabstracteventdispatcher.cpp:149
#19 0x00007faa19bcb8fc in QEventDispatcherGlib::processEvents (this=0x55e5195d3e00, flags=...) at kernel/qeventdispatcher_glib.cpp:430
#20 0x00007faa19b72ceb in QEventLoop::exec (this=this@entry=0x7ffebb18ebc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#21 0x00007faa19b7af60 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#22 0x000055e5182464da in main (argc=<optimized out>, argv=0x7ffebb18ece0) at /usr/src/debug/systemsettings5-5.21.0-1.1.x86_64/app/main.cpp:222
[Inferior 1 (process 12213) detached]
Comment 2 Nate Graham 2021-02-23 06:05:31 UTC

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