Intrepid: Sensor can't be used after resume from hibernation

[Matthäus Brandl]

On my Thinkpad X60s running Intrepid I noticed that after resuming from hibernation the fingerprint reader is no longer available. (sudo, gdm and gksudo only asking for my password, not to swipe finger)
After a normal boot tf-tool correctly communicates with the sensor and recognizes my finerprint. But after resuming from hibernation tf-tool yields this message:
$ tf-tool --verify --verbose

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <email address hidden>

Running in verbose mode.

* Mode: verify
* Biometric identification record file: '/home/matthaeus/.thinkfinger.bir'

Initializing...Sending HELLO failed.

The Fingerprint Reader still shows up in lsusb and lshal.
dmesg shows an interesting entry connected with tf-tool:
[ 1030.834881] usb 4-2: usbfs: USBDEVFS_CONTROL failed cmd tf-tool rqt 0 rq 9 len 0 ret -71

I'm using kernel 2.6.27-7-generic, libpam-thinkfinger is 0.3+r118-0ubuntu3 (affects 0.3+r118-0ubuntu4~ppa1 from the PPA by Jon Oberheide as well (see #256429))

[Matthäus Brandl (matthaeus)]

Never mind, I realized today that everything works fine again though I don't know what changed the problem.

[Matthäus Brandl (matthaeus)]

This bug doesn't appear anymore

[stecklum (stecklum)]

It is still there on my M1330 running 2.6.27-8-generic. A workaround is to unload/load uhci_hcd from the command line. Un/re-loading using /etc/default/acpi-support does not work.

[Matthäus Brandl (matthaeus)]

Status changed to confirmed due to stecklum's post

[Matthäus Brandl (matthaeus)]

That's kind of frustrating, sometimes I can use my sensor sometimes not. (after a wake up)
And still no idea what's causing this. (my guess would be HAL though)

[Matthäus Brandl (matthaeus)]

I just discovered, that the sensor is not usable after I resume from a "suspend to disk" (Fn-F12) but it is usable after a "suspend to ram" (Fn-F4) even if it wasn't usable before the "suspend to ram"

[Matthäus Brandl (matthaeus)]

Seems to be fixed in jaunty

[Matthäus Brandl (matthaeus)]

% apt-cache policy libthinkfinger0
libthinkfinger0:
  Installed: 0.3+r118-0ubuntu3
  Candidate: 0.3+r118-0ubuntu3
  Version table:
 *** 0.3+r118-0ubuntu3 0
        500 http://de.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

[AndyL (thelees-andy)]

I'm still seeing these symptoms on jaunty

apt-cache policy libthinkfinger0
libthinkfinger0:
  Installed: 0.3+r118-0ubuntu5~ppa1
  Candidate: 0.3+r118-0ubuntu5~ppa1
  Version table:
 *** 0.3+r118-0ubuntu5~ppa1 0
        500 http://ppa.launchpad.net jaunty/main Packages
        100 /var/lib/dpkg/status
     0.3+r118-0ubuntu3 0
        500 http://us.archive.ubuntu.com jaunty/main Packages

[Matthäus Brandl (matthaeus)]

No problems here:
% LC_ALL=C apt-cache policy libthinkfinger0
libthinkfinger0:
  Installed: 0.3+r118-0ubuntu4
  Candidate: 0.3+r118-0ubuntu4
  Version table:
 *** 0.3+r118-0ubuntu4 0
        500 http://ppa.launchpad.net jaunty/main Packages
        100 /var/lib/dpkg/status
     0.3+r118-0ubuntu3 0
        500 http://de.archive.ubuntu.com jaunty/main Packages

I don't know which ppa you use, but seems like that is the problem.
I use Tom Jaeger's: https://launchpad.net/~thjaeger/+archive/ppa
% cat /etc/apt/sources.list.d/thinkfinger.list
# Recent, non-delayed variants of thinkfinger
# 2009-07-10
deb http://ppa.launchpad.net/thjaeger/ppa/ubuntu jaunty main

Other information:
% uname -r
2.6.28-15-generic
% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 9.04
Release: 9.04
Codename: jaunty