[GH-ISSUE #842] Client loses server IP if server is unavailable at startup #668

New issue

Closed

opened 2026-05-05 06:52:33 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 06:52:33 -06:00

Owner

Originally created by @txtad on GitHub (Aug 18, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/842

Operating Systems

Server: Linux Mint 20: Linux tadpc 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Client: Linux Mint 20: Linux tadpc 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Barrier Version

dpkg -l: 2.3.2+dfsg-1build1
Help->About: 2.3.2-Release-00000000

Steps to reproduce bug

Configure a server and client machine, get them working with Barrier
Turn them off
Turn on the client machine first
Turn on the server machine next
The client machine will not be connected and will lose the IP address of the server. The IP address of the server will have to be re-typed into the client

Other info

When did the problem start to occur? When I started using Barrier
Is there a way to work around it? Yes, be mindful of the machines' startup order
Does this bug prevent you from using Barrier entirely? No

Other versions

I would have built 2.3.3 to test with that, but libqt4-dev isn't easily available on Mint 20.

Originally created by @txtad on GitHub (Aug 18, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/842 ### Operating Systems ### Server: Linux Mint 20: Linux tadpc 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Client: Linux Mint 20: Linux tadpc 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ### Barrier Version ### dpkg -l: 2.3.2+dfsg-1build1 Help->About: 2.3.2-Release-00000000 ### Steps to reproduce bug ### * Configure a server and client machine, get them working with Barrier * Turn them off * Turn on the client machine first * Turn on the server machine next * The client machine will not be connected and will lose the IP address of the server. The IP address of the server will have to be re-typed into the client ### Other info ### * When did the problem start to occur? When I started using Barrier * Is there a way to work around it? Yes, be mindful of the machines' startup order * Does this bug prevent you from using Barrier entirely? No ### Other versions ### I would have built 2.3.3 to test with that, but libqt4-dev isn't easily available on Mint 20.

gitea-mirror closed this issue

2026-05-05 06:52:35 -06:00

gitea-mirror commented

2026-05-05 06:52:37 -06:00

Author

Owner

@txtad commented on GitHub (Aug 21, 2020):

It turns out that I had misdiagnosed the problem. It wasn't the order of startup, but rather I needed to log out of Cinnamon once on the client to get Barrier to save the server IP. Once I did that, it starts up and reliably connects on auto-login.

@txtad commented on GitHub (Aug 21, 2020): It turns out that I had misdiagnosed the problem. It wasn't the order of startup, but rather I needed to log out of Cinnamon once on the client to get Barrier to save the server IP. Once I did that, it starts up and reliably connects on auto-login.

gitea-mirror referenced this issue

2026-05-05 06:57:16 -06:00

[GH-ISSUE #868] error The XTest extension ... ‘XIEventMask’ ... on ./clean_build.sh #693