Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
majenkotech opened this issue Jul 2, 2024 · 2 comments
Open

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

majenkotech opened this issue Jul 2, 2024 · 2 comments

Comments

@majenkotech
Copy link

majenkotech commented Jul 2, 2024 •
edited
Loading

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
Copy link
Author

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 added a commit that referenced this issue Jul 5, 2024
@r-c-f
Update hostname on each connection attempt
e556649 
Per #104, some users are setting hostname via dhcp, which may be
delayed, and desktop environment autostart doesn't necessarily allow for
accounting for this. So call gethostname() on connection, rather than on
startup.
@r-c-f r-c-f mentioned this issue Jul 5, 2024
Open
@r-c-f
Copy link
Owner

r-c-f commented Jul 5, 2024

Does #106 resolve this for you?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@majenkotech @r-c-f