Bug 150077 - Default windowmanager is Gnome altogh GNOME is not installed
Summary: Default windowmanager is Gnome altogh GNOME is not installed
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 3
Hardware: Other Other
: P5 - None : Minor (vote)
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-10 21:31 UTC by Ladislav Michnovic
Modified: 2006-03-15 14:20 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ladislav Michnovic 2006-02-10 21:31:13 UTC 
I choosed to install minimal graphical system, so GNOME is not installed on my maschine. But I have installed gdm. 

In /etc/sysconfig/windowmanager is 

## Path:        Desktop/Window manager
## Description:
## Type:        string(kde,fvwm,gnome,windowmaker)
## Default:     kde
## Config:      profiles,kde,susewm
#
# Here you can set the default window manager (kde, fvwm, ...)
# changes here require at least a re-login
DEFAULT_WM="gnome"
            ^^^^^

Gdm offers me to choose FVWM2 or Windowmaker etc., but not GNOME. 
Even though, gnome is in /etc/sysconfig/windowmanager. 

In gdm I can choose GNOME.failsafe but after that it writes a warning:
"Could not find the GNOME installation..." and ran terminal.failsafe.
Comment 1 Mark Gordon 2006-03-02 20:45:41 UTC 
I would expect the installer to set this, presumably to fvwm in a minimal graphic system.
Comment 2 Martin Vidner 2006-03-03 08:22:05 UTC 
Jirka, this should be already fixed in yast2-installation, but the bug number in the changelog is wrong.
- fixed setting default desktop according to destop dialog (bug #152709)
- 2.13.25
Comment 3 Lukas Ocilka 2006-03-15 14:20:26 UTC 
Well, but it has been already fixed :)
If it isn't, please, reopen the bug.