Bug 1017463 - after install from LIVE and running all updates, X fails to start at boot.
Summary: after install from LIVE and running all updates, X fails to start at boot.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 20
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-10 00:10 UTC by fred smith
Modified: 2015-06-29 12:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 12:36:02 UTC
Type: Bug


Attachments (Terms of Use)
console output from startx failure (2.36 KB, text/plain)
2013-10-10 00:10 UTC, fred smith
no flags Details
xorg log file from period when failure occurred (27.05 KB, text/plain)
2013-10-10 00:12 UTC, fred smith
no flags Details
dmesg file (dmesg > ./dmesg) covering period of failure (58.56 KB, text/plain)
2013-10-10 00:13 UTC, fred smith
no flags Details

Description fred smith 2013-10-10 00:10:38 UTC
Created attachment 810208 [details]
console output from startx failure

Description of problem:
Installed F20 Beta TC2, using USB HD, on Asus eeepc 901. after install it works well, so I did a full update using yumex. after update, reboot. when rebooting, X fails to start, leaving you at a text login prompt. doing a text login, then typing "startx" spews some messages then returns to a text login prompt.

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

How reproducible:
did the full install and update twice. same thing both times.

Steps to Reproduce:
1. install F20 Beta TC2 on Asus eeepc 901
2. after install, reboot
3. after reboot, use yumex to update all necessary packages.
4. after update, reboot
5. when it gets near to starting X/lightdm, it drops to a text login prompt.

Actual results:
X won't start

Expected results:
X starts and works.

Additional info:
several files uploaded (see above).

Comment 1 fred smith 2013-10-10 00:12:28 UTC
Created attachment 810209 [details]
xorg log file from period when failure occurred

Comment 2 fred smith 2013-10-10 00:13:26 UTC
Created attachment 810210 [details]
dmesg file (dmesg > ./dmesg) covering period of failure

Comment 3 fred smith 2013-10-10 02:58:10 UTC
As an experiment, I just did exactly the same thing on my Acer netbook and got exactly the same result.

something in the update is breaking things, but I dunno what. in an earlier iteration of the same steps, on my Asus 901, I had tried updating in stages, first all the xorg packages, then a reboot, then all the mate packages, then a reboot, and none of those caused it to break. from there I wasn't sure which groups to update next, and just did all the remaining ones and again it failed.

I can try some more stepwise updates if anyone can suggest specific things to try.

Comment 4 fred smith 2013-10-10 02:59:16 UTC
Sigh. I see I neglected to mention this was the MATE LIVE spin.

Comment 5 Fedora End Of Life 2015-05-29 09:32:47 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-06-29 12:36:02 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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