Bug 992

Woops, this is fixed by gstreamer-plugins-bad-0.10.17, for which I have prepared an update 2 weeks ago, but somehow forgot to build it.

I've build it now. Knurd, can you push this directly to updates stable please?

This isn't fixed by the update.

The LADSPA plugins in -good shouldn't have been enabled, it's dead code that contains an object that's already available in libgstsignalprocessor-0.10.so (in -bad).

Instead the LADSPA plugin should be enabled in -bad.

I'm fixing the -good packages now

Hi,

Hmm, the new -bad fixed totem and rythmbox not starting for me. Anyways, so you want me to enable the ladspa-plugins in -bad (until we can get parts of -bad into Fedora) ?

Should I push this directly to stable updates, or to -testing first ?

Regards,

Hans

The error is this:

(plugin-scanner:6099): GLib-GObject-WARNING **: cannot register existing type `GstSignalProcessor'

(plugin-scanner:6099): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

(plugin-scanner:6099): GLib-GObject-CRITICAL **: g_type_register_static: assertion `parent_type > 0' failed

(plugin-scanner:6099): GStreamer-CRITICAL **: gst_element_register: assertion `g_type_is_a (type, GST_TYPE_ELEMENT)' failed

and a failure to start up.

This is caused by both the LADSPA plugin in -good, and libgstsignalprocessor including a GstSignalProcessor object. The LADSPA plugins in good are removed (as they shouldn't have been built in the first place), and the package on its way to stable.

Which means that -bad should include the LADSPA plugins (which are updated and bug fixed to a certain extent).

I'm pushing the -good package to stable directly. The -bad package can probably go through testing, as it only re-adds plugins. Why wasn't this caught before?

(In reply to comment #5)
> I'm pushing the -good package to stable directly. The -bad package can probably
> go through testing, as it only re-adds plugins. Why wasn't this caught before?
> 

It was caught before, but as said it no longer seems to happen with bad 0.10.17,
with 0.10.16 I was hitting this and I was about to do an updated 0.10.16 release which removed the libgstlv2.so plugin (which drags in libgstsignalprocessor-0.10.so.0 and thus was triggering the problem), when 0.10.17 got released.

And for some magical reason (I did not know the ladspa plugins in -good where
the real problem), 0.10.17 works fine even with libgstlv2.so packaged up, at least on my test system, so I assumed that the cause lay in -bad and was fixed by .17 .

After that I got hit by a brick wall of work and somehow forgot to actually build the 0.10.17 (which was 100% ready to tag and build at that time), for which I'm sorry.

Updated packages with the LADSPA plugins enabled are building for devel and F-12, and should show up in the updates repo when an admin gets around to pushing them, closing.

(In reply to comment #7)
> Updated packages with the LADSPA plugins enabled are building for devel and
> F-12, and should show up in the updates repo when an admin gets around to
> pushing them, closing.

But I guess I should not push them to any rpmfusion-updates or -testing before the new -good package hits fedora-updates, as there will be file conflicts otherwise?

Forget that -- seem the push that sends gstreamer-plugins-good-0.10.17-3.fc12 to fedora-updates is allready in progress, so it'll land there soon anyway

*** Bug 1002 has been marked as a duplicate of this bug. ***

*** Bug 998 has been marked as a duplicate of this bug. ***

I reopen this bug because it is still not fixed in Fedora 12.

For Fedora Rawhide there is a package gstreamer-plugins-bad-0.10.17-3.fc13, but for Fedora 12 there is still only the broken gstreamer-plugins-bad-0.10.17-2.fc12 available (nor in updates-testing).

(In reply to comment #12)
> I reopen this bug because it is still not fixed in Fedora 12.
> 
> For Fedora Rawhide there is a package gstreamer-plugins-bad-0.10.17-3.fc13, but
> for Fedora 12 there is still only the broken
> gstreamer-plugins-bad-0.10.17-2.fc12 available (nor in updates-testing).
> 

??

0.10.17-2 has the ladspa plugins enabled, the only thing new in gstreamer-plugins-bad-0.10.17-3, is that the muscbrainz / trm plugin was disabled as the musicbrainz servers are being discontinued. See bug 1001.

Oh I'm really sorry. In your comment #1 of bug #1002 I was reading 'gstreamer-plugins-bad' while you have written 'gstreamer-plugins-good'. I have installed all the updates and everythings seems to work fine. Confirming fix, thanks.