** Changed in: thinkfinger (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/138957
Title:
(gutsy) lock screen doesn't support fingerprint readers driven by
** Changed in: thinkfinger (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/138957
Title:
(gutsy) lock screen doesn't support fingerprint readers driven by
hi,
I am using a thinkpad x300 with ubuntu jaunty.
thinkfinger is working great except for unlocking the screensaver.
I can't find the file .thingfinger.bir you are talking about.
I am new to linux. Can you explain me how to change permissions on
home/.thinkfinger.bir ?
Thanks
--
(gutsy) lock
I did all the 3 steps (owner for .thinkfinger.bir, owner for uinput and
udev rule) and it still doesn't unlock my screensaver. Any ideas?
--
(gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
https://bugs.launchpad.net/bugs/138957
You received this bug notification
I should add a 4th thing to do :
4. give /dev/input/uinput the right permissions for gnome-screensaver to
work :
chmod g+w /dev/input/uinput
On my system, the udev rule didn't apply instantly, and I needed the
chmod, else G-S never showed or swipe finger prompt and swiping
didn't work.
Doing 3 things fixed this for me.
1. Change the permissions on $HOME/.thinkfinger_bir so that it is owned
by the user, not by root:
$ sudo chown pauljohn .thinkfinger.bir
2. Changing the permissions of the uinput device, which was root:root,
and instead this is needed:
chown root\:plugdev
Broken again for Intrepid and Jaunty. A udev rule appears to be one
possible solution.
** Also affects: thinkfinger (Ubuntu)
Importance: Undecided
Status: New
--
(gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
https://bugs.launchpad.net/bugs/138957
You
The fix described in
https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/138957/comments/18,
and included as an attachment here, fixes this for me in Jaunty as well
as Intrepid.
What would it take to get that as a fix to be included in our
thinkfinger distribution?
** Attachment added:
It works for me consistently after applying the change of ownership
(thank you, by the way). Are you current on updates (I am), and have
you applied the thinkfinge code from the PPA (I have not, yet, since I
haven't checked to see exactly what was changed).
$ dpkg -l | grep thinkfinger
ii
My system is up to date (at least I install everything that auto-updater
reports) and I have the packages from Jon Oberheide's PPA suggested in
the discussion of the 256429 bug:
$ dpkg -l | grep thinkfinger
ii libpam-thinkfinger
Timur,
I presume that you mean after locking the screen you should see 'Password or
swipe finger: ' prompt in the unlock dialog but unlocking doesn't work. Swiping
finger
has no effect and after entering password the dialog hangs saying
'Checking...'.
I am not sure what was unclear about
Noel,
Thanks for the clarification. In my case even if it seems to work after
changing owner, this happens only two or three times and the dialog
hangs again after that. This is really weird.
--
(gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
It seems that the problem has two parts. The first is wrong owner of
/dev/input/uinput: it should be root:plugdev instead of root:root
The second part of the problem can be seen after manually changing the owner:
sudo chown root\:plugdev /dev/input/uinput
Now after locking the screen you
Sorry, forgot to add that this is on Intrepid.
--
(gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
https://bugs.launchpad.net/bugs/138957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Adding
/etc/udev/rules.d/60-thinkfinger.rules
#
# udev rules file for the thinkfinger fingerprint scanner
#
# uinput device
KERNEL==uinput, MODE=0660, GROUP=plugdev
makes it work for me now. Consistently, so far. This is not required
in Hardy (8.04.1).
--
(gutsy) lock screen doesn't
Noel, obviously, this will only set correct owner/permissions. Did you
try to reproduce the second part of the problem in Intrepid?
--
(gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
https://bugs.launchpad.net/bugs/138957
You received this bug notification because
thinkfinger works with gnome-screensaver for me under Hardy, but has
regressed with Intrepid. I do have:
-rw--- 1 noel noel 182 2008-09-14 00:16 .thinkfinger.bir
in my home directory, and thinkfinger works with other programs as we'd
expect (with the other known regression that one has to
Brian,
What did you do to make gnome-screensaver work with thinkfinger. I just
installed it and gdm and sudo work fine, but no gnome-screensaver unlock
without using password
Thanks
--
(gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
Check permissions on your $HOME/.thinkfinger.bir file. Mine was owned
by root and everything worked except gnome-screensaver. Changing
ownership to me solved the problem. I had done the enrollment using
'sudo tf-tool --acquire' because it claimed that the USB device couldn't
be claimed when run
Cool that is the answer what did it for me. Thanks a lot.
--
(gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
https://bugs.launchpad.net/bugs/138957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Either it's broken again or there was a configuration change. It's not
working for me and i have the latest thinkfinger package. sudo, gdm
works. gnome-screensaver isn't.
--
(gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
https://bugs.launchpad.net/bugs/138957
You
/etc/pam.d/common-auth:
authsufficient pam_thinkfinger.so
authrequiredpam_unix.so try_first_pass nullok_secure
--
(gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
https://bugs.launchpad.net/bugs/138957
You received this bug notification because
Nevermind. It works now. Thanks.
--
(gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
https://bugs.launchpad.net/bugs/138957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Reported as working on Hardy with updated thinkfinger packages. Thanks!
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed = Fix Released
--
(gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
https://bugs.launchpad.net/bugs/138957
You received this
With thinkfinger packages 0.3+r118-0ubuntu1 on hardy, gnome screen saver
now unlocks for me. Yay!
--
(gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
https://bugs.launchpad.net/bugs/138957
You received this bug notification because you are a member of Ubuntu
Bugs,
** Summary changed:
- (gutsy) lock screen doesn't seem to use pam
+ (gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
--
(gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
https://bugs.launchpad.net/bugs/138957
You received this bug
If gnome-screensaver isn't root during authentication, then how does an
ordinary password work? They are stored in a root readable file
/etc/shadow. Whatever credential switching that is done in order for
ordinary passwords to work could also be done for thinkfinger to work.
--
(gutsy) lock
Never mind - found the answer. A setuid helper binary is used -
http://linux.die.net/man/8/unix_chkpwd
This means that the correct solution for thinkfinger is to also have a helper
binary that verifies
fingerprint only for the invoking user.
--
(gutsy) lock screen doesn't support fingerprint
28 matches
Mail list logo
