Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#27141 - [hplip] Invalid keys in the udev rules
Attached to Project:
Arch Linux
Opened by Hector Mtz-Seara Monne (hseara) - Sunday, 20 November 2011, 13:15 GMT
Last edited by Eric Belanger (Snowman) - Tuesday, 10 January 2012, 03:24 GMT
Opened by Hector Mtz-Seara Monne (hseara) - Sunday, 20 November 2011, 13:15 GMT
Last edited by Eric Belanger (Snowman) - Tuesday, 10 January 2012, 03:24 GMT
|
DetailsDescription:
After yesterday update I get the following message when rebooting the computer (the computer boots fine): ##################################################### Sun Nov 20 12:45:34 2011: :: Starting UDev Daemon [BUSY] [DONE] Sun Nov 20 12:45:34 2011: :: Triggering UDev uevents [BUSY] [DONE] Sun Nov 20 12:45:34 2011: :: Loading User-specified Modules [BUSY] udevd[221]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/86-hpmud-hp_laserjet_p1005.rules:6 Sun Nov 20 12:45:34 2011: Sun Nov 20 12:45:34 2011: udevd[221]: invalid rule '/etc/udev/rules.d/86-hpmud-hp_laserjet_p1005.rules:6' Sun Nov 20 12:45:34 2011: Sun Nov 20 12:45:34 2011: udevd[221]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/86-hpmud-hp_laserjet_p1005.rules:9 Sun Nov 20 12:45:34 2011: Sun Nov 20 12:45:34 2011: udevd[221]: invalid rule '/etc/udev/rules.d/86-hpmud-hp_laserjet_p1005.rules:9' Sun Nov 20 12:45:34 2011: Sun Nov 20 12:45:34 2011: [FAIL] Sun Nov 20 12:45:34 2011: :: Waiting for UDev uevents to be processed [BUSY] [DONE] #################################################### The rules in question are those coming with the hplip package for my printer (this is only one example). Since then the printer don't work, not that I'm surprise. Here is the rule: ###################################################### # Load hp firmware for this printer. ACTION!="add", GOTO="hpmud_rules_end" # hp_laserjet_p1005 for Suse 10.3 SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="3d17", PROGRAM="/bin/sh -c 'logger -p user.info loading hp_laserjet_p1005 firmware $env{BUSNUM} $env{DEVNUM}'", RUN+="/bin/sh -c '/usr/bin/hp-firmware -y3 -s$env{BUSNUM}:$env{DEVNUM} &'" # hp_laserjet_p1005 SUBSYSTEM=="usb_device", SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="3d17", PROGRAM="/bin/sh -c 'X=%k; X=$${X#usbdev}; B=$${X%%%%.*}; D=$${X#*.}; logger -p user.info loading hp_laserjet_p1005 firmware $$B $$D; printf %%03i:%%03i $$B $$D'", RUN+="/bin/sh -c '/usr/bin/hp-firmware -y3 -s%c &'" LABEL="hpmud_rules_end" ###################################################### I guess that one of this two updates triggered the problem: libusb-compat (0.1.3-1 -> 0.1.3-2) linux (3.1-4 -> 3.1.1-1) Additional info: * package version(s) * config and/or log files etc. My system is fully updated. extra/hplip 3.11.10-1 Steps to reproduce: |
This task depends upon
Closed by Eric Belanger (Snowman)
Tuesday, 10 January 2012, 03:24 GMT
Reason for closing: Not a bug
Additional comments about closing: The SYSFS key was removed by upstream in latest hplip release. I guess the plugin package in AUR will get the same change.
Tuesday, 10 January 2012, 03:24 GMT
Reason for closing: Not a bug
Additional comments about closing: The SYSFS key was removed by upstream in latest hplip release. I guess the plugin package in AUR will get the same change.
error: No package owns /etc/udev/rules.d/86-hpmud-hp_laserjet_1005_series.rules
Solution: Delete the hp rules from /etc/udev/rules.d/ and install from AUR hplip-plugin. Every should work then.
You can report the problem upstream. Some of us has already done it but they have ignored us as most of distributions still do not suffer this problem as they use old udev versions. I hope this helps.