mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #441] auto start when installed via flatpak #342
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#342
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 @Alexivia on GitHub (Sep 24, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/441
Operating Systems
Server: Windows 10
Client: Ubuntu 18.04
Barrier Version
2.3.1
Question
If I installed Barrier via
flatpakon the client side (linux), how do I make the client auto start? This is because the client is installed on a server to which I have no easy access to the keyboard/mouse, only to its display output, and since I frequently need to reboot the machine, it would be useful if I could promptly start using the keyboard/mouse of the server instead of having to start the Barrier software manually after each restart. Also, the client machine has auto-login enabled, so my user session is started immediately, and I do not require Barrier to run as root.Thank you for your time. Regards,
Alexandre Vieira
@AdrianKoshka commented on GitHub (Sep 24, 2019):
I guess through your desktop-environments auto-start mechanism, you could try to add
flatpak run com.github.debauchee.barrier.@Alexivia commented on GitHub (Sep 25, 2019):
Thank you for your reply! This however does not configure the client to point to the correct server IP, how should I do this?
@AdrianKoshka commented on GitHub (Sep 25, 2019):
Oh, hrm, let me get back to you on that! :)
@MPArnold commented on GitHub (Sep 27, 2019):
Every time I booted Linux I too had to re-input the server IP. Seems to be a wider issue in play; "Barrier client not necessarily retaining server IP across Linux executions." Plus a really good question: "How is it meant to do so!"
Anyway, it's now remembering the IP address! I don't know why but one thing I did was go through the motions of the (client-side) 'Save Configuration'.
To get autostart working I did the following ...
(1) Copy the flatpak desktop to /etc/xdg/autostart/
sudo cp /var/lib/flatpak/app/com.github.debauchee.barrier/current/active/files/share/applications/com.github.debauchee.barrier.desktop /etc/xdg/autostart/(2) Edit the 'Exec' directive
Exec=flatpak run com.github.debauchee.barrierNB: This was on a Debian setup.
@SkOrPn commented on GitHub (Sep 28, 2019):
"Exec=flatpak run com.github.debauchee.barrier"
This did not work on a fresh install of MX-18.3 with an error output of "bash: run: command not found". I had thought that since MX is also based on Debian that your Exec directive edit command would have worked here too. But nope, lol. Probably going to take me a long time to figure out how to auto start Barrier today.
@AdrianKoshka commented on GitHub (Sep 28, 2019):
It seems that bash thought you wanted to execute
runinstead offlatpak run.@SkOrPn commented on GitHub (Sep 28, 2019):
Haha, wow you replied in like a minute after I posted that above. Lol, you must have been sitting waiting for me, haha. J/K
EDIT: Got it working by simply using the built in Auto start in "Session and Startup" manager. Just put that "flatpak run com.github.debauchee.barrier" in the command section and rebooted. It remembered the settings just fine. Thanks for the quick reply.
@AdrianKoshka commented on GitHub (Sep 28, 2019):
No problem, I had just gotten out of bed.
@Alexivia commented on GitHub (Sep 29, 2019):
I too solved my problem using "Session and Startup" manager, but using the Barrier installed from the "Ubuntu Software" app installer, since I figured out it was available through there, and thus uninstalled the flatpack version.
Thank you for all your replies.
@byteshiva commented on GitHub (Nov 23, 2020):
How to specify server address while running flatpak run on "startup and sessions" in ubuntu
@shymega commented on GitHub (Dec 7, 2020):
Just a minor note, but please keep your question in the original issue you made on the Flatpak repo - your question here is not particularly clear either, but also, its best to keep it separate. I have proposed a fix on your original issue.