Thanks for the help Claus, really appreciate it. Unfortunately, adding
c709 to that hidraw* is the very first thing I tried on seeing your
last post (kinda "monkey see, monkey do" :-) ). It doesn't help.
And now after more tinkering around at the weekend, I am even more
confused. I tried to run hid2hci manually with the params implied by
the matching rules in 70-hid2hci.rules, and it doesn't even accept the
params. For example it doesn't like the devpath argument (the fact
there is one, not its value) and it does not accept a --method value
of logitech-hid, closest acceptable value is logitech.
Looks like the hid2hci program on my machine is not the one udev is
expecting. And it further looks like the change may have come from the
bluez package, which is same version in testing as unstable, whose
NEWS entry says it introduced a new hid2hci program.
But if this were as simple as a conflict between these 2 packages, I'd
expect to see many more people affected than seem to be...
Mark
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
