[Bug 384427] [NEW] Bluetooth suddenly stops working on Karmic

[Michael Marley]

Public bug reported:

Binary package hint: bluez

I am using fully up-to-date Kubuntu Karmic amd64, and earlier today my
bluetooth stopped working completely.  On startup, instead of displaying
its icon, kbluetooth4 only displays a blank space in the tray.
Restarting it displays the icon, but it does not work and outputs this
error message to the console:

michael at michaelspc:~$ kbluetooth4        
kbluetooth4(4752) Experimental::KNotificationItemDBus::KNotificationItemDBus: service is "org.kde.NotificationItem-4752-1"                                                                              
kbluetooth4(4752) Experimental::KNotificationItemPrivate::registerToDaemon: Registering a client interface to the system tray daemon                                                                    
kbluetooth4(4752) Experimental::KNotificationItemPrivate::registerToDaemon: service is "org.kde.NotificationItem-4752-1"                                                                                
kbluetooth4(4752) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded:  "BlueZ"         
kbluetooth4(4752) Solid::Control::BluetoothManager::buildDeviceList: UBI List  ("/org/bluez/3887/hci0")                                                                                                 
kbluetooth4(4752) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface  "/org/bluez/3887/hci0"                                                   
kbluetooth4(4752) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Creating New Interface  "/org/bluez/3887/hci0"                                                             
kbluetooth4(4752) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Calling Backend to Creating New Interface  "/org/bluez/3887/hci0"                                          
kbluetooth4(4752) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: BackendIface created                                                                                       
kbluetooth4(4752) BluezBluetoothManager::defaultInterface: Calling Backend Default Interface        
QDBusObjectPath: invalid path ""                                                                    
kbluetooth4(4752) KBlueTray::onlineMode: online Mode                                                
kbluetooth4(4752) Solid::Control::BluetoothManager::buildDeviceList: UBI List  ("/org/bluez/3887/hci0")                                                                                                 
kbluetooth4(4752) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface  "/org/bluez/3887/hci0"                                                   
kbluetooth4(4752) KBlueTray::onlineMode: adapter size  1                                            
kbluetooth4(4752) BluezBluetoothManager::defaultInterface: Calling Backend Default Interface        
QDBusObjectPath: invalid path ""                                                                    
kbluetooth4(4752) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface  ""                                                                       
kbluetooth4(4752) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Creating New Interface  ""
kbluetooth4(4752) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Calling Backend to Creating New Interface  ""
kbluetooth4(4752) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: BackendIface created
process 4752: 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"
kbluetooth4(4752) KBlueTray::onlineMode: Adapter found  ""
process 4752: 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"
AGENT registered !
kbluetooth4(4752) KBlueTray::updateTooltip: Updating Tooltip
process 4752: 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"
kbluetooth4(4752) ObexServer::ObexServer: ""
kbluetooth4(4752) ObexServer::serverCreatedError: Error creating Bluetooth Server:  "Invalid Bluetooth address"
kbluetooth4(4751): Communication problem with  "kbluetooth4" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

michael at michaelspc:~$

In addition to kbluetooth4, I have also tried the gnome-bluetooth-applet
thing, which also does not properly detect the adapter and fails to
correctly use it.

** Affects: bluez (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Bluetooth suddenly stops working on Karmic
https://bugs.launchpad.net/bugs/384427
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez in ubuntu.