Bug#553343: gnome-session: after upgrading, something continuously sends data to gconfd making it occupy 100% of the CPU

[Vasilis Vasaitis]

On Tue, Nov 03, 2009 at 03:00:42PM +0100, Josselin Mouette wrote:
> Le mardi 03 novembre 2009 à 13:16 +0000, Vasilis Vasaitis a écrit : 
> > > This should work as well then. But it will not if you have saved a
> > > session including another window manager, of course.
> > 
> >   Well, it doesn't (I just tried again). I also tried removing
> > 'windowmanager' from /desktop/gnome/session/required_components_list,
> > again no effect.
> 
> This is because it is already started as part of your saved session!

  Ah. I had assumed that, since it didn't appear in either the
gnome-session properties dialog, or ~/.gnome2/session, that it wasn't
part of the saved session. Apparently I had overlooked
~/.config/gnome-session/saved-session/ (a hint for where to look would
have saved us both some trouble). I'm now running compiz, and
gnome-session doesn't try to start metacity any more. Thanks. :^)

  It's unfortunate then that gnome-session tries to start the window
manager both through gnome-wm and through the saved session, it can be
a cause of much confusion (as the present exchange amply demonstrates
;^) ). Do you reckon it's a behaviour worth modifying? Should I take
it upstream?

Thanks,
Vasilis

-- 
Vasilis Vasaitis
"A man is well or woe as he thinks himself so."