Upgraded to KDE 4.2 (Beta2) to try it out using adept.
Everything looks ok in the KDE GUI (see a bluetooth icon etc) but am
unable to run device manager and am getting a DBUS and further down a
symbol lookup error when input wizard attempts to connect the device
after finding it. This could easily be something I've done wrong of
course or may be due to KDE 4.2 Beta, but thought I'd list it just in
case it's important.
Log below:
/usr/bin$ kbluetooth4-inputwizard
kbluetooth4-wizard(7568) Solid::Control::ManagerBasePrivate::loadBackend:
Backend loaded: "BlueZ"
p...@golum:/usr/bin$ kbluetooth4-wizard(7568) BTWizard::slotNext: Page ID: 1
kbluetooth4-wizard(7568) BTWizard::slotNext: Page ID: 2
kbluetooth4-wizard(7568) BTWizard::slotNext: page 2 reached!
kbluetooth4-wizard(7568) BTWizard::slotSearch: Text "&Search"
kbluetooth4-wizard(7568) BTWizard::slotSearch: searching...
QDBusObjectPath: invalid path ""
process 7568: arguments to dbus_message_new_method_call() were incorrect,
assertion "path != NULL" failed in file dbus-message.c line 1070.
This is normally a bug in some application using the D-Bus library.
QDBusConnection: error: could not send message to service "org.bluez" path ""
interface "org.freedesktop.DBus.Introspectable" member "Introspect"
Object::connect: No such signal
Solid::Control::BluetoothRemoteDevice::nodeCreated(QString)
Object::connect: No such signal
Solid::Control::BluetoothRemoteDevice::nodeRemoved(QString)
Object::connect: No such signal
Solid::Control::BluetoothRemoteDevice::nodeCreated(QString)
Object::connect: No such signal
Solid::Control::BluetoothRemoteDevice::nodeRemoved(QString)
Object::connect: No such signal
Solid::Control::BluetoothRemoteDevice::nodeCreated(QString)
Object::connect: No such signal
Solid::Control::BluetoothRemoteDevice::nodeRemoved(QString)
kbluetooth4-wizard(7568) BTWizard::slotSearch: Configured Devices: 1
kbluetooth4-wizard(7568) BTWizard::slotSearch: Text "&Stop Search"
kbluetooth4-wizard(7568) BTWizard::slotSearch: Stop searching
kbluetooth4-wizard(7568) BTWizard::slotSearch: Text "&Search"
kbluetooth4-wizard(7568) BTWizard::slotSearch: searching...
QDBusObjectPath: invalid path ""
Object::connect: No such signal
Solid::Control::BluetoothRemoteDevice::nodeCreated(QString)
Object::connect: No such signal
Solid::Control::BluetoothRemoteDevice::nodeRemoved(QString)
Object::connect: No such signal
Solid::Control::BluetoothRemoteDevice::nodeCreated(QString)
Object::connect: No such signal
Solid::Control::BluetoothRemoteDevice::nodeRemoved(QString)
kbluetooth4-wizard(7568) BTWizard::slotSearch: Configured Devices: 1
kbluetooth4(7462) BluezBluetoothInterface::slotDeviceFound: device found
"00:0C:55:03:0D:DF" QVariant(QString, "Kensington PocketMouse Bluetooth")
kbluetooth4-wizard(7568) BluezBluetoothInterface::slotDeviceFound: device found
"00:0C:55:03:0D:DF" QVariant(QString, "Kensington PocketMouse Bluetooth")
kbluetooth4-wizard(7568) BTWizard::slotRemoteDeviceFound: Configured Devices
from slotRemoteDeviceFound: 1
kbluetooth4-inputwizard: symbol lookup error: kbluetooth4-inputwizard:
undefined symbol: _ZN5Solid7Control21BluetoothRemoteDevice7addressEv
--
solid-bluetooth needs update for bluez 4.x
https://bugs.launchpad.net/bugs/280997
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
