Bug 453214 - kwin_wayland SIGSEGV when switching monitor input with a KVM
Summary: kwin_wayland SIGSEGV when switching monitor input with a KVM
Status: RESOLVED DUPLICATE of bug 448102
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.24.4
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-30 00:07 UTC by Johan Sköld
Modified: 2022-05-03 14:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Backtrace produced by GDB (23.50 KB, text/plain)
2022-04-30 00:07 UTC, Johan Sköld 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Johan Sköld 2022-04-30 00:07:38 UTC 
Created attachment 148466 [details]
Backtrace produced by GDB

SUMMARY
I have my computer connected to a KVM through DisplayPort. When I switch input away from it and then back again, kwin_wayland segfaults after a very brief moment of showing my desktop (milliseconds rather than seconds).

I'm attaching a backtrace as produced using the commands at https://community.kde.org/KWin/Debugging#TL.3BDR_for_bug_reporters

STEPS TO REPRODUCE
1. Using a KVM switch input away from the machine running KDE
2. Using the same KVM switch, switch input back to the machine running KDE

OBSERVED RESULT
kwin_wayland segfaults, taking the entire desktop and everything that was running in it down with it before restarting.

EXPECTED RESULT
kwin_wayland does not crash.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.17.4-300.fc36.x86_64
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.91.0
Qt Version: 5.13.3
Comment 1 Johan Sköld 2022-04-30 03:19:51 UTC 
After some testing it appears this may be triggered by bismuth resizing/moving windows when switching the display back. kwin_wayland no longer crashes after removing bismuth.
Comment 2 Nate Graham 2022-05-03 14:41:08 UTC 

*** This bug has been marked as a duplicate of bug 448102 ***