Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Fingerprint enrollment hangs on EgisTec EH570 (1c7a:0570) — sensor detected but driver can't communicate during enrollment
Reported by 7kulk37 · filed Sep 5, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
What happened
Omarchy 4.0.2-1 on Arch Linux with kernel 7.1.9-arch1-2.
The EgisTec EH570 fingerprint sensor (1c7a:0570) is correctly detected by the kernel and libfprint — fprintd-list shows the device and fprintd-enroll begins without error. However, enrollment hangs indefinitely waiting for sensor responses that never arrive.
The egis0570 driver is loaded and the device is claimed, but the init packet sequence never completes. Neither the stock libfprint 1.94.100 nor libfprint-git 1.94.10.r12.gd79f157 nor the community libfprint-egismoc-sdcp-git driver resolves the issue.
Steps to reproduce
- Install Omarchy on a laptop with EgisTec EH570 fingerprint sensor
- Run
omarchy setup security fingerprint - Sensor is detected ("Using device /net/reactivated/Fprint/Device/0")
fprintd-enrollhangs indefinitely — no enrollment completes- Ctrl+C to abort, then
fprintd-verifyshows "No enrolled prints"
System details
- OS: Omarchy 4.0.2-1 (Arch Linux)
- Kernel: 7.1.9-arch1-2
- CPU: Intel i5-1035G1 (Ice Lake)
- GPU: Intel Iris Plus Graphics G1
- RAM: 7.4 GiB, NVMe 512 GB
- Sensor: LighTuning Technology Inc. EgisTec Touch Fingerprint Sensor (
1c7a:0570,bcdDevice 10.41) - fprintd: 1.94.5-2
- libfprint: 1.94.100 (stock), 1.94.10.r12.gd79f157 (git), and 1.94.9 (egismoc-sdcp-git) — all exhibit the same hang
What works
- Kernel detects the sensor:
usb 3-5: Product: EgisTec Touch Fingerprint Sensor - libfprint detects the device:
fprintd-listshows "found 1 devices" - Device is properly claimed by fprintd
- udev rules are correctly configured (70-libfprint-2.rules with 1c7a:0570)
What doesn't work
fprintd-enrollhangs — the egis0570 driver sends init packets but the sensor never responds- The enrollment state machine (SM_INIT → SM_START → SM_REQ → SM_RESP) gets stuck waiting for a response that never arrives
- The driver has
EGIS0570_TIMEOUT 10000(10s) per packet round, and the full init sequence has multiple rounds, so total enrollment time exceeds 2+ minutes without completing - This affects all libfprint versions tested (stable, git, egismoc-sdcp-git)
Diagnostics
fprintd-list: "found 1 devices" — sensor is detectedfprintd-verify: "No enrolled prints" — no enrollment completed- Kernel logs show no USB errors — the sensor is properly enumerated
dmesgshows:usb 3-5: Product: EgisTec Touch Fingerprint Sensor— no errors- The
egis0570.cdriver source includes the sensor in itsid_table({ .vid = 0x1c7a, .pid = 0x0570 }) - The driver has
egismoc_open,egismoc_probe,fpi_device_egis0570_init— the driver is properly loaded
Expected behavior
The egis0570 driver should communicate with the EgisTec EH570 sensor during enrollment, completing the init packet sequence and allowing fingerprint enrollment to succeed (similar to how the driver works for other supported sensors like the egismoc Match-on-Chip devices).
Additional context
- The Acer Swift 3 SF-316-51 (EgisTec EH575,
1c7a:0575) has the same reported issue on the Acer community forums — Linux doesn't have working drivers for EgisTec fingerprint sensors - The libfprint egis0570 driver was added with limited testing data (see commit
8dc6f15 egismoc: comment out other variants until test data can be captured) - The sensor revision
bcdDevice 10.41may be newer than what the driver was developed for
Model and driver info
- Model: LighTuning Technology Inc. EgisTec EH570
- USB ID: 1c7a:0570
- Driver: libfprint egis0570
- Kernel driver: /sys/bus/usb/drivers/usb (generic, claimed by libfprint)
View raw text
## What happened
Omarchy 4.0.2-1 on Arch Linux with kernel 7.1.9-arch1-2.
The EgisTec EH570 fingerprint sensor (`1c7a:0570`) is correctly detected by the kernel and libfprint — `fprintd-list` shows the device and `fprintd-enroll` begins without error. However, enrollment **hangs indefinitely** waiting for sensor responses that never arrive.
The `egis0570` driver is loaded and the device is claimed, but the init packet sequence never completes. Neither the stock `libfprint 1.94.100` nor `libfprint-git 1.94.10.r12.gd79f157` nor the community `libfprint-egismoc-sdcp-git` driver resolves the issue.
## Steps to reproduce
1. Install Omarchy on a laptop with EgisTec EH570 fingerprint sensor
2. Run `omarchy setup security fingerprint`
3. Sensor is detected ("Using device /net/reactivated/Fprint/Device/0")
4. `fprintd-enroll` hangs indefinitely — no enrollment completes
5. Ctrl+C to abort, then `fprintd-verify` shows "No enrolled prints"
## System details
- **OS:** Omarchy 4.0.2-1 (Arch Linux)
- **Kernel:** 7.1.9-arch1-2
- **CPU:** Intel i5-1035G1 (Ice Lake)
- **GPU:** Intel Iris Plus Graphics G1
- **RAM:** 7.4 GiB, NVMe 512 GB
- **Sensor:** LighTuning Technology Inc. EgisTec Touch Fingerprint Sensor (`1c7a:0570`, `bcdDevice 10.41`)
- **fprintd:** 1.94.5-2
- **libfprint:** 1.94.100 (stock), 1.94.10.r12.gd79f157 (git), and 1.94.9 (egismoc-sdcp-git) — all exhibit the same hang
## What works
- Kernel detects the sensor: `usb 3-5: Product: EgisTec Touch Fingerprint Sensor`
- libfprint detects the device: `fprintd-list` shows "found 1 devices"
- Device is properly claimed by fprintd
- udev rules are correctly configured (70-libfprint-2.rules with 1c7a:0570)
## What doesn't work
- `fprintd-enroll` hangs — the egis0570 driver sends init packets but the sensor never responds
- The enrollment state machine (SM_INIT → SM_START → SM_REQ → SM_RESP) gets stuck waiting for a response that never arrives
- The driver has `EGIS0570_TIMEOUT 10000` (10s) per packet round, and the full init sequence has multiple rounds, so total enrollment time exceeds 2+ minutes without completing
- This affects all libfprint versions tested (stable, git, egismoc-sdcp-git)
## Diagnostics
- `fprintd-list`: "found 1 devices" — sensor is detected
- `fprintd-verify`: "No enrolled prints" — no enrollment completed
- Kernel logs show no USB errors — the sensor is properly enumerated
- `dmesg` shows: `usb 3-5: Product: EgisTec Touch Fingerprint Sensor` — no errors
- The `egis0570.c` driver source includes the sensor in its `id_table` (`{ .vid = 0x1c7a, .pid = 0x0570 }`)
- The driver has `egismoc_open`, `egismoc_probe`, `fpi_device_egis0570_init` — the driver is properly loaded
## Expected behavior
The egis0570 driver should communicate with the EgisTec EH570 sensor during enrollment, completing the init packet sequence and allowing fingerprint enrollment to succeed (similar to how the driver works for other supported sensors like the egismoc Match-on-Chip devices).
## Additional context
- The Acer Swift 3 SF-316-51 (EgisTec EH575, `1c7a:0575`) has the same reported issue on the Acer community forums — Linux doesn't have working drivers for EgisTec fingerprint sensors
- The libfprint egis0570 driver was added with limited testing data (see commit `8dc6f15 egismoc: comment out other variants until test data can be captured`)
- The sensor revision `bcdDevice 10.41` may be newer than what the driver was developed for
## Model and driver info
- **Model:** LighTuning Technology Inc. EgisTec EH570
- **USB ID:** 1c7a:0570
- **Driver:** libfprint egis0570
- **Kernel driver:** /sys/bus/usb/drivers/usb (generic, claimed by libfprint)Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 10:50 UTC