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

2020-09-03 Thread 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

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

2020-07-23 Thread 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

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

2020-07-23 Thread 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

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

2020-07-22 Thread 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

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

2020-07-22 Thread 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

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

2020-05-30 Thread 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

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

2020-05-29 Thread 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

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

2017-07-28 Thread 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

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

2017-05-08 Thread 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

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

2017-05-05 Thread 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:

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

2011-03-30 Thread 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

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

2011-03-09 Thread 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

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

2011-03-08 Thread 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