Finger print not working

Help with the version of MX KDE officially released by the Development Team.
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
andyprough
MX Packager
Posts: 918
Joined: Tue Jul 23, 2019 10:16 pm

Re: Finger print not working

#11 Post by andyprough »

Mymoon wrote: Wed Sep 02, 2020 2:24 pm i have installed and open application ,
but it is showing no enrolled :frown:
I have attached the screenshot, please see :frown: :frown:
Then I'm out of ideas, sorry. As I said, I don't have anything to test it on.
Primary Computer - Commodore 64: Processor - MOS 6510/8500, 1.023MHz; Memory - 64kb RAM, 20kB ROM - 8k BASIC V2, 8k Kernel, 4k Character ROM; Display output - 320x200, 16 colours; OS - BASIC V2.0; Weight: 1.8kg

User avatar
j2mcgreg
Global Moderator
Posts: 6974
Joined: Tue Oct 23, 2007 12:04 pm

Re: Finger print not working

#12 Post by j2mcgreg »

Mymoon wrote: Wed Sep 02, 2020 1:17 pm ok means,
i have wait right >
I too have an HP laptop equipped with a fingerprint reader and yes we are going to have to wait and wait and wait... and like Godot, the driver will never appear. Fingerprint readers were a passing fad because they were never very reliable and there are better ways to protect your laptop (like encrypting your hard drive). The laptop manufacturers have moved on and so must we.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
andyprough
MX Packager
Posts: 918
Joined: Tue Jul 23, 2019 10:16 pm

Re: Finger print not working

#13 Post by andyprough »

j2mcgreg wrote: Wed Sep 02, 2020 3:01 pmI too have an HP laptop equipped with a fingerprint reader and yes we are going to have to wait and wait and wait... and like Godot, the driver will never appear. Fingerprint readers were a passing fad because they were never very reliable and there are better ways to protect your laptop (like encrypting your hard drive). The laptop manufacturers have moved on and so must we.
I guess you are right. My new laptop doesn't have it, and none of my older laptops had it. I guess I missed the fad. My uncle used to call me and ask for help getting it working on his Windows laptop, and I told him to give up and just use a password like everyone's been doing since computers were first built. I don't even think fingerprint scanners increase security, as they've been proven to be relatively simple to hack if you have the right materials.
Primary Computer - Commodore 64: Processor - MOS 6510/8500, 1.023MHz; Memory - 64kb RAM, 20kB ROM - 8k BASIC V2, 8k Kernel, 4k Character ROM; Display output - 320x200, 16 colours; OS - BASIC V2.0; Weight: 1.8kg

kangburra
Posts: 54
Joined: Wed Jul 31, 2019 3:10 am

Re: Finger print not working

#14 Post by kangburra »

I have a fingerprint working for Konsole and to unlock the screen I need a password and then a fingerprint. For the login screen only a password.
Of course this doesn't help if you have no driver. I have an older Metabox laptop with Upek TCS5B Fingerprint sensor.
I used a PPA for Ubuntu and the KDE instructions but it is not perfect.

User avatar
JayM
Posts: 6796
Joined: Tue Jan 08, 2019 3:47 am

Re: Finger print not working

#15 Post by JayM »

Is fprintd installed? MX Package Installer, Stable Repo tab. You would need to reboot afterward as it's a system daemon (service.)
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

User avatar
Vanitarium
Posts: 34
Joined: Wed Feb 03, 2021 4:35 am

Re: Finger print not working

#16 Post by Vanitarium »

SYS INFO:

Code: Select all

System:    Kernel: 5.10.0-11-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-11-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.20.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 7 
           dm: SDDM Distro: MX-21_KDE_x64 Wildflower October 20  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: TUXEDO product: TUXEDO Aura 15 Gen1 v: N/A 
           serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: NB01 model: NL5xRU serial: <filter> UEFI: INSYDE v: 1.07.08TTR3 
           date: 03/18/2021 
Battery:   ID-1: BAT0 charge: 9.4 Wh (22.9%) condition: 41.1/48.3 Wh (85.1%) volts: 14.3 
           min: 15.2 model: Notebook BAT type: Li-ion serial: <filter> 
           status: Discharging 
CPU:       Info: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 type: MCP 
           arch: Zen 2 family: 17 (23) model-id: 60 (96) stepping: 1 microcode: 8600106 
           cache: L2: 4 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 31940 
           Speed: 1402 MHz min/max: 1400/2000 MHz boost: enabled Core speeds (MHz): 
           1: 1402 2: 1491 3: 1358 4: 1969 5: 2005 6: 1883 7: 1318 8: 1322 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 
           mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: AMD Renoir vendor: CLEVO/KAPOK driver: amdgpu v: kernel 
           bus-ID: 05:00.0 chip-ID: 1002:1636 class-ID: 0300 
           Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 3-4:3 
           chip-ID: 5986:9102 class-ID: 0e02 
           Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: 
           loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: eDP res: 1920x1080 hz: 60 dpi: 142 size: 344x193mm (13.5x7.6") 
           diag: 394mm (15.5") 
           OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.10.0-11-amd64 LLVM 12.0.1) 
           v: 4.6 Mesa 21.2.5 direct render: Yes 
Audio:     Device-1: AMD Renoir Radeon High Definition Audio vendor: CLEVO/KAPOK 
           driver: snd_hda_intel v: kernel bus-ID: 05:00.1 chip-ID: 1002:1637 
           class-ID: 0403 
           Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor 
           vendor: CLEVO/KAPOK driver: N/A alternate: snd_pci_acp3x, snd_rn_pci_acp3x 
           bus-ID: 05:00.5 chip-ID: 1022:15e2 class-ID: 0480 
           Device-3: AMD Family 17h HD Audio vendor: CLEVO/KAPOK driver: snd_hda_intel 
           v: kernel bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-11-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: CLEVO/KAPOK driver: r8169 v: kernel port: 2000 bus-ID: 02:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel modules: wl 
           port: 2000 bus-ID: 03:00.0 chip-ID: 8086:2723 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-3:2 
           chip-ID: 8087:0029 class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 
           lmp-v: 5.2 sub-v: 24bf hci-v: 5.2 rev: 24bf 
           Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff 
           link-mode: slave accept 
           service-classes: rendering, capturing, object transfer, audio 
Drives:    Local Storage: total: 942.67 GiB used: 121.23 GiB (12.9%) 
           ID-1: /dev/mmcblk0 maj-min: 179:0 model: GFAQK size: 476.91 GiB block-size: 
           physical: 512 B logical: 512 B type: SSD serial: <filter> scheme: GPT 
           SMART Message: Unknown smartctl error. Unable to generate data. 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-2: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 500GB 
           size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s 
           lanes: 4 type: SSD serial: <filter> rev: 1B2QGXA7 temp: 28.9 C scheme: GPT 
Partition: ID-1: / raw-size: 118.95 GiB size: 116.52 GiB (97.96%) 
           used: 15.42 GiB (13.2%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2 
           ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 2.9 MiB (1.2%) 
           fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 
           ID-3: /home raw-size: 338.56 GiB size: 332.25 GiB (98.13%) 
           used: 44.19 GiB (13.3%) fs: ext4 dev: /dev/nvme0n1p4 maj-min: 259:4 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/nvme0n1p3 maj-min: 259:3 
Sensors:   System Temperatures: cpu: 32.2 C mobo: 32.0 C gpu: amdgpu temp: 31.0 C 
           Fan Speeds (RPM): N/A 
Repos:     Packages: 2492 note: see --pkg apt: 2479 lib: 1342 flatpak: 13 
           Active apt repos in: /etc/apt/sources.list 
           1: deb http://deb.tuxedocomputers.com/ubuntu/ focal main
           2: deb http://kernel.tuxedocomputers.com/ubuntu/ focal main
           3: deb https://ppa.launchpad.net/fingerprint/fingerprint-gui/ubuntu bullseye main
           Active apt repos in: /etc/apt/sources.list.d/bluemail.list 
           1: deb https://packages.bluemail.me/repos/debian/ ./
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian/ bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free
           3: deb-src http://deb.debian.org/debian/ bullseye main contrib non-free
           4: deb http://deb.debian.org/debian/ bullseye-backports main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/fingerprint-ubuntu-fingerprint-gui-jammy.list 
           1: deb http://ppa.launchpad.net/fingerprint/fingerprint-gui/ubuntu jammy main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
           2: deb http:/fprintd-enroll -f left-index-finger
Using device /net/reactivated/Fprint/Device/0
Enrolling left-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-unknown-error
/mxlinux.mirrors.uk2.net/packages/mx/testrepo/ bullseye test
           3: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye ahs
Info:      Processes: 271 Uptime: 15m wakeups: 2 Memory: 30.74 GiB used: 2.1 GiB (6.8%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: 
           gcc: 10.2.1 alt: 10 Shell: quick-system-in default: Bash v: 5.1.4 
           running-in: quick-system-in inxi: 3.3.06 
My fingerprint scanner is not recording prints.
Here is lsusb output:

Code: Select all

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 5986:9102 Acer, Inc BisonCam,NB Pro
Bus 003 Device 002: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 04f3:0c63 Elan Microelectronics Corp. ELAN:Fingerprint
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I have installed fprintd_1.94.1-1 and all dependencies from Debian sid repo.
When I tried to record a print Doing fprintd-enroll I get this:

Code: Select all

sudo fprintd-enroll -f left-index-finger
Using device /net/reactivated/Fprint/Device/0
Enrolling left-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-unknown-error
It seems to timeout very quickly and does not give any more helps or logs to learn what is happening!!

All GUI facilities have been discontinued and nothing helpful is available on the internet.
Does this all mean that fingerprint scanning in linux is dead??? :bawling:
Maybe somebody can help with this or tell the debian developers to explain what needs to be done...

Thank you for Wildflower: it is very nice to use!! :number1:
User of TUXEDO AURA15v.1 laptop: AMD RYZEN 7 running MX Linux.Yunohost on Intel i3
Don't use Windows, tolerates macOS, loves MX Linux

AltTabDelete
Posts: 130
Joined: Sun Sep 05, 2021 9:29 am

Re: Finger print not working

#17 Post by AltTabDelete »

In case it is helpful to someone able to do the coding, my System 76 notebook from 2012 ( a Clevo P150HM ) came with Ubuntu 11.10 and a System 76 code patch to enable the fingerprint reader. That code was merged in the kernel in later Ubuntu versions. I realize that is all historical, but the code should have been contributed to upstream. I know this is a historical artifact, but it did exist.

Post Reply

Return to “MX KDE Official Release”