Bug 9966 - Parole can't play videos on VirtualBox
Summary: Parole can't play videos on VirtualBox
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-03 18:05 CEST by Robert Ottlovich
Modified: 2013-05-04 16:18 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Robert Ottlovich 2013-05-03 18:05:25 CEST
Description of problem:
Parole cannot open any files because of missing gstreamer.
Gtreamer backend error, videosink doesn't work.
Totem (Videos) can open this video.

http://mypublics.files.wordpress.com/2013/04/parole-gstreamer.jpg

Sorry no available error log because of removing Mageia 3 RC from VBox.





Reproducible: 

Steps to Reproduce:
Comment 1 Jani Välimaa 2013-05-04 13:54:57 CEST
Can't reproduce this.

I'm sorry to say this, but if you (or anyone else) can't provide any further infomation about this issue, I'm going to close this as WORKSFORME.

CC: (none) => jani.valimaa

Comment 2 Jani Välimaa 2013-05-04 16:18:42 CEST
Tried previously only on a real HW and now tried also with VirtualBox.

Seems VirtualBox's video driver doesn't support XVideo (xv) and parole tries to use xv output by default (unless user have disabled it). This causes your issue and it's only reproducible with video drivers not suppporting XVideo. Cmd 'xvinfo' from pkg xvinfo tells if XVideo is supported.

Users can disable XVideo support in parole with cmd 'parole --xv false' and enable it again with 'parole --xv --true'. Those cmd's needs to be used only once. After disabling XVideo, videos should work.

This isn't really a bug in parole or pkg'ing so I'm closing this as WORKSFORME.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME
Summary: Parole cannot open any files => Parole can't play videos on VirtualBox


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