Framework 13 fingerprint scanner

Hello,

  • OpenMandriva Lx version:
    Latest Rock (5)

  • Desktop environment (KDE, LXQT…):
    KDE

  • Description of the issue (screenshots if relevant):
    I am wondering if it is possible to get the Framework 13 fingerprint scanner working. On other distros this is a consequence of getting the latest libprintf, etc Anyone else here with a Framework and interested in something similar?

  • Relevant informations (hardware involved, software version, logs or output…):
    Goodix fingerprint sensor. lsusb shows that the kernel sees it and that it is connected.

Make a package or feature request here. Select new issue and select what you want to do.

Ok, I know you all are really working on the next Rock release, so I’ll slow my roll. This isn’t something that I just have to have. I’m just I could figure something out if I am in a rush. Perhaps later, I’ll request it. Thanks!

Just to make sure all bases are covered, the directions here do not work?

I don’t know if you’ve seen this, but it might be worth looking at.

1 Like

So installing fprintd and fprintd-pam is easy as they are available. Enabling them via systemctl is easy as well. BUT registering a fingerprint fails when you first scan a finger.

Looking into getting around it, but if any of you have some tips, they would be appreciated!

Turns out that fprintd is just too old. I am curious if it is possible to pull something out of the Rome or Cooker repos, but not base the entire system on it?

Could someone maybe tell me how to do that?

Hello!

I tried this on a framework 13 intel gen 11.
I used the ROME version, updated to the latest as of today.
I am having issues.

  1. I managed to install the fprintd, the pam package. 1.94.2-2 version.
  2. I edited the config file fprintd.service, in /usr/lib… as per arch and ubuntu forums
  3. I was able to systemctl enable fprintd and systemctl start fprintd.
  4. I was able to register fingerprints both with gui and console, and I was able to verify them.

The problem occurs with either rebooting to login screen or opening system settings. The state of the fprintd service changes to loaded(it is stopped by something I guess). So I am unable to use it to login.

If I open system settings, the service stops again. If I use a terminal to systemctl start fprintd with the system settings open, then I can set up fingerprints in system settings/users, but closing system settings stops the service again. If I open the system settings without restarting the fprintd service, then it doesn’t show up at the users part of the system settings.

I am no desktop expert, pls help!

I tried this on ubuntu 24.04 and win 11, and both work.

I’m guessing it’s failing when it’s trying to start. After you’ve rebooted but but before restart fprintd what does systemctl status fprintd return? Does it say failed or anythng like that? I’d also run the following and see what you might find.

sudo dmesg | grep fprintd

Hello!

sytemctl status fprintd:

systemctl status fprintd
○ fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/usr/lib/systemd/system/fprintd.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead) since Mon 2025-02-03 12:18:51 CET; 31s ago
 Invocation: 9406f683cfb8416d96ddd02b77e840f8
       Docs: man:fprintd(1)
    Process: 815 ExecStart=/usr/libexec/fprintd (code=exited, status=0/SUCCESS)
   Main PID: 815 (code=exited, status=0/SUCCESS)
   Mem peak: 5.1M
        CPU: 56ms


Feb 03 13:18:21 bogyesz systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Feb 03 13:18:21 bogyesz systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Feb 03 12:18:51 bogyesz systemd[1]: fprintd.service: Deactivated successfully.

sudo dmesg | grep fprintd
it is empty, nothing comes up

journalctl -u fprintd today:

-- Boot d1c5da760533435fa8afa6e2db97f2e8 --
Feb 03 13:18:21 bogyesz systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Feb 03 13:18:21 bogyesz systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Feb 03 12:18:51 bogyesz systemd[1]: fprintd.service: Deactivated successfully.

journalctl -u fprintd yesterday:


