[GH-ISSUE #1287] No configuration available #1029

Open
opened 2026-05-05 07:23:42 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @drschwabe on GitHub (Sep 12, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1287

What happened?

Is there anything I am doing wrong?

flatpak run --command=barriers com.github.debauchee.barrier --config /home/derrick/barrierServer.conf
> barriers: no configuration available

The file is there and it is saved config from the GUI; the GUI works fine I just wanted to start calling it from terminal today so I can launch this on all my machines on boot.

Version

v2.3.3

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

No response

What OSes are you seeing the problem on? (Check all that apply)

Linux

What OS versions are you using?

Ubuntu 20

Relevant log output

No response

Any other information

No response

Originally created by @drschwabe on GitHub (Sep 12, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1287 ### What happened? Is there anything I am doing wrong? ```bash flatpak run --command=barriers com.github.debauchee.barrier --config /home/derrick/barrierServer.conf > barriers: no configuration available ``` The file is there and it is saved config from the GUI; the GUI works fine I just wanted to start calling it from terminal today so I can launch this on all my machines on boot. ### Version v2.3.3 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? _No response_ ### What OSes are you seeing the problem on? (Check all that apply) Linux ### What OS versions are you using? Ubuntu 20 ### Relevant log output _No response_ ### Any other information _No response_
gitea-mirror added the
bug
label 2026-05-05 07:23:42 -06:00
Author
Owner

@dayne commented on GitHub (Sep 16, 2021):

I don't use flatpak but I have a guess as to what is going on here. If I understand flatpak tries to sandbox applications limiting their access to the broader filesystem.

https://docs.flatpak.org/en/latest/sandbox-permissions.html

You may have to add a --filesystem=home option to your call.

Report back if you figure out what the fix is for this. If that doesn't work it might inspire me to setup a system using the flatpak to test it out.

<!-- gh-comment-id:921219830 --> @dayne commented on GitHub (Sep 16, 2021): I don't use flatpak but I have a guess as to what is going on here. If I understand flatpak tries to sandbox applications limiting their access to the broader filesystem. https://docs.flatpak.org/en/latest/sandbox-permissions.html You may have to add a `--filesystem=home` option to your call. Report back if you figure out what the fix is for this. If that doesn't work it might inspire me to setup a system using the flatpak to test it out.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#1029
No description provided.