Yes. I agree.
Btw new commits were pushed at Making sure you're not a bot! so maybe they will fix it for u
I have now, in Morphius, sudo and screen unlock working in Kde plasma with Fedora 43 ultramarine, without setenforce 0.
In gnome screen unlock somehow fails due to some interference of the GUI.
These were the steps, if I recall them well. I confess that I asked for some help to my friend Gemini:)
So, assuming you have got the build environment and the necessary depndencies, which I don’t exactly remember. In my terminal chronology it looks they are
sudo dnf install git meson ninja-build gcc gcc-c++ \
glib2-devel libgusb-devel nss-devel pixman-devel \
libusb1-devel libgudev-devel pam-devel \
gobject-introspection-devel python3-docutils
Then
git clone Making sure you're not a bot!
cd libfprint
git checkout 9a6b086
(it’ s the commit that works for my device)
meson setup builddir --prefix=/usr
ninja -C builddir
sudo ninja -C builddir install
The following code to avoid setenforce 0
sudo setenforce 0
sudo ausearch -c fprintd --raw | audit2allow -M my_fprintd_custom
sudo semodule -i my_fprintd_custom.pp
sudo setenforce 1
These were, more or less, the steps I followed.
Maybe also
sudo ldconfig
I did everything in a gnome session, so I spent a lot of time to let it work in such session, but I failed.
I enrolled a fingerprint with the terminal
fprintd-enroll
(no more sudo required)
and then installed kde plasma desktop, where everything works fine.
sudo dnf install @kde-desktop-environmentkde-desktop-environmentkde-desktop-environmentkde-desktop-environment --allowerasing
Disclaimer: I may have missed some step, because it was not a polished install and config, but more a hit and miss thing and I have recovered the above code from the chronology of my terminal app.