When outputs are disabled+enabled, all windows die or freeze #6642
Comments
|
Hmmm, all those |
|
Sway sends a keymap event for each of your attached keyboards. Not technically necessary, but it's been that way for a long time so it's unlikely to be the cause of your issue. |
|
Ah, thanks for the clarification there. Saved me going on a wild goose chase.
|
|
Your debug paste gives me 502 bad gateway... |
|
Same experience. Looks something like this:
Processes for those windows are alive and responding, but it looks as if windows get cut off from processes. |
|
So, I've tried investigating it further, by starting sway on vt1 and starting a sacrificial program in vt2 I am trying to get into "limbo" state with WAYLAND_DEBUG=1 WAYLAND_DISPLAY=wayland-1 alacritty 2>&1 | tee sacrifitial-alacritty.log(Cheers, #6640) After a bit of monkey-testing stuff, I've managed to get limbo-ed by reloading sway in the middle of loading huge GPU load (4 firefox windows, 2 codium windows, and some other stuff at once). (and to crash display connection multiple times ) So, here's log from that limbo-ed alacritty
I didn't record a usable log from sway (I have one where I crashed sway, and another, 160Mb long) |
|
I think I found a reproduction:
I think the issue may be related to #6310. Those keymap events might be related after all. |
|
Does #6629 help? |
|
#6310 definitely sounds related. I think this might be a duplicate if it, TBH. But I'm not 100% certain.
|
|
#6629 seems to fix this for me. |
|
Opt to reopen. Can still repro on that fork. |
|
Also, it seems like (30% sure) that setting |
Please fill out the following:
Sway Version:
sway version 1.6-aaf68cf4 (Oct 27 2021, branch 'master')Debug Log:
sway -d-> https://paste.sr.ht/~whynothugo/694f96d74f2c47c50dee186fe36ee6139d3c4a4cConfiguration File:
I don't see anything specific in my config that triggers it. It's this one.
Description:
After outputs are turned off and on again, Firefox windows die and most other windows are frozen.
This is the log output of
swaymsg -- exec 'WAYLAND_DEBUG=1 alacritty 2> alacritty.log'This
alacrittywindow was frozen, and using mykillmapping (bindsym $super+Shift+q kill) won't work.This looks close to #6640, but:
swaylockfreezes, nothing responds, but I haven't seen it crash (I wasn't running swaylock in this test to make things simpler).The text was updated successfully, but these errors were encountered: