[gstreamer-bugs] [Bug 361753] New: gst-inspect fails on first run

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Thu Oct 12 10:18:09 PDT 2006


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=361753

  GStreamer | gstreamer (core) | Ver: 0.10.8

           Summary: gst-inspect fails on first run
           Product: GStreamer
           Version: 0.10.8
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: elliot at bentlogic.net
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: 2.15/2.16
   GNOME milestone: Unspecified


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:


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email




More information about the Gstreamer-bugs mailing list