GNOME Bugzilla – Bug 103244
Eliminate window-manager gconf key (and perhaps WINDOW_MANAGER env variable)
Last modified: 2004-12-22 21:47:04 UTC
Bugzilla-Product: gnome-session Description: Please see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=68652 for the original bug report. ------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-12 20:55 ------- Reassigning to the default owner of the component, gnome-session-maint@bugzilla.gnome.org.
The original problem: Setting WINDOW_MANAGER=sawfish, saving your sesssion and then unsetting the WINDOW_MANAGER variable, doesn't cause us to switch back to metactiy. Havoc's proposed solution: > 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. So, the idea here would be that all WM's should support a --replace arg so that the way you change to using sawfish would be: $> sawfish --replace; gnome-session-save I think $WINDOW_MANAGER is just an okay hack to specify the default WM used in GNOME for new users and we shouldn't expect any more of it than that. I don't see the harm in leaving it there. So, what the original reporter was seeing is "expected behaviour" and what Havoc is proposing (all WMs should have --replace) just makes switching WMs after the first login easier.