https://bugs.kde.org/show_bug.cgi?id=457757
Nate Graham <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Plasmashell crash after |kwin_wayland crashed |login | Resolution|--- |BACKTRACE Assignee|[email protected] |[email protected] Status|REPORTED |NEEDSINFO Version|master |5.24.4 Target Milestone|1.0 |--- Component|generic-crash |wayland-generic CC| |[email protected] Product|plasmashell |kwin --- Comment #1 from Nate Graham <[email protected]> --- > The Wayland connection broke. Did the Wayland compositor die 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.
