Bug 447472 - Mesa: Some graphics-eyecandy doesn't display on VIA KM400 IGP
Summary: Mesa: Some graphics-eyecandy doesn't display on VIA KM400 IGP
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 7
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-20 00:25 UTC by Chris Schembari
Modified: 2008-06-17 03:08 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-06-17 03:08:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Output from "glxinfo -i -l -t -v" (7.74 KB, text/plain)
2008-05-20 00:25 UTC, Chris Schembari
no flags Details
Composite of four screenshots from blobAndConquer 0.91, on my VIA box. (232.37 KB, image/jpeg)
2008-05-20 00:28 UTC, Chris Schembari
no flags Details

Description Chris Schembari 2008-05-20 00:25:37 UTC
Description of problem:
This bug shows up with my first home-brew PC using an Abit VA-10 motherboard
with an S3 UniChrome/VIA KM400 IGP; but it does not on my newest home-brew box
that uses an ECS GeForce 6100SM-M2 motherboard with an NVidia MCP61S IGP.
  The bug causes certain graphics in blobAndConquer and SuperTux to not display
properly, to the extent that those graphics elements appear as empty, glaring
white boxes.  The places where this occurs in blobAndConquer are obvious from
the attached screenshots.  In SuperTux, it shows up in a loss of background
pictures, which are all washed-out; but the most obvious place it shows up is on
two game levels: "No More Mr. Ice Guy" and the hidden bonus level, "Light and
Magic".  In NMMIG, when you defeat the Ice Guy, half the screen disappears and
goes white, but the game is still playable.  On the NVidia box, I learned that
this is when you see an even _more_ cartoonish picture of the Ice Guy with stars
and little birds flying around his head.  In LaM, the entire level is
unplayable, since everything, even Tux himself, is now invisible and the whole
screen again goes white.
  I first thought this was a bug against blobAndConquer, and filed a bug report
against it, but I was advised that this was really a problem with mesa, and told
to file this report. See my screenshot attachment (#305309) to bug #446306, as
well as the below.  Please note that all screenshots in attachment #305309 [details] were
taken on the above NVidia box, whereas most of the below were taken on this VIA box.

Version-Release number of selected component (if applicable):
  In querying for existing mesa bugs, I found mention of the "glxinfo" command,
and included its verbose output below.

How reproducible:
  Problem appears 100% consistently in certain graphical parts of blobAndConquer
and SuperTux, as already described.

Steps to Reproduce:
1. Install each game.
2. Start one game or the other.
3. [With regards to blobAndConquer] stumble through various parts of the game
without benefit of some of the game's provided data.
  
Actual results:
White boxes

Expected results:
Properly displayed graphics

Additional info:
  This bug may be affecting some elements' display in Adanaxis, as well, but I
can't say for sure as I haven't tried that game on the NVidia box yet.

Comment 1 Chris Schembari 2008-05-20 00:25:37 UTC
Created attachment 306036 [details]
Output from "glxinfo -i -l -t -v"

Comment 2 Chris Schembari 2008-05-20 00:28:17 UTC
Created attachment 306037 [details]
Composite of four screenshots from blobAndConquer 0.91, on my VIA box.

Comment 3 Bug Zapper 2008-06-17 03:08:20 UTC
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.


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