Red Hat Bugzilla – Bug 427450
ATI/Radeon: XVideo output filled with topmost pixel row of image
Last modified: 2009-01-09 02:34:24 EST
Description of problem:
Programs that use XVideo (mplayer, totem) and attempt to show a movie only
display a "striped" image. This image is actually composed of the topmost pixel
row repeated over and over to fill the entire output rectangle.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start totem or mplayer, with output set to XVideo
2. Start playback of movie (example output is 640x480)
Striped image appears.
Normal video image should appear.
Somehow, the test application gstreamer-properties fails to trigger this bug.
Maybe it is related to the image size.
When running lspci -v, the following is displayed for the video card:
01:05.0 VGA compatible controller: ATI Technologies Inc RC410 [Radeon Xpress
200] (prog-if 00 [VGA])
Subsystem: Intel Corporation Unknown device d600
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 21
Memory at d8000000 (32-bit, prefetchable) [size=128M]
I/O ports at ee00 [size=256]
Memory at fdef0000 (32-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at fde00000 [disabled] [size=128K]
Capabilities: <access denied>
Problem still persists with xf86-video-ati from latest git (up to commit
Bug is already being tracked at freedesktop bugzilla in
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.
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Created attachment 294573 [details]
Configuration file used for Xorg
This is the configuration file used for the first test.
Created attachment 294574 [details]
Log file with configuration file
Log file resulting from using above configuration. Bug still persists with
current git at 2008/02/11
Created attachment 294575 [details]
Log file for X server with autodetection
This is the log file when no configuration file is present. Bug still persists.
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. 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 '8'.
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 8'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 8 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 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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.