Bluetooth keyboard after natty upgrade not working

[Thomas Bechtold]

Binary package hint: bluez

i upgrade from maverick to natty and now my bluetooth keyboard (Microsoft Bluetooth mobile keyboard 6000) is no longer working.
I used the gnome-bluetooth applet to configure the keyboard. The configuration was sucessful but now the keyboard does not work.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: bluez 4.84-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic-pae 2.6.37
Uname: Linux 2.6.37-12-generic-pae i686
Architecture: i386
Date: Sat Jan 8 13:22:19 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: LENOVO 746988G
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 LANG=de_DE.UTF-8
 LC_MESSAGES=de_DE.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.37-12-generic-pae root=/dev/mapper/vg0-root ro vt.handoff=7 quiet splash
SourcePackage: bluez
dmi.bios.date: 08/24/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET65WW (3.15 )
dmi.board.name: 746988G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6DET65WW(3.15):bd08/24/2010:svnLENOVO:pn746988G:pvrThinkPadX200s:rvnLENOVO:rn746988G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 746988G
dmi.product.version: ThinkPad X200s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:24:2C:BE:A9:DE ACL MTU: 1021:8 SCO MTU: 64:1
  UP RUNNING PSCAN
  RX bytes:6795 acl:187 sco:0 events:210 errors:0
  TX bytes:3070 acl:69 sco:0 commands:99 errors:0

[Thomas Bechtold (toabctl)]

i started bluetoothd with "-n -d", removed all devices and added the keyboard again (works fine). output of bluetoothd follows.

after the device was added, the keyboard works only for 2 seconds and then it does not work.

bluetoothd[2732]: plugins/hciops.c:hciops_resolve_name() hci0 dba 00:22:48:84:9F:01
bluetoothd[2732]: plugins/hciops.c:remote_name_information() hci0 status 0
bluetoothd[2732]: src/adapter.c:session_ref() 0xb861df98: ref=3
bluetoothd[2732]: src/adapter.c:session_unref() 0xb861df98: ref=2
bluetoothd[2732]: Stopping discovery
bluetoothd[2732]: src/adapter.c:adapter_create_device() 00:22:48:84:9F:01
bluetoothd[2732]: src/device.c:device_create() Creating device /org/bluez/2732/hci0/dev_00_22_48_84_9F_01
bluetoothd[2732]: src/device.c:btd_device_ref() 0xb861fd28: ref=1
bluetoothd[2732]: src/device.c:bonding_request_new() Requesting bonding for 00:22:48:84:9F:01
bluetoothd[2732]: src/device.c:bonding_request_new() Temporary agent registered for 00:22:48:84:9F:01 at :1.56:/org/bluez/agent/wizard
bluetoothd[2732]: src/adapter.c:adapter_suspend_discovery() Suspending discovery
bluetoothd[2732]: plugins/hciops.c:hciops_stop_inquiry() hci0
bluetoothd[2732]: src/adapter.c:adapter_get_device() 00:22:48:84:9F:01
bluetoothd[2732]: plugins/hciops.c:remote_features_information() hci0 status 0
bluetoothd[2732]: plugins/hciops.c:link_key_request() hci0 dba 00:22:48:84:9F:01
bluetoothd[2732]: plugins/hciops.c:link_key_request() kernel auth requirements = 0x03
bluetoothd[2732]: plugins/hciops.c:link_key_request() Matching key not found
bluetoothd[2732]: plugins/hciops.c:pin_code_request() hci0 PIN request for 00:22:48:84:9F:01
bluetoothd[2732]: src/adapter.c:adapter_get_device() 00:22:48:84:9F:01
bluetoothd[2732]: src/device.c:device_request_authentication() Requesting agent authentication for 00:22:48:84:9F:01
bluetoothd[2732]: plugins/hciops.c:hciops_pincode_reply() hci0 dba 00:22:48:84:9F:01
bluetoothd[2732]: plugins/hciops.c:link_key_notify() hci0 dba 00:22:48:84:9F:01 type 0
bluetoothd[2732]: src/adapter.c:adapter_get_device() 00:22:48:84:9F:01
bluetoothd[2732]: plugins/hciops.c:hciops_get_auth_info() hci0 dba 00:22:48:84:9F:01
bluetoothd[2732]: src/event.c:btd_event_link_key_notify() key type 0x00 old key type 0xff new key type 0x00
bluetoothd[2732]: src/event.c:btd_event_link_key_notify() local auth 0x03 and remote auth 0xff
bluetoothd[2732]: src/event.c:btd_event_link_key_notify() storing link key of type 0x00
bluetoothd[2732]: plugins/hciops.c:hciops_request_authentication() hci0 handle 12
bluetoothd[2732]: plugins/hciops.c:auth_complete() hci0 status 0
bluetoothd[2732]: src/event.c:btd_event_bonding_process_complete() status=00
bluetoothd[2732]: src/adapter.c:adapter_get_device() 00:22:48:84:9F:01
bluetoothd[2732]: src/device.c:btd_device_ref() 0xb861fd28: ref=2
bluetoothd[2732]: src/adapter.c:adapter_resume_discovery() Resuming discovery
bluetoothd[2732]: plugins/hciops.c:hciops_start_inquiry() hci0 length 8 periodic 1
bluetoothd[2732]: src/agent.c:agent_release() Releasing agent :1.56, /org/bluez/agent/wizard
bluetoothd[2732]: plugins/hciops.c:link_key_request() hci0 dba 00:22:48:84:9F:01
bluetoothd[2732]: plugins/hciops.c:link_k...

