I've apparently managed to break it already. I was attempting to pair it with my cellphone when the "kbluetooth4-devicemanager" crashed. It now refuses to open with the following output:
kbluetooth4-devicemanager(8445) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "BlueZ" kbluetooth4-devicemanager(8445) DeviceMan::DeviceMan: Device Manager - Welcome QDBusObjectPath: invalid path "" process 8445: 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-devicemanager(8445) DeviceMan::getConfiguredDevices: Device List Size: 1 kbluetooth4-devicemanager: symbol lookup error: kbluetooth4-devicemanager: undefined symbol: _ZN5Solid7Control21BluetoothRemoteDevice4nameEv --- I believe it's refusing to open again because of a half-entry from the original crash, If I could find the config file where it's stored and wipe it I might have another shot. It may have crashed originally because no obex server was installed yet it was enabled in the menu. Trying to disable the obex without installing the server caused the entire app to crash. If anyone knows where the cfg is stored would you mind letting me know? Thanks. On Thu, Jan 22, 2009 at 5:23 PM, Javier Jardón <javierjc1...@gmail.com>wrote: > Kubuntu 8.10 with 4.1.96 (4.2rc) > > Pairing and send files to my mobile phone works great here, thank you! > > -- > solid-bluetooth needs update for bluez 4.x > https://bugs.launchpad.net/bugs/280997 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in KDE Base Components: Confirmed > Status in Ubuntu Release Notes: Fix Released > Status in "kdebase-workspace" source package in Ubuntu: Fix Released > Status in kdebase-workspace in Ubuntu Intrepid: Fix Committed > Status in kdebase-workspace in Ubuntu Jaunty: Fix Released > > Bug description: > Binary package hint: kdebase-workspace > > Bluetooth still doesn't work after the kdebluetooth fixes. > > :/usr/bin$ kbluetooth4-devicemanager > kbluetooth4-devicemanager(8525) > Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "BlueZ" > process 8525: 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" > kbluetooth4-devicemanager(8525) DeviceMan::DeviceMan: Device Manager - > Welcome > kbluetooth4-devicemanager(8525) DeviceMan::getConfiguredDevices: Device > List Size: 0 > kbluetooth4-devicemanager(8525) DeviceMan::slotStartWizard: Starting Wizard > kbluetooth4-wizard(8542) Solid::Control::ManagerBasePrivate::loadBackend: > Backend loaded: "BlueZ" > process 8542: 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 slot BTWizard::slotValidatePage() > kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 1 > kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 2 > kbluetooth4-wizard(8542) BTWizard::slotNext: page 2 reached! > kbluetooth4-wizard(8542) BTWizard::slotSearch: searching... > process 8542: 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.bluez.Adapter" member "DiscoverDevices" > > TEST CASE: Install KDE 4.1.4 including kdebase-workspace-bin, -data, and > -libs4+5 4.1.4-0ubuntu1~intrepid2 (after they are published and built) and > the updated kdebluetooth 0.3 from intrepid-proposed. > > Try bluetooth. If you have any, the test is successful (there is none in > the released packages). > -- 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
