After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 103244 - Eliminate window-manager gconf key (and perhaps WINDOW_MANAGER env variable)
Eliminate window-manager gconf key (and perhaps WINDOW_MANAGER env variable)
Status: RESOLVED NOTABUG
Product: gnome-session
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-01-13 01:58 UTC by Havoc Pennington
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Havoc Pennington 2003-01-13 01:55:46 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.

Comment 1 Mark McLoughlin 2004-04-20 09:12:33 UTC
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.