[Thomas Bechtold (toabctl)]

hm. the device is still added and sometimes the keyboard works, sometimes not.strange.

[Thomas Bechtold (toabctl)]

When i press some keys on the keyboard, sometime the keyboard works again. When the keyboard does not work, there is no device in /dev/input (eg event 12 is sometimes there, sometimes not. that's the keyboard).

/var/log/messages say:

Jan 9 19:18:20 zitrone kernel: [ 632.214323] input: Microsoft Bluetooth Mobile Keyboard 6000 as /devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0/bluetooth/hci0/hci0:11/input14
Jan 9 19:18:20 zitrone kernel: [ 632.214596] generic-bluetooth 0005:045E:0762.0003: input,hidraw1: BLUETOOTH HID v0.13 Keyboard [Microsoft Bluetooth Mobile Keyboard 6000] on 00:24:2C:BE:A9:DE
Jan 9 19:19:16 zitrone kernel: [ 688.236413] input: Microsoft Bluetooth Mobile Keyboard 6000 as /devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0/bluetooth/hci0/hci0:12/input15
Jan 9 19:19:16 zitrone kernel: [ 688.236694] generic-bluetooth 0005:045E:0762.0004: input,hidraw1: BLUETOOTH HID v0.13 Keyboard [Microsoft Bluetooth Mobile Keyboard 6000] on 00:24:2C:BE:A9:DE

So device is added again when i press some keys. but that's only sometimes working and if it works, there's a big delay between pressing a key and a response on the monitor.

[Artur Rona (ari-tczew)]

With Bluez 4.85 the same effect?

[Thomas Bechtold (toabctl)]

i use maverick again so i can't test the keyboard.

[Thomas Bechtold (toabctl)]

i tried with natty alpha-3 (from usb stick) and the keyboard is detected and works only sometime (as before). With maverick, all works fine.

[Grant Likely (glikely)]

I see the same behaviour on a MacBook 2,1 with the Apple bluetooth keyboard and magic touchpad. Sometimes it works, sometimes it appears for only 2 seconds before disappearing again.

[Andy Whitcroft (apw)]

It is possible this is related to the bug reported here: https://lkml.org/lkml/2011/4/12/315, therefore adding a kernel task to monitor this.

[Andy Whitcroft (apw)]

Ok there seems to be a possible kernel patch for this kind of issue. I have pulled back the upstream patch to the Natty kernel and produced some kernels for testing. If those of you with this hardware could test the kernels at the URL below and let us know if they resolve your bluetooth issues. Please report any testing back here. Kernels are here:

    http://people.canonical.com/~apw/lp700292-natty/

Thanks!

[Thomas Bechtold (toabctl)]

I use Natty since 2 weeks and i can not detect the problem anymore. My bluetooth keyboard works fine now.

[Andy Whitcroft (apw)]

@Grant -- are you still able to reproduce this issue? If not then we should close it out.

[Grant Likely (glikely)]

I switched to a new macbook pro a week after hitting that bug on my
old machine. I've had zero problems on the new one.

I just dug out the old machine and it still has the trouble. I'm
downloading the new kernel now and I'll report back.

g.

On Wed, Apr 13, 2011 at 8:53 AM, Andy Whitcroft <email address hidden> wrote:
> @Grant -- are you still able to reproduce this issue?  If not then we
> should close it out.
>
> ** Summary changed:
>
> - Bluetooth keybord after natty upgrade not working
> + Bluetooth keyboard after natty upgrade not working
>
> ** Changed in: linux (Ubuntu)
>   Importance: Undecided => Low
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/700292
>
> Title:
>  Bluetooth keyboard after natty upgrade not working
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/700292/+subscribe
>

--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

[Grant Likely (glikely)]

On Wed, Apr 13, 2011 at 9:48 AM, Grant Likely <email address hidden> wrote:
> I switched to a new macbook pro a week after hitting that bug on my
> old machine.  I've had zero problems on the new one.
>
> I just dug out the old machine and it still has the trouble.  I'm
> downloading the new kernel now and I'll report back.

On a related note; this patch is needed to get bt working on the new
machine. However, it is scheduled to be added to 2.6.38.3 so the
problem will solve itself shortly. I won't create a bug for it
(unless you request it).

https://lkml.org/lkml/2011/4/12/218

g.

[Grant Likely (glikely)]

On Wed, Apr 13, 2011 at 9:48 AM, Grant Likely <email address hidden> wrote:
> I switched to a new macbook pro a week after hitting that bug on my
> old machine.  I've had zero problems on the new one.
>
> I just dug out the old machine and it still has the trouble.  I'm
> downloading the new kernel now and I'll report back.

The patch solves the problem on my Macbook2,1. Thanks!

g.

[Andy Whitcroft (apw)]

On Wed, Apr 13, 2011 at 04:02:36PM -0000, Grant Likely wrote:
> On Wed, Apr 13, 2011 at 9:48 AM, Grant Likely <email address hidden> wrote:
> > I switched to a new macbook pro a week after hitting that bug on my
> > old machine.  I've had zero problems on the new one.
> >
> > I just dug out the old machine and it still has the trouble.  I'm
> > downloading the new kernel now and I'll report back.
>
> On a related note; this patch is needed to get bt working on the new
> machine. However, it is scheduled to be added to 2.6.38.3 so the
> problem will solve itself shortly. I won't create a bug for it
> (unless you request it).
>
> https://lkml.org/lkml/2011/4/12/218

Indeed we should get that in the wash either in the final release, or in
the first update depending on GregKH's release schedule.

-apw

[don hardaway (don-hardaway)]

I just installed Natty beta-2 on my macbook pro 3,1 and the bluetooth mouse will not work. Any suggestions.

[Seth Forshee (sforshee)]

@don, it would be helpful if you could install the test kernel packages posted by Andy in comment #10 and see if they fix your issue. The fix under discussion is not included in beta 2. Thanks!

[ubuntic (ubuntic)]

Hi all,
i have a Dicota mouse with a bluetooth-usb-stick wich worked in lucid without problems. But it is very problematic in natty somtimes BT works somtimes not. I can´t see any crash report.

The only thing that i recognise is that the BT-applet is darker if BT not works. And if i push the "Bluetooth start" button nothing happend.

Somtimes after starting natty BT works hours.

thanks for help

ubuntic

[Patrick Meidl (patrick-pantheon)]

the patched kernel from http://people.canonical.com/~apw/lp700292-natty/ solved the problem for me (installed 11.04 beta2 yesterday).

will this patch go into the final 11.04 kernel?

thanks.

[Stefan Nagy (stefan-nagy)]

I have a similar problem since I installed Natty with a 'Compaq Computer Corp. Bluetooth Device' (049f:0086) and a Microsoft Wireless Entertainment Keyboard 7000. In addition, sometimes the keyboard layout changes to english (I have a german keyboard with ö, ü and all this stuff). I have to remove the keyboard and add it again to get the german layout again…

The patched kernel didn't solve the problem for me.

[Thilo Cestonaro (tephraim)]

The patched kernel packages fixed my bluetooth problem!

please integrate it++

[Martin Pitt (pitti)]

Accepted linux into natty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Stefan Nagy (stefan-nagy)]

