Bugzilla – Bug 127781
Bluetooth Doesn't work
Last modified: 2007-06-05 11:20:51 UTC
With default setup bluetooth doesn't work with opensuse 10.0 (for me). I use kde. The problem is the computer looses pairing information and always try to repair devices. Pairing information should be stored in /etc/bluetooth/link_key. It is stored in /usr/var/lib/bluetooth/MAC/linkkeys MAC is the MAC of my bluetooth dongle. After I changed kbluetoothd to use this file everything is working. For me this path looks wrong because nothing else is stored in /usr/var
The path is wrong, yes :( It will be fixed in next autobuild-run. I'll keep this bug open because I have to cross-check with kbluetoothd.
Stefan: is bug #135592 releated to this?
No, that looks like something different.
What's the status of this bug? David Geiger <info AT david-geiger DOT de> just reported in the suse-linux mailinglist he had this problem - he seems to run 10.0 final. Subject: [SOLVED] Re: Bluetooth/BlueZ merkt sich Paired-Devices nicht Message-ID: <43A7034B.10002@david-geiger.de>
The path is not fixed in SUSE 10.0 final too!! (bluez-libs-2.19-2) Therefore i can not estabilish a connection between my phone and PC. This is a very serious bug! Please fix it, or is there any workaround??
http://lists.suse.com/archive/suse-linux/2005-Oct/0840.html says - Bluez uses /usr/var/lib/bluetooth/MAC/linkkeys - kbluetoothd uses /etc/bluetooth/link_keys Workaround: Change one of the settings or create a symlink.
Stefan, is this fixed in 10.1 beta?
No. Sorry, I was off sick.
updating version to make sure this doesn't get forgotten ;-) (I hope beta3 is OK)
Seife, can you take a short look for me? Thanks.
i checked in a partial fix to bluez-utils and kdebluetooth. whenever a new device is paired (the linkkey file is written), a symlink is generated from /var/lib/bluetooth/<device-id>/linkkeys to /var/lib/bluetooth/linkkeys and the kcm_btpaired module now looks per default at /var/lib/bluetooth/linkkeys instead of /etc/bluetooth/linkkeys. If you have multiple bluetooth adapters, you will only see the last one, that paired a device, but AFAICS kcm_btpaired does not support mutliple adapters, so this work around is all i can do now and it is a 90%-solution since most machines will only have one BT adapter.
in 10.1 it should be fixed with Beta4.