On Thu, 2006-01-26 at 09:33 +0100, Alexander Larsson wrote:
> On Wed, 2006-01-25 at 20:46 -0500, Thomas J. Baker wrote:
> >
> >
> > I just updated two more FC5 systems and both of them worked fine
> > without
> > any gconfd problems. Same procedure as before.
>
> There is clearly something strange going on with gconf and schema
> installs...
Problem sounds like a gconfd-2 caching problem - i.e. gconfd-2 is
running as the user and doesn't notice when new schemas are installed.
There has always been the potential for that problem, but it can be much
worse now:
- previously, gconfd-2 would have picked up schemas for newly
installed apps - it would be a new dir under gconf.xml.defaults
which wouldn't have been cached. It wouldn't have picked up new
schemas for an already installed app, if that app had been run and
the new schemas were in the same dir as the old schemas.
- with "merged subtree" mode, though, schemas are added to one big
file which is going to be cached by gconfd-2 already. So, it's not
going to notice any new schemas
- what's more, if you're running an old gconfd-2 and you update, then
the apps all install their schemas into the merged database and
gconfd-2 is still reading from the unmerged version.
Doing the equivalent of "killall -HUP gconfd-2" from gconftool-2
--makefile-install-rule should fix it.
See:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=173869
Cheers,
Mark.
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
