[gstreamer-bugs] [Bug 340338] [v4l2src] crashes with tuner interface in gst-python if device not open yet

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=340338

  GStreamer | gst-plugins-base | Ver: HEAD CVS

Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |t.i.m at zen.co.uk
             Status|NEW                         |RESOLVED
          Component|gst-plugins-good            |gst-plugins-base
         Resolution|                            |FIXED
            Summary|[v4l2src] Doesn't implement |[v4l2src] crashes with tuner
                   |GstImplementsInterface      |interface in gst-python if
                   |properly                    |device not open yet
   Target Milestone|HEAD                        |0.10.11




------- Comment #19 from Tim-Philipp Müller  2007-11-13 22:05 UTC -------
As far as I can see, this has been fixed ages ago, in gst-plugins-base 0.10.11
(feisty shipped 0.10.12), by this commit:

 2006-10-17  Tim-Philipp Müller  <tim at centricular dot net>

        * gst-libs/gst/interfaces/tuner.c: (gst_tuner_list_channels),
        (gst_tuner_set_channel), (gst_tuner_get_channel),
        (gst_tuner_list_norms), (gst_tuner_set_norm), (gst_tuner_get_norm),
        (gst_tuner_set_frequency), (gst_tuner_get_frequency),
        (gst_tuner_signal_strength), (gst_tuner_find_norm_by_name),
        (gst_tuner_find_channel_by_name):
          Fix some function guards, add some more function guards.

The way I read the comments so far:
 - the bug happens with edgy (shipping core/base 0.10.10)
 - the bug report has confirmed it does not happen any longer
   with feisty (shipping core/base 0.10.12) (or rather: you
   only get those assertion failures, which is what is expected
   here given the wrong state; same as with the C API in any case)
 - no one claims they can reproduce the bug with anything > -base 0.10.11

If I'm missing something, please re-open (or preferably file a new bug).


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=340338.