bluetooth keyboard connected but not working

Bug #735523 reported by Lionel Montrieux
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: bluez

I have a Logitech Cordless Mediaboard Pro for PS3 wireless keyboard. I can see it using hcitool scan, and I can pair it with my ubuntu. The dongle appears on lsusb as well. However, I can't seem to be able to type anything, even though it seems to be connected correctly.

here is the output of lsusb:
Bus 002 Device 007: ID 050d:016a Belkin Components Bluetooth Mini Dongle
Bus 002 Device 006: ID 0a5c:4503 Broadcom Corp.
Bus 002 Device 005: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 002 Device 004: ID 046d:c058 Logitech, Inc.
Bus 002 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 002 Device 002: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: bluez 4.69-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11
Uname: Linux 2.6.35-27-generic i686
Architecture: i386
Date: Tue Mar 15 15:06:54 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: Acer Aspire R3610
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-27-generic root=UUID=2564cc2c-a832-4a32-8c76-fc2c5abdccc1 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
SourcePackage: bluez
dmi.bios.date: 12/02/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P01-A4L
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: FMCP7A-ION-LE
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A4L:bd12/02/2009:svnAcer:pnAspireR3610:pvr:rvnAcer:rnFMCP7A-ION-LE:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Aspire R3610
dmi.sys.vendor: Acer
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:19:0E:09:63:06 ACL MTU: 1021:8 SCO MTU: 64:1
  UP RUNNING PSCAN
  RX bytes:1026 acl:0 sco:0 events:36 errors:0
  TX bytes:1594 acl:0 sco:0 commands:36 errors:0

Revision history for this message
Lionel Montrieux (lmontrieux) wrote :
Revision history for this message
Lionel Montrieux (lmontrieux) wrote :

Attached is the output of sudo hcidump -XYt, once the keyboard is connected. I typed a few keystrokes and then stopped the execution of hcidump.

Revision history for this message
Sorin Sbarnea (ssbarnea) wrote :

I think I am encountering the same bug with another Bluetooth keyboard the one from Apple.

The keyboard is detected and connected but no input is received from it. In addition I remember that this worked but recently stopped working, probably after an update.

I will be glad to provide more information if needed.

Revision history for this message
John Ferlito (johnf-inodes) wrote :

I've had a very similar experience. My Apple bluetooth keyboard stopped working in the last few days. Was working fine before.

It looks like it is constantly connecting and reconnecting. I've attached a hcidump. It works fine in MacOsX and with an iPad

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bluez (Ubuntu):
status: New → Confirmed
Revision history for this message
Benjamin Gift (corn8bit) wrote :

My HP bluetooth keyboard connects using blueman, and I can see that when I type on it it is transfering the information (the bits per second increases a lot), but it is not working for typing.

It does however work if I remove it, restart the computer and repair it. But it stops working again on standby resume. It didn't used to do this.

Revision history for this message
Konrad Zapałowicz (kzapalowicz) wrote :

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: Confirmed → Invalid
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.