Description of problem: On bootup, I get the following message printed to the screen: Starting udev: udevd-work[404]: error opening ATTR{/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1:1.0/power/level} for writing: No such file or directory That device is a fingerprint sensor on my laptop: Bus 006 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor The power directory has a 'wakeup' file, but not a 'level' one. There isn't a kernel driver; its all handled in userspace through fprint (although I don't actually use it) The message isn't logged anywhere; I took a photo with my phone camera to be able to copy it down exactly Version-Release number of selected component (if applicable): udev-145-12.fc12.x86_64 How reproducible: Always Steps to Reproduce: 1. Boot computer 2. 3. Actual results: See error message Expected results: Don't see error message Additional info: If you know how I /can/ adjust the power level, that'd be good - powertop complains about it, but obviously can't do anything about it.
*** Bug 551968 has been marked as a duplicate of this bug. ***
/lib/udev/rules.d/65-libsane.rules:ENV{libsane_matched}=="yes", RUN+="/bin/sh -c 'test -e /sys/$env{DEVPATH}/power/level && echo on > /sys/$env{DEVPATH}/power/level'" $ rpm -qf /lib/udev/rules.d/65-libsane.rules sane-backends-1.0.20-10.fc12.x86_64
can you please give me the output of: # grep -r level /{etc,lib}/udev/rules.d
[root@plum ~]# grep -r level /{etc,lib}/udev/rules.d /etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="08ff", ATTRS{idProduct}=="5501", ATTR{power/level}="auto" /etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="08ff", ATTRS{idProduct}=="2500", ATTR{power/level}="auto" /etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="08ff", ATTRS{idProduct}=="2580", ATTR{power/level}="auto" /etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="00bb", ATTR{power/level}="auto" /etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="00bc", ATTR{power/level}="auto" /etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="00bd", ATTR{power/level}="auto" /etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="00ca", ATTR{power/level}="auto" /etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="05ba", ATTRS{idProduct}=="0007", ATTR{power/level}="auto" /etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="05ba", ATTRS{idProduct}=="0008", ATTR{power/level}="auto" /etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="05ba", ATTRS{idProduct}=="000a", ATTR{power/level}="auto" /etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="061a", ATTRS{idProduct}=="0110", ATTR{power/level}="auto" /etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="147e", ATTRS{idProduct}=="2016", ATTR{power/level}="auto" /etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="08ff", ATTRS{idProduct}=="1600", ATTR{power/level}="auto" /etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="08ff", ATTRS{idProduct}=="2810", ATTR{power/level}="auto" /lib/udev/rules.d/70-printers.rules:# Low-level USB device add trigger /lib/udev/rules.d/70-printers.rules:# Low-level USB device remove trigger /lib/udev/rules.d/65-libsane.rules:ENV{libsane_matched}=="yes", RUN+="/bin/sh -c 'test -e /sys/$env{DEVPATH}/power/level && echo on > /sys/$env{DEVPATH}/power/level'" /lib/udev/rules.d/70-acl.rules:# HPLIP devices (necessary for ink level check and HP tool maintenance)
$ rpm -qf /etc/udev/rules.d/60-fprint-autosuspend.rules libfprint-0.1.0-14.pre2.fc12.x86_64 reassigning
That's Matthew's work.
Matthew fixed this already. *** This bug has been marked as a duplicate of bug 505438 ***