github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #29] Barriers works stand-alone, but when ran as systemd user unit, fails to start. #19

New issue

Closed

opened 2026-05-05 04:44:33 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 04:44:33 -06:00

Owner

Originally created by @AdrianKoshka on GitHub (Apr 21, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/29

Operating Systems

Server: Linux

Client: Linux

Server linux version: Fedora 27

Client linux version: Debian stretch

Barrier Version

barriers 2.0.0-RELEASE, protocol version 1.6

Steps to reproduce bug

plop systemd user unit in ~/.config/systemd/user/barriers@.service

[Unit]
Description=Barrier keyboard & mouse sharing software
After=network.target

[Service]
PassEnvironment=DISPLAY
ExecStart=%h/.local/bin/barriers --address %i --no-restart --no-daemon --config %h/.config/Synergy/desktops.conf
Type=simple
ProtectHome=read-only
ProtectSystem=true
ReadWritePaths=%h/.config/Synergy
Restart=always
RestartSec=10

[Install]
WantedBy=alc.target # not really important or needed for debugging

1.5. supply your own config
2. run systemctl --user daemon-reload
3. run systemctl --user start barriers@::1.service
4. it will fail with (code=exited, status=4) when checking systemctl --user status barriers@::1.serivce

Other info

If I run barriers stand-alone, outside of a systemd user unit, it just works. Also unrelated to this issue, but barrierc happily runs as a systemd user unit.

Originally created by @AdrianKoshka on GitHub (Apr 21, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/29 ### Operating Systems ### Server: Linux Client: Linux Server linux version: Fedora 27 Client linux version: Debian stretch ### Barrier Version ### barriers 2.0.0-RELEASE, protocol version 1.6 ### Steps to reproduce bug ### 1. plop systemd user unit in `~/.config/systemd/user/barriers@.service` ```ini [Unit] Description=Barrier keyboard & mouse sharing software After=network.target [Service] PassEnvironment=DISPLAY ExecStart=%h/.local/bin/barriers --address %i --no-restart --no-daemon --config %h/.config/Synergy/desktops.conf Type=simple ProtectHome=read-only ProtectSystem=true ReadWritePaths=%h/.config/Synergy Restart=always RestartSec=10 [Install] WantedBy=alc.target # not really important or needed for debugging ``` 1.5. supply your own config 2. run `systemctl --user daemon-reload` 3. run `systemctl --user start barriers@::1.service` 4. it will fail with `(code=exited, status=4)` when checking `systemctl --user status barriers@::1.serivce` ### Other info ### If I run `barriers` stand-alone, outside of a systemd user unit, it just works. Also unrelated to this issue, but `barrierc` happily runs as a systemd user unit.

gitea-mirror closed this issue

2026-05-05 04:44:36 -06:00

gitea-mirror commented

2026-05-05 04:44:41 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Apr 21, 2018):

False alarm... desktops.conf is supopsed to be desktops.config from my old synergy config, solved this myself.

@AdrianKoshka commented on GitHub (Apr 21, 2018): False alarm... `desktops.conf` is supopsed to be `desktops.config` from my old synergy config, solved this myself.

gitea-mirror commented

2026-05-05 04:44:45 -06:00

Author

Owner

@ghost commented on GitHub (Jun 7, 2018):

@AdrianKoshka Thanks for that service file! Can you tell me what that alc.target is? I can't find anything about. Also what is the reason to use --no-restart and --no-daemon flag?

@ghost commented on GitHub (Jun 7, 2018): @AdrianKoshka Thanks for that service file! Can you tell me what that `alc.target` is? I can't find anything about. Also what is the reason to use `--no-restart` and `--no-daemon` flag?

gitea-mirror commented

2026-05-05 04:44:48 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Jun 7, 2018):

Oh, alc.target is a custom systemd target I wrote. the --no-restart flag means barrier won't try to restart itself, and the --no-daemon flag means it won't fork itself into the background.

@AdrianKoshka commented on GitHub (Jun 7, 2018): Oh, `alc.target` is a custom systemd target I wrote. the `--no-restart` flag means barrier won't try to restart itself, and the `--no-daemon` flag means it won't fork itself into the background.

gitea-mirror commented

2026-05-05 04:44:51 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Jun 7, 2018):

@glumanda99 if you're interested, all my unit files are in this repo: https://github.com/adriankoshka/config

@AdrianKoshka commented on GitHub (Jun 7, 2018): @glumanda99 if you're interested, all my unit files are in this repo: https://github.com/adriankoshka/config

gitea-mirror commented

2026-05-05 04:44:55 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Jun 7, 2018):

Here's the documentation for how I have barrier seutp: https://github.com/AdrianKoshka/config/wiki/My-barrier-setup

@AdrianKoshka commented on GitHub (Jun 7, 2018): Here's the documentation for how I have barrier seutp: https://github.com/AdrianKoshka/config/wiki/My-barrier-setup

gitea-mirror commented

2026-05-05 04:44:58 -06:00

Author

Owner

@ghost commented on GitHub (Jun 7, 2018):

@AdrianKoshka Thanks for your fast response and detailed descriptions! It works great and was one of the reasons I switched to barrier as the 1.8 branch of synergy won't fix running it from systemd service.

@ghost commented on GitHub (Jun 7, 2018): @AdrianKoshka Thanks for your fast response and detailed descriptions! It works great and was one of the reasons I switched to barrier as the 1.8 branch of synergy won't fix running it from systemd service.

gitea-mirror referenced this issue

2026-05-05 07:56:03 -06:00

[PR #19] [MERGED] Add ipv6 support #1545