Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sway outputs grey when toggling secondary monitor (*not* a 1.10 regression) #8445

Open
mm1ke opened this issue Nov 10, 2024 · 5 comments
Open
Labels
bug Not working as intended

Comments

@mm1ke
Copy link

mm1ke commented Nov 10, 2024

  • Sway Version:

    • sway version 1.10
  • Debug Log:

  • Configuration File:
    These are the settings in the configuration file specific for the monitors:

### Output configuration
output DP-1 render_bit_depth 10 pos 0 0 mode [email protected] bg $swaywalls/wallpaper-main fill
output DP-2 pos 3840 -1250 transform 90 mode [email protected] bg $swaywalls/wallpaper-right fill

Details about the monitors:
swaymsg -t get_outputs (i've removed most of the modes)

Output DP-1 'Acer Technologies X32 FP 1246006353G00'
  Current mode: 3840x2160 @ 143.999 Hz
  Power: on
  Position: 0,0
  Scale factor: 1.000000
  Scale filter: nearest
  Subpixel hinting: unknown
  Transform: normal
  Workspace: 1
  Max render time: off
  Adaptive sync: disabled
  Available modes:
    3840x2160 @ 120.000 Hz
    3840x2160 @ 60.000 Hz
    3840x2160 @ 159.750 Hz
    3840x2160 @ 143.999 Hz
    3840x2160 @ 120.000 Hz (16:9)
    3840x2160 @ 119.880 Hz (16:9)
    3840x2160 @ 60.000 Hz (16:9)
    3840x2160 @ 59.940 Hz (16:9)


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.

@mm1ke mm1ke added the bug Not working as intended label Nov 10, 2024
@Lunitur

This comment was marked as off-topic.

@emersion
Copy link
Member

emersion commented Nov 10, 2024

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

@sentientmachin3

This comment was marked as off-topic.

@dR3b

This comment was marked as duplicate.

@emersion emersion changed the title Sway outputs grey when toggling secondary montior (DP-2) Sway outputs grey when toggling secondary monitor (*not* a 1.10 regression) Nov 13, 2024
@emersion
Copy link
Member

emersion commented Nov 13, 2024

@sentientmachin3, your issue is unrelated.

@dR3b, please use the thumbs-up button instead if you're hitting the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Not working as intended
Development

No branches or pull requests

5 participants