Hi,<br><br>The following code:<br><br>---------------------------------------------------------------<br>DBusError e;<br>DBusConnection *conn = NULL;<br><br>g_type_init ();<br>dbus_error_init(&e);<br><br>conn = dbus_bus_get(DBUS_BUS_SESSION, &e);<br>
--------------------------------------------------------------------<br><br>causes:<br><br>3896: assertion failed "(error) == NULL || dbus_error_is_set ((error))" file "D:\kde\distfiles\svn-src\dbus-src\tags\1.2.4\dbus\dbus-sysdeps-win.c" line 3159 function _dbus_get_autolaunch_address<br>
Backtrace:<br>4 KiFastSystemCallRet<br>3 WaitForSingleObject+0x12<br>3 dbus_print_backtrace+0x94<br>3 dbus_abort+0xb<br>3 dbus_real_assert+0x46<br>3 dbus_get_autolaunch_address+0x2b3<br>
3 dbus_transport_open+0x550<br>3 dbus_transport_open+0x11e<br>3 dbus_connection_close+0xe52<br>3 dbus_bus_register+0x3fd<br>3 RegisterWaitForInputIdle+0x49<br><br><br>-> when the dbus-daemon is not running<br>
<br>I think it's not a normal behavior.<br><br>It's hard to test it on ubuntu (for example) because a lot of process needs this daemon (so you may not want to kill it), but on win32 it's easy to reproduce it.<br>
<br>version 1.2.4-1<br><br>Should i report a bug ?<br><br>Note that I 'm new to dbus so maybe I am doing something wrong.<br><br>Sincerely<br><br>Julien<br>