Bug 107580 - Gconfd2 stays running on logout causing next login to fail
Summary: Gconfd2 stays running on logout causing next login to fail
Status: CLOSED DUPLICATE of bug 106826
Alias: None
Product: Fedora
Classification: Fedora
Component: GConf2   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Mark McLoughlin
QA Contact:
Depends On:
Blocks: CambridgeBlocker
TreeView+ depends on / blocked
Reported: 2003-10-20 19:48 UTC by Chris Smith
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 18:59:18 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 Chris Smith 2003-10-20 19:48:44 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031009

Description of problem:
Gconfd2 doesn't get shut down on logging out from gnome once evolution has been
run.  This causes gconfd2 to fail when logging in again and the desktop to die
miserably with a dialog:

"The Settings Daemon restarted too many times."

And then no panel applets or icons will start up.

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

How reproducible:

Steps to Reproduce:
1. Login as a standard user
2. Start evolution
3. Log out
4. Log back in as a standard user
5. Boom! problem

Additional info:

processes still running that shouldnt be:

- gconfd2
- bonobo-activation-server
- evolution-wombat-somethingorother

Killing these processes after logout from the console allows a normal login
again.  These shouldn't exist after logging out from gnome back to gdm.

Both of my machines do this with plain Fedora .95 installs.  this is release
critical IMHO.

Comment 1 Michael K. Johnson 2003-10-21 19:45:55 UTC

*** This bug has been marked as a duplicate of 106826 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:59:18 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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