kbluetooth4-devicemanager does not show devices already configured

[MagnusPI]

Binary package hint: kdebluetooth

1)
jaunty

2)
Architecture: i386
Version: 1:0.3-0ubuntu4

3)
Starting kbluetooth4-devicemanager I expected to see the configured devices in order to be able to connect

4)
No configured devices were shown.

Description.

Start kbluetooth4-devicemanager from a terminal
I get something like

kbluetooth4-devicemanager(30106) DeviceMan::DeviceMan: Device Manager - Welcome
kbluetooth4-devicemanager(30106): Connecting to ObjectPath: "/org/bluez/3318/hci0/dev_00_24_90_68_CC_22"
Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeCreated(const QString &)
Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeRemoved(const QString &)
kbluetooth4-devicemanager(30106): Connecting to ObjectPath: "/org/bluez/3318/hci0/dev_00_1E_45_8D_33_77"
Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeCreated(const QString &)
Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeRemoved(const QString &)
kbluetooth4-devicemanager(30106) DeviceMan::getConfiguredDevices: Device List Size: 2
kbluetooth4-devicemanager(30106) DeviceMan::getConfiguredDevices: "Il super numero1#"
kbluetooth4-devicemanager(30106) DeviceMan::getConfiguredDevices: "Ig"

but no device is shown in the window therefore I believed that no device had been configured.

When I tried to add again one of the configured devices by pressing the button "New.."
they were detected but they again were not shown.

[mityi (mityi)]

I confirm this bug

[niko (niko-berger)]

Same here. At first it worked quite fine (logitech diNovo desktop). but suddenly the keyboard wasnt working any more. I was at first able to remove the device using the devicemanager, but when I wanted to reconnect it, it first found it, but the the inputwizard crashed.
fom then on i wasnt able to see the device any more in the devicemanager - i could neither remove nor readd it (the mouse worked all the time and is visible in the device manager - just the keyboard isnt selectable).

when looking at the output i even see the keyboard:
kbluetooth4-devicemanager(18153) DeviceMan::DeviceMan: Device Manager - Welcome
kbluetooth4-devicemanager(18153): Connecting to ObjectPath: "/org/bluez/17560/hci0/dev_00_07_61_65_6A_B2"
Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeCreated(const QString &)
Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeRemoved(const QString &)
kbluetooth4-devicemanager(18153): Connecting to ObjectPath: "/org/bluez/17560/hci0/dev_00_07_61_61_85_00"
Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeCreated(const QString &)
Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeRemoved(const QString &)
kbluetooth4-devicemanager(18153) DeviceMan::getConfiguredDevices: Device List Size: 2
kbluetooth4-devicemanager(18153) DeviceMan::getConfiguredDevices: "Logitech MX1000 mouse"
kbluetooth4-devicemanager(18153) DeviceMan::getConfiguredDevices: "Logitech diNovo Keyboard"

(the complete logs are attached)

I think it would help if i could find out how to remove the node of the keyboard manually and try to re-add the device (if the wizard doesnt crash). because it already worked once.

[niko (niko-berger)]

i fiddled a little and found the configuration under: /var/lib/bluetooth/FF:FF:FF:FF:FF:FF
i remove every occurance of the keyboard from its files (did a fgrep 00:07:61:61:85:00 *)
and tried adding it again - at first it didnt work, then i killed all open kblue* processes (kblueplugd, kbluetooth-devicemanager) and removed the lines again.

then I started the kblueplugd and tried adding the keyboard again - and suddenly - IT WORKED
(on a side node: there should be a preconfigured pincode that one has to enter in on the keyboard. having to plug in a usb keyboard to provide the first pincode adn then having to enter it on the bluetooth afterwards (dont forget the return key) is kinda awkward)

I attached the logs from the successfull connection.

Maybe the bluetooth manager should check for orphaned entries there