Thanks for th e info. the problem seems to be your manual invocation of metacity --replace (I assume it is manually invoked) does not replace (pid 8725) metacity. gnome-session saw that one of its required component, windowmanager is exiting while it is in running mode, it tries to restart it. The freshly restarted metacity found that a window manager is already running (pid 23032), so it exits and the interaction between gnome-session and metacity keeps on repeating and hence the error you saw. Killing 23032 sorted the problem because the freshly restarted metacity does not exit.
Why did you run metacity --replace ? The bug is more like why does --replace did not work. If you have more information, we would like to know, -Ghee p.s. can you send me your .config/gnome-session/saved-session/* May be there is some info in there that may be helpful. On 11/12/2009 06:03 PM, Shawn Walker wrote: > Ghee Teo wrote: >> Which window manager are you using? >> It seems like gconf values associated with metacity is looping. Is >> metacity running on your machine? >> attached a ptree, please. > > Yes, it is running: > > 791 /usr/sbin/gdm-binary > 792 /usr/sbin/gdm-binary > 17957 /usr/X11/bin/Xorg :0 -nolisten tcp -audit 0 -br -auth > /var/lib/gdm/:0.Xauth > 17987 gnome-session > 18078 gnome-panel > 18079 nautilus > 18080 /usr/perl5/bin/perl /usr/bin/desktop-print-management-applet > 18081 python /usr/lib/system-config-printer/applet.py > 18083 gnome-power-manager > 18086 /usr/lib/nwam-manager > 18091 /usr/bin/xscreensaver -nosplash > 8725 metacity > 18012 dbus-launch --exit-with-session --sh-syntax > 18013 /usr/lib/dbus-daemon --fork --print-pid 7 --print-address 10 > --session > 18066 /usr/lib/gconfd-2 > 18070 /usr/lib/gnome-settings-daemon > 18071 gnome-keyring-daemon --start > 18076 /usr/lib/gvfsd > 18097 /usr/bin/iiimx -iiimd > 18099 iiimd -nodaemon -desktop -udsfile /tmp/.iiim-swalker/:0.0 > -vardir /export/home/ > 18124 iiim-xbe > 18103 /usr/lib/bonobo-activation-server --ac-activate --ior-output-fd=21 > 18105 /usr/lib/gvfsd-trash --spawner :1.7 /org/gtk/gvfs/exec_spaw/0 > 18109 /usr/lib/trashapplet > --oaf-activate-iid=OAFIID:GNOME_Panel_TrashApplet_Factory > 18111 /usr/lib/wnck-applet > --oaf-activate-iid=OAFIID:GNOME_Wncklet_Factory --oaf-ior- > 18113 /usr/lib/gvfs-hal-volume-monitor > 18119 /usr/lib/mixer_applet2 > --oaf-activate-iid=OAFIID:GNOME_MixerApplet_Factory --oa > 18120 /usr/lib/clock-applet > --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf > 18121 /usr/lib/notification-area-applet > --oaf-activate-iid=OAFIID:GNOME_NotificationA > 18126 /usr/lib/notification-daemon > 18144 /usr/bin/gtk-window-decorator --replace --display=:0.0 > 22719 gnome-terminal > 22723 gnome-pty-helper > 22725 bash > 8728 ptree swalker > 23032 metacity --replace > > However, I noticed that its actually starting and exiting over and > over again rapidly which explains a few things. > > Once I killed the last metacity process there (23032), then gconfd > stopped running rampant. > > However, everytime I login, this behaviour starts again :/ > > I've already tried a gnome-cleanup to no avail. > > Cheers,
