-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
barriers seg faults on start #1283
Comments
pass |
Woo! @SamantazFox thank you very much! That worked for me 🐱 |
Though, I think you can keep this issue open, because the GUI still passes |
I am also running into this issue. @SamantazFox's workaround seems to fix it for me, but obviously would be nice if the GUI worked. |
Same issue for me, I was able to work around it by manually launching barriers and specifying the address but for the server the GUI is unusable (Debian 11 amd64). |
Works like a charm! Thank you :) |
What happened?
On start of the server, it prints many
can't read property X on window X
debug2 logs then seg faults.Version
v2.3.3
Git commit hash (if applicable)
No response
If applicable, where did you install Barrier from?
https://archlinux.org/packages/community/x86_64/barrier/
What OSes are you seeing the problem on? (Check all that apply)
Linux
What OS versions are you using?
Linux server and client both running 2.3.3-release
Relevant log output
Any other information
This was working without issue last week (and the past 6 months) but failed to start this morning. I unplugged monitors to do some cleaning and cable management, so maybe that is a cause. I swapped the server and client around, things are working fine to get around this. I have an absolute minimal config (just the single screen name).
The text was updated successfully, but these errors were encountered: