fprintd: Failed to start Tudor host process <...> NoReply: Remote peer disconnected #38
Comments
|
Update: I tried the solution from #14 (and did a restart), unfortunately, it didn't help |
|
It seems like the host launcher is failing to claim its D-Bus name, which causes communication issues. This might be because of it being unable to claim the name (maybe the D-Bus policy isn't picked up?), or maybe there being conflicting claims. |
|
Thank you for your answer, sorry for answering late. I tried to reinstall with recompiling, but it unfortunately hadn't changed situation at all :( Log from terminal (no errors, everything looks perfectly fine) ➜ build git:(relink) sudo ninja uninstall
[sudo] password for evil:
[0/1] /usr/bin/meson --internal uninstall
Deleted: /sbin/tudor/libtudor.so
Deleted: /sbin/tudor/tudor_cli
Deleted: /sbin/tudor/tudor_host
Deleted: /sbin/tudor/tudor_host_launcher
Deleted: /usr/local/lib64/libfprint-2/tod-1/libtudor_tod.so
Deleted: /usr/lib/systemd/system/tudor-host-launcher.service
Deleted: /usr/share/dbus-1/system.d/net.reactivated.TudorHostLauncher.conf
Deleted: /usr/share/dbus-1/system-services/net.reactivated.TudorHostLauncher.service
Deleted: /usr/lib/udev/60-tudor-libfprint-tod.rules
Uninstall finished.
Deleted: 9
Failed: 0
Remember that files created by custom scripts have not been removed.
➜ build git:(relink) ninja clean
[2/2] Cleaning
Cleaning... 85 files.
➜ build git:(relink) cd ..
➜ synaTudor git:(relink) git pull
Already up to date.
➜ synaTudor git:(relink) cd build
➜ build git:(relink) ninja
[78/84] Generating libtudor/driver-download with a custom command
[0] Downloading 'https://download.lenovo.com/pccbbs/mobiles/r19fp02w.exe' ...
Saving 'libtudor/synaFpAdapter104.dll.p/installer.exe'
HTTP response 200 OK [https://download.lenovo.com/pccbbs/mobiles/r19fp02w.exe]
Extracting "version 6.0.33.1104(Synaptics FingerPrint FM3463 Driver)(R19FP02W)" - setup data version 5.5.7 (unicode)
- "code$GetExtractPath$/synaWudfBioUsbUwpSgx.inf" - overwritten
- "code$GetExtractPath$/Setup.bat"
- "code$GetExtractPath$/sgx_capable.dll"
- "code$GetExtractPath$/synaDriverLoader104.dll"
- "code$GetExtractPath$/synaFpAdapter104.dll"
- "code$GetExtractPath$/synaTEE104.signed.dll"
- "code$GetExtractPath$/synaumdfsgx.cat"
- "code$GetExtractPath$/synaWudfBioUsb104.dll"
- "code$GetExtractPath$/synaWudfBioUsbSGX104.dll"
- "code$GetExtractPath$/synaWudfBioUsbUwpSgx.inf"
Done.
[84/84] Linking target tudor-host/tudor_host
➜ build git:(relink) sudo ninja install
[0/1] Installing files.
Installing libtudor/libtudor.so to /sbin/tudor
Installing cli/tudor_cli to /sbin/tudor
Installing tudor-host/tudor_host to /sbin/tudor
Installing tudor-host-launcher/tudor_host_launcher to /sbin/tudor
Installing libfprint-tod/libtudor_tod.so to /usr/local/lib64/libfprint-2/tod-1
Installing /home/evil/Cloned/synaTudor/tudor-host-launcher/tudor-host-launcher.service to /usr/lib/systemd/system
Installing /home/evil/Cloned/synaTudor/tudor-host-launcher/net.reactivated.TudorHostLauncher.conf to /usr/share/dbus-1/system.d
Installing /home/evil/Cloned/synaTudor/build/tudor-host-launcher/net.reactivated.TudorHostLauncher.service to /usr/share/dbus-1/system-services
Installing /home/evil/Cloned/synaTudor/libfprint-tod/60-tudor-libfprint-tod.rules to /usr/lib/udevThere I did a full reboot (just in case) ➜ ~ fprintd-enroll
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
➜ ~ systemctl restart fprintd.service
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have
06cb:00beand experienced the same issue as described in #35. After 1d08e98 commit is made I git-pulled the repo and tried to reinstall everything as described in readme.My environment is ThinkPad L15 Gen 1 with Fedora 41, libfprint-tod is from quantt corp repo
dnf list:journalctl:
Also, unrelated, but
ninja installscript moveslibtudor_tod.soto/usr/local/lib64/<...>, but libfprint-tod checks/usr/lib64/<...>, so I movedlibtudor_tod.soto/usr/lib64/libfprint-2/tod-1/, maybe install script needs a fixjournalctl:
The text was updated successfully, but these errors were encountered: