You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was interacting with the alacritty terminal using the wacom tablet pen. I run alacritty under xwayland because when running under wayland natively, text selection and middle-click paste don't work properly when using the tablet pen. (They work fine using a mouse).
I can't be certain on precisely what it was I was doing. Probably selecting something.
Sway completely locked up, using 100% cpu. All input devices on that computer become unresponsive, but I was able to ssh in from another computer to kill sway.
This has only ever happened once (just now). I can't reproduce on-demand. Hopefully even without full repro steps the debug log is still enough for this to be a useful bug report
The text was updated successfully, but these errors were encountered:
Sway Version: 1.9
Debug Log:
Here's the relevant section of the sway log, when the problem started.
You can see the pattern. It continues indefinitely, with one more "Transfer 0x... still running" line each time.
More complete log: https://gist.github.com/SimonWoolf/b2bbf5f3feb7ef5e1e11b51216e7b7c2 . (This is not quite the full log, because the full log is 14 GiB. I included the first few thousand lines, and a couple thousand before the bug happened)
Configuration File: https://gist.github.com/SimonWoolf/c30f9671cdd00bd668e51cb8eb0cdabb
Stack Trace: n/a
Description:
I was interacting with the alacritty terminal using the wacom tablet pen. I run alacritty under xwayland because when running under wayland natively, text selection and middle-click paste don't work properly when using the tablet pen. (They work fine using a mouse).
I can't be certain on precisely what it was I was doing. Probably selecting something.
Sway completely locked up, using 100% cpu. All input devices on that computer become unresponsive, but I was able to ssh in from another computer to kill sway.
This has only ever happened once (just now). I can't reproduce on-demand. Hopefully even without full repro steps the debug log is still enough for this to be a useful bug report
The text was updated successfully, but these errors were encountered: