Apple bluetooth keyboard non-responsive after reboot

Bug #434007 reported by {c}
116
This bug affects 23 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Undecided
Unassigned
Nominated for Karmic by Fredrik Littmarck

Bug Description

Binary package hint: bluez

(Originally posed this as a question, and was encouraged to report it as a bug here. Despite the numerous similar problems reported over the last several years, I believe this one to be distinct, mainly because of the recently disappeared /etc/default/bluetooth file, as per my description below.) bluez version is 4.51-0ubuntu1, according to synaptic.

After much hanky-panky, I had eventually gotten the keyboard to persistently work in 9.04, but unfortunately needed to update to 9.10 because of the catastrophically broken intel video drivers in 9.04.

The keyboard still works, but after reboot it is in an odd state where the "bluetooth preferences" show it as connected even though it is completely non-responsive. Cycling the connection (disconnect, then reconnect) will bring it right back up, but this requires (at minimum) another wired keyboard present to log in with. (Had to borrow a wired keyboard from work to accomplish this.)

From what I was able to understand during the setup process in 9.04, one of the key steps was modifying /etc/default/bluetooth, which apparently no longer exists in the version of bluez shipping with 9.10. Can anyone enlighten me as to where the settings which were once contained therein have relocated to?

Some details about the system, which is a mac mini purchased in December 2008 (probably missing all the important stuff, but give me a little slack; it's my first attempt at asking a question) ---

$ uname -a
Linux elliot 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 19:25:34 UTC 2009 x86_64 GNU/Linux
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.10
DISTRIB_CODENAME=karmic
DISTRIB_DESCRIPTION="Ubuntu karmic (development branch)"
$ lsusb
Bus 001 Device 004: ID 1058:1003 Western Digital Technologies, Inc.
Bus 001 Device 003: ID 1058:1001 Western Digital Technologies, Inc. External Hard Disk
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 004: ID 05ac:8205 Apple, Inc. Bluetooth HCI
Bus 005 Device 003: ID 05ac:8240 Apple, Inc. IR Receiver [build-in]
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c016 Logitech, Inc. M-UV69a/HP M-UV96 Optical Wheel Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
$ hciconfig
hci0: Type: USB
 BD Address: 00:22:41:D8:06:AD ACL MTU: 384:8 SCO MTU: 64:8
 UP RUNNING PSCAN
 RX bytes:62256 acl:3366 sco:0 events:76 errors:0
 TX bytes:813 acl:22 sco:0 commands:40 errors:0

Revision history for this message
nagrover (ngpublic) wrote :

I'd like to confirm that the apple bluetooth keyboard does not work out of the box. I am on Ubuntu 9.04 and currently what I have to do is:

1) boot up and log in using laptop keyboard

2) type a few letters on apple keyboard so that "Bluetooth Preferences" shows the keyboard connected

3) Using "Bluetooth Preferences", disconnect the Apple keyboard

4) Using laptop keyboard, open terminal and type "sudo hidd --search", then enter root password, and then while it scans for bluetooth devices I type random letters on the Apple keyboard. After it stops scanning my Apple keyboard connects and starts working properly.

If I don't follow the above sequence exactly that way then I can't get the Apple keyboard to work. If I do, then it works 99% of the time. I am using bluez version: 4.32-0ubuntu4.1

Revision history for this message
hads (hads) wrote :

I also have this issue, as with the OP using a mouse to disconnect and reconnect through the bluetooth preferences applet brings the keyboard back to life.

Using karmic up to date as of today with standard x86 hardware.

Revision history for this message
Clarke Wixon (cwixon) wrote :

I will confirm this bug is still present in the 9.10 final release. I'm using the Apple BT aluminum keyboard (first edition) on a Ubuntu 9.10 64-bit system with generic pc hardware.

Like the previous posters, I can get it paired, and it works initially, but not following a reboot.

I have to log on with a USB keyboard attached (which kinda defeats the purpose of having a bluetooth wireless keyboard), then disconnect and reconnect the wireless keyboard through the bluetooth applet. After that it works again.

I would be happy to provide any additional debugging info desired.

summary: - Apple bluetooth keyboard non-responsive after reboot (9.10alpha)
+ Apple bluetooth keyboard non-responsive after reboot (9.10 alpha thru
+ final)
Revision history for this message
hads (hads) wrote : Re: Apple bluetooth keyboard non-responsive after reboot (9.10 alpha thru final)

Yes, confirming I still have this issue.

As an interim workaround is there a way to tell the bluetooth applet to disconnect and reconnect from the command line? For me this would be easier as I can SSH in from another box rather than finding a mouse.

Revision history for this message
tobytes (t-reinwarth) wrote :

Yeah, i have the same problem.
I have to switch my keyboard off/on on ubuntu login screen to type my password.

Revision history for this message
RishiRamraj (thereisnocowlevel) wrote :

Confirmed here as well. I'm running the latest release of 9.10 amd64 as of the date of this post. I'm also using a mighty mouse, which works fine. Here's the dmesg output on startup. You'll notice that I reconnect the keyboard using bluetooth preferences to get it working.

