Red Hat Bugzilla – Bug 247459
Mesa problem with i965Q
Last modified: 2018-04-11 12:39:33 EDT
Description of problem:
When I use an OpenGL software with "i810" or "intel" driver, i have corrupted
displays. The display can be OK with "vesa" driver. Especially, the up-right
quarter of the 3D frame is corrupted in wireframe mode. Plain surfaces can be
corrupted too (pixel with wrong color or transparency).
(I use paraView software to visualize datas in 3D)
Version-Release number of selected component (if applicable):
My intel driver is v2.0.0 (found by F7)
Steps to Reproduce:
3.swtich to wireframe
Works with "vesa" driver.
Could you elaborate a little bit -- this is not exactly descriptive bug report.
Could we get some screenshots of the display corruption?
And certainly please attach your X server config file (/etc/X11/xorg.conf) and X
server log file (/var/log/Xorg.*.log) from running with "intel" driver 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.
Created attachment 189601 [details]
Created attachment 189611 [details]
A screenshot of what I see on the screen.
Created attachment 189631 [details]
The same scene, as it is recorded by paraview (save image function)
I have sent some more information as requested.
My xorg.conf is the one used to make the screenshots. I have made some
modifications from the one generated by Fedora installation, but without change
on that particular bug (but is far better on other little problems).
I have made a screenshot of what I see on the screen with paraView (c.f 189611).
It's interesting to note that with the "save image function" of paraView, the
rendering is OK on the PNG file (c.f 189631).
I will send my /var/log/Xorg.0.log on a later post.
Just to be sure, that we won't forget on that Xorg.0.log file.
Created attachment 191431 [details]
My Xorg.O.log as recorded today.
I'll do the next step (auto xorg.conf generation) as soon as possible.
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. 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 '7'.
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 7'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 7 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. 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. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008.
Fedora 7 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.