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 701420 - Segmentation fault when starting up pitivi
Segmentation fault when starting up pitivi
Status: RESOLVED INCOMPLETE
Product: pitivi
Classification: Other
Component: Build and packaging
Git
Other Linux
: Normal blocker
: 0.91
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2013-06-01 12:26 UTC by Ulrik
Modified: 2014-01-02 19:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ulrik 2013-06-01 12:26:09 UTC
Hi,

I get segmentation fault when starting up pitivi built from source using pitivi-git-environment.sh

ulrik@G74Sx:/usr/local/pitivi_installation$ MYPITIVI=/usr/local/pitivi_installation/ ./pitivi-git-environment.sh
Package gstreamer-1.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gstreamer-1.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gstreamer-1.0' found
Package gstreamer-1.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gstreamer-1.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gstreamer-1.0' found
Using a local build of GStreamer 1.0
[ptv] ulrik@G74Sx:/usr/local/pitivi_installation/pitivi$ pitivi
Segmentation fault (core dumped)

It happens each time I try to start pitivi. The back trace from the core dump contains:

  • #0 gst_value_serialize
    at gstvalue.c line 4931
  • #1 _set_value
    at ges-meta-container.c line 183
  • #2 ges_meta_container_register_meta_string
    at ges-meta-container.c line 623
  • #3 _register_metas
    at ges-formatter.c line 85
  • #4 ges_extractable_register_metas
    at ges-extractable.c line 285
  • #5 object_set_property
    at gobject.c line 1357
  • #6 g_object_constructor
    at gobject.c line 1868
  • #7 g_object_newv
    at gobject.c line 1718
  • #8 g_object_new_valist
    at gobject.c line 1835
  • #9 g_initable_new_valist
    at ginitable.c line 224
  • #10 g_initable_new
    at ginitable.c line 148
  • #11 ges_asset_request
    at ges-asset.c line 767
  • #12 _list_formatters
    at ges-formatter.c line 448
  • #13 _init_formatter_assets
    at ges-formatter.c line 460
  • #14 ges_asset_cache_init
    at ges-asset.c line 568
  • #15 ges_init
    at ges.c line 90
  • #16 ffi_call_unix64
    from /usr/lib/x86_64-linux-gnu/libffi.so.6
  • #17 ffi_call
    from /usr/lib/x86_64-linux-gnu/libffi.so.6
  • #18 g_callable_info_invoke
    at girepository/gicallableinfo.c line 680
  • #19 g_function_info_invoke
    at girepository/gifunctioninfo.c line 274
  • #20 _invoke_callable
    at pygi-invoke.c line 64
  • #21 pygi_callable_info_invoke
    at pygi-invoke.c line 662
  • #22 PyEval_EvalFrameEx
  • #23 PyEval_EvalCodeEx
  • #24 PyEval_EvalFrameEx
  • #25 PyEval_EvalCodeEx
  • #26 PyImport_ExecCodeModuleEx
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 PyEval_EvalFrameEx
  • #33 PyEval_EvalCodeEx
  • #34 PyEval_EvalFrameEx
  • #35 PyEval_EvalCodeEx
  • #36 ??
  • #37 PyObject_Call
  • #38 ??
  • #39 PyObject_Call
  • #40 PyObject_CallMethod
  • #41 ??
  • #42 ??
  • #43 ??
  • #44 ??
  • #45 PyEval_EvalFrameEx
  • #46 PyEval_EvalFrameEx
  • #47 PyEval_EvalFrameEx
  • #48 PyEval_EvalFrameEx
  • #49 PyEval_EvalFrameEx
  • #50 PyEval_EvalCodeEx
  • #51 PyRun_FileExFlags
  • #52 PyRun_SimpleFileExFlags
  • #53 Py_Main
  • #54 __libc_start_main
    at libc-start.c line 226
  • #55 _start


Cheers,
Ulrik
Comment 1 Jean-François Fortin Tam 2013-06-02 14:58:16 UTC
Interesting, you installed the whole thing systemwide/into usr local? I haven't tried that yet... I suppose it doesn't work simply uninstalled, running from the checked out copy?

What distro release is this?
Comment 2 Ulrik 2013-06-02 16:00:45 UTC
I'm running Ubuntu 12.04 with an old GStreamer version (0.10.36), so I tried the command:

   MYPITIVI=/usr/local/pitivi_installation ./pitivi-git-environment.sh --build

It cloned and compiled everything (pitivi, gstreamer, gst, glib, ...) just fine, after I installed some required ubuntu packages such as libffi-dev, python-cairo-dev and libxml2-dev.

Then I also installed the ubuntu package gir1.2-clutter-1.0 to avoid a runtime error message about 'Clutter', that did not appear during the build phase, but was printed when I tried to start pitivi.

I have not actually installed anything build by pitivi-git-environment.sh into /usr/local/bin, /usr/local/lib, etc, or anything like that. I just choosed /usr/local/pitivi_installation as the build directory instead of ~/pitivi-git. 

Then I get the segmentation fault when I try to start pitivi by:
     MYPITIVI=/usr/local/pitivi_installation ./pitivi-git-environment.sh
     pitiv

If I try to start pitiv, without first executing pitivi-git-environment.sh, I get this error message:

['/usr/local/pitivi_installation/gst-editing-services/bindings/python/gi/overrides', '/usr/local/pitivi_installation/gst-python/gi/overrides', '/usr/local/pitivi_installation/pygobject/gi/overrides', '/usr/lib/python2.7/dist-packages/gi/overrides'] gi.overrides
Traceback (most recent call last):
  • File "./pitivi", line 139 in <module>
    _check_dependencies()
  • File "./pitivi", line 97 in _check_dependencies
    missing_hard_deps = check_hard_dependencies()
  • File "/usr/local/pitivi_installation/pitivi/pitivi/check.py", line 181 in check_hard_dependencies
    from gi.repository import Gst
  • File "/usr/local/pitivi_installation/pygobject/gi/repository/__init__.py", line 25 in <module>
    from ..importer import DynamicImporter
  • File "/usr/local/pitivi_installation/pygobject/gi/importer.py", line 28 in <module>
    from .module import DynamicModule
  • File "/usr/local/pitivi_installation/pygobject/gi/module.py", line 37 in <module>
    from .overrides import registry
ImportError: cannot import name registry

Comment 3 Ulrik 2013-06-08 09:25:31 UTC
Changing from NEEDINFO to UNCONFIRMED since I have provided more info. Do you need any more information?
Comment 4 Thibault Saunier 2013-06-08 17:45:23 UTC
It sounds like Gst has not been properly initialized to me. It is pretty weird and do not get how it was no catched before.

Can you check that Gst is initialized please?
Comment 5 Jean-François Fortin Tam 2013-09-30 15:11:59 UTC
Hi there,

As Pitivi 0.91 has now been released, we would like to encourage you to test it.

It is quite possible that your issue is fixed in this version,
as it is a very significant technical overhaul compared to the 0.15 series.
Read more about the 0.91 release here: http://wiki.pitivi.org/wiki/0.91

If you can reproduce this bug against 0.91 or newer (such as the git version),
please update this bug report accordingly with detailed instructions to
reproduce the bug, updated sample files/projects in xges format, etc.

Drop by our IRC channel if you need help getting started or want to help out!

Thanks!
Comment 6 fabien 2013-12-08 22:20:41 UTC
Hi.
I have the same problem.

I have tested with : 
_ the debian packages (0.91 and 0.92 versions )
_ the source package 0.92
_ the master branch of git project (now 8/12/2013)

The only console output is a message : "segmentation fault"

After analyze, the SEGFAULT occurs when executing the function
 def _try_import_from_gi(modulename): (line 75) of file pitivi/check.py


My computer is on debian testing and up-to-date. Suggested package for 0.92 version are installed and version 0.15 works fine.

Cheers,
Fabien
Comment 7 Jean-François Fortin Tam 2013-12-12 20:40:50 UTC
Well if it segfaults just trying to import a module (you'd need to specify which one it is), not cool... but for developers to find out what's going on you need to provide a backtrace at least. Take a look at 

https://wiki.gnome.org/GettingInTouch/Bugzilla/GettingTraces
and
http://wiki.pitivi.org/wiki/Bug_reporting#Stack_traces_for_crashes
Comment 8 fabien 2014-01-02 18:47:23 UTC
Some new of bugs.
 As https://bugzilla.gnome.org/show_bug.cgi?id=721068 , the segmentation fault disappear with a recent update of Debian. Pitivi working well now.
Comment 9 Jean-François Fortin Tam 2014-01-02 19:22:59 UTC
Closing this bug report as no further information has been provided and the similar bug that was reported turned out to be incomplete/notabug too.

Please feel free to reopen this bug if you can provide the info asked for.
Thanks!