SYSFS{}= will be removed in a future udev version

Fixed in gpsd 2.90.1~svn6819-1

HPLIP provides UDEV rules from upstream. They also need to be fixed (in the main package and in the proprietary plug-ins). Adding upstream task for HPLIP.

I checked the HPLIP udev rules in Lucid and did not find any SYSFS in them, Marking HPLIP in Ubuntu as fixed.

HP developers, please check also the upstream packaghe of HPLIP and especially the proprietary plug-in (I do not have it installed currently).

HPLIP got fixed in bug 491346.

brltty fixed already in bug 491775

This bug was fixed in the package libnjb - 2.2.5-4.2ubuntu4

---------------
libnjb (2.2.5-4.2ubuntu4) lucid; urgency=low

  * Switch udev rules from SYSFS to ATTR (Closes 560700, LP: #512464).
 -- Kees Cook <email address hidden> Fri, 05 Mar 2010 19:19:00 -0800

Sorry, 2.90.1~svn6819-1 did not fix the issue, but 2.90-1 does. Will be fixed when https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/534022 is done.

Hello, I get the same warnings after upgrading to 10.04 from 9.10 yesterday. It concerns libnjb and hso.

SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/45-libnjb.rules:22

udevd[384]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:82

/etc/udev/rules.d/45-libnjb.rules is not longer shipped by the libnjb5 package and are deleted (or renamed) on upgrade. If you're running Lucid, it should be safe to delete the file from /etc since the new rules are in /lib now.

I've the same problem and since I've upgraded to Lucid, I wonder if I have to delete all the rules which are in /etc/udev/rules.d. Moreover I want to know if udev still search also in such a directory or if it can be deleted too.
Finally since I have the following rule 10-vboxdrv.rules:

KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="root", MODE="0600"
SUBSYSTEM=="usb_device", GROUP="vboxusers", MODE="0664"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", GROUP="vboxusers", MODE="0664"

which I've written to change file permission of usb device in order to use them with virtualbox, can I move it to /lib/udev/rules.d?

Thank you,
Xwang

I've seen similar errors when installing HPLIP 3.11.1-2 on Debian Sqeeze.

Same errors on Maverick 10.10 (GNOME):

$ uname -a
Linux . 2.6.35-28-generic #49-Ubuntu SMP Tue Mar 1 14:40:58 UTC 2011 i686 GNU/Linux

Note: the system has been continually upgraded since dapper.

$ ls -al /etc/udev/rules.d/
total 104
drwxr-xr-x 2 root root 4096 2011-02-18 08:48 .
drwxr-xr-x 3 root root 4096 2011-01-20 21:02 ..
lrwxrwxrwx 1 root root 20 2009-03-22 12:23 025_libticables.rules -> ../libticables.rules
lrwxrwxrwx 1 root root 22 2008-04-25 20:17 025_logitechmouse.rules -> ../logitechmouse.rules
-rw-r--r-- 1 root root 613 2011-02-18 08:48 10-vboxdrv.rules
-rw-r--r-- 1 root root 814 2008-04-11 05:21 40-basic-permissions.rules~
-rw-r--r-- 1 root root 818 2009-03-10 14:42 40-basic-permissions.rules.dpkg-bak
-rw-r--r-- 1 root root 3513 2008-09-12 13:41 40-permissions.rules~
-rw-r--r-- 1 root root 3368 2008-09-12 13:48 40-permissions.rules.dpkg-bak
-rw-r--r-- 1 root root 3109 2008-04-11 05:21 40-permissions.rules.dpkg-dist
-rw-r--r-- 1 root root 34568 2008-04-10 09:24 45-libmtp7.rules
-rw-r--r-- 1 root root 1704 2008-06-19 02:53 45-libnjb5.rules
-rw-r--r-- 1 root root 170 2010-04-19 09:40 45-scsi-scanner.rules
-rw-r--r-- 1 root root 181 2009-09-05 15:04 45-scsi-scanner.rules~
-rw-r--r-- 1 root root 37 2008-04-22 15:15 50-libibverbs1.rules
-rw-r--r-- 1 root root 927 2007-10-03 17:32 70-persistent-cd.rules
-rw-r--r-- 1 root root 629 2009-05-06 14:17 70-persistent-net.rules
-rw-r--r-- 1 root root 1365 2009-08-04 11:12 85-usbmuxd.rules
-rw-r--r-- 1 root root 599 2009-06-15 02:22 89-libiphone.rules
-rw-r--r-- 1 root root 1157 2009-11-03 02:26 README
lrwxrwxrwx 1 root root 13 2011-01-20 23:04 z80_user.rules -> ../user.rules

$ cat /var/log/boot.log
fsck from util-linux-ng 2.17.2
udevd[361]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /etc/udev/rules.d/025_libticables.rules:6

udevd[361]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/025_libticables.rules:6

udevd[361]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /etc/udev/rules.d/025_logitechmouse.rules:1

udevd[361]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/025_logitechmouse.rules:5

udevd[361]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/025_logitechmouse.rules:6

udevd[361]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/025_logitechmouse.rules:7

udevd[361]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/025_logitechmouse.rules:8

udevd[361]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match...

Hi. I have the Same messages in boot.log but the path is /lib/udev/rules.d/40-avrice.rules:[4|7]

System is oneiric (11.10) with kernel 3.0.0.14-generic

content of 40-avrice.rules is:
-snip-
SUBSYSTEM!="usb_device", ACTION!="add", GOTO="avarice_end"

# Atmel Corp. JTAG ICE mkII
SYSFS{idVendor}=="03eb", SYSFS{idProduct}=="2103", MODE="660", GROUP="dialout"

# Atmel Corp. AVR Dragon
SYSFS{idVendor}=="03eb", SYSFS{idProduct}=="2107", MODE="660", GROUP="dialout"

LABEL="avarice_end"
-snap-

line 4 and 7 are the blank lines between!

Can i simply delete the blank lines to fix it???

Hi,

This is not related to space, needs to replace SYSFS attribute either with ATTR or ATTRS attribute.

e.g.
ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2107", MODE="660", GROUP="dialout"

Thanks & Regards,
Amarnath

Fix released in hplip-3.11.12.