Red Hat Bugzilla – Bug 493113
Could not initialise Xv output
Last modified: 2009-11-08 18:27:46 EST
Description of problem:
ran gstreamer-properties, set video output to X11/XShm/Xv.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.set video output to X11/XShm/Xv
X Window System (X11/XShm/Xv): Could not initialise Xv output
gstreamer-properties-Message: Error running pipeline 'X Window System (X11/XShm/Xv)': Could not initialise Xv output [xvimagesink.c(1352): gst_xvimagesink_get_xv_support (): /GstPipeline:pipeline0/GstXvImageSink:xvimagesink3:
No port available]
Also getting this on ATI Technologies Inc RV610 [Radeon HD 2400 XT] [1002:94c1] :
Same problem on ATI Technologies Inc M76 [Radeon Mobility HD 2600 Series] [1002:9581]
Using radeon test day live usb.
same with Radeon HD 3200 on test day live usb:
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 log file (/var/log/Xorg.*.log) and the output of "dmesg" to the bug report as individual *uncompressed, text/plain* 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.
Thank you in advance.
Fedora Bugzappers volunteer triage team
Created attachment 337675 [details]
xorg log for M76
Created attachment 337676 [details]
dmesg for M76
You can't have KMS and Xv at the same time yet as the code to join the dots isn't written yet.
if this is a pre-r600 card, try the latest xorg-x11-drv-ati from koji which shuold fix it.
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:
I got a similar message when doing the XVideo test for radeon test day.
gstreamer-properties-Message: Error running pipeline 'X Window System (X11/XShm/Xv)': Could not initialise Xv output [xvimagesink.c(1412): gst_xvimagesink_get_xv_support (): /GstPipeline:pipeline0/GstXvImageSink:xvimagesink2:No port available]
playback in totem was fine except for some video corruption when parts of the video is by another window (always on top ticked) while moving around the totem window. The video was also a little jerky while moving around.
While repeating this test for the fast user switch test, I get this in the terminal while playback:
The video output is in use by another application. Please close other video applications, or select another video output in the Multimedia Systems Selector
** Message: Error: Could not initialise Xv output
xvimagesink.c(1412): gst_xvimagesink_get_xv_support (): /GstGConfVideoSink:video-sink/GstBin:bin0/GstXvImageSink:xvimagesink0:
No port available
My hardware is ATI Radeon HD4870
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.]
I can no longer reproduce this on either fc11 or fc12.
Thank you for letting us know.