Bug 466100 - Kwin crash
Summary: Kwin crash
Status: RESOLVED DUPLICATE of bug 438315
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.26.4
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-02-19 18:54 UTC by samuelshorvath17
Modified: 2023-02-19 22:47 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 samuelshorvath17 2023-02-19 18:54:00 UTC
Application: kwin_x11 (5.26.4)
 (Compiled from sources)
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:
After I turn of station, KWin crashed. I was just trying to download discord but nothing

The crash does not seem to be reproducible.

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

[KCrash Handler]
#4  0x0000000000000000 in ?? ()
#5  0x00007f343c26620f in KWin::FocusChain::isUsableFocusCandidate (prev=0x55ed44e07fd0, c=0x55ed44da89f0, this=0x55ed43b1c0a0) at ./src/focuschain.cpp:193
#6  KWin::FocusChain::nextForDesktop (desktop=0x55ed43bd5fb0, reference=0x55ed44e07fd0, this=0x55ed43b1c0a0) at ./src/focuschain.cpp:205
#7  KWin::Workspace::activateNextWindow (this=0x55ed43ad1280, window=<optimized out>) at ./src/activation.cpp:506
#8  0x00007f343c3b7d20 in KWin::X11Window::destroyWindow (this=0x55ed44e07fd0) at ./src/workspace.h:887
#9  0x00007f343c2be042 in KWin::X11Window::unmapNotifyEvent (e=<optimized out>, this=0x55ed44e07fd0) at ./src/events.cpp:585
#10 KWin::X11Window::unmapNotifyEvent (this=0x55ed44e07fd0, e=<optimized out>) at ./src/events.cpp:561
#11 0x00007f343c2c0f8b in KWin::X11Window::windowEvent (this=0x55ed44e07fd0, e=e@entry=0x7f342801e5c0) at ./src/events.cpp:403
#12 0x00007f343c2c2340 in KWin::Workspace::workspaceEvent (this=0x55ed43ad1280, e=0x7f342801e5c0) at ./src/events.cpp:159
#13 0x00007f343aa74467 in QAbstractEventDispatcher::filterNativeEvent (this=<optimized out>, eventType=..., message=message@entry=0x7f342801e5c0, result=result@entry=0x7fffb85abb98) at kernel/qabstracteventdispatcher.cpp:495
#14 0x00007f3434b69595 in QXcbConnection::handleXcbEvent (this=this@entry=0x55ed437bae90, event=event@entry=0x7f342801e5c0) at ./src/plugins/platforms/xcb/qxcbconnection.cpp:579
#15 0x00007f3434b6acd6 in QXcbConnection::processXcbEvents (this=0x55ed437bae90, flags=...) at ./src/plugins/platforms/xcb/qxcbconnection.cpp:1065
#16 0x00007f3434b91c87 in xcbSourceDispatch (source=<optimized out>) at ./src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:103
#17 0x00007f3437f157a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f3437f15a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f3437f15acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f343aad0af8 in QEventDispatcherGlib::processEvents (this=0x55ed438e74a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#21 0x00007f343aa759bb in QEventLoop::exec (this=this@entry=0x7fffb85abe20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#22 0x00007f343aa7df54 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#23 0x00007f343ae554e0 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1870
#24 0x00007f3439cd66d9 in QApplication::exec () at kernel/qapplication.cpp:2829
#25 0x000055ed429b977b in main (argc=<optimized out>, argv=<optimized out>) at ./src/main_x11.cpp:407
[Inferior 1 (process 4395) detached]

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

Reported using DrKonqi
Comment 1 David Edmundson 2023-02-19 22:47:57 UTC

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