| Summary: | The system crash when i was use plasma wayland session | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Pablo Saavedra Soler <pablosaavedrasoler> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | critical | CC: | alois1, kfm-devel, nate |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | The system crash when i was use plasma wayland session | ||
So everything crashed, and this is in the same crash wave as https://bugs.kde.org/show_bug.cgi?id=435406 ? In this case, it is a known bug in Qt that happens when the Wayland compositor (kwin_wayland in this case) vanishes. Yes. We need the backtrace of the crash in kwin_wayland. 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 |
Created attachment 137367 [details] The system crash when i was use plasma wayland session The system crash when i was use plasma wayland session EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION