Red Hat Bugzilla – Bug 469802
Latest bluez-libs and bluez-utils breaks bluetooth keyboard usage
Last modified: 2009-03-05 09:04:33 EST
Description of problem:
After upgrading bluez-utils and bluez-libs my bluetooth keyboard
(Rocketfish RF-BTKB2) stopped working.
Reverting to older bluez-libs and bluez-utils restored functionality
Version-Release number of selected component (if applicable):
Working: bluez-libs 3.20-1.fc8, bluez-utils 3.20-4.fc8
Broken: bluez-libs 3.35-1.fc8 bluez-utils 3.35-3.fc8
Steps to Reproduce:
1. Upgrade to latest bluez-libs and bluez-utils
2. Notice keyboard doesn't work
3. Remove keyboard from bluetooth manager (input and trust)
4. Pair keyboard using bluetooth manager
5. Notice keyboard does not work
6. Check /var/log/messages and see "Encryption link key not found"
7. Revert to older bluez-libs and bluez-utils
8. Remove keyboard from bluetooth manager (input and trust)
9. Pair keyboard using bluetooth manager
10. Notice keyboard works
Keyboard does not work. Errors in /var/log/messages
Keyboard should work.
In an attempt to fix I re-paired the keyboard many times. Each time it would successfully pair, but I would see the following error is /var/log/messages:
Nov 3 20:43:08 jleu-laptop hcid: Encryption link key not found
When I check the contents of /var/lib/bluetooth/<bt dongle mac>/linkkeys
I do not see an entry for my keyboard.
With 3.20 I do not see an entry in linkkeys for the keyboard either, but it
works just fine.
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
I'm tempted to say this still plagues Fedora 10.
I was running Fedora 8, just like the OP, using my bluetooth keyboard when around the same time it stopped working following a yum update. I have now upgraded to Fedora 10 and bluetooth is still broken.
$ tail /var/log/messages:
Dec 8 23:27:45 localhost kernel: bluetoothd: segfault at 7 ip 002e1b53 sp bfef0c50 error 4 in libc-2.9.so[272000+16e000]
$ service bluetooth status
bluetoothd dead but subsys locked
$ lsusb | grep Blue
Bus 002 Device 004: ID 22b8:0850 Motorola PCS Bluetooth Device
Could you please get a backtrace of bluetoothd crashing? Don't forget to install the necessary packages:
Ok I have a backtrace here. Unfortunately I can't reliably make it crash every time. I'm not sure what sequence it takes but the last thing I do before every crash is run "sudo hciconfig hci0 reset". Restarting the bluetoothd and rerunning that command alone doesn't make it crash though.
I got this backtrace by attaching to the bluetoothd pid in gdb.
Program received signal SIGSEGV, Segmentation fault.
malloc_consolidate (av=0x3e3140) at malloc.c:4886
4886 nextp = p->fd;
#0 malloc_consolidate (av=0x3e3140) at malloc.c:4886
#1 0x002e391d in _int_malloc (av=0x3e3140, bytes=8192) at malloc.c:4229
#2 0x002e547f in __libc_calloc (n=1, elem_size=8192) at malloc.c:3946
#3 0x002d973d in open_memstream (bufloc=0xbf86efe4, sizeloc=0xbf86efe0)
#4 0x00352008 in __vsyslog_chk (pri=30, flag=1,
fmt=0xb8069609 "HCI dev %d down", ap=0xbf86f024 "") at ../misc/syslog.c:169
#5 0xb8063294 in vsyslog () at /usr/include/bits/syslog.h:48
#6 vinfo () at logging.c:36
#7 info (format=0xb8069609 "HCI dev %d down") at logging.c:45
#8 0xb8049eec in device_event () at main.c:548
#9 io_stack_event (chan=0xb8b77eb8, cond=G_IO_IN, data=0x0) at main.c:589
#10 0x001a132d in g_io_unix_dispatch (source=0xb8b782c8,
callback=0xb8049dc0 <io_stack_event>, user_data=0x0) at giounix.c:162
#11 0x0016a238 in g_main_dispatch () at gmain.c:2144
#12 IA__g_main_context_dispatch (context=0xb8b72048) at gmain.c:2697
#13 0x0016d8e3 in g_main_context_iterate (context=0xb8b72048, block=1,
dispatch=1, self=0xb8b71200) at gmain.c:2778
#14 0x0016de02 in IA__g_main_loop_run (loop=0xb8b74ea8) at gmain.c:2986
#15 0xb804a681 in main (argc=1, argv=0xbf86f714) at main.c:744
I should also note I'm getting this message repeated a lot in /var/log/messages:
Dec 9 23:13:30 localhost kernel: hci_cmd_task: hci0 command tx timeout
Dec 9 23:13:35 localhost bluetoothd: Can't write class of device: Connection timed out (110)
After googling that I came across a thread, https://bugs.launchpad.net/ubuntu/+bug/281949, and people are pointing fingers at a kernel upgrade that caused bluetooth to stop working for them.
Let me know if there is anything else I can try to help.
Should work fine with recent kernel updates. Let me know if not.
Just last week I upgraded to Fedora 10 and updated to the latest bluez and
kernel. My bluetooth keyboard is working fine.
Good stuff, thanks.