Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • L libfprint
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 66
    • Issues 66
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • libfprint
  • libfprint
  • Issues
  • #442

Closed
Open
Created Dec 22, 2021 by Doomsdayrs@Doomsdayrs

ASUS Vivobook TP401MAR_T : Unknown ElanTech fails to work properly

The ASUS Vivobook I recently acquired has a fingerprint sensor.

This sensor is detected, detailed as an "ElanTech" sensor

# fprintd-list admin
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
Fingerprints for user admin on ElanTech Embedded Fingerprint Sensor (swipe):
 - #0: left-index-finger
 - #1: right-index-finger

Attempting to use the GNOME settings to add a fingerprint results with the following issues. Problem reading device upon fingerprint completion, in the same dialog as the fingerprint enrollment process.

Failed to stop enrollment: Failed to communicate with the device during enrollment after dialog closed. I noted that the fingerprint still appeared afterwards.

Using the CLI tool has 0 issues visible.

Trying using the fingerprint reader for CLI, such as a "sudo" command leads to "Failed to match fingerprint", similar to GDM when trying to login.

This device did not show up in either lsusb, lspci, or lshw

Assignee
Assign to
Time tracking