Panic from cosmic-comp when switching back to Desktop using KVM

[dkowis]

Describe the bug
I have a Level One Techs KVM that is providing me with dual display port connections for my displays, one of which is a 4k display, and the other is a 1900x1200 display.

I work from home, so I use that KVM to switch my display over to the work computer. When I switch back, I'm always greeted with a locked, but fresh cosmic desktop. None of my windows are open, it's as if I just logged in.

Looking at the logs I can find a panic in cosmic-comp right after the KVM switches back over. I see USB connections and then a Cosmic-comp crash, as attached. I have included all the journalctl logs, because there's a whole pile of other errors that show up after that Wayland compositor dies.

The order of events seems to be:

1. KVM reconnects
2. cosmic-comp panics

Dec 17 17:00:36 raziel-linux.dark.kow.is cosmic-comp[301174]: Failed to destroy old mode property blob: No such file or directory (os error 2)
Dec 17 17:00:36 raziel-linux.dark.kow.is cosmic-comp[301174]: thread 'main' panicked at 'called `Option::unwrap()` on a `None` value': src/shell/layout/floating/mod.rs:308

3. so many broken pipe errors form cosmic-everything
4. cosmic-session panics

Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: Io error: Broken pipe (os error 32)
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: Io error: Broken pipe (os error 32)
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: [2025-12-17T23:00:38Z ERROR iced_winit::platform_specific::wayland::event_loop] SCTK dispatch error: other error during loop operation: underlying IO error: Broken pipe (os error 32)
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]:
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: thread '<unnamed>' panicked at src/backend/wayland/mod.rs:333:54:
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: called `Result::unwrap()` on an `Err` value: OtherError(IoError(Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }))

5. cosmic-things start exiting
6. cosmic-session dies again

Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: Error: other error during loop operation: underlying IO error: Broken pipe (os error 32)
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]:
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: Caused by:
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]:     0: underlying IO error: Broken pipe (os error 32)
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]:     1: Broken pipe (os error 32)
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: Io error: Broken pipe (os error 32)
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: Error:
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]:    0: other error during loop operation: underlying IO error: Broken pipe (os error 32)
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]:    1: underlying IO error: Broken pipe (os error 32)

7. cosmic-session finally sees that cosmic-comp died

Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: process ' COSMIC_SESSION_SOCK=12 cosmic-comp ' terminated with signal 6
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: cosmic-comp exited by signal
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: draining stdin receiver before restarting process
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: sleeping for 2ms before restarting process cosmic-comp (restart 0)
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: restarted process ' DISPLAY=:1 WAYLAND_DISPLAY=wayland-1 XDG_SESSION_TYPE=wayland GTK_MODULES=gail:atk-bridge QT_ACCESSIBILITY=1 QTWEBENGINE_DICTIONARIES_PATH=/usr/share/hunspell-bdic/ GSM_SKIP_SSH_AGENT_WORKAROUND=true cosmic-bg ', now at 1 restarts

8. it does not succssfully restart cosmic-comp

Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: RESTARTING: session restarted by request
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: cosmic-bg exited with error 137
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: restarted process ' COSMIC_SESSION_SOCK=12 cosmic-comp ', now at 1 restarts
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: process 'ProcessKey(1v1)' cancelled

9. cosmic comp dies, and cosmic-greeter die

Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: cosmic-comp exited with error code 137
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: cosmic-greeter exited with error 137

