Bug 638159

Summary: gstreamer-properties xvideo test fails
Product: [Fedora] Fedora Reporter: tiredman
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: airlied, ajax, bskeggs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-29 01:05:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Xorg.0.log
none
smolt profile
none
dmesg output none

Description tiredman 2010-09-28 12:12:43 UTC 
Description of problem:
test fails with alert "X Window System (X11/XShm/Xv): Could not initialise Xv output"


Version-Release number of selected component (if applicable):
Test Day:2010-09-28 Nouveau x86_64 live cd


How reproducible:


Steps to Reproduce:
1. run gstreamer-properties
2. set default output plugin to "X Window System (X11/XShm/Xv)
3. click test
  
Actual results:
An alert appears with message "X Window System (X11/XShm/Xv): Could not initialise Xv output" and the following message appear in the terminal "gstreamer-properties-Message: Error running pipeline 'X Window System (X11/XShm/Xv)': Could not initialise Xv output [xvimagesink.c(1433): gst_xvimagesink_get_xv_support (): /GstPipeline:pipeline2/GstXvImageSink:xvimagesink3:
No port available]"



Expected results:
video plays

Additional info:
Comment 1 tiredman 2010-09-28 12:15:37 UTC 
Created attachment 450160 [details]
Xorg.0.log
Comment 2 tiredman 2010-09-28 12:18:20 UTC 
Created attachment 450162 [details]
smolt profile
Comment 3 tiredman 2010-09-28 12:19:47 UTC 
Created attachment 450164 [details]
dmesg output
Comment 4 Ben Skeggs 2010-09-29 01:05:07 UTC 

*** This bug has been marked as a duplicate of bug 638174 ***