Bug 109449 - Gnome setting daemon errors after pannel creation
Summary: Gnome setting daemon errors after pannel creation
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center   
(Show other bugs)
Version: 1
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-11-07 21:58 UTC by Maxwell Bottiger
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-11 22:12:22 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Maxwell Bottiger 2003-11-07 21:58:31 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b)
Gecko/20030516 Mozilla Firebird/0.6

Description of problem:
After having luck with the Fedora test 3 distro on my work computer
and laptop I decided to update my main home computer.  Fedora
installed ok, but after adding some gnome pannels I'm now having lots
of problems.  I would suspect there is something wrong in a gnome
settings file, but I've never edited them so I don't know where to
start really.

I added a second bottom pannel on my second monitor, and placed in it
a clock, workpace switcher, and a window menu.  I also added the gnome
fish to my main pannel.

When I now login, everything but the clock needs to be removed from
the pannel.  Once removed I cannot add them again.  Also, I get the
following error message:
There was an error starting the GNOME Settings Daemon.

Some 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 occurred

GNOME will still try to restart the Settings Daemon next time you log in.

When I log out, and log back in the same error appears, and I am still
unalbe to load any more of the util applets. This is a real pain
because I can't switch to multiple desktops any longer.  Oh, if it
makes a difference, I'm using the sawfish window manager, not metacity.

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

How reproducible:

Steps to Reproduce:
1.log in

Additional info:

Comment 1 Kyle R Maxwell 2003-11-12 17:56:00 UTC
Same happens to me. Worked fine after upgrading from test3 to core 1
(at that point, just XFree86 and mozilla updates) a few days ago, but
logging in this morning, I get this same error.

Comment 2 Maxwell Bottiger 2003-11-15 15:01:46 UTC
Actually, for no apparent reason my error messages disappeared.  I
ended up removing all my pannels but the main one, and every applet I
had on my desktop.  After a reboot or so it suddenly seems ok to add
stuff again.  With the exception of my gnome pager everything seems to
be back to normal.  The pager however, now looses the relative
position of all the windows when I move from one desktop.  Keying in
Alt-F1, etc. seems to work for changing desktops though.  I'm going to
report this to a gnome mailing list and see if I can find some help there.

Comment 3 Kyle R Maxwell 2003-11-15 17:37:57 UTC
I've been able to "solve" it by going to a text console and killing
bonobo-activation server (see
That's why rebooting seems to fix it. 

Comment 4 Jones Lee 2004-04-04 09:38:33 UTC
Yah, I got same too, very annoying.

Comment 5 Jonathan Blandford 2004-04-22 14:43:20 UTC
Can anyone reproduce this reliably?  If so, can I get them to try a
couple things?

Comment 6 Jeff Needle 2004-08-06 01:06:13 UTC
I can reproduce it 100% of the time on boot - still interested in
debugging it?  If so, my laptop is at your disposal.

Comment 7 Jeff Needle 2004-08-06 01:07:28 UTC
err, make that "on login", not on boot.

Comment 8 Ray Strode [halfline] 2005-05-11 22:12:22 UTC
Fedora Core 1 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.

Note You need to log in before you can comment on or make changes to this bug.