hal_initialize() overrides other filter/object/fallback functions on separate connection

[Dan Williams]

Hi,

Use the referenced testcase to verify and debug.  Symptom is that if
hal_initialize is called, filter/object/fallback functions registered on
another _separate_ DBusConnection never get called.  Seems to be a dbus
problem?

http://people.redhat.com/dcbw/testcase.tgz

Reference versions (FC3 Rawhide):
hal = 0.2.93.cvs20040712-2
dbus = 0.21.cvs20040722-3

To verify:

1) Untar
2) copy client.conf to /etc/dbus-1/system.d
3) copy client.conf to /etc/dbus-1/system.d
4) restart dbus daemon
5) restart hal daemon
6) ./autogen.sh
7) make
8) ./daemon
9) ./client
10) Look for "SUCCESS!!" from the client, CTRL-C both daemon and client
11) Modify the client code to UN-comment the "#define
MAKE_TESTCASE_FAIL" line (thus hal_initialize() is called)
12) make
13) ./daemon
14) ./client
15) Client should not print out SUCCESS!!

(forgive the detailed instructions...)

Dan

_______________________________________________
hal mailing list
hal at freedesktop.org
http://freedesktop.org/mailman/listinfo/hal