apple bluetooth keyboard stopped working

Bug #223132 reported by a.l.e
4
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

i've installed the latest RC for hardy and i got my shiny new apple wireless keyboard following this howto:

https://help.ubuntu.com/community/BluetoothInputDevices

suddenly, it stopped working. now the computer can connect but loses the connection after a few seconds, without that i can tip any character.

the failure may be associated with the upgrade to the final packages for hardy:

Upgraded the following packages:
app-install-data (0.5.10.1) to 0.5.10.2
apt (0.7.9ubuntu16) to 0.7.9ubuntu17
apt-utils (0.7.9ubuntu16) to 0.7.9ubuntu17
bluez-audio (3.26-0ubuntu5) to 3.26-0ubuntu6
bluez-cups (3.26-0ubuntu5) to 3.26-0ubuntu6
bluez-utils (3.26-0ubuntu5) to 3.26-0ubuntu6

i attach two screenshots where it shows that the keyboard is paired but loses its connection.

btw, every times i press a key, the connected icon appears and vanishes 2-3 seconds afterwards.

no warning in dmesg nor on the comandline

i also tried to remove the /var/lib/bluetooth directory but with no success.

is there anything i can do to help you debug this issue?

Revision history for this message
a.l.e (ale-comp-06) wrote :
Revision history for this message
a.l.e (ale-comp-06) wrote :
Revision history for this message
MrMEEE (mj-casalogic) wrote :

Hi...

I had this problem too... I think what solved it was the followering:

Turn off the keyboard....

Turn on the keyboard....

connect to the keyboard through either kbluetooth, gnome-bluetooth or using hidd --connect XX:XX:XX:XX:XX:XX (MAC Address...

When you have the dialog where you can enter a pairing code, enter 0000, but dont press the button yet...

Turn off the keyboard

Turn on the keyboard..

Enter: 0000 and press "Enter" (On the Apple Wireless keyboard, YES)

After this, press ok in the pairing code dialog...

Well ... It worked for me anyways... Try it out :D

Revision history for this message
Ian Weisser (ian-weisser) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Revision history for this message
a.l.e (ale-comp-06) wrote :

thank you for taking the time for a timly reaction and helping to make ubuntu better.

since a long time i can connect to the bluetooth keyboard. still gdm can't connect to the bt keyboard.
i don't recall how i got it to work but it was a hack.

we were wondering if you still were maintaining hardy, but if it is still a concern for you, please ask for details and you may get answers.

btw, beacause of other kernel related issues with hardy i will certainly upgrade to 08.10 as soon as it gets released. not before.

thanks in advance.

Revision history for this message
Ian Weisser (ian-weisser) wrote :

This bug report is being closed due to your last comment regarding this no linger being an issue. I the issue recurs, please reopen it. If you find the hack you used, please post it here (even if closed, it still is searchable).
This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage .
For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in bluez:
status: Incomplete → 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.