Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Sigh! Here is this report for real. 'man gnome-wm' from gnome-session package claims: The user can overwrite the selection of a window manager by setting the WINDOW_MANAGER environment variable. OK, lets try. 'echo $WINDOW_MANAGER' shows 'sawish' (in case you wonder I do have sawfish compiled for rawhide and it was even running not so long time ago). What actually runs? metacity. A script /usr/bin/gnome-wm looks at a value provided by gconftool-2 --get /apps/gnome-session/rh/window_manager in case WINDOW_MANAGER was not set. So lets try to set that to "sawfish". What runs? You guessed it - metacity. That is not so surprising when even after "hardwiring" WINDOW_MANAGER=sawfish in /usr/bin/gnome-wm script one ends up running .... metacity! So how to change that default? gnome-session-2.23.2.2-3.fc10
Obviously susbstitute above "sawfish" for "sawish".
export WINDOW_MANAGER ?
> export WINDOW_MANAGER ? It is exported but if write directly in /usr/bin/gnome-wm WINDOW_MANAGER=sawfish before it is used then one would think that this is even "stronger". Going through a bug search again it appears that bug 447309 would be another, more specific, instance of really the same issue.
*** This bug has been marked as a duplicate of 447309 ***