Bluetooth Mighty Mouse Left and Right Clicks do not register in 8.10

[RobertGilbert]

Operating System: Ubuntu 8.10 32-bit

Installation Type: Clean Install, Updated to current as of 1/19/09 2000 EDT
Repositories Enabled: Proposed repository enabled. As well as all of the other default repositories, OpenOffice PPA, Wine and VirtualBox

Bluetooth H/W: D-Link DBT-120 B4
Bluetooth H/W: Microsoft Bluetooth desktop USB adapter
Mouse H/W: Apple Bluetooth Mighty Mouse Model A1197
Mouse H/W: Microsoft Wireless IntelliMouse Explorer for Bluetooth
Mouse H/W: Apple Wired Mighty Mouse Model A1152
Mouse H/W: Logitech V270 Bluetooth Mouse

Issue:
     This issue is with the Bluetooth Mighty Mouse. The problem is that none of the clicks, 1, 2 or 3 performed physically on the mouse actually translate into viewable events via xev. Mouse motion is registered, horizontal and vertical scrolling is registered, but the left, right and center mouse clicks are not registered.

Solution:
     None. Bluetooth Mighty Mouse is unusable. No click events are registered.

Status:
     Regression from Ubuntu 7.04. This mouse was being used with horizontal and vertical scrolling via a modification to the xorg.conf file in previous version. It is understood that Bluetooth handling has changed in 8.10, however Wired Mighty Mouse works with no issues as well as other Bluetooth mice. It is also understood that dropped connections as well as inability to pair are a issues with 8.10. This is not the issue being described.

Steps to reproduce:

1. Install 8.10 clean.
2. Attach USB Bluetooth dongle ( both dongles attempted produced the same result )
3. Perform pairing operation through Bluetooth Applet 1.8
4. Bluetooth Mighty Mouse pairs correctly
5. Move Bluetooth Mighty Mouse horizontally on flat surface. -> Provides motion to cursor
6. Attempt to left click ( button 1 ) -> Nothing happens
7. Repeat with buttons 2 and 3 and receive same result.

Attempted Fixes:
1. Multiple Bluetooth mice.
Result: All mice performed as expected.
2. Wired Mighty Mouse.
Result: Mouse performs as expected.
3. Added entry to xorg.conf as was done in 7.04
Result: No change in behavior. -> Mighty Mouse still does not left click.
4. Multiple computers with different USB Bluetooth dongles.
Result: No change in behavior.
5. Modify /etc/default/bluetooth with the following:
BLUETOOTH_ENABLED=1
HIDD_ENABLED=1
HIDD_OPTIONS="--master --server"
Result: No change in behavior

Steps Not Attempted:
1. Install old Bluetooth functionality
Reason: If this is the new Bluetooth model, it should be fixed as those applications are deprecated.

[Charles Profitt (cprofitt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments.

Also please attach xorg.conf and xorg.0.log

Thanks.

[Charles Profitt (cprofitt)]

I am not convinced this is a bluez problem. The description clearly states that the device can move the cursor, but the buttons are not recognized.

[RobertGilbert (robert.gilbert)]

I marked the bug for the package "bluetooth" and bluez was selected upon bug creation.

[RobertGilbert (robert.gilbert)]

Bus 002 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

[RobertGilbert (robert.gilbert)]

xorg.conf has Mighty Mouse segment commented out because it did nothing one way or the other. It let's you know what I did use though.

[Charles Profitt (cprofitt)]

based on the dmesg lines below I confirmed and changed to kernel

[ 6129.466893] input: Mighty Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:44/input12
[ 7177.356056] atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
[ 7177.356072] atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.

[Connor Imes (ckimes)]

Robert, thank you for reporting this, and thank you for the triage, Charles. I will mark this as Triaged and assign importance so a developer can begin work.

Robert, to get a head start, the issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Jaunty Jackalope. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

[Connor Imes (ckimes)]

Robert,
You really shouldn't make assumptions about anything being fixed, esp.
since this is a regression type bug - you did the right thing to report
it! It is not likely that this will be fixed in 8.10 since it probably
doesn't meet the requirements for a Stable Release Update (SRU) [1].
The kernel team very often likes users reporting bugs to test LiveCDs of
Ubuntu's development version, which is why I asked you. Since they
often don't have access to the specific hardware that bugs are filed
for, they need to see if the problem is already fixed in newer releases,
or test patches that they include.
If you have a workaround that you can implement yourself, include it in
the bug report and put it into action on your 8.10 install, I wouldn't
wait for an update to fix it.

For future reference, please reply all in your emails so that the bug is
updated with your responses. Thanks!

[1] https://wiki.ubuntu.com/StableReleaseUpdates

-Connor

Robert Gilbert wrote:
> Connor,
> Thanks for the response. Two quick things, I didn't think needed
> to be posted on launchpad. First, I assume the bug will be updated
> with what release it was fixed in so I can test it in the live cd.
> Second, is it possible to get this fixed in 8.10, without having to
> manually fix it. I can see the workaround now, so, should I wait, or
> will this just not be fixed in this release?
>
> Thanks.
>
> Robert Gilbert

[Kjetil Thuen (kjetil-thuen)]

I just tested this with a Jaunty alpha4 live cd, and can confirm that the problem is still there. Also - I am not seing the atkbd.c error in my dmesg, so I am not sure that is related.

[Kevin Tsui (kevintyk)]

just tried fedora 10 also got the same problem...

[PeterWoodman (peter-shortbus)]

I also have this problem, and do not have the atkbd.c error in my dmesg log. Also using a USB dongle.

--- dmesg.log ---
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.27-7-generic (buildd@rothera) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu10) ) #1 SMP Fri Oct 24 06:42:44 UTC 2008 (Ubuntu 2.6.27-7.14-generic)
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009e800 (usable)
[ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000007fef0000 (usable)
[ 0.000000] BIOS-e820: 000000007fef0000 - 000000007fef3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007fef3000 - 000000007ff00000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000e4000000 - 00000000e6000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] last_pfn = 0x7fef0 max_arch_pfn = 0x100000
[ 0.000000] kernel direct mapping tables up to 38000000 @ 7000-c000
[ 0.000000] RAMDISK: 37822000 - 37fef50b
[ 0.000000] DMI 2.4 present.
[ 0.000000] ACPI: RSDP 000F6600, 0014 (r0 GBT )
[ 0.000000] ACPI: RSDT 7FEF3040, 0038 (r1 GBT GBTUACPI 42302E31 GBTU 1010101)
[ 0.000000] ACPI: FACP 7FEF30C0, 0074 (r1 GBT GBTUACPI 42302E31 GBTU 1010101)
[ 0.000000] ACPI: DSDT 7FEF3180, 52C6 (r1 GBT GBTUACPI 1000 MSFT 100000C)
[ 0.000000] ACPI: FACS 7FEF1800, 0040
[ 0.000000] ACPI: HPET 7FEF85C0, 0038 (r1 GBT GBTUACPI 42302E31 GBTU 98)
[ 0.000000] ACPI: MCFG 7FEF8640, 003C (r1 GBT GBTUACPI 42302E31 GBTU 1010101)
[ 0.000000] ACPI: APIC 7FEF84C0, 0098 (r1 GBT GBTUACPI 42302E31 GBTU 1010101)
[ 0.000000] ACPI: SSDT 7FEF8CE0, 02FC (r1 PmRef CpuPm 3000 INTL 20040311)
[ 0.000000] 1150MB HIGHMEM available.
[ 0.000000] 896MB LOWMEM available.
[ 0.000000] mapped low ram: 0 - 38000000
[ 0.000000] low ram: 00000000 - 38000000
[ 0.000000] bootmap 00008000 - 0000f000
[ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 0038000000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
[ 0.000000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
[ 0.000000] #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
[ 0.000000] #3 [0000100000 - 00005c0a20] TEXT DATA BSS ==> [0000100000 - 00005c0a20]
[ 0.000000] #4 [0037822000 - 0037fef50b] RAMDISK ==> [0037822000 - 0037fef50b]
[ 0.000000] #5 [00005c1000 - 00005c4000] INIT_PG_TABLE ==> [00005c1000 - 00005c4000]
[ 0.000000] #6 [000009e800 - 0000100000] BIOS reserved ==> [000009e800 - 0000100000]
[ 0.000000] #7 [0000007000 - 0000008000] PGTABLE ==> [0000007000 - 0000008000]
[ 0.000000] #8 [0000008000 - 000000f000] BOOTMAP ==> [0000008000 - 000000f000]
[ 0.000000] found SMP MP-table at [c00f4cf0] 000f4cf0
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000000 -> 0x00001000
[ 0.000...

[asier (asier-azaceta)]

Hi,
same problem here. I neither have the atkbd.c error in my dmesg log. And I'm using a USB dongle as well.
Can I report any info to help?
Rgrds,
Asier.

[Leann Ogasawara (leannogasawara)]

If anyone is still experiencing this issue with the final Jaunty 9.04 release, could you attach your dmesg output when using the latest jaunty kernel (currently 2.6.28-11)? Thanks.

[Kjetil Thuen (kjetil-thuen)]

It seems this mouse does not work at all in final Jaunty. dmesg output attached.

Installing bluez-compat makes it possible to get the old bahaviour of working movement but no buttons back.

[Kjetil Thuen (kjetil-thuen)]

Running the commands

$ sudo apt-get install bluez-compat
$ sudo hidd --search

and then a new dmesg, adds the following three lines to the dmesg output:

 [ 2501.152499] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
 [ 2537.337003] input: Apple Computer, Inc. Mighty Mouse as /devices/pci0000:00/0000:00:09.0/0000:05:08.1/usb3/3-2/3-2:1.0/bluetooth/hci0/hci0:42/input7
 [ 2537.369016] apple 0005:05AC:030C.0005: input,hidraw4: BLUETOOTH HID v2.00 Mouse [Apple Computer, Inc. Mighty Mouse] on 00:40:05:52:79:0D

But still no functioning mousebuttons.

[Damien Ciabrini (dciabrin)]

Hi,

I have the same issues with by Wireless Might Mouse and 9.04 Amd64. Click events are not generated.
My packages version:
bluez:
  Installed: 4.32-0ubuntu4
linux-image-2.6.28-11-generic:
  Installed: 2.6.28-11.42

I have a CSR bluetooth dongle (lsusb)
Bus 006 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Info from "hcitool con":
Connections:
 < ACL 00:1D:4F:50:6D:AC handle 41 state 1 lm MASTER

When I do a hcidump, I can see some packets printed whenever I move the mouse, but never when i click on any of its buttons.
HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
> ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(d): cid 0x0040 len 8 [psm 0]
...

Interestingly, when launching "evtest" on the relevant input device, I'm getting:
Input driver version is 1.0.0
Input device ID: bus 0x5 vendor 0x5ac product 0x30c version 0x200
Input device name: "Mighty Mouse"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 272 (LeftBtn)
    Event code 273 (RightBtn)
    Event code 274 (MiddleBtn)
    Event code 275 (SideBtn)
  Event type 2 (Relative)
    Event code 0 (X)
    Event code 1 (Y)
    Event code 6 (HWheel)
    Event code 8 (Wheel)
  Event type 4 (Misc)
    Event code 4 (ScanCode)
  Event type 20 (Repeat)
Testing ... (interrupt to exit)

It seems that on this mouse, buttons are advertised as "keys".
Given the output of hcidump, maybe this means that events for those keys are not correctly handled at kernel level? (hence click issues under X)
I can confirm those they events were seen on Ubuntu 8.10.

Rgrds,
Damien

[Damien Ciabrini (dciabrin)]

Hi,

After a bit of testing, when I boot my machine with older kernel 2.6.24-21-generic, the Wireless Mighty Mouse buttons are correctly detected.

It seems to me that the problem may be linked to a change in the kernel rather than a user space bluez issue.

Robert, could you give this kernel a try and let us know whether you can reproduce this behavior?

[Samuel Abels (knipknap)]

Same problem here with 2.6.28-13-generic. 2.6.24 is not available in the Jaunty repositories, so not tested.

[Samuel Abels (knipknap)]

I just pulled linux-image-2.6.30-9-generic from the karmic repositories (without upgrading anything else), the problem persists there. Coincidentally (?), the left mouse button of my Logitech USB mouse stopped working with that kernel.

[Samuel Abels (knipknap)]

Yay, everything works fine after downgrading to linux-image-2.6.25-2-386 from the intrepid repositories.

[Samuel Abels (knipknap)]

Note for others who are planning to downgrade: The function key of the Apple wireless keyboard does not work in kernel 2.6.25-2. I have been unable to find a workaround.

[miobio (miobio)]

I can confirm this bug using a bluetooth mighty mouse.

[miobio (miobio)]

P.S. I'm running 9.04 clean install

[Kjetil Thuen (kjetil-thuen)]

Fixed for me in the Karmic Koala Beta. Yay! :)

[Matteo Broggi (matte-broggi)]

Fixed also for me in the Karmic Koala Beta.

[Kjetil Thuen (kjetil-thuen)]

This is strange; It works out of the box on my MacBook running a fresh 64 bit Karmic install, but on my no-name desktop that is also running 64 bit Karmic (although that one is upgraded from jaunty), I cannot get the buttons to work. The same bluetooth packages are installed on both.

Could it be that some special apple-hardware sauce are required in the mix, or is some old configuration file on my desktop putting gravel in the machinery?

The Bluetooth adapter on my desktop presents itself as a Cambridge Silicon Radio, Ltd Bluetooth Dongle if that matters.

[Kjetil Thuen (kjetil-thuen)]

Further testing has me leaning towards the Apple Sauce theory. I tried both the MacBook and the generic desktop pc with the Karmic live cd. The mouse worked fine with all buttons on the MacBook but was buttonless on the generic desktop pc.

[Kjetil Thuen (kjetil-thuen)]

Tested with an Dell Inspiron 510m laptop (Karmic live cd). Same result as desktop PC; Mouse movement and nipple thingy works, buttons does not. Will test a mac mini later.

[Kjetil Thuen (kjetil-thuen)]

Tested on the Mac Mini now (with the same Karmic live cd), and the buttons work fine. So far the mouse has worked on 2 of 2 Macs, and failed on 3 of 3 PCs.

[Julien Pourtet (j-pourtet-deactivatedaccount-deactivatedaccount)]

I have exactly the same problem now. Mouse pointer moves across the screen, scrolling is OK on both axis (no problem with inverted axis) but clicks are not detected.

I'm running a very recent install of 9.10 (install, no update from previous version).

Is there a workaround?

[pedro ribeiro (pedroribeiro)]

Using the bluetooth wireless A1197 Mighty Mouse. I can confirm this is still an issue for Ubuntu 10.04 (Lucid).

[Larry Stewart (l-ubuntu)]

Same in 10.10, new install 32 bit, mouse movement of Apple A1197 mouse works, but not the buttons.
(Mouse does work on MACOS)

root@arctic:/dev/input# cat /etc/issue
Ubuntu 10.10 \n \l

root@arctic:/dev/input# uname -a
Linux arctic 2.6.35-23-generic-pae #40-Ubuntu SMP Wed Nov 17 22:32:51 UTC 2010 i686 GNU/Linux
root@arctic:/dev/input#

[Jeremy Foshee (jeremyfoshee)]

adjusting from "In Progress" as Andy is no longer assigned.

~JFo

[Mark Szentes-Wanner (markiboy)]

I have 10.10 i386 and this is still an issue. I tried with different Mighty Mice that work in other Operating Systems. Mouse movements work, the wheel works in 2 dimensions, but Button 1, Button 2 and Button 3 klicks do not arrive in X (xev). What a pity.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in supported series, please file a new bug.

[Kostiantyn Rybnikov (k-bx)]

11.04 (Natty). Still an issue.

[Mark Szentes-Wanner (markiboy)]

11.10 (Oneiric) beta 1; kernel 3.0.0-10 still the same issue.

A certain Gustavo F. Padovan reported it works on kernel 2.6.39-rc1.
http://www.spinics.net/lists/linux-bluetooth/msg12279.html

I give up, I will try a different distribution, perhaps it will help.