| Summary: | System hangs when unplugging/plugging in multiple monitors or enabling/disabling displays in settings | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Brian Tipton <brian.p.tipton> |
| Component: | multi-screen | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | major | CC: | nate |
| Priority: | NOR | Keywords: | multiscreen |
| Version First Reported In: | 5.27.0 | ||
| Target Milestone: | --- | ||
| Platform: | NixOS | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
GDB
Diagnosis Info |
||
|
Description
Brian Tipton
2023-02-24 01:40:46 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports. Can you please attach one? Thanks! (In reply to Nate Graham from comment #1) > If something crashed, we need a backtrace of it so we can figure out what's > going on. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports. > > Can you please attach one? Thanks! Yea sorry, I meant to post one the other night. Another couple thing to note, I have 2 GPU's attached to my machine with VFIO setup. Whenever I swap the monitors via KVM I am swapping to the output of the 2nd GPU. The swapping seems to be okay when removing monitors, but when I am attempting to reconnect the monitors via KVM the system gets very laggy on the running monitor (mouse/windows visually jumping around). Then when I go inside the system settings to disable/enable to attempt to get them to work it crashes. Also tested on 5.27.1 with same results. I will also attach diagnosis info. Thanks Created attachment 156743 [details]
GDB
Created attachment 156744 [details]
Diagnosis Info
The gdb backtrace doesn't show that kwin_wayland crashed but rather than it was interrupted. Can you get a backtrace of the crash itself? (In reply to Nate Graham from comment #5) > The gdb backtrace doesn't show that kwin_wayland crashed but rather than it > was interrupted. > > Can you get a backtrace of the crash itself? This gdb was during the "crash", I didn't realize it wasn't actually crashing the kwin process. It (In reply to Nate Graham from comment #5) > The gdb backtrace doesn't show that kwin_wayland crashed but rather than it > was interrupted. > > Can you get a backtrace of the crash itself? (In reply to Brian Tipton from comment #6) > (In reply to Nate Graham from comment #5) > > The gdb backtrace doesn't show that kwin_wayland crashed but rather than it > > was interrupted. > > > > Can you get a backtrace of the crash itself? > > This gdb was during the "crash", I didn't realize it wasn't actually > crashing the kwin process. (In reply to Brian Tipton from comment #6) > (In reply to Nate Graham from comment #5) > > The gdb backtrace doesn't show that kwin_wayland crashed but rather than it > > was interrupted. > > > > Can you get a backtrace of the crash itself? > > This gdb was during the "crash", I didn't realize it wasn't actually > crashing the kwin process. What I see on my side during the "crash" is that the cursor doesn't have the ability to move, the keyboard doesn't do anything except sometimes lets me get to a TTY. And windows seems to be stuck at there last position. Most of the time it requires a reboot to get out of this state Ah, that's not a crash. :) That's a hang. |