swaywm / sway

i3-compatible Wayland compositor
https://swaywm.org
MIT License
14.68k stars 1.11k forks source link

Sway outputs grey when toggling secondary montior (DP-2) #8445

Open mm1ke opened 2 days ago

mm1ke commented 2 days ago

Output DP-2 'Acer Technologies XB283K KV 120918FA54200' (focused) Current mode: 3840x2160 @ 144.004 Hz Power: on Position: 3840,-1250 Scale factor: 1.000000 Scale filter: nearest Subpixel hinting: unknown Transform: 90 Workspace: 2 Max render time: off Adaptive sync: disabled Available modes: 3840x2160 @ 59.997 Hz 3840x2160 @ 144.004 Hz 3840x2160 @ 120.000 Hz (16:9) 3840x2160 @ 119.880 Hz (16:9) 3840x2160 @ 119.910 Hz 3840x2160 @ 60.000 Hz (16:9) 3840x2160 @ 59.940 Hz (16:9) 2560x1440 @ 143.912 Hz



- **Description:**
The issue is pretty simple to explain.
Most of the time when i'm disabling my secondary right monitor (`DP-2 / Acer Technologies XB283K KV`) via hotkey `bindsym $mod+Shift+F12 output DP-2 toggle` sway does turn off the monitor but also shows a completely greyed output on the main monitor (`DP-1`). In that case i cannot to anything and it even looks like sway crashed.
However, sway still runs and i've found a workaround to get the desktop back. I just need to switch to another VT and back (via `CTRL-ALT-F5` for example) and i have my desktop again.
Afterwards i also can add (toggle) my secondary monitor again without problems.
Also, it doesn't happen all the time. (but lets say 90%). After a clean start of sway i can fairly simple reproduce it, but sometimes it works without this issue, but i didn't found a clue what could be different when it works..

Please note, this is **NOT** a regression to 1.9. This issue already happend with 1.9. I just wanted to wait for the final 1.10 release to see if 1.10 might fix this. Also, as far as i can remember i always had that issue.

I've added a debug log file were i've only logged in and turned off (got grey screen), switched VT and turned on the monitor again.
Lunitur commented 2 days ago

I also got similar bug since updating to 1.10. Before when connecting DP-1 it would automatically set up both workspaces, now it glitches out and secondary monitor shows mirror image of primary screen.

emersion commented 2 days ago

@Lunitur, this issue is specifically marked as not being a 1.10 regression.

sentientmachin3 commented 23 hours ago

I'm having the same issue, everything looks fine until i disable the laptop output.

I downgraded to sway 1.9 (using downgrade), and monitor setup is working again (in my case at least), but the symptoms are the same @mm1ke described.