-- Boot dc2e2e14c72143de9f0e868d64be78f3 --
Feb 02 21:01:23 bogyesz systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Feb 02 21:01:24 bogyesz systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Feb 02 21:01:54 bogyesz systemd[1]: fprintd.service: Deactivated successfully.
Feb 02 21:03:03 bogyesz systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Feb 02 21:03:04 bogyesz systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Feb 02 21:03:34 bogyesz systemd[1]: fprintd.service: Deactivated successfully.
Feb 02 21:04:18 bogyesz systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Feb 02 21:04:19 bogyesz systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Feb 02 21:04:49 bogyesz systemd[1]: fprintd.service: Deactivated successfully.
Feb 02 21:05:15 bogyesz systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Feb 02 21:05:15 bogyesz systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Feb 02 21:05:32 bogyesz fprintd[2239]: Authorization denied to :1.110 to call method 'EnrollStop' for device 'Goodix MOC Fingerprint Sensor':>
Feb 02 21:05:32 bogyesz fprintd[2239]: Authorization denied to :1.110 to call method 'Release' for device 'Goodix MOC Fingerprint Sensor': De>
Feb 02 21:05:46 bogyesz systemd[1]: fprintd.service: Deactivated successfully.

It seems someting stops it. I mainly use linux as servers, with only web gui, so I don’t know where to start…

Hello,

Please Post your code as code
How to get better results when posting about problems
I did it for you this time.
Thank you.

2 Likes

Just wanted to pop in and say that I’ve also had this issue on my ThinkPad X13 in ROME. I’ve installed both fprintd and fprintd-pam, edited the config, started the service, etc. I tailed the fprintd journal entries and didn’t get that much useful info, but I did also notice the issue of fprintd stopping itself upon closing System Settings.

Output of journalctl -xefu fprintd starting from when I closed Settings:

Feb 04 10:38:11 fuuka fprintd[17400]: Authorization denied to :1.360 to call method 'EnrollStop' for device 'Synaptics Sensors': Device was not claimed before use
Feb 04 10:38:11 fuuka fprintd[17400]: Authorization denied to :1.360 to call method 'Release' for device 'Synaptics Sensors': Device was not claimed before use
Feb 04 10:38:13 fuuka systemd[1]: fprintd.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://openmandriva.org
░░ 
░░ The unit fprintd.service has successfully entered the 'dead' state.

2 Likes

Hello!

So does this mean that the gui shuts down the fprintd service?

It’s possible. I’ll try the XFCE spin (which I have installed on another fingerprint-enabled laptop) and report back soon.

1 Like

Hello!

Did the XFCE spin fingerprint reader work?

Hi, sorry for the delayed response, I don’t use the forums as often as I should.

I tried my fingerprint scanner on the XFCE spin and had the same issue :frowning:

I have been able to get this working on my Framework 13 11th gen (currently 12th gen).

Here are the details for getting it up and running. Basically when you install fprintd and fprint-pam (not sure about the spelling on this, but guides will make it clear. I am just typing this up fast) the service will not autostart as it is supposed to.

This is because a dbus connection is not created. To fix that do the following:

sudo nano /usr/share/dbus-1/system-services/net.reactivated.Fprint.service

then put the following in the file:

[D-BUS Service]
Name=net.reactivated.Fprint
Exec=/usr/libexec/fprintd
User=root
SystemdService=fprintd.service

Save and exit.

Now we need to restart dbus:

sudo systemctl reload dbus

This will get it working as it should. To verify you can open system settings and then go to users. You should see an option there to configure the fingerprint scanner.

If you would like to get the fingerprint scanner working in the terminal do the following:
Make a copy of pam.d sudo file:

sudo cp /etc/pam.d/sudo /etc/pam.d/sudo.bak

Then open it and edit it:

sudo nano /etc/pam.d/sudo

add the following line to the top of the file:

auth       sufficient   pam_fprintd.so

such that your file looks similar to this:

auth       sufficient   pam_fprintd.so
auth       include      system-auth
account    include      system-auth
password   include      system-auth
session    include      system-auth

Save and exit (Ctril + O and Ctrl + X)

As you have just used sudo, you should close the terminal and reopen it. Then try the following:

sudo -i

If everything is good, it will prompt you for your fingerprint. (This assumes you set one up when you were checking it in system settings under users.)

For me this means that Open Mandriva works perfectly on the Framework 13.

3 Likes

Can confirm this also works on my ThinkPads! This ought to be pinned.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.