After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 773815 - Build of GES-1.0.gir gives critical warnings
Build of GES-1.0.gir gives critical warnings
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-build
1.9.90
Other Linux
: Normal normal
: 1.11.1
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-11-02 09:09 UTC by Sebastian Dröge (slomo)
Modified: 2016-11-23 11:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastian Dröge (slomo) 2016-11-02 09:09:51 UTC
Doesn't happen with the autotools based build.


[2474/2594] 'Generating GES-1.0.gir with a custom command.'

(GES-1.0:15044): GStreamer-CRITICAL **: gst_object_unref: assertion 'object != NULL' failed

(GES-1.0:15044): GStreamer-CRITICAL **: gst_object_unref: assertion 'object != NULL' failed

(GES-1.0:15044): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(GES-1.0:15044): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

** (GES-1.0:15044): CRITICAL **: gst_discoverer_start: assertion 'GST_IS_DISCOVERER (discoverer)' failed
Comment 1 Thibault Saunier 2016-11-23 11:23:52 UTC
GES:

commit 9bc06c755ad9e640dc6d01b2a547cb8e803391f5
Author: Thibault Saunier <thibault.saunier@osg.samsung.com>
Date:   Tue Nov 15 15:09:10 2016 -0300

    ges: Check if GstDiscoverer could be created at init time
    
    And fail initialization if it is not the case, we make the assumption
    it worked all around the codebase so we should really concider it fatal.

-base:

commit 0c0dfbd45521498b8242150f35f568695ea034d1
Author: Thibault Saunier <thibault.saunier@osg.samsung.com>
Date:   Tue Nov 15 15:12:12 2016 -0300

    discoverer: Do not try to unref the bus if it has not been set yet
    
    It might happen if creation of the discoverer failed