Red Hat Bugzilla – Bug 473124
X corruption problems
Last modified: 2018-04-11 03:23:54 EDT
Created attachment 324756 [details]
A photo of the corruption (from my cell phone camera)
Description of problem:
I've been running rawhide in preparation for the release of F10, and haven't had any problems up until last week or so (which should be all the components of Fedora 10 itself).
If I boot to runlevel 3 and then log in as a non-root user and then type "startx", the display is corrupted. If I boot to runlevel 5 (with or without rhgb, and with or without appending the "nomodeset" option), I have approximately a 50/50 chance of successfully making my way into X without corruption issues. If I boot into the 22.214.171.124-109 kernel it *seems* to work more often than either 126.96.36.199-117 or -113, but that's just a gut feeling.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot Fedora 10
2. Boot into runlevel 5, or boot to runlevel 3 and then start X
Corrupted graphics (see screenshot)
[root@frankenbox ~]# uname -a
Linux frankenbox 188.8.131.52-117.fc10.x86_64 #1 SMP Tue Nov 18 11:58:53 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
[root@frankenbox ~]# grep '(EE)' /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) Unable to locate/open config file
(EE) open /dev/fb0: No such file or directory
[root@frankenbox ~]# lspci | grep GeFo
03:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7600 GS] (rev a1)
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
I'm not using an xorg.conf file... X is running without it. I'll attach two Xorg.0.log files... one from a working startup of X, and one from a corrupted one. At first glance, I'm not able to tell anything different between the two files that would indicate where the problem might lie.
Created attachment 326327 [details]
A log from a working X session
Created attachment 326328 [details]
A log from a corrupted X session
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 WONTFIX if it remains open with a Fedora
'version' of '10'.
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 prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.
Thank you for reporting this bug and we are sorry it could not be fixed.