-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Nested sway crashes randomly #5055
Comments
Please post a backtrace of sway. coredumpctl gdb sway
...
(gdb) bt
<copy this bit>
(gdb) q |
@ascent12 |
That debug log shows something going horribly wrong.
|
I think this happens when I change tty. (I do this quite often sometimes) |
This is totally related to a tty switch.The crash occurs after 6 switches. I have another problem with firefox in a nested sway (which I did not report because I only encountered it with firefox): |
Previously, each time a wl_seat.capabilities event was received the Wayland backend created new input devices. It now only does so the first time. Input devices are now destroyed when the cap is removed. Closes: swaywm/sway#5055
Can you try this patch? swaywm/wlroots#2048 |
@emersion |
Sorry for the little information. The coredump happend in the nested sway. |
Previously, each time a wl_seat.capabilities event was received the Wayland backend created new input devices. It now only does so the first time. Input devices are now destroyed when the cap is removed. Closes: swaywm/sway#5055
Ah, sorry about that. Should be fixed now. |
@emersion |
Previously, each time a wl_seat.capabilities event was received the Wayland backend created new input devices. It now only does so the first time. Input devices are now destroyed when the cap is removed. Closes: swaywm/sway#5055
Previously, each time a wl_seat.capabilities event was received the Wayland backend created new input devices. It now only does so the first time. Input devices are now destroyed when the cap is removed. Closes: swaywm/sway#5055
Previously, each time a wl_seat.capabilities event was received the Wayland backend created new input devices. It now only does so the first time. Input devices are now destroyed when the cap is removed. Closes: swaywm/sway#5055
I run a nested sway and sometimes it crashes. It happens usually when there is no interaction (I am on another workspace in the host sway).
I use this config:
Here is a debug log: http://sprunge.us/8mSZHv
My sway version is
sway version 1.4
.Steps to reproduce:
I basically do nothing.
I start sway with the config and pipe the debug log into a file.
Sometimes I change to the workspace with the nested sway to see if it crashed, then go back to another workspace.
I am using an uptodate Arch Linux with intel graphics card.
The crash is also reproducible when I start firefox, claws-mail or anyithing else in sway.
The text was updated successfully, but these errors were encountered: