[Bug 1888495] Re: fprintd-verify fails with an USB UPEK reader

[Jesús Diéguez Fernández]

I've been quite busy lately and couldn't debug it too much, but today I
was just thinking: if this new version will drop support for existing
hardware, can't we just have the package and source from 18.04 with a
"-legacy" suffix in both the pam client and library?

That would be a low effort fix where everyone wins: old hardware works
again and developers can focus on newer features.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888495

Title:
  fprintd-verify fails with an USB UPEK reader

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1888495/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888495] Re: fprintd-verify fails with an USB UPEK reader

[Jesús Diéguez Fernández]

About the PAM module issue, I followed Benjamin changes and this one is
a bug:

https://gitlab.freedesktop.org/libfprint/fprintd/-/commit/a7cf0ae3b266f9c5ead7d8acc4e5210adbc088cf

That's the double free error origin. I was able to download the source
code from there, build it and patch it and now it shows the following
error on syslog:

Jul 23 13:15:02 izanagi fprintd[98658]: Device reported an error during verify: 
Response had wrong subcommand type
Jul 23 13:15:26 izanagi fprintd[98658]: Device reported an error during verify: 
Response had wrong subcommand type

Which matches the last message from Benjamin about the subcommand f0:
https://bugzilla.redhat.com/show_bug.cgi?id=1832229#c57

I will try to debug it in the next days, If I find something I will
report it here.

** Bug watch added: Red Hat Bugzilla #1832229
   https://bugzilla.redhat.com/show_bug.cgi?id=1832229

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888495

Title:
  fprintd-verify fails with an USB UPEK reader

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1888495/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888495] Re: fprintd-verify fails with an USB UPEK reader

[Jesús Diéguez Fernández]

I'm trying to provide the stacktrace, I installed the debug symbols and
made the following:

$ fprintd-verify 
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
 - #0: right-index-finger
Verify result: verify-disconnected (done)

Execution ends there. I also tried the following with the same result:

$ fprintd-verify -f right-index-finger
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
 - #0: right-index-finger
Verify result: verify-disconnected (done)

$ fprintd-verify -f 0
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
 - #0: right-index-finger
Verify result: verify-disconnected (done)

Then I run gdb but it does not record anything meaningful:

$ sudo LANG=C gdb -p $(pgrep -U fprintd -x fprintd) -batch   -ex "set logging 
on" -ex continue   -ex "bt full"   -ex quit
pgrep: nombre de usuario inválido: fprintd
GNU gdb (Ubuntu 9.1-0ubuntu1) 9.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Illegal process-id: -batch.
Copying output to gdb.txt.
Copying debug output to gdb.txt.
The program is not being run.
No stack.

$ cat gdb.txt 
The program is not being run.
No stack.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888495

Title:
  fprintd-verify fails with an USB UPEK reader

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1888495/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881380] Re: fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB UPEK reader

[Jesús Diéguez Fernández]

It appears that in the RedHat bugtracker people are stuck at the same spot.
I'm changing the tag to verification-failed since registration of fingerprints 
works but validation fails.

** Tags removed: verification-needed-focal
** Tags added: verification-failed-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881380

Title:
  fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB
  UPEK reader

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint/+bug/1881380/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881380] Re: fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB UPEK reader

[Jesús Diéguez Fernández]

Hi,
I enabled proposed updates and updated my packages to:

libfprint-2-2:amd64 (1:1.90.2+tod1-0ubuntu1~20.04.1)
libfprint-2-tod1:amd64 (1:1.90.2+tod1-0ubuntu1~20.04.1)

And I can confirm that enrollment of fingerprints now succeeds:

$ fprintd-enroll 
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-completed

However, trying to use su or sudo after this returns another error:

$ LANG=C sudo ls
Swipe your right index finger across the fingerprint reader
free(): double free detected in tcache 2
Abortado

$ LANG=C su
Swipe your right index finger across the fingerprint reader
free(): double free detected in tcache 2
Abortado

Should this be addressed in another bugtrack or can it be solved on this
one?

Thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881380

Title:
  fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB
  UPEK reader

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint/+bug/1881380/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881380] Re: fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB UPEK reader

[Jesús Diéguez Fernández]

** Bug watch added: Red Hat Bugzilla #1832229
   https://bugzilla.redhat.com/show_bug.cgi?id=1832229

** Also affects: fprintd via
   https://bugzilla.redhat.com/show_bug.cgi?id=1832229
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881380

Title:
  fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB
  UPEK reader

To manage notifications about this bug go to:
https://bugs.launchpad.net/fprintd/+bug/1881380/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881380] [NEW] fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB UPEK reader

[Jesús Diéguez Fernández]

Public bug reported:

The fingerprint reader is an UPEK TCRE3C usb fingerprint reader. It was
working fine with ubuntu 16.04 and 18.04.

lsusb shows:

0483:2016 STMicroelectronics Fingerprint Reader

user@xubuntu:~$ fprintd-enroll 
Using device /net/reactivated/Fprint/Device/0
failed to claim device: Open failed with error: transfer timed out

user@xubuntu:~$ fprintd-list user
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
User user has no fingers enrolled for UPEK TouchStrip.


This bug is probably the same as:

https://bugzilla.redhat.com/show_bug.cgi?id=1832229

** Affects: fprintd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881380

Title:
  fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB
  UPEK reader

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1881380/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1688663] Re: udev 97-hid2hci.rules missing usb id for logitech dinovo 2

[Jesús Diéguez Fernández]

Any news on this topic? Do you need any additional information?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688663

Title:
  udev 97-hid2hci.rules missing usb id for logitech dinovo 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688663/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1688663] Re: udev 97-hid2hci.rules missing usb id for logitech dinovo 2

[Jesús Diéguez Fernández]

The keyboard is quite old, it has a technology prior to the Logitech
Unifying, but probably this led to it. It has a dongle that it autopairs
to it, so really you don't have to manually pair/configure it. For
example, it works out of the box accessing the bios of the computer.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688663

Title:
  udev 97-hid2hci.rules missing usb id for logitech dinovo 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688663/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1688663] [NEW] udev 97-hid2hci.rules missing usb id for logitech dinovo 2

[Jesús Diéguez Fernández]

Public bug reported:

Trying to install kubuntu 16.04.2 (Xenial Xerus) today, the Logitech
dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor
after being installed using another keyboard and mouse.

In /lib/udev/rules.d/97-hid2hci.rules there are two lines for Logitech
devices:

# Logitech devices
KERNEL=="hiddev*", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \
  RUN+="hid2hci --method=logitech-hid --devpath=%p"
# Logitech, Inc. diNovo Edge Keyboard
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c714", \
  RUN+="hid2hci --method=logitech-hid --devpath=%p"

lsusb shows in my computer:

Bus 001 Device 006: ID 046d:c704 Logitech, Inc. diNovo Wireless Desktop

The id is almost equal (c714 <> c704). After adding a new line with the
missing id, the keyboard and mouse started to work:

# Logitech, Inc. diNovo 2
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c704", \
  RUN+="hid2hci --method=logitech-hid --devpath=%p"

I've also followed these other bugs to find out the file that I needed
to modify and that my keyboard needs hidraw instead of hiddev:

https://bugs.launchpad.net/ubuntu/+source/udev/+bug/872940
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 97-hid2hci.rules bluetooth dinovo logitech udev

** Attachment added: "IMG_20170505_181434.jpg"
   
https://bugs.launchpad.net/bugs/1688663/+attachment/4872443/+files/IMG_20170505_181434.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688663

Title:
  udev 97-hid2hci.rules missing usb id for logitech dinovo 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688663/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 727220] Re: Command fuse returned error 1 (with TrueCrypt)

[Jesús Diéguez Fernández]

Hi, I'm using Lucid 10.04 updated to date.
I marked as install the two packages, upgraded, and the problem appeared 
again.

I confirm that after uninstalling loop-aes-utils It works with the
latest version of libfuse and fuse-utils.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727220

Title:
  Command fuse returned error 1 (with TrueCrypt)

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 727220] Re: Command fuse returned error 1 (with TrueCrypt)

[Jesús Diéguez Fernández]

Thanks! This also worked for me!

In 10.04 the current working version is libfuse2_2.8.1-1.1ubuntu2.

I downloaded it from
http://launchpadlibrarian.net/38427956/libfuse2_2.8.1-1.1ubuntu2_amd64.deb
and installed as you said:

root@ubuntu:/var/cache/apt/archives# wget 
http://launchpadlibrarian.net/38427956/libfuse2_2.8.1-1.1ubuntu2_amd64.deb
--2011-03-09 22:30:50--  
http://launchpadlibrarian.net/38427956/libfuse2_2.8.1-1.1ubuntu2_amd64.deb
Resolviendo launchpadlibrarian.net... 91.189.89.228, 91.189.89.229
Conectando a launchpadlibrarian.net|91.189.89.228|:80... conectado.
Petición HTTP enviada, esperando respuesta... 200 OK
Longitud: 146138 (143K) [application/x-debian-package]
Guardando en: «libfuse2_2.8.1-1.1ubuntu2_amd64.deb»

100%[==] 146.138  130K/s   en
1,1s

2011-03-09 22:30:52 (130 KB/s) - «libfuse2_2.8.1-1.1ubuntu2_amd64.deb»
guardado [146138/146138]

root@ubuntu:/var/cache/apt/archives# dpkg -i --force-downgrade 
libfuse2_2.8.1-1.1ubuntu
libfuse2_2.8.1-1.1ubuntu2_amd64.deblibfuse2_2.8.1-1.1ubuntu3.1_amd64.deb
root@getsuga:/var/cache/apt/archives# dpkg -i --force-downgrade 
libfuse2_2.8.1-1.1ubuntu2_amd64.deb 
dpkg: aviso: desactualizando libfuse2 de 2.8.1-1.1ubuntu3.1 a 2.8.1-1.1ubuntu2.
(Leyendo la base de datos ...  00%
448929 ficheros y directorios instalados actualmente.)
Preparando para reemplazar libfuse2 2.8.1-1.1ubuntu3.1 (usando 
libfuse2_2.8.1-1.1ubuntu2_amd64.deb) ...
Desempaquetando el reemplazo de libfuse2 ...
Configurando libfuse2 (2.8.1-1.1ubuntu2) ...

Procesando disparadores para libc-bin ...
ldconfig deferred processing now taking place
root@ubuntu:/var/cache/apt/archives#

And It works:

root@ubuntu:/var/cache/apt/archives# mount | grep truecrypt
truecrypt on /tmp/.truecrypt_aux_mnt1 type fuse.truecrypt 
(rw,nosuid,nodev,allow_other)
/dev/mapper/truecrypt1 on /media/truecrypt1 type vfat 
(rw,uid=1000,gid=1000,umask=077)
root@ubuntu:/var/cache/apt/archives#

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727220

Title:
  Command fuse returned error 1 (with TrueCrypt)

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 727220] Re: Command fuse returned error 1 (with TrueCrypt)

[Jesús Diéguez Fernández]

Same issue here with Ubuntu 10.04 Lucid AMD64 and True Crypt 7.0a, was
working until I updated last week:

Linux ubuntu 2.6.32-30-generic #59-Ubuntu SMP Tue Mar 1 21:30:46 UTC
2011 x86_64 GNU/Linux

$ apt-cache showpkg libfuse2
Package: libfuse2
Versions: 
2.8.1-1.1ubuntu3.1
2.8.1-1.1ubuntu2 
Dependencies: 
2.8.1-1.1ubuntu3.1 - libc6 (2 2.7) mount (2 2.17.2-0ubuntu1.10.04.1) fuse-utils 
(0 (null)) fuse-utils (3 2.8.1-1.1ubuntu3.1) 
2.8.1-1.1ubuntu2 - libc6 (2 2.7) fuse-utils (0 (null)) fuse-utils (3 
2.8.1-1.1ubuntu2) 

If I downgrade to 2.8.1-1.1ubuntu2  then it uninstalls the following
packages: fuse-utils gvfs-fuse ntfs-3g ntfsprogs sshfs. :(

Is there something I can do to help solving it?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727220

Title:
  Command fuse returned error 1 (with TrueCrypt)

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs