GNOME Bugzilla – Bug 361753
gst-inspect fails on first run
Last modified: 2006-10-12 17:36:26 UTC
Please describe the problem: When gst-inspect is run for the first time it fails with: bash-3.1# gst-inspect-0.10 decodebin No such element or plugin 'decodebin' This creates the ~/.gstreamer-0.10 directory. Running for a second time outputs the details for decodebin that are expected. If you delete the ~/.gstreamer-0.10 directory and rerun gst-inspect-0.10 decodebin you get the same error as above. Steps to reproduce: 1. run gst-inspect-0.10 decodebin without the ~/.gstreamer-0.10 directory 2. gst-inspect-0.10 outputs an error 3. Actual results: It causes my build of banshee to fail in a chrooted environment because gst-inspect has never been run before. Expected results: The directory should be created and gst-inspect-0.10 should provide the correct output. Does this happen every time? Yes, as long as there is no ~/.gstreamer-0.10 directory. Other information:
This has been fixed shortly after the 0.10.8 release: 2006-06-13 Tim-Philipp Müller <tim at centricular dot net> * gst/gstregistryxml.c: (gst_registry_xml_write_cache): Fix silly bug that prevented us from creating ~/.gstreamer-0.10 and writing the registry in one go (the first call to g_mkstemp() would overwrite the placeholder in the template string, so the second call to g_mkstemp() after creating the missing directory would then error out with 'invalid argument'). Please re-open if you can still reproduce this with GStreamer core >= 0.10.9 or CVS HEAD.