Bug 449048
| Summary: | new gnome-session no longer honors (uses?) gnome-wm preferences | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal> |
| Component: | gnome-session | Assignee: | Ray Strode [halfline] <rstrode> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-05-30 18:27:35 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Michal Jaegermann
2008-05-30 02:59:08 UTC
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. |