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 136296 - Gstreamer plugin/mime issues
Gstreamer plugin/mime issues
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: dont know
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-03-05 16:15 UTC by Tim Vismor
Modified: 2005-06-30 15:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Attachments
Console log of gstreamer errors during rhythmbox crash (7.05 KB, text/plain)
2004-03-05 16:18 UTC, Tim Vismor
Details

Description Tim Vismor 2004-03-05 16:15:53 UTC
Since the Gnome switch over to the new mime-type system (based on
freedesktop.org's shared-mime-info), rhythmbox has crashed every time I try
to listen to internet radio. I'm not sure if this is a rhythmbox or
gstreamer issue; however, the rhythmbox people seem to think it is a
gstreamer problem (see bug 135069).
 
I am running Gnome 2.5.x built from CVS HEAD using jhbuild on 3/4/04.
Gstreamer, gst-plugins, and rhythmbox were also built from CVS at that time.

I have been running rhythmbox from CVS with gstreamer from CVS since late
October 2003. Everything worked relatively smoothly until this problem
occurred.

The only debug info I have is the console log of a session in which
rhythmbox died. It is atttached. You can see there appear to be numerous
issues with mime types.
Comment 1 Tim Vismor 2004-03-05 16:18:34 UTC
Created attachment 25218 [details]
Console log of gstreamer errors during rhythmbox crash
Comment 2 Benjamin Otte (Company) 2004-03-05 22:06:40 UTC
that sounds a lot like you need to run gst-register.
Comment 3 Tim Vismor 2004-03-05 23:25:50 UTC
I re-registered the plugins per Benjamin's suggestion, then ran
rhythmbox. It displayed an error message about no mime type to handle
"video/x-theora" when I tried to listen to the radio. I then restarted
rhythmbox and there have been no subsequent problems.

The console log for the aberant seesion follows:

[tdv@redbud tdv]$ rhythmbox
ERROR          spider( 7381)
gstspider.c(419):gst_spider_identity_plug:<decoder>  There is no
element present to handle the stream's mime type video/x-theora.
ERROR          spider( 7381)
gstspider.c(419):gst_spider_identity_plug:<decoder>  (null)
ERROR       scheduler( 7381)
gstoptimalscheduler.c(2075):gst_opt_scheduler_iterate:<GstOptScheduler@0x90fe050>
in error state

Since I am listening to the radio as I type this reply, I guess the
problem is resolved.

Note: I have re-registered my plugins many times over the last few
weeks after rebuilding the gstreamer software; however, upon getting
the video/x-theora mime-type error I would just give up (assuming a
problem was still present). This is the first time I actually
restarted rhytmbox after the mime-type error.
Comment 4 David Schleef 2004-03-06 00:43:51 UTC
Ok, I added fixate functions to GstPlay at appropriate places.  I
didn't add pad_renegotiate()s, since I'm not entirely sure when the
best time to call it is.  This should clear up some problems.
Comment 5 David Schleef 2004-03-09 01:25:20 UTC
Ignore that comment, it was meant for a different bug.
Comment 6 Thomas Vander Stichele 2004-10-27 09:23:59 UTC
who closed and fixed this bug ? I don't see any comment detailing this resolution...

I'm reopening for lack of info.
Comment 7 Tim Vismor 2004-10-27 19:45:36 UTC
I closed this bug. When the report was submitted, I was tracking gnome CVS
locally. I assumed that the problem was due to the transition in mime type
processing that was occurring in gnome CVS sources at the time. When the problem
went away, I assumed updates to some component in the CVS repository had fixed
the bug. 

I have not seen this problem for several months. I just ran rhythmbox from the
terminal, no errors were displayed. I am currently running FC3-RC2.

Feel free to proceed as you see fit.
Comment 8 Stephane Loeuillet 2004-12-17 10:19:38 UTC
so, could be close guys at this seems fixed ?
Comment 9 Stephane Loeuillet 2004-12-18 23:45:15 UTC
closing as it seems it is no more an issue