GNOME Bugzilla – Bug 638677
gnome-session starts saved-sessions before the windowmanager/panel components from the gconf dir
Last modified: 2011-03-09 17:10:07 UTC
I'm using from time to time the awesome WM (with gnome-session) instead of gnome-panel/metacity. Sometimes after wanting to start awesome(set /desktop/gnome/session/required_components windowmanager to awesome and panel to nil) gnome-panel and metacity got started. Today I figured out why: because of the entries in .conf/gnome-session/saved-session/ . If this folder contains entries for apps which provide certain services (X-Gnome-Provides) then these services are started before the required_components. If in the /desktop/gnome/session/required_components gconf dir is an app which is different from an app in saved_sessions but provides the same (X-Gnome-Provides) service then the app in required_components is ignored!! warning in .xsession-errors: GsmManager: service 'windowmanager' is already provided
Created attachment 177507 [details] gs with an non empty save_session dir (contains entries for gnome-panel and metacity)
Created attachment 177508 [details] gs with an empty save_session dir
Created attachment 177509 [details] xsession startup script loaded from GDM awesome-gnomesession.desktop calls a script which contains exec $curdir/start-gnome-session awesome false same with gnome-gnome-session.desktop except exec $curdir/start-gnome-session metacity true
We don't have a sane story here, see bug 642367 *** This bug has been marked as a duplicate of bug 642367 ***