From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050910 CentOS/1.0.6-1.4.2.centos4 Firefox/1.0.6
Description of problem:
update my fc4 installation yesterday... the latest update x update hangs my computer - login screen is garbled
Version-Release number of selected component (if applicable):
last x update
Steps to Reproduce:
2.launch up2date and install/update x11 rpms
Actual Results: FC$ freezes
Expected Results: login screen should come up
I have the same problem. The computer does not freeze, but graphics mode does
not initialize properly. I am left with garbled text on the screen. I cannot
ctrl-alt-backspace, or ctrl-alt-F1. The only way to get out is to ctrl-alt-del
and wait for it to reboot.
I was forced to downgrade to the original Xorg packages to get graphics mode back.
>Version-Release number of selected component (if applicable):
>last x update
That is not good enough. Always specify the exact name-version-release,
otherwise the second a new update comes out, your comment is no longer
Run "rpm -q xorg-x11" and paste the results. Also always attach your
X server log and config file to every X bug report as individual uncompressed
file attachments using the bugzilla file attachment feature - even if
you think the log/config file may not be useful. They always tell
developers useful information 99.9% of the time that is helpful in
Thanks in advance.
Setting status to NEEDINFO_REPORTER, and awaiting file attachments and
Christopher can you please post or email the version and xServer log to to Mike.
I removed my installation of FC4 and will have to spend almost an entire day to
recreate this problem..
Created attachment 119152 [details]
X log file
The version that gave be problems was 6.8.2-37.FC4.48.1
The attached log file is what I think is the log for the failed attempt.
The attached log file is an unreadable binary file. Always attach log files
as uncompressed text/plain files so they can be viewed directly in a web
We've released a new update 6.8.2-37.FC4.49.2, which should resolve this
*** This bug has been marked as a duplicate of 168752 ***