Bug 137274 - prefdm does not correctly fall back to installed DMs
prefdm does not correctly fall back to installed DMs
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-10-27 02:38 EDT by Isam Bayazidi
Modified: 2014-03-16 22:49 EDT (History)
1 user (show)

See Also:
Fixed In Version: 7.93.1-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-27 15:25:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Isam Bayazidi 2004-10-27 02:38:13 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020
Firefox/0.10.1

Description of problem:
the /etc/X11/prefdm looks for the DISPLAYMANAGER in the
/etc/sysconfig/display while in the file /etc/sysconfig/display there
is  DESKTOP.

I am installing a Fedorda Core without Gnome, but with KDE instead,
thus gdm (the first option for fallback in prefdm) is not there, and
for some reason, it does not reach kdm, and X is not started upon init 5.

Version-Release number of selected component (if applicable):
initscripts-7.93-1

How reproducible:
Always

Steps to Reproduce:
1. Install FC without Gnome, with KDE instead
2. Reboot
3. Enter init 5
    

Actual Results:  X not started, DESKTOP setting in
/etc/sysconfig/display is not considered by prefdm

Expected Results:  settings in /etc/sysconfig/display to be considered
Comment 1 Bill Nottingham 2004-10-27 12:18:03 EDT
That's intentional; DISPLAYMANAGER is a separate config setting.

If you run it by hand, where does it exit?
Comment 2 Bill Nottingham 2004-10-27 15:25:00 EDT
Fixed in 7.93.1-1. Oops.

(Adding shopt -s execfail to prefdm should make it work for you.)

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