Bug 134690 - Xclients file missing a line in latest package (4.0.7-1)
Summary: Xclients file missing a line in latest package (4.0.7-1)
Keywords:
Status: CLOSED DUPLICATE of bug 134673
Alias: None
Product: Fedora
Classification: Fedora
Component: xinitrc
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-05 16:28 UTC by Ryan Skadberg
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

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


Attachments (Terms of Use)

Description Ryan Skadberg 2004-10-05 16:28:02 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041002
Firefox/0.10.1

Description of problem:
In the latest Xclients file an fi is missing that causes you not to be
able to log in.

In the block trying to figure out PREFERRED it has:

if [ -f /etc/sysconfig/desktop ]; then
    . /etc/sysconfig/desktop
    if [ "$DESKTOP" = "GNOME" ]; then
        PREFERRED=gnome-session
    elif [ "$DESKTOP" = "KDE" ]; then
        PREFERRED=startkde
fi


This should be:

if [ -f /etc/sysconfig/desktop ]; then
    . /etc/sysconfig/desktop
    if [ "$DESKTOP" = "GNOME" ]; then
        PREFERRED=gnome-session
    elif [ "$DESKTOP" = "KDE" ]; then
        PREFERRED=startkde
    fi
fi

Note the fi after the startkde line.


Version-Release number of selected component (if applicable):
xinitrc-4.0.7-1

How reproducible:
Always

Steps to Reproduce:
1. startx or try to log in from XDM


Actual Results:  Not able to start X session

Expected Results:  X logs in correctly

Additional info:

Comment 1 Andrew Farris 2004-10-05 20:40:18 UTC
Also bug: #134673 #134711 #134726

Comment 2 Mike A. Harris 2004-10-06 04:10:10 UTC

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

Comment 3 Red Hat Bugzilla 2006-02-21 19:06:08 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.