one way to reproduce: switch to TTY unplug output replug output (for me power cycling causes kwin to think that the output was unplugged and replugged) switch back to session crash
i have an MR for this: https://invent.kde.org/plasma/kwin/-/merge_requests/828 though vlad says that this codepath shouldn't be triggering at all when the session is inactive
Git commit 991aa206d970112b576d3d328b541213799066b3 by Jan Blackquill. Committed on 05/04/2021 at 19:12. Pushed by cblack into branch 'Plasma/5.21'. Fix crash on hotplugging displays while switched to another TTY Currently, we inhibit renderloops when switching to another TTY, and unhibit when switching back. When we hotplug a display while switched to another TTY, its renderloop isn't inhibited by default, yet when we switch back, we try to uninhibit the fresh renderloop, which triggers an assert. Inhibiting newly created outputs while switched to another TTY fixes this crash. FIXED-IN: 5.21 M +4 -0 plugins/platforms/drm/drm_backend.cpp https://invent.kde.org/plasma/kwin/commit/991aa206d970112b576d3d328b541213799066b3
Git commit 9f215a06fa9c436034b368a1be5f357e85b03cd1 by Jan Blackquill. Committed on 05/04/2021 at 19:08. Pushed by cblack into branch 'master'. Fix crash on hotplugging displays while switched to another TTY Currently, we inhibit renderloops when switching to another TTY, and unhibit when switching back. When we hotplug a display while switched to another TTY, its renderloop isn't inhibited by default, yet when we switch back, we try to uninhibit the fresh renderloop, which triggers an assert. Inhibiting newly created outputs while switched to another TTY fixes this crash. FIXED-IN: 5.21 M +4 -0 src/plugins/platforms/drm/drm_backend.cpp https://invent.kde.org/plasma/kwin/commit/9f215a06fa9c436034b368a1be5f357e85b03cd1