Bluetooth Keyboard hard to connect and loses connection on reboot/timeout

Bug #696393 reported by BriC
42
This bug affects 10 people
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://ca.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
        100 /var/lib/dpkg/status
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://bugs.launchpad.net/ubuntu/+source/bluez/+bug/696378

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: bluez 4.69-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic-pae 2.6.35.7
Uname: Linux 2.6.35-23-generic-pae i686
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=/boot/vmlinuz-2.6.35-23-generic-pae root=UUID=67a7ab55-5ad6-4632-9d34-a81e94f8e094 ro quiet splash
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.asset.tag: To Be Filled By O.E.M.
dmi.board.name: H55M-E33(MS-7636)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.8:bd07/05/2010:svnMSI:pnMS-7636:pvr1.0:rvnMSI:rnH55M-E33(MS-7636):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7636
dmi.product.version: 1.0
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

Revision history for this message
BriC (bchabun) wrote :
BriC (bchabun)
description: updated
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.