Retested with the following updates and the problem still remains:

kernel-2.6.29.3-155.fc11.x86_64
xorg-x11-drv-intel-2.7.0-6.fc11.x86_64

(In reply to comment #0)
> Description of problem:
> 
> When playing a video clip in totem, audio plays but video is blank and black.

Are you able to play with just gst-launch?

gst-launch playbin2 uri=http://www.redhat.com/v/ogg/TruthHappensRmx.ogg

if yes, try please

gst-launch -t playbin2 uri=http://www.redhat.com/v/ogg/TruthHappensRmx.ogg 2>&1 \
  |tee gst-launch-debug-log.txt

And the log file to this bug as uncompressed separate attachment.

And of course, please attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, 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.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

When I try to use gst-launch, the clip plays audio but no video.  I have no xorg.conf file.

Created attachment 345809 [details]
output from gst-launch

Created attachment 345811 [details]
output from dmesg

Created attachment 345812 [details]
Xorg log file

retested with xorg-x11-drv-intel-2.7.0-7.fc11.x86_64 and problem still happens.

Matej,

I would be glad to test the latest driver from git (snapshot 2.7.99.1 -2009-04-28) but I have some missing deps.  If you can tell me which devel packages I am needing I could give it a try.

./autogen.sh --prefix=/usr --enable-dri

checking for XORG... configure: error: Package requirements (xorg-server >= 1.6 xproto fontsproto  xineramaproto randrproto renderproto xextproto x11 xextproto) were not met:

No package 'x11' found

(In reply to comment #9)
> Matej,
> 
> I would be glad to test the latest driver from git (snapshot 2.7.99.1
> -2009-04-28) but I have some missing deps.  If you can tell me which devel
> packages I am needing I could give it a try.
> 
> ./autogen.sh --prefix=/usr --enable-dri
> 
> checking for XORG... configure: error: Package requirements (xorg-server >= 1.6
> xproto fontsproto  xineramaproto randrproto renderproto xextproto x11
> xextproto) were not met:
> 
> No package 'x11' found  

I guess the most simple way is to rebuild the Fedora package (yumdownload --src <name-of-src-package>) and then just replace tarball in SOURCES and add autogen.sh to .spec file. Advantage is that you not get build more easily build, but you will have also package.

If you try this, do you have still missing BuildRequires?

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Matej,

I haven't had time to try testing the latest driver from git yet, but I just ran into the exact problem on a older system with integrated i915 video.


(II) intel(0): Integrated Graphics Chipset: Intel(R) 915G

Bryan, what specific chipsets exactly are having this problem?  Various i945 and i965 chips here are working fine in this regard.

Here's the lspci from the Q35 (Intel GMA 3100) system:

00:02.0 "VGA compatible controller [0300]" "Intel Corporation [8086]" "82Q35 Express Integrated Graphics Controller [29b2]" -r02 "Hewlett-Packard Company [103c]" "Device [2819]"
00:02.1 "Display controller [0380]" "Intel Corporation [8086]" "82Q35 Express Integrated Graphics Controller [29b3]" -r02 "Hewlett-Packard Company [103c]" "Device [2819]"

Do you want the same from the 915G (Intel GMA 900) system?

My chipset also has this problem!

00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

*** Bug 515339 has been marked as a duplicate of this bug. ***

Retested with the latest xorg packages from updates-testing on 9/9 and issue still persists.

Created attachment 360646 [details]
tarball containing logs

My system also has this problem, i.e. Xv output cannot be
used with:

Toshiba dynabook TX 3516 (Intel® 855GME)
Tarball attached containing
- lspci -vvv
- dmesg.log
- Xorg.0.log
- boot.log

rpm using:
kernel-2.6.31-2.fc12.i686
xorg-x11-server-Xorg-1.6.99.900-1.fc12.i686
xorg-x11-drv-intel-2.8.0-13.20090909.fc12.i686
libXv-1.0.4-4.fc12.i686

*** Bug 516494 has been marked as a duplicate of this bug. ***

Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

Retested on F12 Live CD and problem still exists.

Created attachment 367750 [details]
A test clip suitable for reproducting the problem with F12 Live CD

Can confirm this problem still occurs in F12 Beta with:
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)

on 
2.6.31.5-117.fc12.i686
2.6.31.5-115.fc12.i686
2.6.31.5-96.fc12.i686
all get
(WW) intel(0): Disabling Xv because no adaptors could be initialized

think this is because Overlay Support is missing for the intel KMS driver (which hasn't yet been implemented). Patch to implement this is as
http://patchwork.kernel.org/patch/47764/
but do not think this made 2.6.32 so think this may not be in Linus's tree till 2.6.33

Think using nomodeset worked around this in F11 but at the moment using the nomodeset option in F12 beta causes X to fail to start.

New Fedora 12 install here (updated to current stable updates) with:
VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02)

xvinfo says "no adaptors present", and yet this worked in Fedora 10.
nomodeset = black screen of death.

I thought upgrades were supposed to make things work better...

Bug still present in fully updated Fedora 12. Workaround of adding 'i915.modeset=0' to the kernel command line fixes it, with the disadvantage of disabling KMS. (Guess you can't have your cake and eat it too.)

Still no Xv adapters in Fedora 12 as of 2010-01-01.
A i915.modeset=0 / nomodeset causes a hard hang of the system so it's not a viable workaround.

I'm also on a 855GME like Ian Collier above
VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02)

kernel-2.6.31.9-74.fc12.i686
xorg-x11-server-Xorg-1.7.1-7.fc12.i686
xorg-x11-drv-intel-2.9.1-1.fc12.i686
libdrm-2.4.15-8.fc12.i686
mesa-dri-drivers-7.6-0.13.fc12.i686

I have the same problem on Intel Corporation 82865G Integrated Graphics Controller (rev 02) with fully updated F12. It worked on F10.  

Excerpt from Xorg.0.log:
...
(--) PCI:*(0:0:2:0) 8086:2572:1028:0151 Intel Corporation 82865G Integrated Graphics Controller rev 2, Mem @ 0xe8000000/134217728, 0xfeb80000/524288, I/O @ 0x0000efa8/8, BIOS @ 0x????????/131072
...
(==) intel(0): Intel XvMC decoder disabled
(WW) intel(0): Disabling Xv because no adaptors could be initialized.

kernel-2.6.31.9-174.fc12.i686
xorg-x11-server-Xorg-1.7.1-7.fc12.i686
xorg-x11-drv-intel-2.9.1-1.fc12.i686
libdrm-2.4.15-8.fc12.i686
mesa-dri-drivers-7.6-0.13.fc12.i686

Just checked, and adding nomodeset to kernel allows xvideo to work again for Intel Corporation 82865G Integrated Graphics Controller (rev 02) - same software versions as above.

I think this is what I have too.
lspci shows a 82852/855GM IGP and xvinfo cannot find any adapters.

It sounds a lot like https://bugs.freedesktop.org/show_bug.cgi?id=24543 which should work with xorg-video-intel-2.10.0 and kernel 2.6.33 or a backport found here: http://gitorious.org/daniel-s-linux-stuff/linux-kernel/commits/intel-kms-overlay-for-2.6.32 (mentioned in the release announcement for the intel 2.10.0 driver, found here http://thread.gmane.org/gmane.comp.freedesktop.xorg/41865)
If you do not have this patch already, please consider porting it.

Fixed in F13 beta. No workarounds needed, works out of the box.

$ xvinfo
X-Video Extension version 2.2
screen #0
  Adaptor #0: "Intel(R) Video Overlay"
    number of ports: 1
    port base: 82
    operations supported: PutImage 
    supported visuals:
      depth 24, visualID 0x21
    number of attributes: 5
      "XV_COLORKEY" (range 0 to 16777215)
              client settable attribute
              client gettable attribute (current value is 66046)
      "XV_BRIGHTNESS" (range -128 to 127)
              client settable attribute
              client gettable attribute (current value is -19)
      "XV_CONTRAST" (range 0 to 255)
              client settable attribute
              client gettable attribute (current value is 75)
      "XV_SATURATION" (range 0 to 1023)
              client settable attribute
              client gettable attribute (current value is 146)
      "XV_PIPE" (range -1 to 1)
              client settable attribute
              client gettable attribute (current value is -1)
    maximum XvImage size: 2048 x 2048
    Number of image formats: 4
      id: 0x32595559 (YUY2)
        guid: 59555932-0000-0010-8000-00aa00389b71
        bits per pixel: 16
        number of planes: 1
        type: YUV (packed)
      id: 0x32315659 (YV12)
        guid: 59563132-0000-0010-8000-00aa00389b71
        bits per pixel: 12
        number of planes: 3
        type: YUV (planar)
      id: 0x30323449 (I420)
        guid: 49343230-0000-0010-8000-00aa00389b71
        bits per pixel: 12
        number of planes: 3
        type: YUV (planar)
      id: 0x59565955 (UYVY)
        guid: 55595659-0000-0010-8000-00aa00389b71
        bits per pixel: 16
        number of planes: 1
        type: YUV (packed)

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Any chance this will get fixed for 12?  And do we need to open a new bug to say the problem still exists in Fedora 12?

Well, I no longer use F-11 and am using F-13 on my computer
Toshiba dynabook TX 3516 (Intel® 855GME), and now Xv is working
(with F-11/12 Xv did not work)

Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.