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 376062 - critical warnings when rebuilding the registry
critical warnings when rebuilding the registry
Status: RESOLVED INVALID
Product: GStreamer
Classification: Platform
Component: dont know
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-16 19:09 UTC by Christian Persch
Modified: 2006-11-18 16:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Persch 2006-11-16 19:09:01 UTC 
(gstreamer/gst-plugins-*/gst-ffmpeg uptodate from cvs)

After removing the registry, I get the following error when starting totem/gst:

$ rm -f ~/.gstreamer-0.10/registry*
$ totem

(<unknown>:7247): GLib-GObject-WARNING **: cannot register existing type `GstMultiFileSink'

(<unknown>:7247): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(<unknown>:7247): GStreamer-CRITICAL **: gst_element_register: assertion `g_type_is_a (type, GST_TYPE_ELEMENT)' failed


Starting totem afterwards doesn't show the warnings again.
Comment 1 Tim-Philipp Müller 2006-11-16 22:29:49 UTC 
That's because the multifilesink plugin has been moved/renamed in -bad CVS and become the multifile plugin. This means that the GStreamer plugins dir now has both the old and the new .so around and the type is registered twice (I assume you didn't do 'sudo make uninstall' before cvs updating, since no one ever does that ...).

You'll have to either

  sudo rm $prefix/lib/gstreamer-0.10/libgstmultifilesink.*

and/or (if you're running uninstalled)

  rm -rf gst-plugins-bad/gst/multifilesink/.*
  rm gst-plugins-bad/gst/multifilesink/*gst*
  rm gst-plugins-bad/gst/multifilesink/Makefile*

to manually to remove the old instance.
Comment 2 Christian Persch 2006-11-17 11:54:46 UTC 
Thanks, that fixed it.

(I'm using jhbuild which doesn't do make uninstall.)

I guess this bug is INVALID.