This can be handled by the module loader (i.e. GDM) and in any case we
may want to have setups where fprintd is always active waiting for a
fingerprint, as modern devices support this with no problems.
Currently translated at 100.0% (60 of 60 strings)
Co-authored-by: Oğuz Ersen <oguzersen@protonmail.com>
Co-authored-by: Weblate <noreply@weblate.org>
Translate-URL: https://translate.fedoraproject.org/projects/fprintd/fprintd/tr/
Translation: fprintd/fprintd
Currently translated at 100.0% (60 of 60 strings)
Co-authored-by: Pavel Borecki <pavel.borecki@gmail.com>
Co-authored-by: Weblate <noreply@weblate.org>
Translate-URL: https://translate.fedoraproject.org/projects/fprintd/fprintd/cs/
Translation: fprintd/fprintd
Currently translated at 100.0% (60 of 60 strings)
Co-authored-by: Jan Kuparinen <copper_fin@hotmail.com>
Co-authored-by: Weblate <noreply@weblate.org>
Translate-URL: https://translate.fedoraproject.org/projects/fprintd/fprintd/fi/
Translation: fprintd/fprintd
Currently translated at 100.0% (60 of 60 strings)
Co-authored-by: Thibault HEINRICH <thibault@lexikal-seo.net>
Co-authored-by: Weblate <noreply@weblate.org>
Translate-URL: https://translate.fedoraproject.org/projects/fprintd/fprintd/fr/
Translation: fprintd/fprintd
This was forgotten after the last string changes in commit b483edbe.
Co-authored-by: Thibault HEINRICH <thibault.heinrich@ac-nancy-metz.fr>
Fixes: #123
PrivateNetwork=true is a bad idea, as it means that udev events cannot
be delivered. Remove it, we already restrict the address families
sufficiently anyway.
Closes: #119
This was never really used and it's breaking meson 60.
While this may just become a warning in 60.1, it's just better to avoid
using it.
See: https://github.com/mesonbuild/meson/issues/9441
Currently translated at 100.0% (60 of 60 strings)
Co-authored-by: Pavel Borecki <pavel.borecki@gmail.com>
Co-authored-by: Weblate <noreply@weblate.org>
Translate-URL: https://translate.fedoraproject.org/projects/fprintd/fprintd/cs/
Translation: fprintd/fprintd
Currently translated at 100.0% (60 of 60 strings)
Translated using Weblate (Marathi)
Currently translated at 5.0% (3 of 60 strings)
Co-authored-by: Weblate <noreply@weblate.org>
Co-authored-by: girish joshi <girish946@gmail.com>
Translate-URL: https://translate.fedoraproject.org/projects/fprintd/fprintd/mr/
Translation: fprintd/fprintd
If the user specified "any" finger, then we would mirror this back even
if there is only one finger available. Change it so that we act as if
that finger was passed explicitly, meaning we use the "verify" method
and also send the signal for the selected finger accordingly.
While the delay inhibitor is grabbed almost immediately, this can be
slow enough to not have happened immediately after the bus name has been
registered. Add a generous timeout to prevent issues.
If a print we have stored locally is not available in device anymore, we
need to cleanup the local database.
We do not get a proper DATA_NOT_FOUND error for most devices (indeed, at
this point no device does this properly). As such, do this when we see a
DATA_NOT_FOUND error and the first time that we get a verify-no-match
results on a device which is capable of listing all known prints.
Co-Authored-by: Marco Trevisan (Treviño) <mail@3v1n0.net>
In case we got a data-not-found error, it means that the device has not
such prints stored, and thus the verification failed, and there's no
need to expose the internal reasons to fprintd clients.