[ 19.215060] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 19.215422] input: Mighty Mouse as /devices/pci0000:00/0000:00:13.3/usb5/5-1/5-1:1.0/bluetooth/hci0/hci0:11/input4
[ 19.215519] generic-bluetooth 0005:05AC:030C.0001: input,hidraw0: BLUETOOTH HID v2.00 Mouse [Mighty Mouse] on 00:02:72:1C:0E:99
[ 19.349493] [fglrx] Gart USWC size:1279 M.
[ 19.349496] [fglrx] Gart cacheable size:508 M.
[ 19.349501] [fglrx] Reserved FB block: Shared offset:0, size:1000000
[ 19.349504] [fglrx] Reserved FB block: Unshared offset:fbff000, size:401000
[ 19.349506] [fglrx] Reserved FB block: Unshared offset:1fffb000, size:5000
[ 23.972506] eth0: no IPv6 routers present
[ 30.816466] apple 0005:05AC:022C.0002: parse failed
[ 30.816473] apple: probe of 0005:05AC:022C.0002 failed with error -14
[ 80.330023] usb 4-1: new low speed USB device using ohci_hcd and address 2
[ 80.545112] usb 4-1: configuration #1 chosen from 1 choice
[ 80.605552] usbcore: registered new interface driver hiddev
[ 80.612349] input: Logitech NetPlay Keyboard as /devices/pci0000:00/0000:00:13.2/usb4/4-1/4-1:1.0/input/input5
[ 80.612442] generic-usb 0003:046D:C30B.0003: input,hidraw1: USB HID v1.10 Keyboard [Logitech NetPlay Keyboard] on usb-0000:00:13.2-1/input0
[ 80.612464] usbcore: registered new interface driver usbhid
[ 80.612469] usbhid: v2.6:USB HID core driver
[ 89.216610] Intel AES-NI instructions are not detected.
[ 89.272859] padlock: VIA PadLock not detected.
[ 197.199837] input: Apple Wireless Keyboard as /devices/pci0000:00/0000:00:13.3/usb5/5-1/5-1:1.0/bluetooth/hci0/hci0:12/input6
[ 197.199925] apple 0005:05AC:022C.0004: input,hidraw2: BLUETOOTH HID v1.36 Keyboard [Apple Wireless Keyboard] on 00:02:72:1C:0E:99

The error seems to occur here, but I haven't been able to track down that error number:
[ 30.816466] apple 0005:05AC:022C.0002: parse failed
[ 30.816473] apple: probe of 0005:05AC:022C.0002 failed with error -14

To all who have posted, could you post the output of:
$ dmesg | grep apple
to see if we're all getting the same error?

Revision history for this message
hads (hads) wrote :

Yup, same thing here;

hads@frog:~$ dmesg | grep apple
[ 2563.596844] apple 0005:05AC:022C.0001: parse failed
[ 2563.596856] apple: probe of 0005:05AC:022C.0001 failed with error -14

Revision history for this message
nagrover (ngpublic) wrote :

$ dmesg | grep apple
[ 178.875478] apple 0005:05AC:022C.0002: parse failed
[ 178.875492] apple: probe of 0005:05AC:022C.0002 failed with error -14
[ 217.357205] apple 0005:05AC:022C.0003: input,hidraw1: BLUETOOTH HID v1.40 Keyboard [Apple Wireless Keyboard] on 00:1D:60:69:C2:B0

Revision history for this message
AZ (m-dev) wrote :

As a workaround, I currently have a cron script running launching hidd --connect 00:1D:60:69:C2:B0 every few minutes (as the keyboard once reconnected suddenly becomes disconnected when the machine idles for a while.)

Revision history for this message
AZ (m-dev) wrote :

