https://bugzilla.novell.com/show_bug.cgi?id=461369 User led@lenday.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461369#c6 Len Day <led@lenday.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |led@lenday.com --- Comment #6 from Len Day <led@lenday.com> 2008-12-31 23:20:02 MST --- Beat my head against this until I figured out that my problem was not bluez... I had to learn bluez to find that out. I have now discovered that the gnome bluetooth applet and browser work fine for me with 4.19 (I should have tried it first but the wiki seemed to say I needed to upgrade bluez and I use KDE anyway so I'd like it to work). This is the case on my D830 notebook and on my desktop with a Broadcom USB dongle. Works with 4.19, 4.22 and 4.25... kbluetooth won't do anyting, however. With any of those three versions. On a right-click, all menu entries are gray and a left-click gets "The process for the bluetooth protocol died unexpectedly.". This is the error message from kbluetooth after a left click: Launched ok, pid = 6280 process 6283: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace kioslave: ####### CRASH ###### protocol = kio_bluetooth pid = 6283 signal = 6 akode: Guessed format: xiph KNotify::playTimeout Anyway, is there a way to get kbluetooth to work? Or to make the gnome applet from KDE? (I tried it, it runs but browsing doesn't work). Or to get the functionality from something else? BTW, the symptom in the original post about not getting on the D-bus happens if one does bluetooth -nd while it is already running in the background. Voice of experience here... So maybe this is a different problem than the one originally reported. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.