Description of problem:

After the latest round of updates, not always but often enough,
when a desktop session starts I am greeted with an alert which
says the following:

<quote>
There was an error starting the GNOME Settings Daemon.

Smome things, such as themes, sounds, or background settings
may not work correctly.

The Settings Daemon restarted too many times

The last error message was:

Child process did not give an error message, unknown failure
occured.

GNOME will still try to restart the Settings Daemon next time
you log in.
</quote>

Nothing seems to be particularly amiss and on the next attempt
to logon usually there is no alert.  This happens both for
non-root and root sessions.  The only possible clue is that
in /var/log/messages things like that show up:

Jul 30 15:05:35 dyna0 bonobo-activation-server (michal-13328): iid
OAFIID:BrokenNoType:20000808 has a NULL type
Jul 30 15:05:35 dyna0 bonobo-activation-server (michal-13328): invalid
character '#' in iid 'OAFIID:This#!!%$iid%^$%_|~!OAFIID_ContainsBadChars'
Jul 30 15:05:37 dyna0 bonobo-activation-server (michal-13328): file
object-directory-corba.c: line 686 (add_active_server): assertion
failed: (!strcmp (iid, NAMING_CONTEXT_IID) || !strcmp(iid,
EVENT_SOURCE_IID))
Jul 30 15:05:37 dyna0 bonobo-activation-server (michal-13382): iid
OAFIID:BrokenNoType:20000808 has a NULL type
Jul 30 15:05:37 dyna0 bonobo-activation-server (michal-13382): invalid
character '#' in iid 'OAFIID:This#!!%$iid%^$%_|~!OAFIID_ContainsBadChars'

Some other component may be actually responsible since alert
started to show up later then the latest libbonobo update was
done.  Other most likely candidates seem to be 
libgnomeui, ORBit2 and gtk2.

Version-Release number of selected component (if applicable):
libbonobo-2.6.0-3

How reproducible:
about fifty-fifty