(running on mac mini ppc with 2.6.31-14-powerpc #48)

Revision history for this message
axelmasok (axelmasok-hotmail) wrote :

Same problem here "Logitech Cordless Elite keyboard for Bluetooth" and both Logitech MX900 and MX1000 bluetooth mice.
All work when you pair them. If the laptop (built-in bluetooth) is rebooted or the bluetooth "service" is restarted then the keyboard won't work and the mice mostly work but sometimes fail also. And I thought Karmic was trouble free!

Revision history for this message
axelmasok (axelmasok-hotmail) wrote :

Update: As of a couple days ago, an Ubuntu update for Karmic (not sure what updated...) seemed to have cured the problem. I can now reboot or power down and back up with both keyboard and mouse being discovered and working. I no longer have this issue I suppose.

Revision history for this message
nagrover (ngpublic) wrote :

Still not working for me. I have the Apple wireless keyboard. axelmasok is probably posting under the wrong bug report because he is using a "Logitech MX900 and MX1000"

Revision history for this message
Marty Vowles (mvowles311) wrote :

Not sure if it's useful, but I can confirm as well. The trick of powering on, off and back on is a good workaround, but still not ideal.

Revision history for this message
Nico Schlömer (nschloe) wrote :

My Apple keyboard doesn't pair at all when using the graphical applications -- I'll have to switch it on and off a couple of times, run 'sudo hidd --search', cross my fingers and one out of five times it would connect.

Revision history for this message
jeroen (ijs) wrote :

I didn't investigate fully but it seems the hid_apple driver wants to be loaded *before* the bluez connection is setup. If not the "parse failed" message shows up in the kernel log.
To solve this I put "hid_apple" in my /etc/modules.conf and regenerated the initrd (don't know if this is realy needed)

Revision history for this message
RishiRamraj (thereisnocowlevel) wrote :

Workaround confirmed. I put hid_apple in /etc/modules, rebooted and my keyboard worked. Thanks jeroen!

Revision history for this message
Clarke Wixon (cwixon) wrote :

Good work, jeroen. I too can confirm the solution, and it worked at the login screen as well. There was no need to regenerate the initrd.

I agree with RishiRamraj that this falls into the "workaround" category (and isn't a real fix) until changes are made to get this happening automatically. Can hal do it via appropriate fdi?

Revision history for this message
Arnaud Lechevallier (arnaud-lechevallier) wrote :

Thanks for the workaround. It works well here with karmic and with my media center running Jaunty.

Revision history for this message
David Gee (launchpad-allpowerfuldave) wrote :

This is also affecting me in Lucid Lynx with all the latest updates and kernel installed.

[ 30.153601] apple 0005:05AC:0239.0003: parse failed
[ 30.153609] apple: probe of 0005:05AC:0239.0003 failed with error -14

Revision history for this message
jwm (jwm-angrymonkey) wrote :

My current experience under Lucid is that the keyboard needs to be power cycled after reboot before it will work, which is annoying, but better than requiring a bluetooth stack restart. Anyone else still experiencing this or worse?

Revision history for this message
white_gecko (natanaela) wrote :

The /etc/modules.conf is now /etc/modules in lucid, but this fix works also for me, thank you jeroen.

Revision history for this message
papukaija (papukaija) wrote :

This bug is affecting 15 people.

summary: - Apple bluetooth keyboard non-responsive after reboot (9.10 alpha thru
- final)
+ Apple bluetooth keyboard non-responsive after reboot
tags: added: karmic
tags: added: lucid
Changed in bluez (Ubuntu):
status: New → Confirmed
Revision history for this message
L3ttuce (ifearx) wrote :

On Hardy, once paired, the keyboard would work subsequently, without having to go through the PIN challenge again after initial pairing, by just pressing a key or two, even at the GDM screen. On Karmic, to get the keyboard to work (whether after first boot or reboot), I have to press a couple of keys, at which point Bluez thinks it's connected, but gives me the errors as above in dmesg. To get it to work, I have to disable bluetooth, and re-enable it. It will then detect the keyboard properly. Except, lately I've been getting this more and more whilst doing this: https://bugs.launchpad.net/fedora/+source/linux/+bug/54273

Revision history for this message
L3ttuce (ifearx) wrote :

jeroen: Thank you, that now causes the keyboard to work perfectly. If only I'd known about this earlier. :)

Revision history for this message
papukaija (papukaija) wrote :

@Sabiene: Please don't PM me. What you're asking is answered in comment 16 :"To solve this I put "hid_apple" in my /etc/modules.conf and regenerated the initrd (don't know if this is realy needed)" (ok, there's a small mistake but using tab completion in terminal solves the issue if you don't know the filename)

That is run (with sudo)

gedit /etc/modules (NO .conf).

add hid_apple to the list, one item per line, save and run (again with sudo):

update-initramfs -u

and restart

Revision history for this message
papukaija (papukaija) wrote :

Btw, can anyone confirm this bug in Maverick?

Revision history for this message
François Pradel (sirdharma) wrote :

I am affected by this bug as well.

Software:
Ubuntu lucid, 10.04.3 LTS
2.6.32-34-generic
bluez 4.60-0ubuntu8

In dmesg:
[ 81.025920] apple 0005:05AC:0239.0003: parse failed
[ 81.025942] apple: probe of 0005:05AC:0239.0003 failed with error -14

The workaround in comment #16 worked for me as well.

Revision history for this message
Hicks (hicks1gb) wrote :

I have this problem too with a bluetooth mouse (magic mouse or logitech mouse) using Mavericks or Yosemite, and usign LTS 12.04 64 bits.*************

The mouse works correctly on Linux and Mac, but after using it on Mac, the mouse stops responding on Linux.
When configuring bluetooth on Linux appears as connected and configured.
To make it work again, you must delete it and pair it again.

Another problem I found is that many times, regardless of using Mac, Linux bluetooth mouse does not initialize correctly. I have been compelled to create a script in the system startup to initialize it properly:
hcitool cc DEVICE ADDRESS

On the other hand, if you are using the KDE desktop, there is another major failure when trying to pair a Bluetooth device, in this case a mouse. The system shows you a notice that you want to connect a mouse, but that message does not appear in a window in which you can press the keyboard intro to accept. The notification appears on the taskbar, where you can not interact with it.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu. Ubuntu 9.10 (karmic) reached EOL on April 30, 2011.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Please upgrade to the latest version and re-test.

Changed in bluez (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

Changed in bluez (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers