Bluetooth Keyboard hard to connect and loses connection on reboot/timeout
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
*******
Marked as Duplicate:
The connection problems are not a duplicate but the disconnection problems were a duplicate.
Since I did eventually get connected (even though it was beyond what most people might have tried) I marked this as a duplicate bug. I don't know if the way it (fails) to connect/pair in my case is related to the way that it disconnects.
*******
Binary package hint: bluez
Using a Logitech Mediaboard Pro Wireless Keyboad with integrated trackpad (touchpad) and an IOGear class 1 bluetooth adapter (GBU321) pairing requires repeatedly running the wizard even after reported success.
Description: Ubuntu 10.10
Release: 10.10
bluez:
Installed: 4.69-0ubuntu2
Candidate: 4.69-0ubuntu2
Version table:
*** 4.69-0ubuntu2 0
500 http://
100 /var/lib/
What I expected to happen:
Plug in bluetooth adapter. Use wired or rf keyboard to go to bluetooth preference dialogue. Start 'set up new device wizard'. Turn on keyboard. Detect. Enter pin. Presto, bluetooth keyboard works henceforth.
What happens:
Plug in bluetooth adapter. Use wired or rf keyboard to go to bluetooth preference dialogue. Start 'set up new device wizard'. Turn on keyboard. Detect. Enter pin. Success reported. Second dialogue box pops up asking for pin to be entered into a textbox field (enter with rf or wired keyboard this time since bluetooth isn't actually working yet). At the 'bluetooth properties' window remove the device and then start 'set up new device wizard'. Turn on BT keyboard. Detect. Enter pin. This time (hopefully) the bluetooth works after entering the pin and no more dialogue boxes. (or else use the wired KB to enter pin in dialogue box, repeat the remove and set up new device wizard process until it does work). Hooray it's working...
but now at first reboot or timeout (~1/2 hour) the bluetooth connection is lost and we must repeat the process (or install blueman and bluez-compat and use hidd --search to reconnect).... NOTE: this failure to stay connected seems to be part of this bug: https:/
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: bluez 4.69-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.35-
Architecture: i386
Date: Sat Jan 1 19:09:26 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: MSI MS-7636
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: bluez
dmi.bios.date: 07/05/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.8
dmi.board.
dmi.board.name: H55M-E33(MS-7636)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-7636
dmi.product.
dmi.sys.vendor: MSI
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: 00:02:72:AC:C8:EA ACL MTU: 1021:7 SCO MTU: 64:1
UP RUNNING PSCAN ISCAN
RX bytes:11110 acl:499 sco:0 events:108 errors:0
TX bytes:2386 acl:36 sco:0 commands:48 errors:0
rfkill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
description: | updated |
description: | updated |