[GH-ISSUE #955] Question: How to auto configure client setup before login using flatpak barrier #768

Closed
opened 2026-05-05 07:02:51 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @byteshiva on GitHub (Nov 22, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/955

How to auto configure client setup before login in linux distro using flatpak barrier (https://flathub.org/apps/details/com.github.debauchee.barrier) .

I'm using mxlinx 19.02.
uname -a Linux 5.8.0-3-amd64 #1 SMP Debian 5.8.14-1~mx19+2 x86_64 GNU/Linux

I know how to do it when installed on host machine using apt installation.

ps aux | grep barrier
/app/bin/barrierc -f --no-tray --debug INFO --name desktop --enable-crypto [192.168.9.3]:24800

But I'm not sure how to do it when done using flatpak installation.

I'm wondering if the below command will work in linux distro.

flatpak run --command="barrierc -f --no-tray --debug INFO --name desktop --enable-crypto [192.168.9.3]:24800" com.github.debauchee.barrier

Originally created by @byteshiva on GitHub (Nov 22, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/955 How to auto configure client setup before login in linux distro using flatpak barrier (https://flathub.org/apps/details/com.github.debauchee.barrier) . I'm using mxlinx 19.02. ` uname -a Linux 5.8.0-3-amd64 #1 SMP Debian 5.8.14-1~mx19+2 x86_64 GNU/Linux ` I know how to do it when installed on host machine using apt installation. ``` ps aux | grep barrier /app/bin/barrierc -f --no-tray --debug INFO --name desktop --enable-crypto [192.168.9.3]:24800 ``` ~But I'm not sure how to do it when done using flatpak installation.~ I'm wondering if the below command will work in linux distro. ` flatpak run --command="barrierc -f --no-tray --debug INFO --name desktop --enable-crypto [192.168.9.3]:24800" com.github.debauchee.barrier `
gitea-mirror 2026-05-05 07:02:51 -06:00
  • closed this issue
  • added the
    invalid
    label
Author
Owner

@shymega commented on GitHub (Nov 22, 2020):

I can see you've already opened a issue on the Flatpak repo too. Please don't cross-post; it makes more work for us.

Closing in favour of the Flatpak repo issue. Alternatively, I can reopen if you want, and close the Flatpak repo issue.

<!-- gh-comment-id:731768237 --> @shymega commented on GitHub (Nov 22, 2020): I can see you've already opened a issue on the Flatpak repo too. Please don't cross-post; it makes more work for us. Closing in favour of the Flatpak repo issue. Alternatively, I can reopen if you want, and close the Flatpak repo issue.
Author
Owner

@byteshiva commented on GitHub (Nov 23, 2020):

My Mistake. Sorry for that, Initially I thought this was for barrier flatpak. Later found a separate repository so that's the reason behind cross post.

<!-- gh-comment-id:732354929 --> @byteshiva commented on GitHub (Nov 23, 2020): My Mistake. Sorry for that, Initially I thought this was for barrier flatpak. Later found a separate repository so that's the reason behind cross post.
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#768
No description provided.