Apple wireless mouse not working

Bug #837206 reported by Wolf Rogner
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After upgrading Ubuntu yesterday, my Apple wireless mouse stopped working again.
Last time, it was an error in the kernel, this time, it looks like an error in libbluetooth3 or any of the bluez stack (as these were the only libs upgraded).

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: bluez 4.91-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Tue Aug 30 09:38:14 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64+mac (20101008)
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: Apple Inc. MacBookPro6,2
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=de_AT.UTF-8
 LC_MESSAGES=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=3c3557ca-1f0a-428b-be8d-07b30f05771c ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to natty on 2011-04-30 (121 days ago)
dmi.bios.date: 07/26/10
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP61.88Z.0057.B0C.1007261552
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F22586C8
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22586C8
dmi.modalias: dmi:bvnAppleInc.:bvrMBP61.88Z.0057.B0C.1007261552:bd07/26/10:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
dmi.product.name: MacBookPro6,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: C8:BC:C8:F0:43:3B ACL MTU: 1021:8 SCO MTU: 64:1
  UP RUNNING PSCAN
  RX bytes:1529 acl:1 sco:0 events:52 errors:0
  TX bytes:776 acl:4 sco:0 commands:34 errors:0

Revision history for this message
Wolf Rogner (war-rsb) wrote :
Revision history for this message
Wolf Rogner (war-rsb) wrote :

Tried to revert to the old bluez stack. Did not work either.

So it seems this is a regression of Bug 814250 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/814250)

Excerpt from /var/log/syslog:

Aug 30 23:30:17 wm kernel: [ 3745.652378] btusb_bulk_complete: hci0 corrupted ACL packet
Aug 30 23:30:17 wm kernel: [ 3745.652396] l2cap_recv_acldata: Unexpected continuation frame (len 1)
Aug 30 23:30:28 wm kernel: [ 3756.864800] btusb_bulk_complete: hci0 corrupted ACL packet
Aug 30 23:30:28 wm kernel: [ 3756.864845] hci_acldata_packet: hci0 ACL packet for unknown connection handle 12
Aug 30 23:30:28 wm kernel: [ 3756.864849] hci_acldata_packet: hci0 ACL packet for unknown connection handle 12
Aug 30 23:30:43 wm kernel: [ 3771.378024] btusb_bulk_complete: hci0 corrupted ACL packet
Aug 30 23:30:43 wm kernel: [ 3771.378049] l2cap_recv_acldata: Unexpected continuation frame (len 1)
Aug 30 23:30:54 wm kernel: [ 3782.695191] btusb_bulk_complete: hci0 corrupted ACL packet
Aug 30 23:30:54 wm kernel: [ 3782.695206] hci_acldata_packet: hci0 ACL packet for unknown connection handle 12
Aug 30 23:30:54 wm kernel: [ 3782.695210] hci_acldata_packet: hci0 ACL packet for unknown connection handle 12
Aug 30 23:31:19 wm kernel: [ 3807.160072] btusb_bulk_complete: hci0 corrupted ACL packet
Aug 30 23:31:19 wm kernel: [ 3807.160101] l2cap_recv_acldata: Unexpected continuation frame (len 1)
Aug 30 23:31:30 wm kernel: [ 3818.398809] btusb_bulk_complete: hci0 corrupted ACL packet
Aug 30 23:31:30 wm kernel: [ 3818.398862] hci_acldata_packet: hci0 ACL packet for unknown connection handle 12
Aug 30 23:31:30 wm kernel: [ 3818.398867] hci_acldata_packet: hci0 ACL packet for unknown connection handle 12
Aug 30 23:31:47 wm kernel: [ 3835.251273] btusb_bulk_complete: hci0 corrupted ACL packet
Aug 30 23:31:47 wm kernel: [ 3835.251293] l2cap_recv_acldata: Unexpected continuation frame (len 1)
Aug 30 23:31:55 wm kernel: [ 3843.201684] btusb_bulk_complete: hci0 corrupted ACL packet
Aug 30 23:31:55 wm kernel: [ 3843.201794] l2cap_recv_acldata: Unexpected continuation frame (len 8)
Aug 30 23:32:08 wm kernel: [ 3856.853270] btusb_bulk_complete: hci0 corrupted ACL packet
Aug 30 23:32:08 wm kernel: [ 3856.853301] hci_acldata_packet: hci0 ACL packet for unknown connection handle 12
Aug 30 23:32:17 wm kernel: [ 3865.031873] btusb_bulk_complete: hci0 corrupted ACL packet
Aug 30 23:32:17 wm kernel: [ 3865.032832] hci_acldata_packet: hci0 ACL packet for unknown connection handle 12

Revision history for this message
Xavier Besnard (xavier-besnard) wrote :

I faced a problem wit some similarities but I am not sure to face the same bug.

My conf: Kubuntu 12.04 alpha 1 with KDE 4.8 updated dayly. Laptop : ACER one D531h

My bluetooth hardware: a USB Belkin bluetooth dongle + wireless Mouse and keyboard

lsusb
...
Bus 004 Device 006: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 004 Device 007: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 004 Device 008: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass)
Bus 004 Device 009: ID 050d:016a Belkin Components Bluetooth Mini Dongle

My cellular phone is a Samsung Jet S9000.

I sent sucessfully JPG files from the phone to the PC. But I am not able to send files from my laptop to my phone.

In Dmesg, I found the following error messages:

[45671.258277] Bluetooth: Unexpected continuation frame (len 0)
[45678.543461] Bluetooth: Unexpected continuation frame (len 0)
[45681.709535] Bluetooth: Unexpected continuation frame (len 0)

When trying to explore my phone files from my laptop using the bluetooth link, the message is "périphérique occupé" (device busy).

Is that the same bug? Thanks for the reply. Yours. Xavier

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
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.