Sway crashes when hotplugging with Assertion layout_output failed

[LaserEyess]

• Sway Version: sway version 1.4-82d02ce7 (Mar 28 2020, branch 'master')

• Debug Log: https://0x0.st/iB08.txt
  Created with WAYLAND_DEBUG=1 sway -d -c /etc/sway/config 2> ~/log.file

• Configuration File: default (/etc/sway/config)

Reproducing this requires two monitors. It's worth noting that the second monitor is HDMI and the first monitor is DP

1. Start sway with only one monitor on (second monitor is plugged in but turned off)
2. Turn on the second monitor
3. Sway crashes almost instantly, after first trying to set the second monitor output

• Stack Trace, if sway crashes: https://0x0.st/iB0K.txt

[LaserEyess]

Ok, on closer inspection the log file seems to recognize HDMI-A-1 as soon as sway starts.

Perhaps a little more information about my setup then, I use an HDMI splitter to connect my GPU to my TV, so I can switch between other inputs. When sway is started, the TV is off, as is the splitter (which is powered by the TV). Sway still seems to detect the splitter/TV when both are powered off, but when powered on it appears to destroy HDMI-A-1 as an output and then create a new one.

[emersion]

This stack trace is missing wlroots symbols.

[LaserEyess]

My fault, here's a trace with wlroots debugging symbols: https://0x0.st/iB7G.txt

This issue also occurs in 1.4, but it doesn't crash. Instead it just destroys all my work spaces and leaves sway in a near unusable state. I'm able to start new terminals and programs but my bar is gone and workspaces don't seem to work properly.

[emersion]

output = 0x0

Hmm, so a client is using an inert output and we're not dealing with that correctly.

[emersion]

Note, we should add checks to all wlr_output_from_resource call sites.