GNOME Bugzilla – Bug 345068
gst-inspect initial run
Last modified: 2006-06-16 08:04:33 UTC
due to our recent switch of buildsystem, we ran into a curious problem with building packages depending on gstreamer. The would all fail to configure, not finding the playbin plugin. The reason is that our new buildsystem is always populating fresh build roots, and apparently, the very first run of gst-inspect on a fresh gstreamer installation fails to find any plugins. As a workaround, I had to run gst-inspect --print-all before configure.
This should be fixed in core CVS with these two commits: 2006-06-13 Tim-Philipp Müller <tim at centricular dot net> * gst/gst.c: (scan_and_update_registry), (init_post): If the fork()'ed child process can't write the updated registry cache file to disk for some reason, make it exit with a failure exit code, so that the parent can then re-scan the plugins itself and update the registry structures in memory and work with that (rather than failing when creating elements because seemingly no plugins are available). Refactor registry scanning code into separate function for this and also separate fork() and non-fork() code paths. Fixes #344748. 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'). *** This bug has been marked as a duplicate of 344748 ***