After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 144349 - totem-gstreamer-0.99.12 won't load on FC2
totem-gstreamer-0.99.12 won't load on FC2
Status: RESOLVED INVALID
Product: GStreamer
Classification: Platform
Component: gst-plugins
0.8.1
Other Linux
: Urgent major
: NONE
Assigned To: Julien MOUTTE
GStreamer Maintainers
: 140905 143496 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-06-14 15:40 UTC by Darren
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Darren 2004-06-14 15:40:14 UTC
Start with a stock Fedora Core 2 desktop install. Install the following:

rpm -ivh xvidcore-1.0.1-1.1.fc2.fr.i386.rpm
rpm -ivh aalib-1.4.0-5.1.fc2.fr.i386.rpm
rpm -ivh libdvdcss-1.2.8-4.1.fc2.fr.i386.rpm
rpm -ivh libfame-0.9.1-1.1.fc2.fr.i386.rpm
rpm -ivh freeglut-2.2.0-0.11.fr.i386.rpm
rpm -ivh xine-lib-1.0.0-0.13.rc4a.1.fc2.fr.i386.rpm
rpm -ivh lirc-0.6.6-2.1.fc2.fr.i386.rpm
rpm -ivh totem-0.99.12-1.1.fc2.fr.i386.rpm
rpm -ivh totem-gstreamer-0.99.12-1.1.fc2.fr.i386.rpm

Now try to launch totem and watch it die with the following error.

** (totem:3577): WARNING **: libgstplay: failed initializing pipeline, error:
Could not link video output thread (cs and balance)

I'm adding this bug here as Hadess thinks this is a gstreamer issue not a totem
issue. Here is a link to the totem bug tracking this issue...
http://bugzilla.gnome.org/show_bug.cgi?id=143496
Comment 1 Ronald Bultje 2004-06-14 15:54:10 UTC
I think you need to install gstreamer-gconf and restart gconfd after that.
Comment 2 Bastien Nocera 2004-06-14 18:31:43 UTC
*** Bug 143496 has been marked as a duplicate of this bug. ***
Comment 3 Darren 2004-06-14 18:55:38 UTC
Thanks for the tip Ronald, unfortunately it didn't seem to help. I couldn't find
any source or binary rpms from the gstreamer.net web site so I grabed
gstreamer-GConf-0.8.1-3.1.fc2.nr.i386.rpm from
http://people.ecsc.co.uk/~matt/downloads/rpms/gstreamer/0.8.1/RPMS/?C=S;O=A
But I'm still getting the exact same error... I was a bit surprised that I had
to use --force to install the rpm since there was a gstreamer-plugins shared
library that conflicted I also rebooted just for good restart measure. Did I
just get a bad rpm or is the problem really something else?
Comment 4 Ronald Bultje 2004-06-14 20:57:12 UTC
Did it actually install the schemas? Is there something in
/system/gstreamer/0.8/default/* (try using gconf-editor)?
Comment 5 Balamurali Viswanathan 2004-06-16 11:35:46 UTC
I have gstreamer schemas installed
(/etc/gconf/gconf.xml.defaults/system/gstreamer/0.8/default/%gconf.xml is
present). But still I see this problem. 
Comment 6 Ronald Bultje 2004-06-16 15:55:56 UTC
Thanks, that helps... I'll try to see why FC2 gets this, will take me a few days
to setup a proper FC2 box, though.
Comment 7 Darren 2004-06-28 03:15:24 UTC
For what it's worth this issue doesn't seem to be totem specific. I installed
gst-player
rpm -ivh gstreamer-player-0.8.0-0.fdr.1.2.i386.rpm

and I get the exact same error when trying to launch gst-player...
** (gst-player:3687): WARNING **: libgstplay: failed initializing pipeline,
error: Could not link video output thread (cs and balance)

I'll bet that if we can figure out why gst-player doesn't work on Fedora Core 2
then we will also solve the totem player issue as well...
Comment 8 Thomas Vander Stichele 2004-07-06 11:33:51 UTC
darren, do you have gst-ffmpeg installed ?

what does gst-inspect ffcolorspace say ?
Comment 9 Darren 2004-07-06 18:52:35 UTC
Thanks Thomas! That seemed to be the missing piece. I did not have it installed
but a 
yum install gstreamer-ffmpeg
installed gstreamer-ffmpeg 0.8.0-0.lvn.2.2.i386 which took care of the
totem/gst-player not loading problem I was having. I can now play ogg files
successfully in both totem and gst-player so the basics seem to be working now.
I consider this issue solved for my needs now so I will work work on getting
video next. I tried a .avi file and an .mpg file and got sound but no video in
both cases. But I play to upgrade all my gstreamer components from Fedora Core 2
basic level to the latest release from gstreamer.net and then trying again.

Thanks again for all the help on this issue everyone.
Comment 10 Balamurali Viswanathan 2004-07-09 05:50:57 UTC
I compiled and installed gst-plugins-0.8.1/gst/ffmpegcolorspace, And then did a
gst-regsiter-0.8 and I was able to launch totem and I was able to play ogg files. 

When I tried to play a .mpg file, the status bar says "Paused 0:00/0:00". When I
repeatedly click on the Play/Pause button I get the following error message

(totem:5381): GStreamer-WARNING **: element work_thread claimed state-change
success,but state didn't change to PLAYING. State is PAUSED (NONE_PENDING
pending), fix the element
Comment 11 Ronald Bultje 2004-07-09 14:14:12 UTC
opt/mpeg don't like each other, try --gst-scheduler=basicgthread for now, we're
working on a real fix.
Comment 12 Thomas Vander Stichele 2004-07-16 10:07:36 UTC
and please don't add new bugs to the initial bug.

this is still a bug somewhere, the ffmpegcolorspace element from gst-plugins
should be preferred/looked for, keeping this open.
Comment 13 Darren 2004-08-30 05:50:37 UTC
One more update, I installed Fedora core II on a brand new machine and verified
again that gstreamer-ffmpeg is indeed the only rpm required for a successful
gst-player rpm installation. Is it the gst-player rpm that should require ffmpeg
or should it be required by plugins or plugins extra? Which spec file needs this
patch?
Comment 14 Ronald Bultje 2004-08-30 06:55:47 UTC
None. Like Thomas said, gst-player depends on the ffcolorspace element, whereas
it should use the ffmpegcolorspace element (which is in gst-plugins).
Comment 15 Bastien Nocera 2004-09-21 14:38:54 UTC
*** Bug 140905 has been marked as a duplicate of this bug. ***
Comment 16 Ronald Bultje 2004-12-03 23:07:33 UTC
This bug no longer applies, since the totem backend was rewritten.