Closed ossimoi closed 6 years ago
makes sway crash (without core dump)
Eh. It's probably because it's got the suid bit set. Can you try installing elogind, unsetting the suid bit on the sway binary and try again?
You could also probably start sway, connect to your system with SSH, attaching GDB to the sway session via SSH, undock it and get the backtrace via the SSH connection.
Ah, of course. Linux is hard :)
Here's the dump: https://pastebin.com/zTzYx17w
I have the same issue (intermittently) on my Thinkpad dock. Unplugging other monitors seems fine.
It looks like there's some kind of a bus reset, because eDP-1 (laptops internal monitor) gets destroyed as well.
https://github.com/swaywm/sway/issues/2337 might actually fix this?
2337 might actually fix this?
Unlikely. This issue is kind of weird, because what happens is basically:
It seems that the wlr_drm_connector
gets free'd (or at least has invalid data) by the time we get the pageflip event. It's weird because even if you disconnect an output we keep the wlr_drm_connector
around. Maybe it's because the connector goes away (it's not just disconnected), but in this case this should probably cancel the pageflip? I'm confused.
Another crash log: sway2.log
Sway version 1.0-alpha.6-43-ga032925a (Sep 24 2018, branch 'master')
Managed to unplug today withou crashing, only once though.
Can you try https://github.com/swaywm/wlroots/pull/1268 and say if it fixes your issue?
Unplugging works now, but replugging causes a crash.
Can you run it with valgrind
and paste the logs here?
Took like 5 replug cycles to get a crash.
It's weird because the stack trace (https://pastebin.com/Yq30MLGh) doesn't match with the Valgrind one (https://pastebin.com/Ew6xWpQv).
Can you try again to get a stack trace via coredumpctl gdb
, and run bt full
?
I can reliably get sway to crash everytime when unplugging from dock, even with https://github.com/swaywm/sway/issues/2337.
I can reliably get sway to crash everytime when unplugging from dock, even with #2337.
You probably mean swaywm/wlroots#1268?
Please always include a debug log and a stack trace. It doesn't help a lot to know that "it crashes".
You probably mean
swaywm/wlroots#1268?
Yes, my bad.
Please always include a debug log and a stack
trace.
I'll try and come back.
Updated sway to 1.0-alpha.6-105-g51f68e10
Valgrind and gdb dumps: https://pastebin.com/k4kqS4vR
Seems to be fixed, thank you!
Running
sway version 1.0-alpha.6-47-gc43374cd
on Gentoo Linux. Connecting a Thunderbolt 3 dock with external monitor and other peripherals works, but unplugging the dock makes sway crash (without core dump). I can get swaybg to dump if I do this with wallpaper set.Sway crash log (without swaybg): https://pastebin.com/iT1TqYvi
Swaybg core dump: https://pastebin.com/w5TmPPnQ
Also worth mentioning that nothing crashes if I suspend the machine before unplugging the dock and resume right after.