-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
-
Symptom:
face-auth camera-testfails or crashes. -
Fix: Check your device path in
config.yaml. The default is0or/dev/video0. If you have multiple cameras (or IR emitters), you might need/dev/video2. -
Command:
ls -l /dev/video*to see available devices.
- Symptom: Python import errors.
-
Fix: Ensure you are running commands inside the virtual environment (
source venv/bin/activate) or using theface-authwrapper script which handles this for you.
-
Fix: Face recognition is sensitive to lighting. Use
face-auth add-sampleto add 3-5 more samples in the challenging lighting condition.
- Symptom: NumPy/dlib import fails with missing library error.
-
Fix: Install BLAS libraries. The installer should do this automatically with
sudo ./install.sh. Manual fix:# Fedora/RHEL sudo dnf install openblas blas lapack # Ubuntu/Debian sudo apt install libopenblas-dev libblas-dev liblapack-dev # Arch sudo pacman -S openblas
-
Fix: Check logs with
journalctl --user -u face-auth-monitor -e. EnsureDISPLAYandXAUTHORITYenvironment variables are correctly set in the service file (installer handles this, but manual moves might break it).
Q: Does this work with IR cameras (Windows Hello hardware)?
A: It works with the video stream from them, but Linux Hello currently uses standard OpenCV/dlib libraries which are optimized for RGB. It does not yet leverage specific IR depth features for anti-spoofing in the same way Howdy does, but it will function if the camera outputs a video feed.
Q: Can I use this for root?
A: Yes, if you use the PAM module with sudo. However, we recommend keeping a password for root operations for security.
Q: Where is my face data stored?
A: ~/.local/share/face-auth/face_auth.db. It is an encrypted SQLite database.
Q: I'm locked out!
A: If PAM fails, it falls back to password. If you somehow broke PAM entirely, boot into a live USB, chroot, and revert changes to /etc/pam.d/.
- Check if face-auth is installed:
which face-auth - Test manually:
face-auth pam-authenticate $USER - Check PAM config:
grep face-auth /etc/pam.d/sudo
sudo sed -i '/pam_exec.so.*face-auth/d' /etc/pam.d/sudo
sudo sed -i '/pam_exec.so.*face-auth/d' /etc/pam.d/gdm-password- High CPU usage during enrollment (dlib dependency).
- Rotation invariance adds latency (checking 4 orientations).
- Conflict with other apps using the camera (only one app can access
/dev/video0at a time).