Request of testing new fingerprint reader library
Hello list(s), we, together with Florian "Sp1rit" have created packages for "new" libfprint- tod library/fork, which is going to replace current one used in distribution. This library has advantage of loading external drivers as libraries, typically closed source ones. These closed source drivers are soon going to appear on Packman as "libfprint2-tod1-*" packages (the SR is pending). The library source code is located on https://gitlab.freedesktop.org/3v1n0/libfprint/-/ tree/tod and is always re-based on current libfprint "upstream". It is also the default one in Ubuntu, Arch and Debian (if i checked correctly). We are able to test the closed source drivers, since we have access to devices using them. However, what we cannot test are fingerprint readers, that are supported directly by libfprint library. For this, i would like to ask anyone, who is using his fingerprint reader on openSUSE Tumbleweed with libfprint library to test with this new library using following steps: 1) Add home:sp1rit:factory repository: :~> sudo zypper ar --refresh --name libfprint-tod https:// download.opensuse.org/repositories/home:/sp1rit:/factory/openSUSE_Tumbleweed/ home:sp1rit:factory.repo 2) Install libfprint-2-2 package from it (and do NOT install libfprint-2- tod1): :~> sudo zypper in --from libfprint-tod libfprint-2-2 fprintd 3) Open one terminal window, su to root and start fprintd in debug mode: :~> su [enter] :~ # env G_MESSAGES_DEBUG=all /usr/libexec/fprintd 4) Open second terminal window and enroll or verify fingerprint (as normal user): :~> fprintd-enroll or :~> fprintd-verify That is all. After this test, please send us output from the terminal window, that you started fprintd in debug mode (step 3) in. You can use https:// paste.opensuse.org/ for that. For switching back to original libfprint, just remove the repository: :~> sudo zypper rr libfprint-tod and install original libfprint :~> sudo zypper in libfprint-2-2 fprintd That should be all. @Fridrich, @Matthias, @Timo: I am CCing you in case you missed discussion that happened on Factory ML. If you have any objection against planned switch, please step up now. We will be doing SR to hardware/libfprint in forthcomming days, when we get some confirmation that it is working correctly for the users using "native" libfprint. Thanks very much to everyone involved for helping openSUSE get better and better! Regards and happy hacking, Gryffus
On Wed, May 18, 2022 at 5:51 PM Lukáš Krejza <gryffus@hkfree.org> wrote:
Hello list(s),
we, together with Florian "Sp1rit" have created packages for "new" libfprint- tod library/fork, which is going to replace current one used in distribution. This library has advantage of loading external drivers as libraries, typically closed source ones. These closed source drivers are soon going to appear on Packman as "libfprint2-tod1-*" packages (the SR is pending). The library source code is located on https://gitlab.freedesktop.org/3v1n0/libfprint/-/ tree/tod and is always re-based on current libfprint "upstream". It is also the default one in Ubuntu, Arch and Debian (if i checked correctly).
We are able to test the closed source drivers, since we have access to devices using them. However, what we cannot test are fingerprint readers, that are supported directly by libfprint library.
For this, i would like to ask anyone, who is using his fingerprint reader on openSUSE Tumbleweed with libfprint library to test with this new library using following steps:
1) Add home:sp1rit:factory repository: :~> sudo zypper ar --refresh --name libfprint-tod https:// download.opensuse.org/repositories/home:/sp1rit:/factory/openSUSE_Tumbleweed/ home:sp1rit:factory.repo
2) Install libfprint-2-2 package from it (and do NOT install libfprint-2- tod1): :~> sudo zypper in --from libfprint-tod libfprint-2-2 fprintd
3) Open one terminal window, su to root and start fprintd in debug mode: :~> su [enter] :~ # env G_MESSAGES_DEBUG=all /usr/libexec/fprintd
4) Open second terminal window and enroll or verify fingerprint (as normal user): :~> fprintd-enroll or :~> fprintd-verify
That is all. After this test, please send us output from the terminal window, that you started fprintd in debug mode (step 3) in. You can use https:// paste.opensuse.org/ for that.
For switching back to original libfprint, just remove the repository: :~> sudo zypper rr libfprint-tod and install original libfprint :~> sudo zypper in libfprint-2-2 fprintd
That should be all.
@Fridrich, @Matthias, @Timo: I am CCing you in case you missed discussion that happened on Factory ML. If you have any objection against planned switch, please step up now. We will be doing SR to hardware/libfprint in forthcomming days, when we get some confirmation that it is working correctly for the users using "native" libfprint.
Thanks very much to everyone involved for helping openSUSE get better and better!
Is there any plan to reconcile this back into mainline? Or is this a permanent incompatible fork of libfprint? The previous discussion[1] didn't seem to indicate there was any such plan going on. It seems kind of bad to switch to a fork like this without at least some kind of plan for reconciling them. [1]: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/6... -- 真実はいつも一つ！/ Always, there's only one truth!
Dne čtvrtek 19. května 2022 0:04:06 CEST, Neal Gompa napsal(a):
On Wed, May 18, 2022 at 5:51 PM Lukáš Krejza <gryffus@hkfree.org> wrote:
Hello list(s),
we, together with Florian "Sp1rit" have created packages for "new" libfprint- tod library/fork, which is going to replace current one used in distribution. This library has advantage of loading external drivers as libraries, typically closed source ones. These closed source drivers are soon going to appear on Packman as "libfprint2-tod1-*" packages (the SR is pending). The library source code is located on https://gitlab.freedesktop.org/3v1n0/libfprint/-/ tree/tod and is always re-based on current libfprint "upstream". It is also the default one in Ubuntu, Arch and Debian (if i checked correctly).
We are able to test the closed source drivers, since we have access to devices using them. However, what we cannot test are fingerprint readers, that are supported directly by libfprint library.
For this, i would like to ask anyone, who is using his fingerprint reader on openSUSE Tumbleweed with libfprint library to test with this new library using following steps:
1) Add home:sp1rit:factory repository: :~> sudo zypper ar --refresh --name libfprint-tod https://
download.opensuse.org/repositories/home:/sp1rit:/factory/openSUSE_Tumblewe ed/ home:sp1rit:factory.repo
2) Install libfprint-2-2 package from it (and do NOT install libfprint-2-
tod1): :~> sudo zypper in --from libfprint-tod libfprint-2-2 fprintd
3) Open one terminal window, su to root and start fprintd in debug mode: :~> su [enter] :~ # env G_MESSAGES_DEBUG=all /usr/libexec/fprintd
4) Open second terminal window and enroll or verify fingerprint (as normal
user): :~> fprintd-enroll
or
:~> fprintd-verify
That is all. After this test, please send us output from the terminal window, that you started fprintd in debug mode (step 3) in. You can use https:// paste.opensuse.org/ for that.
For switching back to original libfprint, just remove the repository: :~> sudo zypper rr libfprint-tod
and install original libfprint
:~> sudo zypper in libfprint-2-2 fprintd
That should be all.
@Fridrich, @Matthias, @Timo: I am CCing you in case you missed discussion that happened on Factory ML. If you have any objection against planned switch, please step up now. We will be doing SR to hardware/libfprint in forthcomming days, when we get some confirmation that it is working correctly for the users using "native" libfprint.
Thanks very much to everyone involved for helping openSUSE get better and better!
Is there any plan to reconcile this back into mainline? Or is this a permanent incompatible fork of libfprint? The previous discussion[1] didn't seem to indicate there was any such plan going on. It seems kind of bad to switch to a fork like this without at least some kind of plan for reconciling them.
[1]: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/ 6R75CILJ3GAUSKMNJ7ERYZLH75QF5UHX/
The original plan was to do that, but since it has not been the case yet (and it is already some time that this fork exist), distributions started to switch to this one for the time being. It does not seem that this fork will merge back to mainline anytime soon, so we are just following general "trend" of other distros to support more use-cases and hardware for the users. Also, the mainline devs are actively solving bugs reported by users using the "-tod" fork, as you can see for example here: https://gitlab.freedesktop.org/ libfprint/libfprint/-/issues/436 . Also, developers themselves are pointing users to the fork, as you can see here: https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/267 Regards, Gryffus
Am Mittwoch, 18. Mai 2022, 23:51:02 CEST schrieb Lukáš Krejza:
That is all. After this test, please send us output from the terminal window, that you started fprintd in debug mode (step 3) in. You can use https:// paste.opensuse.org/ for that.
Here you go: https://paste.opensuse.org/8687230 HTH Axel
Dne čtvrtek 19. května 2022 10:18:25 CEST, Axel Braun napsal(a):
Am Mittwoch, 18. Mai 2022, 23:51:02 CEST schrieb Lukáš Krejza:
That is all. After this test, please send us output from the terminal window, that you started fprintd in debug mode (step 3) in. You can use https:// paste.opensuse.org/ for that.
Here you go: https://paste.opensuse.org/8687230
HTH Axel
Thank you very much! Regards, Gryffus
participants (3)
-
Axel Braun -
Lukáš Krejza -
Neal Gompa