Phase 1 fprintd shim — end-to-end success evidence =================================================== Date: 2026-10-15 Host: lunar (Arch, GNOME Shell 51 / GDM 51, Wayland, session id 3) Installed service ----------------- /etc/systemd/system/fprintd.service -> work/fprintd-shim/fprintd.service Active: active (running) — serves net.reactivated.Fprint on the system bus (work/fprintd-shim/install.sh, authorized via the fingerprint reader itself) CLI (/usr/bin/fprintd-list) --------------------------- $ fprintd-list nebulon found 1 devices Device at /net/reactivated/Fprint/Device/0 Using device /net/reactivated/Fprint/Device/0 Fingerprints for user nebulon on Synaptics 06cb:0081 (press): - #0: right-index-finger Shell reader detection (same calls as libshell-51.so -> fingerprintManager.js) ------------------------------------------------------------------------------ GetDefaultDevice -> /net/reactivated/Fprint/Device/0 (service auto-started) scan-type -> press => GNOME reader type PRESS (fingerprint mechanism enabled) fprintd-verify (CLI match path) ------------------------------- $ timeout 50 fprintd-verify -f any nebulon Using device /net/reactivated/Fprint/Device/0 Listing enrolled fingers: - #0: right-index-finger Verify started! / Verifying: right-index-finger Verify result: verify-match (done) fprintd-verify rc=0 (An earlier run matched but exited 1 because VerifyStop returned NoActionInProgress after the terminal result; the shim now keeps fprintd's "action in progress" semantics until VerifyStop/Release.) Rollback test (uninstall -> stock fprintd -> reinstall) ------------------------------------------------------- $ sudo work/fprintd-shim/uninstall.sh; fprintd-list nebulon No devices available <- stock fprintd took over $ sudo work/fprintd-shim/install.sh; fprintd-list nebulon Fingerprints for user nebulon on Synaptics 06cb:0081 (press): - #0: right-index-finger pam_fprintd end-to-end (isolated, pam_start_confdir) ---------------------------------------------------- $ /tmp/opencode/pamtest3 -d /tmp/opencode/pam-confdir -s fprintd-test nebulon service=fprintd-test user=nebulon confdir=/tmp/opencode/pam-confdir (touch the sensor) pam_authenticate => 0 (Success) Real lock screen (loginctl lock-session 3, then touch) ------------------------------------------------------ journalctl -u fprintd: 2026-10-15T11:59:01+02:00 fprintd-shim: INFO: claim by :1.2046 for user nebulon 2026-10-15T11:59:06+02:00 fprintd-shim: INFO: verify[1]: Fingerprint matched. 2026-10-15T11:59:06+02:00 fprintd-shim: INFO: claiming client :1.2046 vanished, releasing device ...and the session unlocked (loginctl LockedHint: yes -> no) without a password entry: pam_fprintd disconnects on PAM_SUCCESS (the shim releases the claim via NameOwnerChanged, exactly like fprintd's client-vanished handling). API semantics regression (session bus, no touch) ------------------------------------------------ work/fprintd-shim/apitest.py -> all checks passed: GetDevices, ListEnrolledFingers (enrolled vs other user), Claim twice -> AlreadyInUse, VerifyStart unclaimed -> ClaimDevice, VerifyStart/Release from non-claimer -> AlreadyInUse, unenrolled finger -> NoEnrolledPrints, claim auto-release when the claiming client disconnects. Operational notes ----------------- - Earlier failed `sudo` attempts (fingerprint auth misses) tripped pam_faillock ("User nebulon is temporarily locked out due to 3 consecutive failed login attempts") which blocked the gdm-fingerprint PAM stack before pam_fprintd ran. Reset with: sudo faillock --user nebulon --reset - sudo / polkit are unchanged and still use work/pam/pam_fp.so. - work/fp-verify.sh takes an flock so concurrent verifications (sudo + lock screen) serialize on the USB device.