Bug 112248 - /etc/X11/prefdm never start kdm or xdm
Summary: /etc/X11/prefdm never start kdm or xdm
Keywords:
Status: CLOSED DUPLICATE of bug 72486
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 1
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-12-16 17:38 UTC by Roger Jordan
Modified: 2014-03-17 02:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:00:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Roger Jordan 2003-12-16 17:38:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007

Description of problem:
This code: 

if [ -f /etc/sysconfig/desktop ]; then
        . /etc/sysconfig/desktop
        if [ "$DISPLAYMANAGER" = GNOME ]; then
                preferred=gdm
        elif [ "$DISPLAYMANAGER" = KDE ]; then
                preferred=kdm
        elif [ "$DISPLAYMANAGER" = XDM ]; then
                preferred=xdm
        fi
fi 

looks for the $DISPLAYMANAGER variable but in the
/etc/sysconfig/desktop  the variable is called DESKTOP.

DISPLAYMANAGER is not defined in other places (I think ...) so the
condition will allways be false.


Version-Release number of selected component (if applicable):
7.42

How reproducible:
Always

Steps to Reproduce:
1.define in /etc/sysconfig/desktop DESKTOP="KDE"
2.reboot
    

Actual Results:  when graphic mode go on gdm started, no kdm.

Expected Results:  kdm running 

Additional info:

if I define in /etc/sysconfig/desktop DISPLAYMANAGER="KDE" kdm start
after reboot.

Comment 1 Roger Jordan 2003-12-16 17:45:36 UTC
The code is in the /etc/X11/prefdm file, sorry ...

Comment 2 Bill Nottingham 2003-12-16 17:49:12 UTC
This was intentional.

*** This bug has been marked as a duplicate of 72486 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:00:26 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.