Hi and thanks for your post,
having downloaded synergy-v1.8.8-stable-Linux-x86_64.deb from your link (thanks for that)
I still couldn´t install it. A variety of packets have unfulfilled/unmet dependencies.
Just as an example: libqtcore4 […] but cannot be installed.
There are three more of those.
Never mind. Thanks anyway.
Greetings.
Rosika 
where did you get a package for 18.04? i looked and only saw one for 20.04.
Hi,
I followed the link @daniel.m.tripp provided:
https://www.brahma.world/synergy-stable-builds/ .
And there: https://github.com/brahma-dev/synergy-stable-builds/releases/download/v1.8.8-stable/synergy-v1.8.8-stable-Linux-x86_64.deb
Cheers.
Rosika
i should have been more clear with my question 
i was trying to find a barrier package for 18.04 to test and see if i run into the same difficulties you are having. i saw packages for 19.10 and 20.04 on the parent page of where you posted your support request. i did also see a snap and flatpak available, but was wondering if you had come across a package specifically for 18.04.
Did you run “sudo apt -f install” after you got unmet dependancies? Even installing Pro version I have to do that after installing the DEB file with dpkg command…
@daniel.m.tripp:
Hi,
thanks for your suggestion. I didn´t run “sudo apt -f install”.
It didn´t occur to me as the remark “but cannot be installed” threw me off.
I´ll try that and report back as soon as possible.
Thanks again.
Cheers.
Rosika
Hi again,
in the meantime I ran “sudo apt -f install” but it changed nothing.
Nothing ro remove, to install or to update.
Again the syngergy installation process says:
[…]
Die folgenden Pakete haben unerfüllte Abhängigkeiten:
synergy : Hängt ab von: libqtcore4 (>= 4.6.2) ist aber nicht installierbar
Hängt ab von: libqtgui4 (>= 4.6.2) ist aber nicht installierbar
Hängt ab von: libqt4-network (>= 4.6.2) ist aber nicht installierbar
Hängt ab von: libcurl3 (>= 7.19.7) ist aber nicht installierbar
All those libs cannot be installed.
Well then. At least barrier should run.
And so far I can say it´s the client side which poses problems.
The server side says: “Barrier is running” but the client says: “Barrier is starting”.
So I looked up the logs (from client) which say:
[2020-07-12T14:04:57] INFO: starting client
[2020-07-12T14:04:57] INFO: config file: /tmp/Barrier.TJ2435
[2020-07-12T14:04:57] INFO: log level: INFO
[2020-07-12T14:04:58] NOTE: started client
[2020-07-12T14:04:58] NOTE: connecting to '192.168.2.50': 192.168.2.50:24800
[2020-07-12T14:05:13] WARNING: failed to connect to server: Timed out
[2020-07-12T14:05:14] NOTE: connecting to '192.168.2.50': 192.168.2.50:24800
[2020-07-12T14:05:29] WARNING: failed to connect to server: Timed out
[2020-07-12T14:05:30] NOTE: connecting to '192.168.2.50': 192.168.2.50:24800
[2020-07-12T14:05:45] WARNING: failed to connect to server: Timed out
[2020-07-12T14:05:46] NOTE: connecting to '192.168.2.50': 192.168.2.50:24800
[2020-07-12T14:06:01] WARNING: failed to connect to server: Timed out
[2020-07-12T14:06:02] NOTE: connecting to '192.168.2.50': 192.168.2.50:24800
[2020-07-12T14:06:17] WARNING: failed to connect to server: Timed out
[2020-07-12T14:06:18] NOTE: connecting to '192.168.2.50': 192.168.2.50:24800
[2020-07-12T14:06:33] INFO: stopping barrier desktop process
[2020-07-12T14:06:33] NOTE: stopped client
[2020-07-12T14:06:33] INFO: process exited normally
So it´s basically “failed to connect to server” which is the problem.
Greetings.
Rosika
Do you have to provide the IP address manually or do you use the server’s hostname?
Hi,
I suppose you are referring to my barrier setup.
On the client it looks like this:
Screen name: rosika-e6222 (which is my laptop/client)
Server IP: 192.168.2.50 (which is my PC/server)
Basically I had to enter the server´s IP.
is the server running a firewall?
on the Server:
sudo nc -tlvp 1337
on the Client:
sudo nc -vz 192.168.2.50 1337
And make sure the ports are not blocked by a firewall.
SUCCESS!!!
Well I´ll be blessed. It´s the firewall which is the culprit after all.
I wouldn´t have thought. After all this time of exploring and fiddling… 
I did think of that in the beginning and switched my firewall off with the help of the GUI (both on the server and on the client) but it didn´t have any effect.
Now I did it with CLI:
sudo ufw disable. And suddenly it works!!! Perfect.
Thank you so much. 
But now I have to figure out a respective rule so that my firewall can keep running.
I know it´s port 24800 which is used.
Thank you so much. 
Greetings.
Rosika 
ufw allow 24800/tcp
That´s it. It works.
Thanks a lot. I wouldn´t have know the exact syntax (especially the “/tcp”-part).
I did that just on the server.
Seems I don´t have to do that on the client.
I´m so pleased.
Many thanks to all of you for your great help. 
Cheers and greetings.
Rosika
that’s what made me think of asking 
glad to hear you got it all figured out.
The port needs to be opened only on a server. Generally/usually, servers are the ones needing to open a port, because they listen for connections to arrive. Generally/usually, clients connect to servers and need to open only outgoing ports, which are usually open by default, except you are in a high security environment.
Yes, I noticed that too at the time.
Therefore I switched off the firewall altogether with the GUI.
I still don´t know why that didn´t have any effect. So I dismissed the idea which it now turns out
was false.
I see. Thank you for the clarification.
I´m always glad to learn something new (at least for me it´s new 
).
Now I understand. My laptop as a client uses an incoming port so it doesn´t have to be dealt with.
Thanks a lot again.
Geetings.
Rosika
Client → outgoing port
Server → incoming port
I think you just mistyped there. 
Oh, seems I misunderstood.
I thought as the server transmits my mouse signal it uses the port 24800 in a way that the signal is sent out.
And on the client side this port is used to receive the signal. So I associated it with “incoming”.
Sorry if I got that wrong.