10. finally the rest of cosmic dies, taking down all my apps.

Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: cosmic-files-applet exited with error 137
Dec 17 17:00:38 raziel-linux.dark.kow.is systemd[2670]: cosmic-files-applet.scope: Consumed 11min 18.307s CPU time.
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: cosmic-app-library exited with error 137
Dec 17 17:00:38 raziel-linux.dark.kow.is systemd[2670]: cosmic-app-library.scope: Consumed 6min 9.512s CPU time.
Dec 17 17:00:38 raziel-linux.dark.kow.is systemd[2670]: cosmic-workspaces.scope: Consumed 10min 58.475s CPU time.
Dec 17 17:00:38 raziel-linux.dark.kow.is cosmic-session[2783]: cosmic-workspaces exited with error 137
Dec 17 17:00:38 raziel-linux.dark.kow.is mtp-probe[413992]: checking bus 5, device 25: "/sys/devices/pci0000:00/0000:00:08.1/0000:0e:00.3/usb5/5-4/5-4.4/5-4.4.2"
Dec 17 17:00:38 raziel-linux.dark.kow.is mtp-probe[413992]: bus: 5, device: 25 was not an MTP device
Dec 17 17:00:38 raziel-linux.dark.kow.is mtp-probe[414002]: checking bus 5, device 25: "/sys/devices/pci0000:00/0000:00:08.1/0000:0e:00.3/usb5/5-4/5-4.4/5-4.4.2"
Dec 17 17:00:38 raziel-linux.dark.kow.is mtp-probe[414002]: bus: 5, device: 25 was not an MTP device
Dec 17 17:00:38 raziel-linux.dark.kow.is systemd[2670]: app-cosmic-element-desktop-306129.scope: Consumed 34min 1.367s CPU time.
Dec 17 17:00:38 raziel-linux.dark.kow.is systemd[2670]: app-cosmic-obsidian-315604.scope: Consumed 13min 29.739s CPU time.
Dec 17 17:00:38 raziel-linux.dark.kow.is systemd[2670]: app-cosmic-discord-305571.scope: Consumed 31min 27.972s CPU time.
Dec 17 17:00:39 raziel-linux.dark.kow.is systemd[2670]: dbus-:1.1-org.freedesktop.impl.portal.desktop.cosmic@2.service: Main process exited, code=dumped, status=6/ABRT
Dec 17 17:00:39 raziel-linux.dark.kow.is systemd[2670]: dbus-:1.1-org.freedesktop.impl.portal.desktop.cosmic@2.service: Failed with result 'core-dump'.
Dec 17 17:00:39 raziel-linux.dark.kow.is systemd[2670]: dbus-:1.1-org.freedesktop.impl.portal.desktop.cosmic@2.service: Consumed 6min 35.126s CPU time.

11. Everything gets duitifully restarted by systemd

Dec 17 17:00:40 raziel-linux.dark.kow.is systemd[2670]: Stopped target cosmic-session.target - Cosmic Session Target.
Dec 17 17:00:40 raziel-linux.dark.kow.is systemd[2670]: Stopped target xdg-desktop-autostart.target - Startup of XDG autostart applications.
Dec 17 17:00:40 raziel-linux.dark.kow.is cosmic-session[2783]: Restarting
Dec 17 17:00:40 raziel-linux.dark.kow.is cosmic-session[2783]: Starting cosmic-session

Then I get my bare desktop back and have to start all my apps again. All that happens in like 40 seconds right after switching back. Log with all the gory messages attached.

failure.txt

To Reproduce
Steps to reproduce the behavior:

1. Have a KVM
2. switch displays to your work computer
3. switch back after a work day
4. Have a fresh desktop with no windows :(

Expected behavior
I would like to come back to my desktop environment still being up, and not having problems. It did work this way on Previous PopOS.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Pop!Os 24.04

Additional context
Add any other context about the problem here.

[donniebreve]

Getting this as well although it happens after my monitor sleeps and then I do something to wake it up, such as press a key or move the mouse. Cosmic doesn't completely restart, although Firefox hangs and has to be restarted. I have system suspend turned off.

Dec 25 21:11:22 cosmic-comp[1364]: Failed to destroy old mode property blob: No such file or directory (os error 2)
Dec 25 21:11:24 cosmic-panel[1440]: com.system76.CosmicAppletPower: exited with code 137
Dec 25 21:11:24 cosmic-panel[1440]: com.system76.CosmicAppletNotifications: exited with code 137
Dec 25 21:11:24 cosmic-panel[1440]: com.system76.CosmicAppletNetwork: exited with code 137
Dec 25 21:11:24 cosmic-panel[1440]: com.system76.CosmicAppletMinimize: exited with code 137
Dec 25 21:11:24 cosmic-panel[1440]: com.system76.CosmicAppletBluetooth: exited with code 137
Dec 25 21:11:24 cosmic-panel[1440]: com.system76.CosmicAppletStatusArea: exited with code 137
Dec 25 21:11:24 cosmic-panel[1440]: com.system76.CosmicAppletWorkspaces: exited with code 137
Dec 25 21:11:24 cosmic-panel[1440]: com.system76.CosmicAppletTime: exited with code 137
Dec 25 21:11:24 cosmic-panel[1440]: com.system76.CosmicAppletTiling: exited with code 137
Dec 25 21:11:24 cosmic-panel[1440]: com.system76.CosmicAppletAudio: exited with code 137
Dec 25 21:11:25 cosmic-comp[1364]: Failed to destroy old mode property blob: No such file or directory (os error 2)
Dec 25 21:11:25 cosmic-comp[1364]: Failed to set xwayland primary output: The provided output wasn't known to Xwayland
Dec 25 21:11:25 cosmic-panel[1440]: com.system76.CosmicAppletStatusArea: Acquired bus name: org.kde.StatusNotifierWatcher
Dec 25 21:11:29 cosmic-greeter[20751]: pam_unix(login:account): setuid failed: Operation not permitted

To Reproduce

1. Power & Battery
   1. Turn off the screen after: 15m
   2. Automatic suspend: Never
2. Let the monitor turn off + some additional time (unsure, maybe 1h)
3. Try to wake the monitor with keys or mouse

Desktop

• OS: Arch Linux
• cosmic-comp

cosmic-app-library 1:1.0.0-1 (cosmic)
cosmic-applets 1:1.0.0-2 (cosmic)
cosmic-bg 1:1.0.0-1 (cosmic)
cosmic-comp 1:1.0.0-1 (cosmic)
cosmic-files 1:1.0.0-1 (cosmic)
cosmic-greeter 1:1.0.0-1 (cosmic)
cosmic-icon-theme 1:1.0.0-1
cosmic-idle 1:1.0.0-1 (cosmic)
cosmic-launcher 1:1.0.0-1 (cosmic)
cosmic-notifications 1:1.0.0-1 (cosmic)
cosmic-osd 1:1.0.0-1 (cosmic)
cosmic-panel 1:1.0.0-1 (cosmic)
cosmic-randr 1:1.0.0-1 (cosmic)
cosmic-screenshot 1:1.0.0-1 (cosmic)
cosmic-session 1:1.0.0-1 (cosmic)
cosmic-settings 1:1.0.0-1 (cosmic)
cosmic-settings-daemon 1:1.0.0-1 (cosmic)
cosmic-workspaces 2:1.0.0-1 (cosmic)
xdg-desktop-portal-cosmic 1:1.0.0-1 (cosmic)

[Kore-rep]

I'm having the same issue as donniebreve on Arch Linux

Attached is the log. I'm think kitty crashing is unrelated, as this issue seems to occur commonly after my PC turns off the monitors due to inactivity.

log.txt

[Leafrider]

I'm hitting this same crash on Pop!_OS 24.04 with an NVIDIA RTX 4090 and a single HDMI-A-1 display (5120x2160). My trigger is physically powering off the monitor when leaving the room, then powering it back on later.

cosmic-comp version: 0.1~1769425738~24.04~1dfc948
Kernel: 6.17.9-76061709-generic

Crash pattern

The crash follows the exact same sequence every time:

1. Failed to destroy old mode property blob: No such file or directory (os error 2)
2. thread 'main' panicked at 'called Option::unwrap() on a None value': src/shell/layout/floating/mod.rs:315
3. thread 'surface-HDMI-A-1' panicked at PoisonError: vendor/smithay/src/backend/drm/output.rs:797
4. thread 'surface-HDMI-A-1' panicked at PoisonError: vendor/smithay/src/backend/drm/output.rs:811
5. thread 'surface-HDMI-A-1' panicked at 'panic in a destructor during cleanup': library/core/src/panicking.rs:233
6. cosmic-comp exits with signal 6 (SIGABRT), entire session dies

It's a race condition

I've been tracking this for a month. The same Failed to destroy old mode property blob error fires every time the monitor is powered off, but the crash only happens sometimes — when the floating layout is in a vulnerable state at the moment of the DRM mode change.

Crashes (5):

Date	Time
Jan 10	18:28
Jan 17	13:30
Jan 29	07:22
Jan 30	20:35
Feb 02	11:10

Survived (mode blob error fired but no crash, 4+):

Date	Time
Feb 02	14:09
Feb 02	17:42
Feb 03	05:58
Feb 03	07:05

Example log from the Feb 02 11:10 crash

Feb 02 11:10:57 cwollypop cosmic-comp[76754]: thread 'main' panicked at 'called `Option::unwrap()` on a `None` value': src/shell/layout/floating/mod.rs:315
Feb 02 11:10:57 cwollypop cosmic-comp[76754]: thread 'surface-HDMI-A-1' panicked at 'called `Result::unwrap()` on an `Err` value: PoisonError { .. }': /build/cosmic-comp-YukPIR/cosmic-comp-0.1~1768995933~24.04~996a8a8/vendor/smithay/src/backend/drm/output.rs:797
Feb 02 11:10:57 cwollypop cosmic-comp[76754]: thread 'surface-HDMI-A-1' panicked at 'called `Result::unwrap()` on an `Err` value: PoisonError { .. }': /build/cosmic-comp-YukPIR/cosmic-comp-0.1~1768995933~24.04~996a8a8/vendor/smithay/src/backend/drm/output.rs:811
Feb 02 11:10:57 cwollypop cosmic-comp[76754]: thread 'surface-HDMI-A-1' panicked at 'panic in a destructor during cleanup': library/core/src/panicking.rs:233
Feb 02 11:10:58 cwollypop cosmic-session[3603]: process ' COSMIC_SESSION_SOCK=12 cosmic-comp ' terminated with signal 6
Feb 02 11:10:58 cwollypop cosmic-session[3603]: cosmic-comp exited with error code 137

The unwrap() at floating/mod.rs:315 needs to be replaced with proper error handling for the case where the output/window reference is None during a display disconnect event.

[arashsm79]

Same problem here. I get crashes after I unplug the battery.

Feb 03 21:12:03 cosmicbox cosmic-comp[2394]: Failed to destroy old mode property blob: No such file or directory (os error 2)
Feb 03 21:12:03 cosmicbox cosmic-applet-minimon[3230]: path stroking failed
Feb 03 21:12:05 cosmicbox (udev-worker)[19145]: BAT1: Process '/bin/chmod 666 /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:49/PNP0C0A:00/po>
Feb 03 21:12:05 cosmicbox (udev-worker)[19145]: BAT1: Process '/bin/chmod 666 /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:49/PNP0C0A:00/po>
Feb 03 21:12:05 cosmicbox (udev-worker)[19145]: BAT1: Process '/bin/chmod 666 /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:49/PNP0C0A:00/po>
Feb 03 21:12:05 cosmicbox (udev-worker)[19145]: BAT1: Process '/bin/chmod 666 /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:49/PNP0C0A:00/po>
Feb 03 21:12:05 cosmicbox cosmic-comp[2394]: Failed to set xwayland primary output: The provided output wasn't known to Xwayland
Feb 03 21:12:08 cosmicbox audit[19175]: AUDIT1100 pid=19175 uid=1000 auid=1000 ses=2 msg='op=PAM:unix_chkpwd acct="arashsm79" exe="/usr/bin/unix_chkp>
Feb 03 21:12:08 cosmicbox cosmic-greeter[2630]: gkr-pam: unlocked login keyring
Feb 03 21:12:08 cosmicbox cosmic-greeter[19176]: pam_unix(cosmic-greeter:account): setuid failed: Operation not permitted
Feb 03 21:12:12 cosmicbox cosmic-applet-minimon[3230]: path stroking failed
Feb 03 21:12:14 cosmicbox cosmic-applet-minimon[3230]: path stroking failed
Feb 03 21:12:17 cosmicbox kernel: BUG: kernel NULL pointer dereference, address: 0000000000000086
Feb 03 21:12:17 cosmicbox kernel: #PF: supervisor write access in kernel mode

[donniebreve]

Possibly related to #2851

[leviport]

Might be a duplicate of http://github.com/pop-os/cosmic-epoch/issues/840?

[justacourtjester]

Not sure which of the bugs to report my issue, but I too am experiencing this and continue to on the latest version. My friend Claude suggested that I upload my logs here as they would be a "good addition to issue #2715 or #840".

Kernel version is 6.18.28-1-lts

cosmic-comp KVM Switch Crash — Bug Report

Environment

Component	Details
OS	Arch Linux
Desktop	COSMIC 1.0.12 (all packages)
Compositor	cosmic-comp 1:1.0.12-1
GPU	NVIDIA GeForce RTX 4070 SUPER (AD104)
Driver	nvidia 595.71.05
nvidia-drm modeset	Y
nvidia-drm fbdev	Y
Session type	Wayland (wayland-1) + Xwayland (:1)
Kernel	Linux (Arch)

VRR was enabled on all outputs at time of crash (vrr: Enabled in cosmic-comp output config logs).

Reproduction Steps

1. Log into a COSMIC Wayland session with three monitors active.
2. Switch the KVM to the other computer.
3. Switch the KVM back.
4. cosmic-comp fails to restore output config; cosmic-workspaces and xdg-desktop-portal-cosmic segfault; all panel applets die with exit code 137.

Reproduces 100% of the time on every KVM switch.

Crash Sequence (annotated)

1. KVM switch — USB hub disconnects all devices simultaneously

kernel: usb 1-10: USB disconnect, device number 39
kernel: usb 1-10.1: USB disconnect, device number 40
kernel: usb 1-10.2: USB disconnect, device number 41
kernel: usb 1-10.3: USB disconnect, device number 42
kernel: usb 1-10.4: USB disconnect, device number 43
kernel: usb 1-10.4.1: USB disconnect, device number 44

The KVM presents as a GenesysLogic USB2.1 hub. All downstream devices (mouse receiver, keyboard receiver, audio device, Jabra dongle) disconnect simultaneously.

2. cosmic-comp fails to handle the DRM output config change

cosmic-comp[1491]: Failed to destroy old mode property blob: No such file or directory (os error 2)
cosmic-comp[1491]: Failed to destroy old mode property blob: No such file or directory (os error 2)
cosmic-comp[1491]: Failed to destroy old mode property blob: No such file or directory (os error 2)
cosmic-comp[1491]: Failed to set new config.
cosmic-comp[1491]: Unable to load output config: Failed to reset config
cosmic-comp[1491]: Failed to set new config.

This fires immediately when the display hotplug event is received. The mode property blob cleanup fails, and cosmic-comp is unable to reset the output config.

3. cosmic-comp marks all outputs disabled and logs the broken config

cosmic-comp[1491]: Broken config, all outputs disabled. Resetting...
  [OutputConfig { mode: ((2560, 1440), Some(164958)), vrr: Enabled, scale: 1.0, transform: Normal, position: (0, 0), enabled: Disabled, max_bpc: None, xwayland_primary: false },
   OutputConfig { mode: ((1920, 1080), Some(60000)), vrr: Enabled, scale: 1.0, transform: Normal, position: (2560, 0), enabled: Disabled, max_bpc: None, xwayland_primary: false },
   OutputConfig { mode: ((1920, 1080), Some(60000)), vrr: Enabled, scale: 1.0, transform: Normal, position: (4480, 0), enabled: Disabled, max_bpc: None, xwayland_primary: false }]

All three outputs are marked enabled: Disabled. The reset attempt also fails.

4. Xwayland loses primary output reference

cosmic-comp[1491]: Failed to set xwayland primary output: The provided output wasn't known to Xwayland
cosmic-comp[1491]: Failed to set xwayland primary output: The provided output wasn't known to Xwayland
cosmic-comp[1491]: Failed to set xwayland primary output: The provided output wasn't known to Xwayland
cosmic-comp[1491]: Failed to set xwayland primary output: The provided output wasn't known to Xwayland

5. cosmic-workspaces segfaults (SIGSEGV, signal 11)

kernel: cosmic-workspac[116957]: segfault at 18 ip 000056390ed2a903 sp 00007fd9bf7f80e0 error 4
  in cosmic-workspaces[1658903,56390df05000+13a4000] likely on CPU 0 (core 0, socket 0)

Null pointer dereference (segfault at 18) — consistent with dereferencing an output object that cosmic-comp has just invalidated.

6. xdg-desktop-portal-cosmic segfaults simultaneously

kernel: xdg-desktop-por[34426]: segfault at 18 ip 000055ece733a05d sp 00007f05c215d250 error 4
  in xdg-desktop-portal-cosmic[199a05d,55ece6424000+1772000] likely on CPU 13 (core 5, socket 0)

Same fault address pattern (segfault at 18) suggesting the same root cause — stale output reference.

7. All cosmic-panel applets die (exit code 137 = SIGKILL cascade)

cosmic-panel[1572]: com.system76.CosmicAppletNetwork: exited with code 137
cosmic-panel[1572]: com.system76.CosmicAppletPower: exited with code 137
cosmic-panel[1572]: com.system76.CosmicAppletTiling: exited with code 137
cosmic-panel[1572]: com.system76.CosmicAppletTime: exited with code 137
cosmic-panel[1572]: com.system76.CosmicAppletBluetooth: exited with code 137
cosmic-panel[1572]: com.system76.CosmicAppletNotifications: exited with code 137
cosmic-panel[1572]: com.system76.CosmicAppletAudio: exited with code 137
cosmic-panel[1572]: com.system76.CosmicAppletStatusArea: exited with code 137
cosmic-panel[1572]: com.system76.CosmicAppList: exited with code 137

8. cosmic-session restarts cosmic-workspaces; second USB reconnect triggers the same sequence again

When the KVM cycles back (USB hub reconnects ~7 seconds after disconnect), the entire crash sequence repeats:

kernel: usb 1-10: USB disconnect, device number 45
...
cosmic-comp[1491]: Failed to destroy old mode property blob: No such file or directory (os error 2)
cosmic-comp[1491]: Broken config, all outputs disabled. Resetting...

9. cosmic-workspaces config state is lost on restart

cosmic-session[1316]: [ERROR cosmic_workspaces] Failed to load compositor config:
  [GetKey("workspaces", Os { code: 2, kind: NotFound, ...}),
   GetKey("pinned_workspaces", ...),
   GetKey("input_default", ...),
   ...]

Key Observations

• The crash is not caused by a GPU driver issue — nvidia-drm modeset=Y, fbdev=Y, EDID reads cleanly for all three monitors.
• The crash is not caused by a missing display — all three monitors reconnect successfully at the kernel level after the KVM switch completes.
• The fault address 0x18 in both cosmic-workspaces and xdg-desktop-portal-cosmic segfaults suggests a null pointer dereference on an output struct — consistent with both processes holding a reference to an output object that cosmic-comp invalidated without notifying them.
• The Failed to destroy old mode property blob error fires before any downstream crash, suggesting it is the root cause event.
• This reproduces on every single KVM switch without exception.

Related Issues

• https://github.com/Panic from cosmic-comp when switching back to Desktop using KVM #2715 — identical log signature, dual DP KVM
• https://github.com/[Bug] comsic-session crashes when switching inputs using a KVM #840 — same mode property blob + unwrap() panic on KVM switch
• https://github.com/Panel and dock disappear after wake from sleep mode or KVM switch. Attempted recovery crashes system.  cosmic-panel#287 — panel disappearing on KVM switch / wake from sleep