Red Hat Bugzilla – Bug 68652
Switching back to metacity wm seems to be quite non-trivial operation
Last modified: 2008-05-01 11:38:02 EDT
Description of Problem:
After setting in an environment WINDOW_MANAGER to sawfish indeed this wm
is used in Limbo by session. But reversing that turns out be not that
simple. Neither unsetting WINDOW_MANAGER nor setting it explicitely
to 'metacity' does not have any effect. Only after I edited manually
~/.gnome2/session (removed all lines for 'sawfish' client and decremented
'num_clients') the next session started with no window manager at all
and typing in a terminal window 'metacity' and saving setup allowed for
the next session to start with it.
Going the other way once things are recorded in ~/.gnome2/session seems
to require similar operations. It seems possible to use a browser of
programs in a current session to kill unwanted window manager provided
one knows what "Respawn" means and how to handle this.
Ideally the way this works is that typing "metacity --replace" replaces your
current WM. That should work with fvwm2. I don't think Sawfish supports it, though.
I think the window_manager gconf key and WINDOW_MANAGER env variables should die,
to avoid confusion; and Sawfish should support --replace; but there is no
way the term "window manager" should be in the GUI, and I don't know a way
to make this into a simpler operation without putting it in the GUI.
Anyhow, should all be done upstream.
Changing to MoveUpstream keyword instead of GnomeUpstream tracking bug.
sorry about the spam.
Moved to http://bugzilla.gnome.org/show_bug.cgi?id=103244