https://bugs.kde.org/show_bug.cgi?id=438046
Nate Graham <n...@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |NEEDSINFO Summary|Dolphin high CPU usage on |kwin_wayland crashed |login | Resolution|--- |BACKTRACE Component|general |wayland-generic Assignee|dolphin-bugs-n...@kde.org |kwin-bugs-n...@kde.org Product|dolphin |kwin Version|20.12.3 |5.21.90 CC| |n...@kde.org --- Comment #2 from Nate Graham <n...@kde.org> --- The crash log only tells us that KWin crashed; sadly it's a known and unavoidable issue that when kwin_wayland crashes, all apps crash too (see https://bugreports.qt.io/browse/QTBUG-85631). The app crash logs are not useful; all they do is tell us that KWin crashed. But we need to know why KWin crashed. For that, we need a backtrace of the KWin crash itself. You may be able to retrieve it with `coredumpctl`. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl -- You are receiving this mail because: You are watching all bug changes.