ges-launch-1.0 seg faults when loading and saving a blank project
I have a blank GES project, template.xges, which I would like to edit (add clips, etc). But I can't get started -- it segfaults:
$ ges-launch-1.0 --load template.xges --save-only test.xges (ges-launch-1.0:6794): GStreamer-WARNING **: 12:25:22.736: gst_value_deserialize_g_value_array: unimplemented [repeated many times] sys:1: Warning: g_source_remove: assertion 'tag > 0' failed sys:1: Warning: invalid unclassed pointer in cast to 'GstPipeline' sys:1: Warning: invalid unclassed pointer in cast to 'GObject' sys:1: Warning: g_object_set_data: assertion 'G_IS_OBJECT (object)' failed (ges-launch-1.0:6794): GES-CRITICAL **: 12:25:22.747: ges_pipeline_set_mode: assertion 'GES_IS_PIPELINE (pipeline)' failed sys:1: Warning: invalid unclassed pointer in cast to 'GstElement' (ges-launch-1.0:6794): GStreamer-CRITICAL **: 12:25:22.747: gst_element_set_state: assertion 'GST_IS_ELEMENT (element)' failed (ges-launch-1.0:6794): GES-ERROR **: 12:25:22.747: Failed to start the pipeline Trace/breakpoint trap (core dumped)
I get the same behaviour, including seg fault, if I add in clips, e.g.
ges-launch-1.0 --load template.xges +clip test.mkv --save-only test.xges
On the other hand if I make a project from scratch, e.g.
ges-launch-1.0 +clip test.mkv --save-only test.xges ges-launch-1.0 --load test.xges --save-only test2.xges
then the first command succeeds, and the second command hangs, without seg faulting this time.