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
Please note that xorg-server 1.16 is rootless compared to the older versions, so I guess it's a permission error. Manual deletion of the socket file allows me to start bspwm again.
The text was updated successfully, but these errors were encountered:
If bspwm exits normally, it deletes its socket file.
What I need here is a backtrace of bspwm crashing, not the strace output of bspwm failing to start (with an explicit error message) because of a remnant socket file.
Here's some hints on how you might provide the relevant output: #62 (comment)
After quitting bspwm countless times, it's impossible for me to reproduce this anymore.
There were several updated packages for Xorg, so maybe it has something to do with it. I'll close this bug report for now and will attach a gdb stacktrace (and reopen this bug report) if this happens again some time in the future.
I have been able to reproduce bspwm crashing; however, I can't manage to get the debugging working (if I recall propertly, I couldn't manage to "set logging on" and "bt full"). Any other way to do the debugging?
..resulting in a crash after trying to start bspwm a second time
Distro: Arch Linux x86_64
Strace log: https://gist.github.com/vorenon/6522a0aa979f14905648
Please note that xorg-server 1.16 is rootless compared to the older versions, so I guess it's a permission error. Manual deletion of the socket file allows me to start bspwm again.
The text was updated successfully, but these errors were encountered: