github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #1784] "Barrier is starting." But not working. #1314

New issue

Open

opened 2026-05-05 07:43:22 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 07:43:22 -06:00

Owner

Originally created by @gregrwm on GitHub (Sep 21, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1784

What happened?

Barrier is stuck at "Barrier is starting." What might i need?

Both boxen have a wire to my modem, are fully updated, and can ssh to each other. Both have this /etc/barrier.conf:

section: screens
        e540:
        eb840g3:
end
section: links
        e540:
                up    = eb840g3
        eb840g3:
                down  = e540
end

i invoked barrier(2.4.0-1)(installed by pacman) on e540(manjaro kde), in the terminal it said:

*** WARNING *** The program 'barrier' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/blog/projects/avahi-compat.html

i found https://github.com/input-leap/input-leap/issues/780 via google but it's not clear to me if the comments solved the issue. Perhaps if i give the server address to the client Barrier doesn't really need avahi?

Not knowing what to make of that i went ahead in the barrier GUI, designated it as 'Server', selected 'Use existing configuration:' at /etc/barrier.conf and clicked 'Start'. in the terminal it said:

("-f", "--no-tray", "--debug", "INFO", "--name", "e540", "--disable-client-cert-checking", "-c", "/etc/barrier.conf", "--address", ":24800")

and in the GUI it says "Barrier is running." Then i invoked barrier(2.4.0-1.7)(installed by zypper) on 3b840g3(tumbleweed kde), designated it as 'Client', 'Auto config', clicked 'Start', in the terminal it said:

("-f", "--no-tray", "--debug", "INFO", "--name", "eb840g3", "[]:24800")

and in the GUI it says "Barrier is starting." Tried uncheck 'Auto config', entered Server IP, clicked 'Reload', 'Stop', and 'Start', in the terminal it said:

("-f", "--no-tray", "--debug", "INFO", "--name", "eb840g3", "[10.3.8.21]:24800")

and in the GUI it still says "Barrier is starting."

Both GUIs say "SSL Fingerprint: Disabled". The manjaro default install has no firewall iiuc. Tumbleweed does, but as client does it need anything open? i tried "firewall-cmd --add-port=24800/tcp" on tumbleweed, and clicked 'Stop' and 'Start' on the Server and then the Client, but no change.

What else might i check, or read, or do?
Many thanks,

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

pacman and zypper, from the default repositories

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

Linux

What OS versions are you using?

server on manjaro kde, client on tumbleweed kde, both are rolling release and up to date

Relevant log output

manjaro/server:
Sep 20 23:51:31 e540 barrier[15783]: *** WARNING *** The program 'barrier' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
Sep 20 23:51:31 e540 barrier[15783]: *** WARNING *** Please fix your application to use the native API of Avahi!
Sep 20 23:51:31 e540 barrier[15783]: *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>
Sep 20 23:51:31 e540 dbus-daemon[399]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.322' (uid=1000 pid=15783 comm="barrier")
Sep 20 23:51:31 e540 dbus-daemon[399]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Sep 20 23:51:31 e540 kded5[720]: Registering ":1.71/StatusNotifierItem" to system tray

tumbleweed/client:
Sep 20 23:53:04 eb840g3 kded5[1999]: Registering ":1.75/StatusNotifierItem" to system tray

Any other information

No response

Originally created by @gregrwm on GitHub (Sep 21, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1784 ### What happened? Barrier is stuck at "Barrier is starting." What might i need? Both boxen have a wire to my modem, are fully updated, and can ssh to each other. Both have this /etc/barrier.conf: ``` section: screens e540: eb840g3: end section: links e540: up = eb840g3 eb840g3: down = e540 end ``` i invoked barrier(2.4.0-1)(installed by pacman) on e540(manjaro kde), in the terminal it said: >*** WARNING *** The program 'barrier' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. >*** WARNING *** Please fix your application to use the native API of Avahi! >*** WARNING *** For more information see http://0pointer.de/blog/projects/avahi-compat.html i found https://github.com/input-leap/input-leap/issues/780 via google but it's not clear to me if the comments solved the issue. Perhaps if i give the server address to the client Barrier doesn't really need avahi? Not knowing what to make of that i went ahead in the barrier GUI, designated it as 'Server', selected 'Use existing configuration:' at /etc/barrier.conf and clicked 'Start'. in the terminal it said: >("-f", "--no-tray", "--debug", "INFO", "--name", "e540", "--disable-client-cert-checking", "-c", "/etc/barrier.conf", "--address", ":24800") and in the GUI it says "Barrier is running." Then i invoked barrier(2.4.0-1.7)(installed by zypper) on 3b840g3(tumbleweed kde), designated it as 'Client', 'Auto config', clicked 'Start', in the terminal it said: >("-f", "--no-tray", "--debug", "INFO", "--name", "eb840g3", "[]:24800") and in the GUI it says "Barrier is starting." Tried uncheck 'Auto config', entered Server IP, clicked 'Reload', 'Stop', and 'Start', in the terminal it said: >("-f", "--no-tray", "--debug", "INFO", "--name", "eb840g3", "[10.3.8.21]:24800") and in the GUI it still says "Barrier is starting." Both GUIs say "SSL Fingerprint: Disabled". The manjaro default install has no firewall iiuc. Tumbleweed does, but as client does it need anything open? i tried "firewall-cmd --add-port=24800/tcp" on tumbleweed, and clicked 'Stop' and 'Start' on the Server and then the Client, but no change. What else might i check, or read, or do? Many thanks, ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? pacman and zypper, from the default repositories ### What OSes are you seeing the problem on? (Check all that apply) Linux ### What OS versions are you using? server on manjaro kde, client on tumbleweed kde, both are rolling release and up to date ### Relevant log output ```shell manjaro/server: Sep 20 23:51:31 e540 barrier[15783]: *** WARNING *** The program 'barrier' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. Sep 20 23:51:31 e540 barrier[15783]: *** WARNING *** Please fix your application to use the native API of Avahi! Sep 20 23:51:31 e540 barrier[15783]: *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html> Sep 20 23:51:31 e540 dbus-daemon[399]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.322' (uid=1000 pid=15783 comm="barrier") Sep 20 23:51:31 e540 dbus-daemon[399]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found. Sep 20 23:51:31 e540 kded5[720]: Registering ":1.71/StatusNotifierItem" to system tray tumbleweed/client: Sep 20 23:53:04 eb840g3 kded5[1999]: Registering ":1.75/StatusNotifierItem" to system tray ``` ### Any other information _No response_

gitea-mirror commented

2026-05-05 07:43:25 -06:00

Author

Owner

@gregrwm commented on GitHub (Sep 23, 2022):

on one device barrier is running but on other device its stuck at "barrier is starting", tried all the steps above..
In the server mode it is running but on client mode it's stuck at starting on both devices..
Server mode works, client mode doesn't
Same for me. Says SSL disabled, no firewall on manjaro, disabled tumbleweed firewall, swapped which is server and which is client, whichever is client just says "Barrier is starting."

@gregrwm commented on GitHub (Sep 23, 2022): [on one device barrier is running but on other device its stuck at "barrier is starting", tried all the steps above.. In the server mode it is running but on client mode it's stuck at starting on both devices.. Server mode works, client mode doesn't](https://github.com/debauchee/barrier/issues/480#issuecomment-1016527493) Same for me. Says SSL disabled, no firewall on manjaro, disabled tumbleweed firewall, swapped which is server and which is client, whichever is client just says "Barrier is starting."

gitea-mirror commented

2026-05-05 07:43:26 -06:00

Author

Owner

@gregrwm commented on GitHub (Sep 23, 2022):

just found synergy also in manjaro&tumbleweed repos, and it works

@gregrwm commented on GitHub (Sep 23, 2022): just found synergy also in manjaro&tumbleweed repos, and it works

gitea-mirror commented

2026-05-05 07:43:28 -06:00

Author

Owner

@octoshrimpy commented on GitHub (Oct 20, 2022):

check #1812 as it may have been firewall shenanigans

@octoshrimpy commented on GitHub (Oct 20, 2022): check #1812 as it may have been firewall shenanigans

gitea-mirror commented

2026-05-05 07:43:29 -06:00

Author

Owner

@HCley commented on GitHub (May 23, 2024):

just found synergy also in manjaro&tumbleweed repos, and it works

Sorry, but
What have you done? I'm still stuck on that.

@HCley commented on GitHub (May 23, 2024): > just found synergy also in manjaro&tumbleweed repos, and it works Sorry, but What have you done? I'm still stuck on that.

gitea-mirror commented

2026-05-05 07:43:30 -06:00

Author

Owner

@gregrwm commented on GitHub (Jun 7, 2024):

i found "synergy" in my (opensuse tumbleweed) repos and i'm using it, it works.

@gregrwm commented on GitHub (Jun 7, 2024): i found "synergy" in my (opensuse tumbleweed) repos and i'm using it, it works.

gitea-mirror commented

2026-05-05 07:43:32 -06:00

Author

Owner

@nosbig commented on GitHub (Oct 1, 2024):

In case it becomes useful in the future to the author or others, here's how I fixed the issue.

I had the same symptoms, and I used the troubleshooting steps to narrow the scope of the issue. Specifically, I used "sudo ss -tunlp | grep 24800" once the server process was running to confirm the process and IP and port pairing the Barrier server process was using. As it turned out, my Barrier server process was binding to 127.0.1.1, which isn't obviously on the correct network.

I stopped the server process, manually set my server address in the settings dialog to my internal IP address in my 192.168.1.0/24 network. Once I restarted the process and re-ran the "ss" command, I saw the proper binding. To cross the t's and dot the i's, I also ran a "telnet 192.168.1.100 24800" (where 192.168.1.100 is the IP address of my server in this example) and verified that the server process returned text of "Barrier" indicating that it was ready for connections.

It was at this point that I was able to return to my client system and attempt to start the client process. From there, I was able to start the process successfully, configure the screen location, and immediately use Barrier as intended.

@nosbig commented on GitHub (Oct 1, 2024): In case it becomes useful in the future to the author or others, here's how I fixed the issue. I had the same symptoms, and I used the troubleshooting steps to narrow the scope of the issue. Specifically, I used "sudo ss -tunlp | grep 24800" once the server process was running to confirm the process and IP and port pairing the Barrier server process was using. As it turned out, my Barrier server process was binding to 127.0.1.1, which isn't obviously on the correct network. I stopped the server process, manually set my server address in the settings dialog to my internal IP address in my 192.168.1.0/24 network. Once I restarted the process and re-ran the "ss" command, I saw the proper binding. To cross the t's and dot the i's, I also ran a "telnet 192.168.1.100 24800" (where 192.168.1.100 is the IP address of my server in this example) and verified that the server process returned text of "Barrier" indicating that it was ready for connections. It was at this point that I was able to return to my client system and attempt to start the client process. From there, I was able to start the process successfully, configure the screen location, and immediately use Barrier as intended.

No labels

Rows
Columns