Summary: | Dolphin crash | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | John Shellshear <john.shellshear> |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | kfm-devel, sitter |
Priority: | NOR | Keywords: | drkonqi |
Version: | 20.12.3 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
John Shellshear
2021-06-20 02:11:08 UTC
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 |