Bug 155013 - kcontrol shows wrong data in the bluetooth Paired Devices module
Summary: kcontrol shows wrong data in the bluetooth Paired Devices module
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: KDE (show other bugs)
Version: Beta 6
Hardware: Other Other
: P3 - Medium : Normal (vote)
Target Milestone: ---
Assignee: Daniel Gollub
QA Contact: E-mail List
URL:
Whiteboard:
Keywords: DSLA_REQUIRED
Depends on:
Blocks:
 
Reported: 2006-03-03 15:45 UTC by Forgotten User wMtT3MV6AL
Modified: 2019-10-24 14:35 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User wMtT3MV6AL 2006-03-03 15:45:03 UTC 
Paired Devices in the KDE Control Modul shows wrong data.
the device-addresses are wrong and the shown time too.

For example the entry for today (Fr Mar 2006) paired devices shows "Mon Aug 30 2004"

the dongle's address is: 00:04:61:81:27:7C shown as 3A:30:36:3A:30:30
the phone's address is: 00:60:57:59:29:BD shown as 3A:39:335:3A:37:35
Comment 1 Stephan Kulow 2006-03-03 15:49:22 UTC 
I wonder how it can make up such values :)
Comment 2 Forgotten User wMtT3MV6AL 2006-03-03 17:16:30 UTC 
typing error, the phones address is shown as 3A:39:35:3A:37:35
Comment 3 Stephan Binner 2006-03-08 15:19:35 UTC 
~> rpm -q --changelog bluez-utils
* Wed Apr 20 2005 - behlert@suse.de
- updated to v2.16:
  * Store link keys in ASCII based file format.

Someone way later adapted the file name and position but it's still read as binary data.
Comment 4 Stefan Behlert 2006-03-08 17:00:34 UTC 
Seife, you changed something with the link-keys as far as I remember, and I think that affected this link-key file, or am I wrong?
Comment 5 Forgotten User ZhJd0F0L3x 2006-03-08 17:38:32 UTC 
probably. Not my change, but the update to v2.16 probably broke kdebluetooth.
Is there a newer version? Otherwise we probably should not build the kcm-module.
Comment 6 Stefan Behlert 2006-03-08 17:49:31 UTC 
The update was nearly a year ago, your change only some weeks, so I suspected your change, sorry :)
Comment 7 Daniel Gollub 2006-03-09 09:05:17 UTC 
The problem is the content of the linkkeys file and the change from binary(?) to ASCII base file format. I don't know the old linkkey file format but the new one doesn't provide the same information. kdebluetooth try to get the MAC address of both paired devices and the date of creation. The new format only provide the MAC address of the paired device and the linkkey. 
Where can the missing information (MAC address of bluetooth device and date of creation) be found? Or doesn't provide bluez-utils this anymore?
Comment 8 Forgotten User wMtT3MV6AL 2006-03-10 03:23:18 UTC 
The MAC address of the bluetooth device is in the directory under /var/lib/bluetooth, better it is the directory name.
In that directory you have a linkkeys file. /var/lib/bluetoot/linkkeys is an link to the file in the directory of the last used dongle.
So using /var/lib/bluetooth/linkkeys just shows you the last used bluetooth dongle and his paires. 

I think the time when the pairs were created isn't saved anymore.
Comment 9 Daniel Gollub 2006-03-13 17:40:58 UTC 
Updated kdebluetooth package for the bluez ASCII linkkey format. Also it can handle now more then one local bluetooth device. Checked in for beta 8.