Bug 464539 - Kwin suddenly crash
Summary: Kwin suddenly crash
Status: RESOLVED DUPLICATE of bug 438315
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.26.4
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-01-20 07:29 UTC by Seppri
Modified: 2023-01-20 11:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Seppri 2023-01-20 07:29:26 UTC
Application: kwin_x11 (5.26.4)

Qt Version: 5.15.7
Frameworks Version: 5.101.0
Operating System: Linux 6.1.0-2.1-liquorix-amd64 x86_64
Windowing System: X11
Distribution: Nitrux 2.6.0 build.010123.ff
DrKonqi: 5.26.4 [KCrashBackend]

-- Information about the crash:
Kwin suddenly crash after closing file manager named Index, and sometimes, on some software it still crashes. however, not too bad. I can still do activities as usual

Translate this page

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f3dc591c209 in KWin::FocusChain::isUsableFocusCandidate (prev=0x555cedb29d20, c=0x555cedb2a810, this=0x555cec967310) at ./src/focuschain.cpp:193
#5  KWin::FocusChain::nextForDesktop (desktop=0x555ceca7e370, reference=0x555cedb29d20, this=0x555cec967310) at ./src/focuschain.cpp:205
#6  KWin::Workspace::activateNextWindow (this=0x555cec9ab1b0, window=<optimized out>) at ./src/activation.cpp:506
#7  0x00007f3dc5a6dd20 in KWin::X11Window::destroyWindow (this=0x555cedb29d20) at ./src/workspace.h:887
#8  0x00007f3dc5974042 in KWin::X11Window::unmapNotifyEvent (e=<optimized out>, this=0x555cedb29d20) at ./src/events.cpp:585
#9  KWin::X11Window::unmapNotifyEvent (this=0x555cedb29d20, e=<optimized out>) at ./src/events.cpp:561
#10 0x00007f3dc5976f8b in KWin::X11Window::windowEvent (this=0x555cedb29d20, e=e@entry=0x7f3db0013320) at ./src/events.cpp:403
#11 0x00007f3dc5978340 in KWin::Workspace::workspaceEvent (this=0x555cec9ab1b0, e=0x7f3db0013320) at ./src/events.cpp:159
#12 0x00007f3dc4074467 in QAbstractEventDispatcher::filterNativeEvent (this=<optimized out>, eventType=..., message=message@entry=0x7f3db0013320, result=result@entry=0x7ffe4307ddb8) at kernel/qabstracteventdispatcher.cpp:495
#13 0x00007f3dbe497595 in QXcbConnection::handleXcbEvent (this=this@entry=0x555cec68ce90, event=event@entry=0x7f3db0013320) at ./src/plugins/platforms/xcb/qxcbconnection.cpp:579
#14 0x00007f3dbe498cd6 in QXcbConnection::processXcbEvents (this=0x555cec68ce90, flags=...) at ./src/plugins/platforms/xcb/qxcbconnection.cpp:1065
#15 0x00007f3dbe4bfc87 in xcbSourceDispatch (source=<optimized out>) at ./src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:103
#16 0x00007f3dc15be7a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f3dc15bea38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f3dc15beacc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f3dc40d0af8 in QEventDispatcherGlib::processEvents (this=0x555cec7564a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#20 0x00007f3dc40759bb in QEventLoop::exec (this=this@entry=0x7ffe4307e040, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#21 0x00007f3dc407df54 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#22 0x00007f3dc44554e0 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1870
#23 0x00007f3dc33996d9 in QApplication::exec () at kernel/qapplication.cpp:2829
#24 0x0000555ceae7677b in main (argc=<optimized out>, argv=<optimized out>) at ./src/main_x11.cpp:407
[Inferior 1 (process 4612) detached]

The reporter indicates this bug may be a duplicate of or related to bug 451693, bug 463961, bug 452785, bug 400394, bug 449762, bug 463434.

Reported using DrKonqi
Comment 1 Nicolas Fella 2023-01-20 11:53:07 UTC
*** This bug has been marked as a duplicate of bug 438315 ***