mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1283] barriers seg faults on start #1025
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#1025
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jbpratt on GitHub (Sep 8, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1283
What happened?
On start of the server, it prints many
can't read property X on window Xdebug2 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).
@SamantazFox commented on GitHub (Sep 21, 2021):
pass
--address 0.0.0.0:24800instead, it will solve the problem :)(And if you use the GUI, specify
0.0.0.0in the address field in the settings)@jbpratt commented on GitHub (Sep 22, 2021):
Woo! @SamantazFox thank you very much! That worked for me 🐱
@SamantazFox commented on GitHub (Sep 26, 2021):
Though, I think you can keep this issue open, because the GUI still passes
:24800, which crashes the server daemon, while it worked in previous version. Looks like a regression to me.@Gollum999 commented on GitHub (Apr 26, 2022):
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.
I think #596, #1246, #1413, and #1544 are duplicates.
@mmguero commented on GitHub (May 18, 2022):
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).
@nrnw commented on GitHub (Nov 21, 2022):
Works like a charm! Thank you :)