Comment 2 for bug 134585

Same here.

* No contextual menu in Konqueror.

* Device discovery via bluetooth:/ is slow. My own bluetooth dongle isn't detected? It used to be. Also, after launching kbluetooth, or if connected the dongle while kbluetooth was running, device discovery won't work at all.

* Service discovery only discovers some services via bluetooth:/. I don't know if this is a feature, though (maybe the kio hides the services we can't handle?). Also, after launching kbluetooth, or if connected the dongle while kbluetooth was running, service discovery won't work at all.

* If I disconnect & reconnect the dongle AFTER use the new device config thing, kbluetooth crashes. This output is shown if I run kbluetooth in console:
---------------------------8<----------------------
process 26016: arguments to dbus_message_new_method_call() were incorrect, assertion "destination == NULL || _dbus_check_is_valid_bus_name (destination)" failed in file dbus-message.c line 1073.
This is normally a bug in some application using the D-Bus library.
process 26016: arguments to dbus_message_append_args_valist() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1521.
This is normally a bug in some application using the D-Bus library.
process 26016: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "message != NULL" failed in file dbus-connection.c line 3248.
This is normally a bug in some application using the D-Bus library.
process 26016: arguments to dbus_message_unref() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1391.
This is normally a bug in some application using the D-Bus library.
process 26016: arguments to dbus_message_new_method_call() were incorrect, assertion "destination == NULL || _dbus_check_is_valid_bus_name (destination)" failed in file dbus-message.c line 1073.
This is normally a bug in some application using the D-Bus library.
process 26016: arguments to dbus_message_append_args_valist() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1521.
This is normally a bug in some application using the D-Bus library.
process 26016: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "message != NULL" failed in file dbus-connection.c line 3248.
This is normally a bug in some application using the D-Bus library.
process 26016: arguments to dbus_message_unref() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1391.
This is normally a bug in some application using the D-Bus library.
KCrash: Application 'kbluetooth' crashing...
---------------------------8<----------------------

* The device discovery thing from kbluetooth won't work at all (well... via bluetooth:/ won't work also as I stated up there).