*** This bug is a duplicate of bug 123920 ***
https://bugs.launchpad.net/bugs/123920
I have traced this problem to the Logitech Mini-Received.
This bluetooth receiver supports two modes; in the default mode, it
handles the bluetooth communications and shows an USB HID mouse and an
USB HID keyboard to the system. If you press the reset button while you
connects the dongle or runs the hid2hci tool, it gets transformed in an
standard usb bluetooth dongle.
By default, hid2hci tool gets called at bluetooth subsystem
initizalization (/etc/init.d/bluetooth start). So, at gdm prompt it
seems an standard usb dongle.
When any key is pressed in the keyboard, the keyboard tries to connect
to the computer. HID bluetooth devices uses two LCAP connection, one for
control and one for interrupts. bluetoothd-service-input setups the
control connection correctly, but when the interrupt connection is being
setting up, the usb dongle gets confused and 5 seconds later it resets
itself. I have attached a hcidump trace that shows it.
If the user don't press any key and initiates the connections from the
host to the device (using an vnc session, a wired keyboard...), all go
okay and you have a working keyboard and bluetooth dongle; just until
the connection is lost.
In Windows XP SP2, using the Microsoft BT stack, the dongle works okay
in either case (when the computer connects to the keyboard and when the
keyboard connects to the computer). So it seems like a compatibility
issue between the dongle and bluez stack.
--
logitech dinovo edge bluetooth sometimes works, sometimes not
https://bugs.launchpad.net/bugs/151559
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
