[gst-devel] change behaviour of gst-regiser

Bastien Nocera hadess at hadess.net
Fri Aug 29 00:38:05 CEST 2003

On Tue, 2003-07-08 at 07:35, Ronald Bultje wrote:
> Hey Bastien,
> On Tue, 2003-07-08 at 00:40, Bastien Nocera wrote:
> > I still don't understand why applications can't run construct the
> > plugins database like gst-register does when starting up.
> > That should probably be run automatically from gst_init().
> > 
> > Having an app segfault just because you added a plugin by hand and
> > didn't run gst-register surely isn't the right way to do it.
> That's what happens since 0.6.1 or so, IIRC - I committed a fix for that
> in 0.6.x to make it not segfault but generate the registry instead if it
> was missing. If you're still having troubles here, please let us know.
> It might not do this for registry updates, which is probably the same
> fix.
> And yeah, I do agree. ;).

This hasn't been fixed, even in 0.6.3...
$ ./sound-juicer
INFO (12535: 0) Initializing GStreamer Core Library version 0.6.3
INFO (12535: 0) CPU features: (00000000) MMX SSE
(sound-juicer:12535): GStreamer-WARNING **: No default scheduler name -
do you have a registry ?
(sound-juicer:12535): GStreamer-CRITICAL **: file gstscheduler.c: line
874 (gst_scheduler_factory_find): assertion `name != NULL' failed
GStreamer-ERROR **: Critical error: could not get scheduler "(null)"
Are you sure you have a registry ?
Run gst-register as root if you haven't done so yet.

That's bad...

Bastien Nocera <hadess at hadess.net> 
McMurphy fell 12 stories, hitting the pavement like a paper bag filled
with vegetable soup. 

More information about the gstreamer-devel mailing list