mirror of
https://github.com/feschber/lan-mouse.git
synced 2026-05-15 06:06:07 -06:00
[GH-ISSUE #289] Fingerprint not showing on UI - no way to get it #146
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#146
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 @rzuasti on GitHub (Apr 30, 2025).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/289
I just installed 0.10.0 on both a Windows 11 and Arch machines and in either of them the UI shows the fingerprint and I couldn't find it in the console logs. This is my UI on windows:
(I literally only downloaded the release zip file, unzipped it and run the executable).
On arch the icons do appear (I'm using the release from the official arch repo) but the UI doesn't show the encryption fingerprint either.
I can get the two machines to connect if I manually setup the connection in the UI but if I use a config file it wont work.
Is this a bug?
Thanks
@feschber commented on GitHub (May 1, 2025):
You need to download the pre-release for now. Its not in a point release quite yet
@rzuasti commented on GitHub (May 1, 2025):
Thanks, it definitely works on Arch with the AUR git package. Is there a pre-compiled windows snapshot/pre-release?
@feschber commented on GitHub (May 1, 2025):
https://github.com/feschber/lan-mouse/releases/tag/latest
If this does not work for you, check the build instructions for GTK. The windows installer PR is unfortunately not quite ready.
@rzuasti commented on GitHub (May 1, 2025):
Thanks! Made it work flawlessly. It's afaik the only viable option for wayland systems that dont use KDE or GNOME, awesome work.
@feschber commented on GitHub (May 1, 2025):
glad to hear! :) I will close this issue then