htrefil / rkvm

Virtual KVM switch for Linux machines
MIT License
426 stars 51 forks source link

Enter key inop when server running, new lines #60

Open bashprompt opened 9 months ago

bashprompt commented 9 months ago

I have been appreciating rkvm for a few months now, without issues. Today when the server is running my enter key is inop. I see older posts about this. Whether rkvm-server is started using systemctl start or from the commandline the RETURN is inop until I kill the server via an ssh session. (I see you have a timeout option as well.)

When I start the server from a terminal new lines start and continue indefinitely. If I start the server using systemctl or systemctl from a bash script the effect is the same.

I'm an experienced linux user, not a programmer. If there is any info I can provide let me know.

I tried it in an X session as well as wayland. Rebooted. Rebuilt from latest release tarball.

OS: openSUSE Tumbleweed x86_64 Kernel: 6.7.6-1-default Shell: bash 5.2.26 WM: sway Terminal: kitty CPU: AMD Ryzen 5 2600 (12) @ 3.400GHz GPU: NVIDIA GeForce GTX 1050 3GB

I have been very impressed with rkvm, especially being able to share the mouse and kb independent of the desktop environment.

bashprompt commented 9 months ago

Wayland: If in a wayland session (either sway or gnome-wayland), and rkvm is started from a terminal with sudo systemctl start rkvm-server There will be dozens of new lines and an inop Return key. The Return key won't work until rkvm-server is stopped -OR- I log out of the wayland session and back in again. The keyboard works normally on the rkvm client while the return key is inop on the server machine

If rkvm-server is started from a script that also runs sudo systemctl start rkvm-server and is run as root using visudo settings, sometimes everything works ok and other times the same symptoms occur. Tests are inconsistent.

Xorg

If I am in an X session rkvm server does not cause a problem when started from a terminal. This contradicts the issue above, but the X problems do not duplicate.

tty If I drop to a tty and start rkvm-server with sudo systemctl everything works ok in the wayland sessions.

tedesque commented 2 months ago

Wayland: If in a wayland session (either sway or gnome-wayland), and rkvm is started from a terminal with sudo systemctl start rkvm-server There will be dozens of new lines and an inop Return key. The Return key won't work until rkvm-server is stopped -OR- I log out of the wayland session and back in again. The keyboard works normally on the rkvm client while the return key is inop on the server machine

If rkvm-server is started from a script that also runs sudo systemctl start rkvm-server and is run as root using visudo settings, sometimes everything works ok and other times the same symptoms occur. Tests are inconsistent.

Xorg

If I am in an X session rkvm server does not cause a problem when started from a terminal. This contradicts the issue above, but the X problems do not duplicate.

tty If I drop to a tty and start rkvm-server with sudo systemctl everything works ok in the wayland sessions.

I had same behavior on PoP-OS! running on wayland. Starting service by systemctl with sudo in TTY rkvm runs like charm, but trying with terminal on wayland I can connect and ENTER key not working on server machine.

vitaminmoo commented 1 month ago

Could this maybe be caused by the enter key being held down while rkvm starts?

vitaminmoo commented 1 month ago

Maybe sleep 1 && systemctl start rkvm-server as a test

mrceperka commented 6 days ago

Maybe sleep 1 && systemctl start rkvm-server as a test

This did the trick, thanks!