Same problem on Hardy heron now. 
~$ kbluemon
process 8170: arguments to dbus_message_new_method_call() were incorrect, assert
ion "_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.
process 8170: arguments to dbus_message_append_args_valist() were incorrect, ass
ertion "message != NULL" failed in file dbus-message.c line 1521.
This is normally a bug in some application using the D-Bus library.
process 8170: arguments to dbus_connection_send_with_reply_and_block() were inco
rrect, assertion "message != NULL" failed in file dbus-connection.c line 3252.
This is normally a bug in some application using the D-Bus library.
process 8170: arguments to dbus_message_unref() were incorrect, assertion "messa
ge != NULL" failed in file dbus-message.c line 1391.
This is normally a bug in some application using the D-Bus library.
process 8170: arguments to dbus_message_new_method_call() were incorrect, assert
ion "_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.
process 8170: arguments to dbus_message_append_args_valist() were incorrect, ass
ertion "message != NULL" failed in file dbus-message.c line 1521.
This is normally a bug in some application using the D-Bus library.
process 8170: arguments to dbus_connection_send_with_reply_and_block() were inco
rrect, assertion "message != NULL" failed in file dbus-connection.c line 3252.
This is normally a bug in some application using the D-Bus library.
process 8170: arguments to dbus_message_unref() were incorrect, assertion "messa
ge != NULL" failed in file dbus-message.c line 1391.
This is normally a bug in some application using the D-Bus library.
process 8170: arguments to dbus_message_new_method_call() were incorrect, assert
ion "_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.
process 8170: arguments to dbus_message_append_args_valist() were incorrect, 
ass                                                                             
                      ertion "message != NULL" failed in file dbus-message.c 
line 1521.
This is normally a bug in some application using the D-Bus library.
process 8170: arguments to dbus_connection_send_with_reply_and_block() were 
inco                                                                            
                       rrect, assertion "message != NULL" failed in file 
dbus-connection.c line 3252.
This is normally a bug in some application using the D-Bus library.
process 8170: arguments to dbus_message_unref() were incorrect, assertion 
"messa                                                                          
                         ge != NULL" failed in file dbus-message.c line 1391.
This is normally a bug in some application using the D-Bus library.
process 8170: arguments to dbus_message_new_method_call() were incorrect, 
assert                                                                          
                         ion "_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.
process 8170: arguments to dbus_message_append_args_valist() were incorrect, 
ass                                                                             
                      ertion "message != NULL" failed in file dbus-message.c 
line 1521.
This is normally a bug in some application using the D-Bus library.
process 8170: arguments to dbus_connection_send_with_reply_and_block() were 
inco                                                                            
                       rrect, assertion "message != NULL" failed in file 
dbus-connection.c line 3252.
This is normally a bug in some application using the D-Bus library.
process 8170: arguments to dbus_message_unref() were incorrect, assertion 
"messa                                                                          
                         ge != NULL" failed in file dbus-message.c line 1391.
This is normally a bug in some application using the D-Bus library.
[EMAIL PROTECTED]:~$ process 8170: arguments to dbus_message_new_method_call() 
were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file 
dbus-message.c line 1074.

-- 
[gutsy] kdebluetooth broken in current
https://bugs.launchpad.net/bugs/134585
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to