mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #290] [SOLVED] Barrier wont start and exits with Error Code 4 #234
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#234
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 @TheCire on GitHub (Apr 14, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/290
Operating Systems
Server: macOS Mojave Version 10.14.4
Client: No client yet, can't get server to run
Barrier Version
2.10-RELEASE-8b69f9fe
Steps to reproduce bug
I have no idea how to reproduce this, for some reason Barrier just decided to stop working.
Other info
When did the problem start to occur? When I... try and start the server
Is there a way to work around it? No
Does this bug prevent you from using Barrier entirely? Yes
Here's the brief log file:
here's my very simple config file (i turned to manual config file because interactive wouldn't work), also I got the config file from here and modified that :
@TheCire commented on GitHub (Apr 15, 2019):
So apparently even after deleting the app removing the prefs in the specified macOS "private" directory and removing the prefs from
~/Library/Preferencesi took a look at one of the barrier auto generated config files and it turns out it was remembering settings for some reason... anyway it was remembering my hot key config and was referencing a non-existent Computer name/client so... that was causing it to error out.