| Summary: | Entire session crashes closing all running apps if kwin_wayland crashes | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | smit <smit17xp> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED LATER | ||
| Severity: | crash | CC: | bugseforuns, herzenschein, hsantanna, kde, nate, postix, s.kde, smit17xp, uhhadd |
| Priority: | NOR | Keywords: | wayland-only |
| Version First Reported In: | 5.20.3 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
smit
2020-11-14 11:20:19 UTC
I'm not sure if it's possible to fix this due to Wayland's inherent architecture. It sure would be nice to if it's possible though. Well, some work is being done to make apps survive wayland compositor crashes. Can this be closed now that https://invent.kde.org/plasma/kwin/-/merge_requests/483 has landed? (In reply to Jan Blackquill (Carson Black) from comment #3) > Can this be closed now that > https://invent.kde.org/plasma/kwin/-/merge_requests/483 has landed? I'm afraid not. That fix was merged three weeks ago and I updated my git installation today: while SIGSEV applied to KWin does not crash kwin_wayland, SIGKILL still causes this issue, sending the user back to the login screen. This occurs even when not manually triggered, for instance bug 428268 is still easily reproducible and takes the whole session with it. Sorry, I misread, it was merged 5 days ago. And for the testing I used killall kwin_wayland, sudo kill -SIGSEGV <pid> and sudo kill -SIGKILL <pid>. This is the expected behaviour at the current point in time. To clarify, we are working to improve this incrementally. |