https://bugs.kde.org/show_bug.cgi?id=450711
--- Comment #6 from Guido Winkelmann ---
(In reply to Nate Graham from comment #5)
> Oh, so no other apps died too?
No, it was literally just plasmashell that died (as far as I could tell). All
the other running applications kept running, and I could e
https://bugs.kde.org/show_bug.cgi?id=450711
--- Comment #5 from Nate Graham ---
Oh, so no other apps died too?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450711
--- Comment #4 from Guido Winkelmann ---
Are you sure kwin_wayland crashed anyway? I'd think that would have even worse
consequences, like the entire graphical session stopping to work.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=450711
--- Comment #3 from Nate Graham ---
Oh, well then you can use some other method to get a backtrace of the
kwin_wayland crash.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450711
--- Comment #2 from Guido Winkelmann ---
(In reply to Nate Graham from comment #1)
> > The Wayland connection broke. Did the Wayland compositor die?
> This means kwin_wayland crashed. Can you get a backtrace of it using
> `coredumctl`? See
> https://com
https://bugs.kde.org/show_bug.cgi?id=450711
Nate Graham changed:
What|Removed |Added
Summary|plasmashell exits with |kwin_wayland crashes
|timeout r
