Because hal doesn't exist on the dbus at this time apparently. But it works fine if I restart Thunar later, so there might be a race condition somewhere? Anyway, dbus api doc clearly states that using this function can easily result in a race condition, so I don't really understand why libhal.c uses it...
Hi Martin,
I think that the bug lies in hal finally. :p
I added fprintfs in libthunar-vfs, and the init code fails with libhal_ctx_init(). So I added also some printfs in libhal_ctx_init(), and it fails at:
hald_exists = dbus_bus_ name_has_ owner (ctx->connection, "org.freedeskto p.Hal", &_error);
return FALSE;
[...]
if (!hald_exists) {
}
Because hal doesn't exist on the dbus at this time apparently. But it works fine if I restart Thunar later, so there might be a race condition somewhere? Anyway, dbus api doc clearly states that using this function can easily result in a race condition, so I don't really understand why libhal.c uses it...
Any idea, thoughts, tests to do? Thanks!