Bartłomiej Wierciński

@rodgersan you can try to `sudo mkdir /usr/share/python-validity` and start again, but in my case other errors appeared. @veitw why these packages requires python3.9? any ideas to fix that? `sudo...

@rodgersan nope... i think it's a good occasion to upgrade after fixing permission problems with `/usr/share/python-validity` is the package working?

python-validity is creating `backoff` file by itself but the `/usr/share/python-validity` directory must be created and accessible in my case after creating this directory backoff file was created by itself i...

ok i've upgraded fedora to 33 and install python-validity via provided rpm packages i had the same error with backoff file, then i've initialized it via `sudo touch /usr/share/python-validity/backoff` now...

after `sudo touch /usr/share/python-validity/calib-data.bin` i have: ``` gru 10 15:25:50 LT33728 dbus-service[33971]: Traceback (most recent call last): gru 10 15:25:50 LT33728 dbus-service[33971]: File "/usr/lib/python-validity/dbus-service", line 307, in gru 10 15:25:50...

ok sorry for spamming but happy news! i've managed to make it work! :tada: all you have to do is: ```bash sudo touch /usr/share/python-validity/backoff sudo touch /usr/share/python-validity/calib-data.bin # now you...

try to disable the service, `pip uninstall python-validity` (with or w/o sudo idk), uninstall `python3-validity python-validity open-fprintd fprintd-clients fprintd-clients-pam`, remove this folder `sudo rm -rf /usr/share/python-validity`. after that install rpms...

`fprintd-verify` works? if yes then follow manual of yours window manager i've got lightdm with i3 and its automatically asking me about fingers. make sure to have `auth sufficient pam_fprintd.so`...

restart the service, delete all fingers and reenroll, verify? maybe a bug in this project

@fridjon great great job, please attach my PR fridjon/node-smb2#1 also why there is no `SMB2Request('close',...)` in this code, as it is in `readfile.js` @bchelli