[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

KDE4 Bluetooth



As the KDE3 version of kbluetooth has almost completely ceased to function on kde 4.3 in testing, I decided to test out the version of kbluetooth4 that's in experimental. It appears to launch without trouble, but is unable to see any bluetooth devices. If I launch it from the console, I see the following diagnostic output:
QDBusObjectPath: invalid path ""
QDBusObjectPath: invalid path ""
process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1074.                                                                                                                              
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 "GetProperties"   
process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1074.                                                                                                                              
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 "RegisterAgent"   
QDBusObjectPath: invalid path ""                                                                                                     
AGENT registered !                                                                                                                   
process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1074.                                                                                                                              
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 "GetProperties"   
process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1074.                                                                                                                              
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 "GetProperties"   
kyle@Fireman53:~$ process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1074.                                                                                                            
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 "UnregisterAgent" 

Setting my computer to be discoverable gives me the following messages:
Object::connect: No such signal Solid::Control::BluetoothInterface::discoverableTimeoutChanged(int)
Object::connect:  (receiver name: 'AdapterWidget')
Object::connect: No such signal Solid::Control::BluetoothInterface::nameChanged(const QString&)
Object::connect:  (receiver name: 'AdapterWidget')
Object::connect: No such signal Solid::Control::BluetoothInterface::discoverableTimeoutChanged(int)
Object::connect:  (receiver name: 'AdapterWidget')
Object::connect: No such signal Solid::Control::BluetoothInterface::nameChanged(const QString&)
Object::connect:  (receiver name: 'AdapterWidget')
Agent Release
Object::connect: No such signal Solid::Control::BluetoothInterface::discoverableTimeoutChanged(int)
Object::connect:  (receiver name: 'AdapterWidget')
Object::connect: No such signal Solid::Control::BluetoothInterface::nameChanged(const QString&)
Object::connect:  (receiver name: 'AdapterWidget')
Object::connect: No such signal Solid::Control::BluetoothInterface::discoverableTimeoutChanged(int)
Object::connect:  (receiver name: 'AdapterWidget')
Object::connect: No such signal Solid::Control::BluetoothInterface::nameChanged(const QString&)
Object::connect:  (receiver name: 'AdapterWidget')
AGENT registered !
KCrash: Application 'kbluetooth4' crashing...

As you can see, it crashed shortly after.
Any ideas on what might be going wrong? Is there DBUS permission that I need to change? I'm already a part of both the bluetooth and netdev groups.
Thanks


Reply to: