Bug 55988 - Upgrading from 6.2 to 7.2 breaks graphical login
Summary: Upgrading from 6.2 to 7.2 breaks graphical login
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86   
(Show other bugs)
Version: 7.2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-11-09 21:38 UTC by Need Real Name
Modified: 2007-04-18 16:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-08-08 10:44:31 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Need Real Name 2001-11-09 21:38:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.7-10 i686)

Description of problem:
If you install redhat 6.2, make changes to /etc/X11/xdm/Xsession or
Xsetup_0, then upgrade to 7.2 using the cds, you will find that the
existing Xsession and Xsetup_0 will be renamed to *.rpmsave, and the new
ones will be named *.rpmnew.  When you try to log in, you'll get the
failsafe Xterm session instead of kde or gnome.

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

How reproducible:
Didn't try

Steps to Reproduce:
1.Install RedHat 6.2
2.Modify /etc/X11/xdm/Xsession or Xsetup_0
3.Upgrade to RedHat 7.2
4.Try to login

Actual Results:  Instead of KDE or Gnome, you get the failsafe session.

Expected Results:  A window manager should have started

Additional info:

Renaming *.rpmsave or *.rpmnew to * fixes the problem.

Comment 1 Mike A. Harris 2002-08-08 10:44:27 UTC
Hmm. What modifications were made to these files?  Could you attach
the modified files?  Perhaps your modifications are something worthy
of consideration to add to the default files.

I'll look into this issue probably during our next development cycle.

Comment 2 Mike A. Harris 2002-09-05 20:10:30 UTC
Closing bug due to lack of response.  Please reopen and update the
report with new information if the problem is still an issue and you
would still like to see it addressed in future releases.


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