Yong Sun wrote: > Hi, experts, > > We recently met a problem with gconf, as you may know, iiim-panel is > started earlier than gnome-session, and it calls gconf client APIs, so a > gconfd daemon is started. But gnome-session would start another gconfd > daemon, while iiim-panel still connected and listened to the 1st gconfd. > The new gconf clients (started after gnome-session) would connect to the > 2nd gconfd daemon, so iiim-panel could not receive the setting changing > notifications. > A proper fix for this dbus session daemon starting is described in bugster, 6755007. Though that fix is only in trunk of spec files at the moment. I think there are two things you can do: - Don't start iiim-panel so early, start only when user needs them - push for bug fix 6755007 as a stopper for OpenSolaris 2008.11
-Ghee > Though I could make gnome-session to start iiim-panel, I'd like to know > why gnome-session starts the 2nd gconfd, it dues to the gnome-keyring > (with a ssh-agent)? > > Regards, > _______________________________________________ > desktop-discuss mailing list > desktop-discuss at opensolaris.org >