Since I installed the new kernel (natty-proposed) I can't use my BT-keyboard at all – my bluetooth adapter can't find it anymore… Shall I open a new bug report? My adapter is a 'Compaq Computer Corp. Bluetooth Device' (049f:0086).

[Stefan Nagy (stefan-nagy)]

Since it seems like this patch works for most people I opened a new bug report - see bug 775648.

[Ian Santopietro (isantop)]

This bug affected System76 bluetooth enabled computers as well. Updating with natty-proposed enabled has fixed the issue.

[Brad Figg (brad-figg)]

This commit came in via a stable upstream commit. As such it is not subject to the verification process.

[Martin Pitt (pitti)]

Marking as verification-failed due to the regression-proposed bug 775648.

[Brad Figg (brad-figg)]

@martin,

Take a look at bug 775648. I looks like maybe a case of user error. The original submitter can no longer reproduce the problem.

[yurx cherio (cherio)]

Neither restarting the service nor restarting the device worked for me. The bluetooth seems to be working partially. It can discover pair the device (my phone) but I can no longer browse files on it as I used to in Maverick. Nor I can send files from the phone. I did enabled receiving files on in Ubuntu and I did mark the computer as a trusted device on the phone and it didn't make any difference.

[Steve Conklin (sconklin)]

To make sure that this really is a regression caused by the one commit related to this fix, please test the kernel found at the link below, and let me know whether there are still keyboard problems. This is the exact same kernel as what is in -proposed, with the single commit reverted.

