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

Socket connection #117

Open
chraibi opened this issue Oct 6, 2022 · 2 comments
Open

Socket connection #117

chraibi opened this issue Oct 6, 2022 · 2 comments

Comments

@chraibi
Copy link

chraibi commented Oct 6, 2022

I recently get this error

spacebar-msg: failed to connect to socket..                                  │

Not sure how to debug it. Maybe someone here has an idea?

@tubbo
Copy link

tubbo commented Oct 8, 2022

is spacebar running? this is what i would assume would happen if you try to run spacebar -m ... without the daemon actually running, since it's connecting over a socket

@chraibi
Copy link
Author

chraibi commented Oct 11, 2022

I guess so. This is how it looks. Notice left the numbers for workspaces are missing:

Screen Shot 2022-10-11 at 07 50 59

Trying to explicitly run spacebar gives the following:

spacebar: could not acquire lock-file! abort..
Often, I solve the problem with source $HOME/.config/spacebar/.spacebarrc but, that is not a nice workaround.
Probably the problem is trivial, but I did not figure it out yet!

Screen Shot 2022-10-11 at 07 53 25

My err.log shows a bunch of the following line: ""*ERROR*: Wrong type argument: listp,. Some process is constantly writing this line in the log. It seems this process is Emacs.

I stopped Emacs, just to check and voila:

Screen Shot 2022-10-11 at 08 03 48

Do you think, Emacs spamming spacebar with these error-messages, is the reason for loosing connection?

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