github-starred/barrier
2
0
Fork 0
mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00
Code Issues 1.0k Projects Packages Wiki Activity Actions

[GH-ISSUE #327] No route to host, but can ping #260

New issue
Closed
opened 2026-05-05 05:52:18 -06:00 by gitea-mirror · 3 comments
gitea-mirror commented 2026-05-05 05:52:18 -06:00
Owner
Copy link

Originally created by @chriselrod on GitHub (May 30, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/327

Operating Systems

Server: Fedora 30 (x11)

Client: Clear Linux

Barrier Version

2.2.0
Clear Linux: flatpak
Fedora: flatpak install segfaults (on org.kde.Platform), so I built the 2.2.0 release tarball from source.

Their snapshots ids are different: 53eb... vs 0000.....
Is this a problem?

Steps to reproduce bug

  1. Install as described above.
  2. Give the server and client a name in change settings (F4); input their local ip addresses in the networking address field.
  3. Configure the server, inputting client and server names.
  4. Restart both barrier instances, to make sure name changes took effect.
  5. On client, enter the host ip address.
  6. Start server. Check log, confirm waiting for clients.
  7. Start client with debug level log info. Get
NOTE: connecting to `SERVERIP`: `SERVERIP`:24800 (24800=port in settings of both server&client)
DEBUG: Opening new socket RANDOMHEXSTRING
DEBUG: event queue is ready
DEBUG: Closing socket: SAMERANDOMHEXSTRING
DEBUG: retry in 1 seconds
WARNING: failed to connect to server: No route to host

This repeats until I stop the client (with different sockets).
On the client, I can successfully ping the SERVERIP.

I connected this client to the same server (hardware-wise) succesfully before, back when the server installed Barrier with flatpak.
A workaround that lets me use Barrier is to swap the client and server.

I could try building barrier from source on the client if the snapshot ids must also be an exact match, but I'd have to figure out the appropriate dependencies.
EDIT: An equivalent to libavahi-compat-libdnssd-dev/avahi-compat-libdns_sd-devel does not seem to be available on the client OS.
EDIT: I set log level to debug2:

[2019-05-30T13:54:37] DEBUG: starting process

[2019-05-30T13:54:37] INFO: starting client
[2019-05-30T13:54:37] INFO: command: /app/bin/barrierc -f --no-tray --debug DEBUG2 --name clr7900 [192.168.0.8]:24800
[2019-05-30T13:54:37] INFO: config file: /tmp/Barrier.QBEPeD
[2019-05-30T13:54:37] INFO: log level: DEBUG2
[2019-05-30T13:54:37] DEBUG1: starting client
[2019-05-30T13:54:37] DEBUG: XOpenDisplay(":99.0")
[2019-05-30T13:54:37] DEBUG1: thread 0x00000002 entry
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020000c
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020000d
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020000f
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200011
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200013
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200015
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200171
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200182
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020001d
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200037
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200162
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200168
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200042
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200048
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200017
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200019
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200054
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200611
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020001b
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200030
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200621
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020061f
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200618
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200616
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00600009
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00800001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00800033
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00e00001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00e00002
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01000001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0140000f
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01600001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400016
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400019
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01a00001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01e00001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0140002d
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400031
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01800001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00c00004
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00c00008
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00c00018
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01c00004
[2019-05-30T13:54:37] DEBUG: xscreensaver window: 0x00000000
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020000c
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020000d
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020000f
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200011
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200013
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200015
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200171
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200182
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020001d
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200037
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200162
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200168
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200042
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200048
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200017
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200019
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200054
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200611
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020001b
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200030
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200621
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020061f
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200618
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200616
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00600009
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00800001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00800033
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00e00001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00e00002
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01000001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0140000f
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01600001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400016
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400019
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01a00001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01e00001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0140002d
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400031
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01800001
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00c00004
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00c00008
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00c00018
[2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01c00004
[2019-05-30T13:54:37] DEBUG: screen shape: 0,0 1920x1080 
[2019-05-30T13:54:37] DEBUG: window is 0x01c00004
[2019-05-30T13:54:37] DEBUG: adopting new buffer
[2019-05-30T13:54:37] DEBUG: opened display
[2019-05-30T13:54:37] DEBUG1: registered event type error as 4
[2019-05-30T13:54:37] DEBUG1: registered event type suspend as 5
[2019-05-30T13:54:37] DEBUG1: registered event type resume as 6
[2019-05-30T13:54:37] DEBUG1: registered event type connected as 7
[2019-05-30T13:54:37] DEBUG1: registered event type connectionFailed as 8
[2019-05-30T13:54:37] DEBUG1: registered event type disconnected as 9
[2019-05-30T13:54:37] NOTE: started client
[2019-05-30T13:54:37] NOTE: connecting to '192.168.0.8': 192.168.0.8:24800
[2019-05-30T13:54:37] DEBUG: Opening new socket: EB7F3AD0
[2019-05-30T13:54:37] DEBUG1: connecting to server
[2019-05-30T13:54:37] DEBUG1: registered event type connected as 10
[2019-05-30T13:54:37] DEBUG1: registered event type connectionFailed as 11
[2019-05-30T13:54:37] DEBUG: event queue is ready
[2019-05-30T13:54:37] DEBUG1: registered event type inputReady as 12
[2019-05-30T13:54:37] DEBUG1: registered event type inputShutdown as 13
[2019-05-30T13:54:37] DEBUG: Closing socket: EB7F3AD0
[2019-05-30T13:54:37] DEBUG1: connection failed
[2019-05-30T13:54:37] DEBUG: retry in 1 seconds
[2019-05-30T13:54:37] WARNING: failed to connect to server: No route to host
[2019-05-30T13:54:38] DEBUG: stopping process
[2019-05-30T13:54:38] INFO: stopping barrier desktop process
[2019-05-30T13:54:38] NOTE: connecting to '192.168.0.8': 192.168.0.8:24800
[2019-05-30T13:54:38] DEBUG: Opening new socket: 14000C90
[2019-05-30T13:54:38] DEBUG1: connecting to server
[2019-05-30T13:54:38] DEBUG1: stopping client
[2019-05-30T13:54:38] DEBUG1: registered event type outputError as 14
[2019-05-30T13:54:38] DEBUG1: registered event type outputShutdown as 15
[2019-05-30T13:54:38] DEBUG1: registered event type disconnected as 16
[2019-05-30T13:54:38] DEBUG1: registered event type stopRetry as 17
[2019-05-30T13:54:38] DEBUG: Closing socket: 14000C90
[2019-05-30T13:54:38] DEBUG: adopting new buffer
[2019-05-30T13:54:38] DEBUG: closed display
[2019-05-30T13:54:38] NOTE: stopped client
[2019-05-30T13:54:38] DEBUG1: caught cancel on thread 0x00000002
[2019-05-30T13:54:38] INFO: process exited normally

EDIT:
It works when switching rolls (ie, flatpak + Clear Linux == server, source build + Fedora == client).

Originally created by @chriselrod on GitHub (May 30, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/327 ### Operating Systems ### Server: Fedora 30 (x11) Client: Clear Linux ### Barrier Version ### 2.2.0 Clear Linux: flatpak Fedora: flatpak install segfaults (on org.kde.Platform), so I built the 2.2.0 release tarball from source. Their snapshots ids are different: 53eb... vs 0000..... Is this a problem? ### Steps to reproduce bug ### 1. Install as described above. 2. Give the server and client a name in change settings (F4); input their local ip addresses in the networking address field. 3. Configure the server, inputting client and server names. 4. Restart both barrier instances, to make sure name changes took effect. 5. On client, enter the host ip address. 6. Start server. Check log, confirm `waiting for clients`. 7. Start client with debug level log info. Get ``` NOTE: connecting to `SERVERIP`: `SERVERIP`:24800 (24800=port in settings of both server&client) DEBUG: Opening new socket RANDOMHEXSTRING DEBUG: event queue is ready DEBUG: Closing socket: SAMERANDOMHEXSTRING DEBUG: retry in 1 seconds WARNING: failed to connect to server: No route to host ``` This repeats until I stop the client (with different sockets). On the client, I can successfully ping the `SERVERIP`. I connected this client to the same server (hardware-wise) succesfully before, back when the server installed Barrier with flatpak. A workaround that lets me use Barrier is to swap the client and server. I could try building barrier from source on the client if the snapshot ids must also be an exact match, but I'd have to figure out the appropriate dependencies. EDIT: An equivalent to `libavahi-compat-libdnssd-dev`/`avahi-compat-libdns_sd-devel` does not seem to be available on the client OS. EDIT: I set log level to debug2: ``` [2019-05-30T13:54:37] DEBUG: starting process [2019-05-30T13:54:37] INFO: starting client [2019-05-30T13:54:37] INFO: command: /app/bin/barrierc -f --no-tray --debug DEBUG2 --name clr7900 [192.168.0.8]:24800 [2019-05-30T13:54:37] INFO: config file: /tmp/Barrier.QBEPeD [2019-05-30T13:54:37] INFO: log level: DEBUG2 [2019-05-30T13:54:37] DEBUG1: starting client [2019-05-30T13:54:37] DEBUG: XOpenDisplay(":99.0") [2019-05-30T13:54:37] DEBUG1: thread 0x00000002 entry [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020000c [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020000d [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020000f [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200011 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200013 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200015 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200171 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200182 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020001d [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200037 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200162 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200168 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200042 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200048 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200017 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200019 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200054 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200611 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020001b [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200030 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200621 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020061f [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200618 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200616 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00600009 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00800001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00800033 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00e00001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00e00002 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01000001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0140000f [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01600001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400016 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400019 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01a00001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01e00001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0140002d [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400031 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01800001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00c00004 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00c00008 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00c00018 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01c00004 [2019-05-30T13:54:37] DEBUG: xscreensaver window: 0x00000000 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020000c [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020000d [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020000f [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200011 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200013 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200015 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200171 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200182 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020001d [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200037 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200162 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200168 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200042 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200048 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200017 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200019 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200054 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200611 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020001b [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200030 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200621 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0020061f [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200618 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00200616 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00600009 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00800001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00800033 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00e00001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00e00002 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01000001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0140000f [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01600001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400016 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400019 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01a00001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01e00001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x0140002d [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01400031 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01800001 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00c00004 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00c00008 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x00c00018 [2019-05-30T13:54:37] DEBUG2: can't read property 494 on window 0x01c00004 [2019-05-30T13:54:37] DEBUG: screen shape: 0,0 1920x1080 [2019-05-30T13:54:37] DEBUG: window is 0x01c00004 [2019-05-30T13:54:37] DEBUG: adopting new buffer [2019-05-30T13:54:37] DEBUG: opened display [2019-05-30T13:54:37] DEBUG1: registered event type error as 4 [2019-05-30T13:54:37] DEBUG1: registered event type suspend as 5 [2019-05-30T13:54:37] DEBUG1: registered event type resume as 6 [2019-05-30T13:54:37] DEBUG1: registered event type connected as 7 [2019-05-30T13:54:37] DEBUG1: registered event type connectionFailed as 8 [2019-05-30T13:54:37] DEBUG1: registered event type disconnected as 9 [2019-05-30T13:54:37] NOTE: started client [2019-05-30T13:54:37] NOTE: connecting to '192.168.0.8': 192.168.0.8:24800 [2019-05-30T13:54:37] DEBUG: Opening new socket: EB7F3AD0 [2019-05-30T13:54:37] DEBUG1: connecting to server [2019-05-30T13:54:37] DEBUG1: registered event type connected as 10 [2019-05-30T13:54:37] DEBUG1: registered event type connectionFailed as 11 [2019-05-30T13:54:37] DEBUG: event queue is ready [2019-05-30T13:54:37] DEBUG1: registered event type inputReady as 12 [2019-05-30T13:54:37] DEBUG1: registered event type inputShutdown as 13 [2019-05-30T13:54:37] DEBUG: Closing socket: EB7F3AD0 [2019-05-30T13:54:37] DEBUG1: connection failed [2019-05-30T13:54:37] DEBUG: retry in 1 seconds [2019-05-30T13:54:37] WARNING: failed to connect to server: No route to host [2019-05-30T13:54:38] DEBUG: stopping process [2019-05-30T13:54:38] INFO: stopping barrier desktop process [2019-05-30T13:54:38] NOTE: connecting to '192.168.0.8': 192.168.0.8:24800 [2019-05-30T13:54:38] DEBUG: Opening new socket: 14000C90 [2019-05-30T13:54:38] DEBUG1: connecting to server [2019-05-30T13:54:38] DEBUG1: stopping client [2019-05-30T13:54:38] DEBUG1: registered event type outputError as 14 [2019-05-30T13:54:38] DEBUG1: registered event type outputShutdown as 15 [2019-05-30T13:54:38] DEBUG1: registered event type disconnected as 16 [2019-05-30T13:54:38] DEBUG1: registered event type stopRetry as 17 [2019-05-30T13:54:38] DEBUG: Closing socket: 14000C90 [2019-05-30T13:54:38] DEBUG: adopting new buffer [2019-05-30T13:54:38] DEBUG: closed display [2019-05-30T13:54:38] NOTE: stopped client [2019-05-30T13:54:38] DEBUG1: caught cancel on thread 0x00000002 [2019-05-30T13:54:38] INFO: process exited normally ``` EDIT: It works when switching rolls (ie, flatpak + Clear Linux == server, source build + Fedora == client).
gitea-mirror commented 2026-05-05 05:52:23 -06:00
Author
Owner
Copy link

@noisyshape commented on GitHub (May 30, 2019):

The most likely explanation is a firewall on the server. You can take the Barrier client out of the equation by connecting to the server with netcat or telnet. Any connection should show up in the server log.

<!-- gh-comment-id:497467915 --> @noisyshape commented on GitHub (May 30, 2019): The most likely explanation is a firewall on the server. You can take the Barrier client out of the equation by connecting to the server with netcat or telnet. Any connection should show up in the server log.
gitea-mirror commented 2026-05-05 05:52:25 -06:00
Author
Owner
Copy link

@AdrianKoshka commented on GitHub (May 30, 2019):

I noticed you're using fedora, did you open the port for barrier (likely labelled for synergy) in the firewall fedora ships with?

Here's a screenshot of my firewall settings from cockpit, notice the synergy entry:
firewall

<!-- gh-comment-id:497484202 --> @AdrianKoshka commented on GitHub (May 30, 2019): I noticed you're using fedora, did you open the port for barrier (likely labelled for synergy) in the firewall fedora ships with? Here's a screenshot of my firewall settings from cockpit, notice the synergy entry: ![firewall](https://user-images.githubusercontent.com/8690255/58664370-80748480-82fc-11e9-8c08-8932291792cf.png)
gitea-mirror commented 2026-05-05 05:52:27 -06:00
Author
Owner
Copy link

@chriselrod commented on GitHub (May 30, 2019):

Indeed, it was the firewall. I opened the port/tcp on the command line (I should look into cockpit, if it can restrict the port to only Synergy/Barrier, that'd be more secure -- although my router should block anything from outside the network accessing that port, so I assume this ought to be fine; my other linux distros don't have a firewall afterall).

Now Fedora works as the server. Thanks!

<!-- gh-comment-id:497511632 --> @chriselrod commented on GitHub (May 30, 2019): Indeed, it was the firewall. I opened the port/tcp on the command line (I should look into cockpit, if it can restrict the port to only Synergy/Barrier, that'd be more secure -- although my router should block anything from outside the network accessing that port, so I assume this ought to be fine; my other linux distros don't have a firewall afterall). Now Fedora works as the server. Thanks!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
enhancement/builds/windows-multi-versions-build
martin-furter-barrier-term
enhancement/builds/macos-universal
enhancement/builds/macos-universal-qt6-test
2.3.x
fix/lang-translation/ssl-slash-tls
feature/build/compile/32-bit
feature/build/compile/armv7
testing-framework
README-update
remotes/fork/README-update
remotes/fork/smartzeroconf
smartzeroconf
pages-devel
remotes/fork/pages-devel
pkgconfig
remotes/fork/pkgconfig
release
remotes/fork/release
v2.4.0
v2.3.4
v2.3.3
1.11.0-stable
v1.11.0-rc2
v2.3.2
v1.10.3-stable
v2.3.2-alpha
v2.3.1
v2.3.0
v1.10.2-stable
v1.10.2-rc1
v1.10.2-rc2
v2.1.2
v2.0.8-beta
v2.0.7-beta
v2.0.4-beta
v2.0.3-beta
v2.1.1
v2.1.0
v1.9.1-stable
v2.0.0
v1.9.0-stable
v2.0.0-RC2
v2.0.0-RC1
v2.0.0-stable
v1.8.8-stable
v1.8.7-stable
v1.8.6-stable
v1.8.5-stable
v1.8.4-stable
v1.8.3-stable
v1.8.1-stable
v1.8.0-beta
v1.7.3-stable
v1.7.2-stable
v1.7.1-stable
1.7.0
1.6.3-final
1.6.2
1.6.1
1.6.0
Labels
Clear 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

Mirrored from GitHub Pull Request

  
query

   
question

   
regression

   
regression

   
v2.4.0

   
windows

   
wontfix

   
work-in-progress
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#260
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?