We found a serious problem recently, if your application starts earlier than gnome-session, and has accesses to gconf services, like iiim-panel, you will see two gconfd daemons after you login to gnome. It might due to the introducing of gnome-keyring (with ssh-agent), so that gnome-session does not recognize and reuse the existing gconfd daemon?

Then when iiim-properties(1) is invoked later by user, it actually talks to the
2nd gconfd, but iiim-panel still connects to the 1st gconfd.That's why iiim-panel does not update its language list after adding/removing input-methods with iiim-properties. [OS.o bug #4024]

A workaround is to terminate your gconfd daemon after iiim-panel is started. There would be no explict impacts to existing clients, they will try to connect to the new gconfd. A better solution is to defer the iiim-panel starting after gnome-session.

P.S., it turns out killing gconfd does not work perfectly, iiim-properties(1)
launched from terminal and the one launched by iiim-panel(1) would still start two different gconf daemons.