[systemd-bugs] [Bug 89787] New: udev rule doesn't load automatcially (but manually) for a specific device under certain situtations
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Mar 26 23:31:55 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=89787
Bug ID: 89787
Summary: udev rule doesn't load automatcially (but manually)
for a specific device under certain situtations
Product: systemd
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: general
Assignee: systemd-bugs at lists.freedesktop.org
Reporter: tom.ty89 at gmail.com
QA Contact: systemd-bugs at lists.freedesktop.org
I have two Logitech usb receivers for mouse and keyboard (non-Bluetooth), one
is a "Unifying" receiver and the other is an older traditional one. (Same
idVendor attribute)
The traditional one has a default value of "enabled" for power wakeup (and the
Unifying one has "disabled").
When I try set it to disabled with a udev rule, I found that the rule get
loaded automatically only if it is the only receiver plugged in, or when it's
plugged into a port with a smaller port number than the Unifying one (port
number as shown in lsusb -t, which are presistent among boots).
Otherwise I have to unplug and plug again, or run `udevadm test` to make it
load (which indicates that the rules written are fine I assume).
In another case when none of the receivers were plugged in before boot, I still
need to plug in the receiver twice to get the rules loaded.
It doesn't seem to matter whether I match the device with the idVendor
attribute. Even when I test with rule like `SUBSYSTEM=="USB" and
ATTR="enabled"/"disabled"`, the receiver seems to be an exception (though I
only got the two, others are just the "usb bus").
Yet the Unifying one doesn't have this problem, no matter which port it's
plugged into, the value can be set to enabled without a hassle.
I also have two flash drives plugged into Port 1 and 2 among the tests, which
doesn't seem to affect.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150327/2092d557/attachment.html>
More information about the systemd-bugs
mailing list