Skip to content
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

bspwm is unable to delete the socket file after upgrading to xorg-server 1.16 #163

Closed
ghost opened this issue Jul 31, 2014 · 3 comments
Closed

Comments

@ghost
Copy link

ghost commented Jul 31, 2014

..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.

@baskerville
Copy link
Owner

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)

@ghost
Copy link
Author

ghost commented Jul 31, 2014

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.

@ghost ghost closed this as completed Jul 31, 2014
@vimeitor
Copy link

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?

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants