Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 73401 - Gnome seems to have trouble with saving settings on logout
Summary: Gnome seems to have trouble with saving settings on logout
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-04 18:19 UTC by John Thompson
Modified: 2005-03-02 15:58 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Thompson 2004-12-04 18:19:23 UTC
Everytime I change a panel, delete a panel, add a launcher to a panel, etc., GNOME seems to have trouble dealing with this.  I will log out and try to log back in and I get the error message "I've detected a panel already running and I will now exit."  I try to click ok and the window keeps popping back up.  The splash screen never leaves the screen, you have to click on it to make it go away.  Then the error comes up.  Usually I have to delete some temporary file, such as /tmp/gconfd-john or /home/john/.gnome2/session and the problem goes away.  However, this is kind of annoying because every time I change some setting on my desktop, these configuration files seem to get corrupted.  

This has happened to me more than once.  I am using the meta-package, gnome-base/gnome. I also have mozilla-firefox and mozilla-thunderbird installed as well as openoffice-bin. I did not use USE="-sandbox" emerge openoffice-bin, I just used emerge openoffice-bin (I don't know why that would be relevant).

Reproducible: Sometimes
Steps to Reproduce:
1. First use the so-called stable gnome-base/gnome package of 2.6
2. Then login as a regular user
3. Change around your panels.
4. Then log out
5. Then log back in

Actual Results:  
The splash screen did not go away stopping at nautilus.  I had to click on it to
make it go away.  Then the message came up "I've detected a panel already
running, I will now exit."  You can't get this popup error to go away

Expected Results:  
I should have been able to log back into the desktop.

Here is the .xsession-errors from the user named alan before I changed the
panels around.

 cat /home/alan/.xsession-errors
/etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/X11/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w
/var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/216.77.30.94:0.Xservers" -h
"216.77.30.94" -l "216.77.30.94:0" "alan"
/etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
SESSION_MANAGER=local/bas-backup-linux:/tmp/.ICE-unix/15969
Window manager warning: Log level 32: could not find XKB extension.

** (nautilus:16086): WARNING **: destroyed file still being monitored

** (nautilus:16086): WARNING **: destroyed file still being monitored

** (nautilus:16086): WARNING **: destroyed file still being monitored

** (nautilus:16086): WARNING **: destroyed file still being monitored

(nautilus:16086): Bonobo-WARNING **: Leaked a total of 3 refs to 3 bonobo object(s)

Here is the .xsession-errors after the error occured - after I changed some panels.

 cat /home/alan/.xsession-errors
/etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/X11/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w
/var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/216.77.30.94:0.Xservers" -h
"216.77.30.94" -l "216.77.30.94:0" "alan"
/etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
SESSION_MANAGER=local/bas-backup-linux:/tmp/.ICE-unix/17004
Window manager warning: Log level 32: could not find XKB extension.

(gnome-panel:17110): Gtk-WARNING **: Ignoring the separator setting

(wnck-applet:17125): GConf-CRITICAL **: file gconf-client.c: line 547
(gconf_client_add_dir): assertion `gconf_valid_key (dirname, NULL)' failed

I am also using XDMCP to connect locally on a network, however, I have had
problems while trying to log in locally as well.
Comment 1 foser (RETIRED) gentoo-dev 2005-03-02 14:19:45 UTC
probably your gconf daemon didn't shut down & clean up ..

is this still a problem with most recent gconf-2.8.1-r1 in the tree ?
Comment 2 foser (RETIRED) gentoo-dev 2005-03-02 15:58:53 UTC
reply from author (reply in the bug next time John) : not reproducable anymore.