mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1544] Segfault on launching server #1162
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#1162
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 @zoitrok on GitHub (Jan 30, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1544
What happened?
GUI keeps trying to restart the server. Looks like a SIGSEGV. I've tried debugging it by compiling the latest HEAD and running the server from a terminal. Applicable logs attached.
Version
From Git HEAD or commit (specify below)
Git commit hash (if applicable)
433126e7a1If applicable, where did you install Barrier from?
Self-built from latest HEAD. AUR and flatpak 2.4.0 give the same results.
What OSes are you seeing the problem on? (Check all that apply)
Linux
What OS versions are you using?
Manjaro - rolling release, 2022-01-30.
Relevant log output
Any other information
No response
@lumotroph commented on GitHub (Feb 4, 2022):
Same on Ubuntu via Snap and apt
@zoitrok commented on GitHub (Feb 5, 2022):
Seems that manually putting my local IP address in the commandline such as:
bin/barriers -f --no-tray --debug DEBUG2 --name hubert --disable-client-cert-checking -c /home/zoi/barrier.conf --address 10.2.2.15:24800works.The GUI client claims to run with the parameters as in the bug report above, and thus fails.
@SamantazFox commented on GitHub (Apr 27, 2022):
Yep, you need to specifiy the address to listen on. Without it (so
--address :24800), the server crashes.Idk why, though.