search

r-c-f / waynergy

A synergy client for Wayland compositors
MIT License
423 stars 17 forks source link

Unable to synchronise the protocol when run from KDE autostart #104

Open majenkotech opened 4 months ago

majenkotech commented 4 months ago

I think this is basically because autostart runs waynergy before the network is available, and once the network is available, waynergy is in such a bad way that it really doesn't know how to talk its own native tongue.

Stopping and restarting the autostart job allows waynergy to then connect properly and synchronise the protocol.

Unfortunately autostart has no way of copying the log text, so you'll have to make do with a screenshot...

Screenshot_20240702_124055

This is communicating with a barrier server on Linux KDE X11.

majenkotech commented 4 months ago

Actually.... Now I have managed to get a logfile out of waynergy, I think I see the problem.

Hostname.

When the system boots it has a default hostname (I've not named this installation yet) of archlinux. Then DHCP finally kicks in and renames it to the proper computer name which the barrier server is expecting. waynergy picks up the initial hostname when it first loads from autoload, and tries connecting with that, and fails. And keeps trying with that. Even when the hostname is changed by DHCP to the correct name, it still keeps trying the old one.

I know... "Just name the computer" and I guess I should, but this is a "floating" installation on a removable drive and I want it to set the hostname according to the computer it's plugged into through DHCP.

So it would be nice if, when a hostname hasn't been specified on the command line with --name, it would get the current system hostname each time it tried to connect, rather than just once at the start of execution. That way when DHCP changes the hostname it can start communicating properly with the server without having to be restarted.

r-c-f commented 4 months ago

Does #106 resolve this for you?