tags 414981 +unreproducible thanks This seems to work (or at least not crash on startup). There are two issues in that error message (for reference, I'm a D-Bus developer, so I have a good idea about how this all works).
The name org.bluez was not provided by any .service files This is due to kbluetoothd trying to access an application which isn't running. In this case the submitter doesn't appear to have the bluetooth stack (provided by hcid in the bluez-utils package) running. It is running on my etch system and kdebluetooth depends on bluez-utils. I suggest the submitter should check that their system is both up to date and they haven't disabled bluez-utils for some reason. The second message should be non-fatal: process 20196: Applications must not close shared connections - see dbus_connection_close() docs. This is a bug in the application. This is due to a newer version of libdbus installed than kdebluetooth was compiled with. It should be updated, but it is not fatal and can wait for upstream. It is probably important rather than RC. Can the submitter please reply (and CC me) with the following: version of bluez-utils installed whether hcid is running the output of: dbus-send --system --print-reply --dest=org.freedesktop.DBus --type=method_call / org.freedesktop.DBus.ListNames Matt -- Matthew Johnson www.matthew.ath.cx
signature.asc
Description: Digital signature