> process 8234: 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.
> libhal.c 939 : Couldn't allocate D-BUS message
> error: libhal_device_get_property_type: (null): (null)
> hal_get_property.c 178 : INFO: called LIBHAL_FREE_DBUS_ERROR but
> dbusError was not set.
>
This is different bug, I'm pretty sure. I'll correspond with you and
try to work out a couple things, but it might be a decent thing to file
a bug report about anyway.
> process 8234: arguments to dbus_message_ new_method_ call() were check_is_ valid_path (path)" failed in file device_ get_property_ type: (null): (null) FREE_DBUS_ ERROR but
> incorrect, assertion "_dbus_
> dbus-message.c line 1074.
> This is normally a bug in some application using the D-Bus library.
> libhal.c 939 : Couldn't allocate D-BUS message
> error: libhal_
> hal_get_property.c 178 : INFO: called LIBHAL_
> dbusError was not set.
>
This is different bug, I'm pretty sure. I'll correspond with you and
try to work out a couple things, but it might be a decent thing to file
a bug report about anyway.