Cant see fingerprint option in settings

Acer swift go 14 ryzen 7 7730U 16gb ram

liveuser@localhost-live:~$ sudo systemctl start fprintd
Warning: The unit file, source configuration file or drop-ins of fprintd.service changed on disk. Run 'systemctl daemon-reload' to reload units.
liveuser@localhost-live:~$ sudo systemctl enable fprintd
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
 
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.
liveuser@localhost-live:~$  sudo dnf install fprintd fprintd-pam
Updating and loading repositories:
Repositories loaded.
Package "fprintd-1.94.2-12.fc41.x86_64" is already installed.
Package "fprintd-pam-1.94.2-12.fc41.x86_64" is already installed.

Nothing to do.
liveuser@localhost-live:~$ systemclt status fprintd.service
bash: systemclt: command not found...
Similar command is: 'systemctl'
liveuser@localhost-live:~$ systemctl status fprintd.service
○ fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)
       Docs: man:fprintd(1)

Jan 16 01:37:03 localhost-live systemd[1]: Starting fprintd.service - Fingerprint Authentica>
Jan 16 01:37:03 localhost-live systemd[1]: Started fprintd.service - Fingerprint Authenticat>
Jan 16 01:37:33 localhost-live systemd[1]: fprintd.service: Deactivated successfully.
Jan 16 01:40:19 localhost-live systemd[1]: Starting fprintd.service - Fingerprint Authentica>
Jan 16 01:40:19 localhost-live systemd[1]: Started fprintd.service - Fingerprint Authenticat>
Jan 16 01:40:49 localhost-live systemd[1]: fprintd.service: Deactivated successfully.

liveuser@localhost-live:~$ ^C
liveuser@localhost-live:~$ systemctl enable fprintd.service
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
 
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.
liveuser@localhost-live:~$  fprintd-enroll
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
liveuser@localhost-live:~$ lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
00:02.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7
01:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
02:00.0 Non-Volatile memory controller: Micron Technology Inc 2450 NVMe SSD [HendrixV] (DRAM-less) (rev 01)
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo (rev c4)
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller
03:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
03:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
03:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
03:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor (rev 01)
03:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller
04:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
04:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
liveuser@localhost-live:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 10a5:e340 䘀倀䌀 FPC Sensor Controller
Bus 001 Device 003: ID 04f2:b777 Chicony Electronics Co., Ltd ACER FHD User Facing
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0489:e0e4 Foxconn / Hon Hai Wireless_Device
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

@ilikelinux @vwbusguy @vgaetera can you guys help.
I am tagging you as you guys have solved my issues prior to this

what i get so far Support for FPC Sensor Controller 10a5:e340 (#585) · Issues · libfprint / libfprint · GitLab

Please do not call us this way. We help as we do have time and read new topics as we like it. This @frankjunior is ok, when you mention a person in a Topic the user participates or if you reefer to something important from an other topic.

1 Like

Sorry for that

Here’s what i found with the help of AI

fprintd is installed but not actively running:

systemctl status fprintd.service

shows it’s loaded but inactive. This likely means it’s not configured to start automatically during system boot.

Fingerprint reader is not detected:

fprintd-enroll

reports “No devices available,” indicating that the system cannot find your fingerprint reader.

1 Like

I’ve had a number of machines with Fingerprint readers and my current ThinkPad P14S Gen5 is the first one and only one that just worked out of Box for me on Linux. Unfortunately, there aren’t Linux drivers for a whole lot of them. I even had a fingerprint reader on a System76 laptop that wouldn’t work in Fedora because the proprietary driver was Ubuntu specific, IIRC. Sorry to not be more help, but if it doesn’t show up in fprintd, it’s unlikely it’s going to work.

1 Like

I understand should i try with ubuntu also…
I have created a request in acer don’t know if they will fix or not.

Very much at your own risk, there appears to be a driver for this specific fingerprint vendor that supports Fedora and even then I’m not sure it will work.

Personally, I don’t think I would touch it. It looks like it’s doing more than just adding a driver but also doing various other things to fprintd (I do not read Chinese - this is just based on looking at source files).

I will do it in live mode to check if that works or not if that works or not i will let you know.