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 550463 - importing gtk crashes on x86_64
importing gtk crashes on x86_64
Status: RESOLVED FIXED
Product: pygobject
Classification: Bindings
Component: gobject
2.13.x
Other Linux
: Immediate critical
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-02 13:46 UTC by Götz Waschk
Modified: 2008-09-04 00:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Götz Waschk 2008-09-02 13:46:36 UTC 
This is on Mandriva Cooker x86_64, i586 is not affected:
$ gdb python
GNU gdb 6.8-2mdv2009.0 (Mandriva Linux release 2009.0)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-mandriva-linux-gnu"...
(gdb) run
Starting program: /usr/bin/python 
[Thread debugging using libthread_db enabled]
Python 2.5.2 (r252:60911, Aug 25 2008, 10:52:07) 
[GCC 4.3.1 20080626 (prerelease)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
[New Thread 0x2baa99323fa0 (LWP 20938)]
>>> import gtk

Program received signal SIGSEGV, Segmentation fault.
0x00002baa9a8ebd1b in pygtk_register_classes (d=0x75d540) at gtk.c:119090
119090      pyg_register_interface(d, "CellEditable", GTK_TYPE_CELL_EDITABLE, &PyGtkCellEditable_Type);
Missing debug package(s), you should install: ncurses-debug readline-debug
(gdb) bt

+ Trace 206157

  • #0 pygtk_register_classes
    at gtk.c line 119090
  • #1 init_gtk
    at gtkmodule.c line 225
  • #2 _PyImport_LoadDynamicModule
    at Python/importdl.c line 53
  • #3 import_submodule
    at Python/import.c line 2400
  • #4 ensure_fromlist
    at Python/import.c line 2311
  • #5 import_module_level
    at Python/import.c line 2038
  • #6 PyImport_ImportModuleLevel
    at Python/import.c line 2072
  • #7 builtin___import__
    at Python/bltinmodule.c line 47
  • #8 PyObject_Call
    at Objects/abstract.c line 1861
  • #9 PyEval_CallObjectWithKeywords
    at Python/ceval.c line 3442
  • #10 PyEval_EvalFrameEx
    at Python/ceval.c line 2067
  • #11 PyEval_EvalCodeEx
    at Python/ceval.c line 2836
  • #12 PyEval_EvalCode
    at Python/ceval.c line 494
  • #13 PyImport_ExecCodeModuleEx
    at Python/import.c line 675
  • #14 load_source_module
    at Python/import.c line 959
  • #15 load_package
    at Python/import.c line 1015
  • #16 import_submodule
    at Python/import.c line 2400
  • #17 load_next
    at Python/import.c line 2220
  • #18 import_module_level
    at Python/import.c line 2001
  • #19 PyImport_ImportModuleLevel
    at Python/import.c line 2072
  • #20 builtin___import__
    at Python/bltinmodule.c line 47
  • #21 PyObject_Call
    at Objects/abstract.c line 1861
  • #22 PyEval_CallObjectWithKeywords
    at Python/ceval.c line 3442
  • #23 PyEval_EvalFrameEx
    at Python/ceval.c line 2067
  • #24 PyEval_EvalCodeEx
    at Python/ceval.c line 2836
  • #25 PyEval_EvalCode
    at Python/ceval.c line 494
  • #26 run_mod
    at Python/pythonrun.c line 1273
  • #27 PyRun_InteractiveOneFlags
    at Python/pythonrun.c line 792
  • #28 PyRun_InteractiveLoopFlags
    at Python/pythonrun.c line 723
  • #29 PyRun_AnyFileExFlags
    at Python/pythonrun.c line 692
  • #30 Py_Main
    at Modules/main.c line 523
  • #31 __libc_start_main
  • #32 _start 


This is with pygtk 2.13.0 and pygobject 2.15.3.
Comment 1 Loïc Minier 2008-09-02 14:00:33 UTC 
I get this too on x86-64 and not on i386; it's probably a pygobject 2.15.3 bug as it doesn't happen with pygobject 2.15.2 (pygtk 2.12 in both cases).
Comment 2 André Klapper 2008-09-02 21:32:27 UTC 
Bug 544946 is getting TONS of duplicates and its fix depends on pygtkobject 2.15.3 which is not shipped by distros because of amd64 platform.
We can't block duplicates because the stacktrace is too short.

This is an urgent issue because of the bugsquad workload.
Comment 3 André Klapper 2008-09-02 21:40:00 UTC 
*** Bug 547976 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2008-09-02 21:40:11 UTC 
*** Bug 550517 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2008-09-02 21:40:18 UTC 
*** Bug 550518 has been marked as a duplicate of this bug. ***
Comment 6 André Klapper 2008-09-02 21:40:30 UTC 
*** Bug 550522 has been marked as a duplicate of this bug. ***
Comment 7 André Klapper 2008-09-02 21:40:31 UTC 
*** Bug 550554 has been marked as a duplicate of this bug. ***
Comment 8 André Klapper 2008-09-02 21:40:31 UTC 
*** Bug 550534 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2008-09-02 21:40:33 UTC 
*** Bug 550515 has been marked as a duplicate of this bug. ***
Comment 10 André Klapper 2008-09-02 21:40:34 UTC 
*** Bug 550511 has been marked as a duplicate of this bug. ***
Comment 11 André Klapper 2008-09-02 21:40:37 UTC 
*** Bug 550531 has been marked as a duplicate of this bug. ***
Comment 12 André Klapper 2008-09-02 21:40:40 UTC 
*** Bug 550544 has been marked as a duplicate of this bug. ***
Comment 13 Götz Waschk 2008-09-03 08:32:32 UTC 
Fixed in pygobject 2.15.4.