Thanks!

http://people.canonical.com/~sconklin/lp700292/

[Stefan Nagy (stefan-nagy)]

At least I can't reproduce this problem anymore – see bug 775648. The patched kernel from the natty-proposed repository solved the problem for me.

[Steve Conklin (sconklin)]

I think that the keyboard problems which have been reported are not related to this patch, which has been confirmed to solve the problem that was originally reported.

We've been unable to get clear testing results that indicate that the keyboard problem is due to this patch, so I'm going to mark it as verified and we can let the update go with this fix.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 2.6.38-10.46

---------------
linux (2.6.38-10.46) natty-proposed; urgency=low

  [ Steve Conklin ]

  * Release Tracking Bug
    - LP: #802464

  [ Upstream Kernel Changes ]

  * Revert "put stricter guards on queue dead checks"
  * Revert "fix oops in scsi_run_queue()"

linux (2.6.38-10.45) natty-proposed; urgency=low

  [ Upstream Kernel Changes ]

  * Revert "af_unix: Only allow recv on connected seqpacket sockets."

linux (2.6.38-10.44) natty-proposed; urgency=low

  [ Steve Conklin ]

  * Release Tracking Bug
    - LP: #792013

  [ Robert Nelson ]

  * SAUCE: omap3: beagle: detect new xM revision B
    - LP: #770679
  * SAUCE: omap3: beagle: detect new xM revision C
    - LP: #770679
  * SAUCE: omap3: beagle: if rev unknown, assume xM revision C
    - LP: #770679

  [ Stefan Bader ]

  * Include nls_iso8859-1 for virtual images
    - LP: #732046

  [ Thomas Schlichter ]

  * SAUCE: vesafb: mtrr module parameter is uint, not bool
    - LP: #778043

  [ Tim Gardner ]

  * Revert "SAUCE: acpi battery -- move first lookup asynchronous"
    - LP: #775809
  * updateconfigs after update to v2.6.38.6

  [ Upstream Kernel Changes ]

  * Revert "ALSA: hda - Fix pin-config of Gigabyte mobo"
    - LP: #780546
  * Revert "[SCSI] Retrieve the Caching mode page"
    - LP: #788691
  * Revert "USB: xhci - fix unsafe macro definitions"
  * Revert "USB: xhci - fix math in xhci_get_endpoint_interval()"
  * Revert "USB: xhci - also free streams when resetting devices"
  * ath9k_hw: fix stopping rx DMA during resets
    - LP: #775809
  * netxen: limit skb frags for non tso packet
    - LP: #775809
  * ath: add missing regdomain pair 0x5c mapping
    - LP: #775809
  * block, blk-sysfs: Fix an err return path in blk_register_queue()
    - LP: #775809
  * p54: Initialize extra_len in p54_tx_80211
    - LP: #775809
  * qlcnic: limit skb frags for non tso packet
    - LP: #775809
  * nfsd4: fix struct file leak on delegation
    - LP: #775809
  * nfsd4: Fix filp leak
    - LP: #775809
  * virtio: Decrement avail idx on buffer detach
    - LP: #775809
  * x86, gart: Set DISTLBWALKPRB bit always
    - LP: #775809
  * x86, gart: Make sure GART does not map physmem above 1TB
    - LP: #775809
  * intel-iommu: Fix use after release during device attach
    - LP: #775809
  * intel-iommu: Unlink domain from iommu
    - LP: #775809
  * intel-iommu: Fix get_domain_for_dev() error path
    - LP: #775809
  * drm/radeon/kms: pll tweaks for r7xx
    - LP: #775809
  * drm/nouveau: fix notifier memory corruption bug
    - LP: #775809
  * drm/radeon/kms: fix bad shift in atom iio table parser
    - LP: #775809
  * drm/i915/tv: Remember the detected TV type
    - LP: #775809
  * tty/n_gsm: fix bug in CRC calculation for gsm1 mode
    - LP: #775809
  * serial/imx: read cts state only after acking cts change irq
    - LP: #775809
  * ASoC: Fix output PGA enabling in wm_hubs CODECs
    - LP: #775809
  * ASoC: codecs: JZ4740: Fix OOPS
    - LP: #775809
  * ALSA: hda - Add a fix-up for Acer dmic with ALC271x codec
    - LP: #775809
  * ahci: don't enable port irq before handler is registered
    - LP: #775809
  * libata: Implement ATA_FLAG_NO_...