https://bugzilla.novell.com/show_bug.cgi?id=438956
User coomac@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=438956#c7
Nkoli Ukpabi changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |coomac@gmail.com
--- Comment #7 from Nkoli Ukpabi 2008-11-30 08:01:31 MST ---
Using RC1 as well. When I turn on my bluetooth radio with the hardware switch,
dmesg indicates that it is detected correctly. However, kbluetooth4 is not
started automatically. I start it manually from the command line and just as
with the other commenters, nothing happens.
If I try to run either kbluetooth4-devicemanager or kbluetooth4-inputwizard,
the bluetooth stack segfaults. I get the following error message:
process 9534: arguments to dbus_message_new_method_call() were incorrect,
assertion "path != NULL" failed in file dbus-message.c line 1070.
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
kbluetooth4-wizard(9533): Communication problem with "kbluetooth4-wizard" , it
probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not
receive a reply (timeout by message bus)" "
I thought kde4 dropped dbus for dcop :S I can paste the backtrace if it'll
help.
--
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.