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 574272 - Python plugin loader causes SIGSEGV if "import gst" fails
Python plugin loader causes SIGSEGV if "import gst" fails
Status: RESOLVED DUPLICATE of bug 576145
Product: GStreamer
Classification: Platform
Component: gst-python
git master
Other Linux
: Normal blocker
: 0.10.15
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-05 13:56 UTC by Sebastian Dröge (slomo)
Modified: 2009-03-24 10:29 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastian Dröge (slomo) 2009-03-05 13:56:09 UTC
Hi,
the python plugin loader causes a SIGSEGV if "import gst" fails. This happens on my buildslaves as no pygst is installed in the standard Python paths.

http://pitivi.org:8010/builders/sid-good-fast/builds/238/steps/make-check/logs/stdio


gdb backtrace:

0:00:07.506876391 22090  0x80541c0 ERROR             pyplugin gstpythonplugin.c:256:pygst_require: the pygst module is not available!
ImportError: No module named pygst

Program received signal SIGSEGV, Segmentation fault.

Thread 1078937792 (LWP 22090)

  • #0 plugin_init
    at gstpythonplugin.c line 329
  • #1 gst_plugin_register_func
    at gstplugin.c line 342
  • #2 gst_plugin_load_file
    at gstplugin.c line 553
  • #3 gst_registry_scan_path_level
    at gstregistry.c line 919
  • #4 gst_registry_scan_path
    at gstregistry.c line 955
  • #5 scan_and_update_registry
    at gst.c line 695
  • #6 ensure_current_registry
    at gst.c line 787
  • #7 init_post
    at gst.c line 1108
  • #8 IA__g_option_context_parse
    at /build/buildd/glib2.0-2.18.4/glib/goption.c line 1799
  • #9 gst_init_check
    at gst.c line 432
  • #10 gst_init
    at gst.c line 479
  • #11 gst_check_init
    at gstcheck.c line 89
  • #12 main
    at elements/xingmux.c line 155

Comment 1 Edward Hervey 2009-03-24 10:29:58 UTC

*** This bug has been marked as a duplicate of 576145 ***