** Changed in: pam (Debian)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1817897
Title:
attempting to enable fingerprint with
** Changed in: pam (Debian)
Status: Unknown => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1817897
Title:
attempting to enable fingerprint with
https://forums.lenovo.com/t5/Linux-Discussion/X1-Carbon-2018-X1C6
-FingerPrint-Reader-under-Linux-Ubuntu-18-04/td-p/4255423 seems to
discuss that topic as well
There are no Chicony devices listed in the upstream list of supported
hardware on https://fprint.freedesktop.org/supported-devices.html
I don't have an explanation of the behavior of pam-auth-update, but
Debian bug #923362 has also just been filed regarding pam_systemd
inexplicably getting disabled, and may be related.
** Bug watch added: Debian Bug tracker #923362
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923362
**
I called Lenovo and asked and the support rep I spoke with said that the
X1 Carbon's fingerprint reader isn't supported in Linux yet.
I don't know whether to trust that information as accurate, but that's
what he said.
I don't know whether that's worthy of a separate bug report or not. I
mean,
As far as I can tell, the BIOS is able to see the fingerprint reader --
I just booted into the BIOS and told it to reset the fingerprint data,
and it said that it had done so successfully -- so this appears to be a
Linux-specific issue.
--
You received this bug notification because you are a
I have a new Thinkpad X1 Carbon 6th generation. I can see the
fingerprint reader right next to the trackpad, and the specs say that it
has one, but I don't see it showing up in the output of lspci or lsusb.
Maybe I'm missing it? Maybe it's not supported? Or maybe there's a
hardware issue? I'm not
You are right that pam shouldn't lead to gdm not working in any case.
Knowing the context help to define the priority of the issue though.
The initial report/tools indicate that you are on 19.04, fingerprint
authentification should work out of the box there (if you have a
supported reader, which
So, whether or not I needed to run pam-auth-update, doing so and
enabling fingerprint authentication there should not cause GDM to break,
nor should the other weird behavior I described above be happening.
Having said that, yes, I was trying to enable login with fingerprint. I
googled how to do
Thanks for your bug report, what do you need pam-auth-update? What are
you trying to configure? Enabling log-in with fingerprint shouldn't
requiring having to fiddle with pam tools on a command line if that's
what you are trying to enable
--
You received this bug notification because you are a
Actually, it's even weirder than that.
I went through all this several times while trying to narrow down the
repro steps, and it's all very bizarre. Somehow I managed to get gdm
working again, and then in a logged in gdm session, I enabled
fingerprint, and exited from pam-auth-update, then ran
11 matches
Mail list logo
