This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
What is the status on this bug? I would like to get this working but I
have over a 150 other machines to deal with and I don't want to break
other logitech devices just to get this keyboard to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Reassigning to bluez, as hid2hci stuff moved to the bluez project now
and was dropped from udev.
** Package changed: udev (Ubuntu) = bluez (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Odd behavior is still present in Natty. I use the Logitech MX-5500
Revolution combo, and the bluetooth dongle does not show up as a
Bluetooth device by default in Natty at all, though the keyboard/mouse
do work by default in Logitech's fallback mode which connects the
devices as pseudo-wired when
Additional info:
With default Natty configuration in /lib/udev/rules.d/70-hid2hci.rules,
I get the following three devices reported by lsusb:
Bus 005 Device 025: ID 046d:c71c Logitech, Inc.
Bus 005 Device 024: ID 046d:c71b Logitech, Inc.
Bus 005 Device 023: ID 046d:0b06 Logitech, Inc.
After
Ugh, an update to udev (without this patch) just overwrote my fix from
comment #6.
Note to people using my fix: until my patch, or something equivalent,
gets released, first copy /lib/udev/rules.d/70-hid2hci.rules to
/etc/udev/rules.d/ and then apply the patch to that copy. Files in
Mario,
but that would again cause the regressions that we saw in bug 550288,
when we already tried hiddev*|hidraw*
--
udev fails to call hid2hci for Logitech USB Bluetooth adapter
https://bugs.launchpad.net/bugs/658471
You received this bug notification because you are a member of Ubuntu
Bugs,
My problem with the KERNEL==hidraw* line was that it would not match
for my adapter (even though my adapter appeared as a hidraw device).
Was the problem encountered in bug #550288 that it would not match for
KERNEL==hiddev*|hidraw* but it would match for KERNEL==hidraw*?
I ask this, because I
Unfortunately this rule cause eternal grief. It seems now matter how we
switch them around, something will always break for somebody :-(
We already tested the combined hiddev|hidraw rule in bug 550288 (comment
31 ff) and it broke stuff for other people.
Mario, since you wrote hid2hci, do you
Martin:
What about instead settings KERNEL==hid*? That should cover both
hiddev and hidraw devices without being too open.
--
udev fails to call hid2hci for Logitech USB Bluetooth adapter
https://bugs.launchpad.net/bugs/658471
You received this bug notification because you are a member of
** Attachment added: `udevadm monitor` output with original udev rules
https://bugs.launchpad.net/bugs/658471/+attachment/1685145/+files/udevadm_monitor.log
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/658471/+attachment/1685146/+files/BootDmesg.txt
** Attachment
I made the following change in /lib/udev/rules.d/70-hid2hci.rules and
now it works.
KERNEL==hidraw*, ATTRS{idVendor}==046d,
ATTRS{idProduct}==c70[4abc]|c71[34bc], \
changed to:
KERNEL==hiddev*|hidraw*, ATTRS{idVendor}==046d,
ATTRS{idProduct}==c70[4abc]|c71[34bc], \
I don't understand this,
** Tags added: patch
--
udev fails to call hid2hci for Logitech USB Bluetooth adapter
https://bugs.launchpad.net/bugs/658471
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
13 matches
Mail list logo
