Red Hat Bugzilla – Bug 493522
[radeon test day] After updating to xorg-x11-drv-ati-6.12.1-1.fc11.x86_64, X is unable to start
Last modified: 2018-04-11 05:32:06 EDT
Created attachment 337717 [details]
Log when X crashes (includes traceback)
Description of problem:
As part of the radeon test day, I created a USB key with the rawhide image installed on it, as well as a 100MB overlay. After installing xorg-x11-drv-ati-6.12.1-1.fc11.x86_64.rpm and rebooting, X no longer starts (see attachment).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Update to xorg-x11-drv-ati-6.12.1-1.fc11.x86_64.rpm
Smolt profile: http://smolt.fedoraproject.org/show?uuid=pub_f2464a1c-0f51-4652-8830-fa985b02ac30
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command
yum upgrade --enablerepo='*-updates-testing'
Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .
Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
It's been working fine for a while now, closing...