Arch Linux

Please read this before reporting a bug:

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#45314 - [systemd] udev's sysfs attributes changed in systemd 220 compared to 219

Attached to Project: Arch Linux
Opened by xduugu (xduugu) - Saturday, 13 June 2015, 12:52 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 20 June 2015, 13:11 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Thomas B├Ąchler (brain0)
Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


For some reason, the sysfs attributes (ATTR) changed in systemd 220 which breaks (some) udev rules (lomoco in my case). I couldn't find any references to this issue. It neither seems to be an intentional change nor, since it breaks the rules itself, to be a display issue in udevadm info.

In the case of lomoco, all the information like idVendor, idProduct, etc. is missing in the usb device folder in the sysfs.

With systemd 219-6:
$ udevadm info -a /dev/input/mouse0 | grep -c ATTR

With systemd 220-5:
$ udevadm info -a /dev/input/mouse0 | grep -c ATTR

Additional info:
* systemd 220-5
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 20 June 2015, 13:11 GMT
Reason for closing:  Fixed
Additional comments about closing:  systemd 221-1
Comment by Dave Reisner (falconindy) - Saturday, 13 June 2015, 13:41 GMT
Could you post an actual diff rather than just a count? 'udevadm test' against the sysfs node might be useful here, too...
Comment by xduugu (xduugu) - Saturday, 13 June 2015, 14:11 GMT
Thanks for your answer. I've attached the requested outputs. The used commands are in the first line of each file as well as in the filename.

udevadm test shows some errors that I noticed before, but didn't compare with the 219 output. It seems that these are the culprits, but I don't know where they could come from.
Comment by xduugu (xduugu) - Saturday, 20 June 2015, 09:21 GMT
It works again with systemd 221-1.