On Mon, 2004-02-16 at 17:07, Matt Brubeck wrote: > Kevin Collins wrote: > > > > It should be there. Sounds like a configuration problem. What's > > > the value of this gconf key: > > > > > > gconftool-2 -g /desktop/gnome/applications/window_manager/default > > > > > > (It should be "/usr/bin/metacity".) > > > > Ahhhh... > > > > It's set to /usr/bin/sawfish. > > > > How do I fix that? > > You can set it with gconftool-2 (see the example at the end of the man > page), or edit it in gconf-editor. > > > Once I installed Metacity, I did a "dpkg-reconfigigure > > x-window-manager" and chose Metacity. Didn't that do it? > > Ideally, the gconf key would be set automatically, but I'm not sure > where this is supposed to happen or why it doesn't. Looks like it was baggage carried over from a pre-Debian home folder. I deleted the .gconf and .gconfd folders in my home folder, restarted Gnome and walllaah, everything is like it should be. > Looking in upstream Bugzilla, it seems the long-term solution is to get > rid of this gconf key completely: > > http://bugzilla.gnome.org/show_bug.cgi?id=103244 > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=68652 Yeah, being a victim of the (self-inflicted) problem, I can see where the deletion of this would help. Thanks again for your help... -- Kevin L. Collins, MCSE Systems Manager Nesbitt Engineering, Inc. --------------------------------------------------- "Linux -- The OS people choose without $200,000,000 of persuasion." --Mike Coleman
Attachment:
signature.asc
Description: This is a digitally signed message part