github-starred/lan-mouse

Fork 0

mirror of https://github.com/feschber/lan-mouse.git synced 2026-05-15 14:15:52 -06:00

[GH-ISSUE #148] BUG: stoped working after upgrading to Plasma 6.1.0 #66

New issue

Closed

opened 2026-05-05 22:07:41 -06:00 by gitea-mirror · 9 comments

gitea-mirror commented

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

Owner

Originally created by @DrYak on GitHub (Jun 27, 2024).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/148

This morning I updated both my workstation and my laptop's Tumbleweed.

New versions:
Plasma: 6.1.0
KDE Framework: 6.3.0
Qt: 6.7.2

In that environment:

once I move the cursor to the edge, it's not taking over the other machine.
moving the cursor back doesn't return it to the machine
hitting the Ctrl+Alt+Shift+Super sequence doesn't work, still doesn't return the control to the machine.
The only way to return the control is to SSH into the machine and kill lan-mouse

Originally created by @DrYak on GitHub (Jun 27, 2024). Original GitHub issue: https://github.com/feschber/lan-mouse/issues/148 This morning I updated both my workstation and my laptop's Tumbleweed. New versions: Plasma: 6.1.0 KDE Framework: 6.3.0 Qt: 6.7.2 In that environment: - once I move the cursor to the edge, it's not taking over the other machine. - moving the cursor back doesn't return it to the machine - hitting the Ctrl+Alt+Shift+Super sequence doesn't work, still doesn't return the control to the machine. The only way to return the control is to SSH into the machine and kill lan-mouse

gitea-mirror closed this issue

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

gitea-mirror commented

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

Author

Owner

@aksdb commented on GitHub (Jun 27, 2024):

Same with 6.1.1 here.

@aksdb commented on GitHub (Jun 27, 2024): Same with 6.1.1 here.

gitea-mirror commented

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

Author

Owner

@feschber commented on GitHub (Jun 27, 2024):

Ah yeah, I wanted to give an update on this: I originally thought, this would be fixed in plasma 6.1.1 but there turned out to be another issue: Plasma currently does not report barrier ids which I rely on for the libei backend.

You should be able to work around this by compiling with

cargo build --release --no-default-features --features wayland,x11,xdg_desktop_portal,gtk

to disable the libei backend and fallback to layer-shell until it works properly.

Its going to require a workaround or implementation for barrier ids in kwin.

#140

@feschber commented on GitHub (Jun 27, 2024): Ah yeah, I wanted to give an update on this: I originally thought, this would be fixed in plasma 6.1.1 but there turned out to be another issue: Plasma currently does not report barrier ids which I rely on for the libei backend. You should be able to work around this by compiling with ```sh cargo build --release --no-default-features --features wayland,x11,xdg_desktop_portal,gtk ``` to disable the libei backend and fallback to layer-shell until it works properly. Its going to require a workaround or implementation for barrier ids in kwin. #140

gitea-mirror commented

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

Author

Owner

@DrYak commented on GitHub (Jun 27, 2024):

Suggestion: a command line or config file option for individually enabling/disabling protocols?

(so that it would possible to, e.g., lan-mouse --disable-libei even if it is compiled in?)

@DrYak commented on GitHub (Jun 27, 2024): Suggestion: a command line or config file option for individually enabling/disabling protocols? (so that it would possible to, e.g., `lan-mouse --disable-libei` even if it is compiled in?)

gitea-mirror commented

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

Author

Owner

@feschber commented on GitHub (Jun 27, 2024):

Yeah that is probably a good idea. As well as a --force-backend option

@feschber commented on GitHub (Jun 27, 2024): Yeah that is probably a good idea. As well as a `--force-backend` option

gitea-mirror commented

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

Author

Owner

@DrYak commented on GitHub (Jun 27, 2024):

You should be able to work around this by compiling with
cargo build --release --no-default-features --features wayland,x11,xdg_desktop_portal,gtk

BTW, I've updated my OBS package for Tumbleweed to exclude libei.

(I hope there isn't somewhere some Tumbleweed user who was both relying on my home repo project and happens to run Gnome or wherever libei isn't broken 😅 ).

Of course, I'll revert this once:

either Plasma fixes their libei support
or some option would allow to disable libei at runtime instead of compile time

@DrYak commented on GitHub (Jun 27, 2024): > You should be able to work around this by compiling with > ```shell > cargo build --release --no-default-features --features wayland,x11,xdg_desktop_portal,gtk > ``` BTW, I've updated my OBS package for Tumbleweed to exclude libei. (I hope there isn't somewhere some Tumbleweed user who was _both_ relying on my home repo project _and_ happens to run Gnome or wherever libei isn't broken :sweat_smile: ). Of course, I'll revert this once: - either Plasma fixes their libei support - or some option would allow to disable libei at runtime instead of compile time

gitea-mirror commented

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

Author

Owner

@feschber commented on GitHub (Jun 28, 2024):

Duplicate of #140

@feschber commented on GitHub (Jun 28, 2024): Duplicate of #140

gitea-mirror commented

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

Author

Owner

@feschber commented on GitHub (Jun 29, 2024):

or some option would allow to disable libei at runtime instead of compile time

You can revert now :)

@feschber commented on GitHub (Jun 29, 2024): > - or some option would allow to disable libei at runtime instead of compile time You can revert now :)

gitea-mirror commented

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

Author

Owner

@DrYak commented on GitHub (Jul 31, 2024):

Updated my package (after testing locally) to your release 0.9.1 and enabled back compiling libei into it.
Seems to be working nearly(*) all the time! 👍

Speaking about package, once the encryption feature is addressed some time in the future, I'll try to request getting it into the main Tumbleweed repo.

(*): To be honest, I had one single occurrence of this happening on 0.9.1. But I can't reproduce, and one of the two affected machine was a chromebook-like (PineBook Pro) running Manjaro ARM stable with Plasma 6.0, so I suspect this isn't due to libei support and more probably due to the suboptimal Wifi I am currently connecting both machines - e.g. a few dropped packets having left he whole setup in a very weird state. It eventually recovered)

@DrYak commented on GitHub (Jul 31, 2024): Updated my package (after testing locally) to your release 0.9.1 and enabled back compiling libei into it. Seems to be working nearly(*) all the time! :+1: Speaking about package, once the encryption feature is addressed some time in the future, I'll try to request getting it into the main Tumbleweed repo. (*): To be honest, I had one single occurrence of this happening on 0.9.1. But I can't reproduce, and one of the two affected machine was a chromebook-like (PineBook Pro) running Manjaro ARM stable with _Plasma 6.**0**_, so I suspect this isn't due to libei support and more probably due to the suboptimal Wifi I am currently connecting both machines - e.g. a few dropped packets having left he whole setup in a very weird state. It eventually recovered)

gitea-mirror commented

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

Author

Owner

@feschber commented on GitHub (Aug 1, 2024):

Awesome, thank you!

@feschber commented on GitHub (Aug 1, 2024): Awesome, thank you!