[gstreamer-bugs] [Bug 345068] gst-inspect initial run

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=345068
 GStreamer | gst-plugins | Ver: 0.10.8


Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE
   Target Milestone|HEAD                        |NONE




------- Comment #1 from Tim-Philipp Müller  2006-06-16 08:04 UTC -------
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 ***


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.