mirror of
https://github.com/feschber/lan-mouse.git
synced 2026-05-15 14:15:52 -06:00
[GH-ISSUE #196] On Fedora KDE 40 the port won't open #89
Labels
No labels
Xorg
documentation
enhancement
macos
pull-request
question
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/lan-mouse#89
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @livexia on GitHub (Sep 10, 2024).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/196
After launch both lan-mouse both on macOS and Linux, I found that the port on Fedora won't open.
On Fedora I can add macOS as a client but I got
input capture exited: error creating input-capture: no backend availableas expected. So macOS port is open.But other way around there is no log on Fedora. I tested with
nc -l 4242on Fedora. On macOS I can usingncto test, and connection is succeeded. Also running lan-mouse while runningncwith same port,ncrun as normal.Firewalld: 1025-65535 udp/tcp ports are open.

@livexia commented on GitHub (Sep 10, 2024):
macOS logs:
@livexia commented on GitHub (Sep 10, 2024):
Fedora logs:
@feschber commented on GitHub (Sep 10, 2024):
It looks like you have not added the respective clients on both devices:
Make sure to add the Mac on the Linux device and vice verca.
This is necessary even when only controlling one device from the other one (#164) and will change once #104 is resolved.
@livexia commented on GitHub (Sep 10, 2024):
macos

@livexia commented on GitHub (Sep 10, 2024):
Fedora
@feschber commented on GitHub (Sep 10, 2024):
for some reason you seem to be receiving events form port 4222 instead of 4242:
Did you change the port in the configuration file?
@livexia commented on GitHub (Sep 10, 2024):
Sorry for the confusion, I change the port for testing, the port is indeed open. But I can't pass macOS to Fedora, and pass Fedora to macOS lead to Fedora cursor invisibe.
@feschber commented on GitHub (Sep 10, 2024):
I'm assuming, you are using version 0.9.1?
In that case only Fedora -> MacOS will work.
On latest git, you should be able to control fedora from the mac as well, but make sure to use the exact same version in that case!
Regardless: Could you try port 4242 on both devices? There might be an issue with the port not being displayed correctly.
@livexia commented on GitHub (Sep 10, 2024):
yes 0.9.1, but Fedora -> MacOS didn't work, cursor became invisible. KDE has a feature when shake cursor, cursor become bigger, so even the cursor is invisible when I shake cursor, I still can see the cursor in the Fedora. Also click and keyboard don't work.After I disable Fedora in macOS the cursor become usable again.
Maybe I should just try install the git version?
@feschber commented on GitHub (Sep 10, 2024):
It sounds like its not a connection issue.
Did you get a prompt on the mac device to allow lan-mouse to control the device?
To confirm that this is configured correctly, you can run
from a terminal (on macos)
This should make the cursor move in a loop.
(you can cancel it via CTRL+C)
@livexia commented on GitHub (Sep 10, 2024):
Yes cursor move in a loop.
@livexia commented on GitHub (Sep 10, 2024):
No luck with git version. First time launch on macOS there is a popup asking internet access. But still unable to connect either.
there is a panicked in the macOS log.
@feschber commented on GitHub (Sep 10, 2024):
okay this seems to be the issue, did this log show up earlier as well?
@livexia commented on GitHub (Sep 10, 2024):
don't think so.
@livexia commented on GitHub (Sep 10, 2024):
I am using a global target location config for cargo, I will
cargo cleanand rebuild see if this help.@feschber commented on GitHub (Sep 10, 2024):
the "Failed creating tap:" error is usually because the controlling this device setting is disabled.
You could help me out by sending a tracelog from both devices when trying to move the cursor across.
To do that, run it via
or
depending on how you set things up.
@livexia commented on GitHub (Sep 10, 2024):
Wow, Before I also run lan-mouse through ssh, I think my problem is because of this.If I run it by the machine, it just works on both way.
Running without the ssh the error is no more.
I will try run through the ssh to capture the logs for you. But I think my problem is my laziness, Thank you very much, what a great project.
@feschber commented on GitHub (Sep 10, 2024):
Interesting. It could be that the service kept running in the background somehow.
@livexia commented on GitHub (Sep 10, 2024):
with ssh:
@livexia commented on GitHub (Sep 10, 2024):
I think the panic occur because of the new mac capture support.
When I launch through the ssh, there is lots of logs like
[2024-09-10T18:24:45Z TRACE lan_mouse::server::emulation_task] Enter(0) <-<-<-<------ 192.168.31.127:4242appers in macOS log. So macOS must got the Fedora input but unable to emulate it.@livexia commented on GitHub (Sep 10, 2024):
Also there is a interesting problem, that the scroll direction is opposite. I am not using invert scroll on both machine.
@livexia commented on GitHub (Sep 10, 2024):
Maybe I have to get used to it. For now this is working good, thanks for you help and your project, maybe I should close this issue.
@feschber commented on GitHub (Sep 10, 2024):
Yeah it's a bit weird on macos. It also ignores the natural scroll setting iirc.
After the emulation panic occurs it makes sense that it cant emulate it but it should be unrelated to the input capture PR.
I will need to work on better error handling in macos and handle this case better.
@livexia commented on GitHub (Sep 10, 2024):
I am very confuse right now because of this, but I think I can live with it. I will close this issue now, you are doing a great job thanks again.
@feschber commented on GitHub (Sep 10, 2024):
glad I could help :)