Impossible to enroll gdbus error net reactivated fprint error nosuchdevice no devices available

Hello All,
I would like to be able to unlock my archlinux with my finger. It is not a notebook.
I have looked around and currently decided on the finger scanner from Xystec which is also listed on the fprint compatibility list with «04f3:0c3d ElanTech Fingerprint Sensor».
My desktop environment is GNOME 40.

The finger scanner is also recognized by the system:

[root@arch ~]# lsusb
Bus 001 Device 008: ID 04f3:0c3d Elan Microelectronics Corp. ELAN:Fingerprint

Because of the wiki article I have now tried to set up the software Fprint.
I skipped the «Login Configuration» listed in the wiki because I use GDM and it says that you can skip the section.

My problem now is that there is no option in GDM to unlock with the finger, also in the Gnome settings there is no option anywhere and when I run fprint-enroll I get «No device abailable».

[root@arch ~]# fprintd-enroll
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available

The following command, which I often read about in my research, does not work either:

[root@arch ~]# pam-auth-update
-bash: pam-auth-update: Kommando nicht gefunden.

As you can see, i am not very familiar with this topic. Maybe someone has the same problem and already a solution?
If another fingerprint scanner is needed, that’s no problem either, I can gladly replace this one.
But actually mine is recognized with lsusb. A configuration should therefore possibly be possible?

Here is the output of journalctl:

[root@arch bin]# systemctl status fprintd.service 
○ fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
     Active: inactive (dead)
       Docs: man:fprintd(1)

Jun 26 09:07:43 arch systemd[1]: fprintd.service: Deactivated successfully.
Jun 26 09:28:25 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 09:28:25 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 09:28:56 arch systemd[1]: fprintd.service: Deactivated successfully.
Jun 26 10:10:17 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 10:10:17 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 10:10:47 arch systemd[1]: fprintd.service: Deactivated successfully.
Jun 26 13:38:42 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:38:42 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 13:39:13 arch systemd[1]: fprintd.service: Deactivated successfully.
[root@arch bin]# systemctl start fprintd.service 

[root@arch bin]# systemctl status fprintd.service 
● fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
     Active: active (running) since Sat 2021-06-26 13:40:03 CEST; 3s ago
       Docs: man:fprintd(1)
   Main PID: 10500 (fprintd)
      Tasks: 5 (limit: 18919)
     Memory: 1.5M
        CPU: 45ms
     CGroup: /system.slice/fprintd.service
             └─10500 /usr/lib/fprintd

Jun 26 13:40:03 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:40:03 arch systemd[1]: Started Fingerprint Authentication Daemon.

[root@arch bin]# journalctl -u fprintd.service
Jun 26 13:38:42 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:38:42 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 13:39:13 arch systemd[1]: fprintd.service: Deactivated successfully.
Jun 26 13:40:03 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:40:03 arch systemd[1]: Started Fingerprint Authentication Daemon.

So fprint service didn’t run at first, so started it now, but doesn’t change anything. Error message at «frpintd-enroll» is still the same.
After a while the service is «deactivated» again???

[root@arch bin]# systemctl status fprintd.service 
○ fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
     Active: inactive (dead)
       Docs: man:fprintd(1)

Jun 26 10:10:47 arch systemd[1]: fprintd.service: Deactivated successfully.
Jun 26 13:38:42 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:38:42 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 13:39:13 arch systemd[1]: fprintd.service: Deactivated successfully.
Jun 26 13:40:03 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:40:03 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 13:40:33 arch systemd[1]: fprintd.service: Deactivated successfully.
Jun 26 13:42:21 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:42:21 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 13:42:51 arch systemd[1]: fprintd.service: Deactivated successfully.

I hope someone can help me

Many greetings
mabo

Arch Linux

You are not logged in.

#1 2021-01-08 21:09:03

[SOLVED] Fingerprint Authentication with GDM and fprint not working

I have a Thinkpad P14s with an integrated fingerprint reader. I’d like to use it to login in via GDM.
I followed the Arch Wiki’s instructions for setting up fprint.
As it is stated there, I skipped the «Login Configuration» step, because I use GDM.

In the terminal, I can use

to enroll my fingerprint. This seems to work fine (no error message).
I can also use

to verify if my fingerprint was saved correctly. It matches every time it should.
Since I installed fprintd, the login screen prompts «(or swipe finger)», so obviously it detected it in some way.

But now the problem:
When I use the fingerprint sensor during login, nothing happens. I can try it as many times as I want, nothing changes.
When I try

again after reboot, it says

So I would say that there are some conflicting services who’d like to access the fingerprint reader. But how can I investigate this?

What is «error: 789»? Where can I find out?

GDM version is «gdm 3.38.2.1-1»
fprintd version is «1.90.8-1»
uname -r gives «5.10.5-arch1-1»

Thanks in advance.
Cheers, eearcher

Last edited by eearcher (2021-01-09 15:31:57)

#2 2021-01-08 21:28:42

Re: [SOLVED] Fingerprint Authentication with GDM and fprint not working

Assuming you use Gnome since you are using GDM.

There is an option to enroll your fingerprint in the Gnome Settings. I would delete the one you created through the terminal and give that tool a shot. It’s under your account management page.

#3 2021-01-08 21:55:24

Re: [SOLVED] Fingerprint Authentication with GDM and fprint not working

Thanks for your reply.

So I reverted the config changes I made and found the entry you mentioned in Gnome Settings.
I activated fingerprint login there and saw that my fingerprint from before is saved.

My problem still persists, but it seems to me like there is a permission problem. Gnome Settings says «Some Settings must be unlocked before they can be changed».
But when I do this, it will be locked again when I reboot. (Fingerprint reader: exact same problem, can’t log in and fprintd states that device is already claimed).

Any ideas what could cause this?

Last edited by eearcher (2021-01-09 15:31:32)

#4 2021-01-09 15:31:10

Re: [SOLVED] Fingerprint Authentication with GDM and fprint not working

Ok, I think I got it.

According to this issue, this is a problem with the BIOS.
There is something called «Predesktop Authentication», and as far as I understand it, this allows to use the fingerprint reader before boot. The problem is, that the device is therefore claimed by the BIOS first (this is where the «device is already claimed» error comes from, I guess) and meant to be handed over to Windows (!). So if you’re not using Windows, but want to use the fingerprint reader, you need to:

Disable «Predesktop Authentication» in BIOS (Security -> Fingerprint)

Reset Fingerprint Data in BIOS (Security -> Fingerprint)

Источник

Драйвера для сканера отпечатков пальцев Goodix

Нужны драйвера для сего девайса на Linux

Попробовал поставить отсюда — не завели

Так же нашёл этот репозиторий, но здесь нет моей модели

OS — Linux Mint 21

Laptop: Redmi Book Pro 15 2022

Kernel version: 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:53:30 UTC 2022 x86_64

У меня для тебя плохие новости

Ну жди. Для mi air 2017 появились спустя несколько лет с подачи какого-то энтузиаста

оно штоле фотки пальцев в юзерспейсе гоняет?

и никакая сертификация эти ноуты не зарубила?

Какая-то сертификация? Где? о_О

Это сраная биометрия, за неё дерут так, что глаза выпадают. От хорошей жизни, думаешь, все андроиды хранят отпечатки в отдельном чипе и/или не имеют к ним доступа из ОС?

Это да, я оттуда дрова на клаву ставил, но драйвер сканера там только для другого сканера, мой не поддерживает

Ну извини, libfprint тоже весь в юзерспейсе работает, испокон веков причем.

От хорошей жизни, думаешь, никто из вендоров ънтерпрайз-Линукса не заявлает «поддержку сканеров отпечатков пальцев» и сисюрити с их использованием?

Причину и следствие путаешь.

Хм. Вопрос в том, как получать изображения от сканера? И как потом встроить это в систему

Никто бы не тяпал отпечатки вручную, рискуя их слить, если бы вендоры поставили нормальное железо, делающее распознавание без участия ОС (или в защищённом анклаве, если х86 в это умеет), как в телефонах.

Вендоры Линукса железо не ставят, ибо не производят.
Ноутопроизводители ставят — внезапно — такие же модули, как и в смартфонах. Просто софтина, которая ими рулит на Андроиде, огорожена в ТЕЕ (TrustZone).
Точно же сделано и в виндовых драйверах для тех же Goodixов — работа с данными со сканера строго в анклаве SGX.

А редгаду и каноникалу, видимо, незачем.

А линукс же опенсорсный, неужели никому не приходит в голову запилить модуль ядра для сканеров?

Модуль ядра будет немногим секурнее юзерспейсной библиотеки, так что всем плевать.

А в мыльном пузыре настольного Linux от семейства технологий Trusted Computing все кто не редгад и не каноникал шарахаются как чёрт от ладана.

Ниже ядра же только хардвар, как это от системы зависит

А возможно ли поменять сканер на ноуте?

Если да, то по каким параметрам стоит его подбирать кроме, собственно, диаметра и наличия на него драйвера?

А зачем тебе так нужно это не особо полезное устройство? Как минимум оно не мгновенно сканит, лишняя возня. Пароли/шифрование разделов/системы авторизации всё это не нужно)

Как минимум разблокировка экрана. Как максимум — sudo

Пароли/шифрование разделов/системы авторизации всё это не нужно)

Источник

Arch Linux

You are not logged in.

#1 2021-07-02 05:05:20

Fingerprint scanner installation!

Hello All,
I would like to be able to unlock my archlinux with my finger. It is not a notebook.
I have looked around and currently decided on the finger scanner from Xystec which is also listed on the fprint compatibility list with «04f3:0c3d ElanTech Fingerprint Sensor».
My desktop environment is GNOME 40.

The finger scanner is also recognized by the system:

Because of the wiki article I have now tried to set up the software Fprint.
I skipped the «Login Configuration» listed in the wiki because I use GDM and it says that you can skip the section.

My problem now is that there is no option in GDM to unlock with the finger, also in the Gnome settings there is no option anywhere and when I run fprint-enroll I get «No device abailable».

The following command, which I often read about in my research, does not work either:

As you can see, i am not very familiar with this topic. Maybe someone has the same problem and already a solution?
If another fingerprint scanner is needed, that’s no problem either, I can gladly replace this one.
But actually mine is recognized with lsusb. A configuration should therefore possibly be possible?

Here is the output of journalctl:

So fprint service didn’t run at first, so started it now, but doesn’t change anything. Error message at «frpintd-enroll» is still the same.
After a while the service is «deactivated» again.

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

Linux driver for fingerprint sensor

Linux driver for fingerprint sensor

Post by Nadeem » Thu Sep 02, 2021 6:06 am

I guess this means there is no driver.

Anyone can help? I went to check on http://www.focaltech-systems.com/, the manufacturer’s site. Apparently they have no support for Linux.

Any workaround? Thanks

Re: Linux driver for fingerprint sensor

Post by xenopeek » Thu Sep 02, 2021 7:42 am

Re: Linux driver for fingerprint sensor

Post by Nadeem » Thu Sep 02, 2021 8:06 am

Thanks for your reply. It says:

Error 22: Unsupported option: -Jxxx
Check -h for correct parameters.

Re: Linux driver for fingerprint sensor

Post by xenopeek » Thu Sep 02, 2021 8:09 am

Hm. Must be a old version of inxi.

Please share instead output of command:
lsusb

Re: Linux driver for fingerprint sensor

Post by Nadeem » Thu Sep 02, 2021 8:13 am

Re: Linux driver for fingerprint sensor

Post by xenopeek » Thu Sep 02, 2021 8:24 am

It doesn’t look good. No driver for that according to https://linux-hardware.org/?id=usb:2808-9338.

Focaltech Systems have some open source driver https://github.com/focaltech-systems but not for this fingerprint device.

Re: Linux driver for fingerprint sensor

Post by Nadeem » Thu Sep 02, 2021 8:38 am

Re: Linux driver for fingerprint sensor

Post by xenopeek » Thu Sep 02, 2021 10:01 am

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

Lost fingerprint during upgrade to Mint 21

Lost fingerprint during upgrade to Mint 21

Post by matm » Wed Aug 31, 2022 6:35 pm

The upgrade assistant asked me to disable the repositories related to dell:

, but it did not bring anything new

lsusb show the sensor:

This lib https://launchpad.net/libfprint-2-tod1-goodix should solve my issues, but I don’t know how to get it;

Can someone help ?

Re: Lost fingerprint during upgrade to Mint 21

Post by MiZoG » Wed Aug 31, 2022 8:49 pm

Re: Lost fingerprint during upgrade to Mint 21

Post by hglee » Thu Sep 01, 2022 3:10 am

This lib https://launchpad.net/libfprint-2-tod1-goodix should solve my issues, but I don’t know how to get it;

Can someone help ?

This fingerprint reader thread doesn’t look too ancient to be useful, though it’s closed to comments: Fingerprint support mint 20 Ulyana

To start here, post detailed data about your PC hardware and system software.

Plug in all relevant dongles, accessories, and peripherals. Then .

1. Use the Mint menus to launch System Reports.
2. Click on System information there. Your system details appear.
3. At the bottom-right of that window, click on the [Copy] button.
4. Your clipboard now has your PC info. Open a Reply here and paste everything in, by Ctrl-V or mouse right-click menu.

Re: Lost fingerprint during upgrade to Mint 21

Post by matm » Thu Sep 01, 2022 5:47 pm

I tried to deploy the rules and the lib from the github repo, but that did not improve the situation.
The topic you mentioned is probably the one I used when I get the machine to enable the fingerprint sensor.

Here are my information:

Re: Lost fingerprint during upgrade to Mint 21

Post by terry_dwyer » Fri Sep 02, 2022 4:44 am

I had a similar situation. It’s caused by the fingerprint reader hardware retaining a fingerprint.

I did a lot of research to find the solution. This refers to a Dell XPS 17 9710 which has a Goodix reader installed:

I made a note of what I had to do to clear the previouslly stored fingerprint causing the problem:

Bus 003 Device 003: ID 27c6:63ac Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC

Delete then enroll fingerprints:

sudo fprintd-delete «$USER»

For my laptop with the reader on the keypad lust below the screen:
for finger in right—finger; do sudo fprintd-enroll -f «$finger» «$USER»; done

Re: Lost fingerprint during upgrade to Mint 21

Post by matm » Sun Sep 04, 2022 5:14 pm

@terry_dwyer : I would love to be in that situation.

But, although the sensor is detected

Re: Lost fingerprint during upgrade to Mint 21

Post by mp37c4 » Sun Sep 11, 2022 4:11 pm

Re: Lost fingerprint during upgrade to Mint 21

Post by ricardogroetaers » Sun Sep 11, 2022 5:02 pm

Thanks for the official Dell repositories regarding Ubuntu. One day I will need them.

Источник

scanbe

Registered Member

Posts

4

Karma

0

OS

thebluequasar

Registered Member

Posts

33

Karma

0

OS

swisstonwalter

Registered Member

Posts

1

Karma

0

kauwlquabbe

Registered Member

Posts

1

Karma

0

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group

© Copyright 2012 KDE Community Forum Team. All rights reserved.
KDE Community Forums has no liability for any content or post. All messages belong to and are the opinion of their respective authors.
KDE and K Desktop Environment are trademarks of KDE e.V. • For more details, contact the Forum Administrators.

Hi, I am seeing the same. Here some context:

$ snap list validity-sensors-tools
Name                    Version            Rev  Tracking       Publisher  Notes
validity-sensors-tools  0.5+git23.5813f6e  65   latest/stable  3v1n0      -

$ apt-cache policy libfprint-2-2 libfprint-2-tod-vfs0090 libfprint-2-tod1 fprintd
libfprint-2-2:
  Installed: 1:1.90.3+tod1-0ubuntu1
  Candidate: 1:1.90.3+tod1-0ubuntu1
  Version table:
 *** 1:1.90.3+tod1-0ubuntu1 500
        500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
        100 /var/lib/dpkg/status
libfprint-2-tod-vfs0090:
  Installed: 0.90~f2
  Candidate: 0.90~f2
  Version table:
 *** 0.90~f2 500
        500 http://ppa.launchpad.net/3v1n0/libfprint-vfs0090/ubuntu groovy/main amd64 Packages
        100 /var/lib/dpkg/status
libfprint-2-tod1:
  Installed: 1:1.90.3+tod1-0ubuntu1
  Candidate: 1:1.90.3+tod1-0ubuntu1
  Version table:
 *** 1:1.90.3+tod1-0ubuntu1 500
        500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
        100 /var/lib/dpkg/status
fprintd:
  Installed: 1.90.1-1ubuntu1
  Candidate: 1.90.1-1ubuntu1
  Version table:
 *** 1.90.1-1ubuntu1 500
        500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
        100 /var/lib/dpkg/status

$ lsusb | fgrep Validity
Bus 001 Device 012: ID 138a:0097 Validity Sensors, Inc.

$ sudo validity-sensors-tools --tool led-dance
# works
$ sudo validity-sensors-tools.enroll --finger-id 0
# also works

$ fprintd-verify
list_devices failed: No devices available

$ sudo systemctl status fprintd
● fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/lib/systemd/system/fprintd.service; static)
     Active: inactive (dead)
       Docs: man:fprintd(1)

Oct 25 02:53:33 x1-yoga systemd[1]: fprintd.service: Succeeded.
Oct 25 02:53:45 x1-yoga systemd[1]: Starting Fingerprint Authentication Daemon...
Oct 25 02:53:45 x1-yoga systemd[1]: Started Fingerprint Authentication Daemon.
Oct 25 02:54:15 x1-yoga systemd[1]: fprintd.service: Succeeded.
Oct 25 02:58:19 x1-yoga systemd[1]: Starting Fingerprint Authentication Daemon...
Oct 25 02:58:19 x1-yoga systemd[1]: Started Fingerprint Authentication Daemon.
Oct 25 02:58:49 x1-yoga systemd[1]: fprintd.service: Succeeded.
Oct 25 02:12:40 x1-yoga systemd[1]: Starting Fingerprint Authentication Daemon...
Oct 25 02:12:40 x1-yoga systemd[1]: Started Fingerprint Authentication Daemon.
Oct 25 02:13:10 x1-yoga systemd[1]: fprintd.service: Succeeded.

What can be done to debug this further?