i3lock has no fingerprint-reader specific code, it just uses PAM. see also #852

[Original comment by va@…]

Replying to comment 1 @…:

i3lock has no fingerprint-reader specific code, it just uses PAM. see also #852

I tried to change /etc/pam.d/i3lock and left only

auth required pam_fprintd.so

But this doesn't solve the problem.

I also used slimlock in this case and it works fine.

[Original comment by TonyC]

Closing due to inactivity

[Original comment by moemoe <c+i3wm.org@…>]

I can confirm this behaviour, but it has to do nothing with where i3lock was launched from, at least neither starting from urxvt nor via i3 keybinding works.

This problem seems to be related to the switch pam-fprint -> pam-fprintd.

[Original comment by moemoe <c+i3wm.org@…>]

Okay, just digged a little bit further into the problem, and in fact it's thought to behave like this:

> grep -C1 allow /usr/share/polkit-1/actions/net.reactivated.fprint.device.policy
    <defaults>
      <allow_any>no</allow_any>
      <allow_inactive>no</allow_inactive>
      <allow_active>yes</allow_active>
    </defaults>
--
    <defaults>
      <allow_any>no</allow_any>
      <allow_inactive>no</allow_inactive>
      <allow_active>yes</allow_active>
    </defaults>
--
    <defaults>
      <allow_any>no</allow_any>
      <allow_inactive>no</allow_inactive>
      <allow_active>auth_admin_keep</allow_active>
    </defaults>

No valid/active console kit session means no fingerprint, if I understand this correctly.

From what I can tell we don't believe this to be an i3lock issue. Given the inactivity and the fact that it belongs to the i3lock repository, I will close this issue. If there is reason to believe i3lock needs to be adapted for this, please open a new issue in the correct repository and link this issue there.