FS#32034 - [python-gobject] gi introspection SIGSEGV

Attached to Project: Arch Linux
Opened by Simonas (nagi) - Wednesday, 17 October 2012, 18:14 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 31 October 2012, 08:46 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Description:
Importing gi.repository.Gtk from python3 terminates with SIGSEGV

Additional info:
* package version(s)
Python 3.3.0-1
gtk3 3.4.4-1

Steps to reproduce:
$ python
Python 3.3.0 (default, Sep 29 2012, 15:50:43)
[GCC 4.7.1 20120721 (prerelease)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi.repository.Gtk
fish: Job 1, “python” terminated by signal SIGSEGV (Address boundary error)
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 31 October 2012, 08:46 GMT
Reason for closing:  Fixed
Comment by Stéphane Gaudreault (stephane) - Wednesday, 17 October 2012, 19:49 GMT
Looks like the signal is comes from /usr/lib/python3.3/site-packages/gi/_gobject/_gobject.so wich is in python-gobject.
Reassinged.
Comment by Jan de Groot (JGC) - Wednesday, 17 October 2012, 19:54 GMT
Works fine with python-gobject from gnome-unstable.
Comment by Simonas (nagi) - Wednesday, 17 October 2012, 19:56 GMT
It really would be fine if gnome-unstable was stable.

Edit: I did mark bug as `Packages: Extra`, which is what I meant.
Comment by Stéphane Gaudreault (stephane) - Wednesday, 17 October 2012, 19:57 GMT
I can reproduce the problem with python-gobject-3.2.2-2 from [extra] (which is probably the version installed by the reporter).
Comment by Allan McRae (Allan) - Wednesday, 17 October 2012, 23:57 GMT
gnome-unstable will move to the main repos very soon at which point this will be fixed.
Comment by lilydjwg (lilydjwg) - Friday, 19 October 2012, 11:56 GMT
I can reproduce this too!

% pacman -Q python python-gobject
python 3.3.0-1
python-gobject 3.2.2-2

>>> from gi.repository import Gdk
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff2ad2fda in ?? () from /usr/lib/python3.3/site-packages/gi/_gobject/_gobject.so
Comment by Balló György (City-busz) - Saturday, 20 October 2012, 14:49 GMT
I attached a fixed 3.2.2 package with two upstream patches for python 3.3, which solves the problem.

The source of the patches:
http://git.gnome.org/browse/pygobject/commit/?id=1bee194274bcda9ba5f6751fa921218a92c8ac72
http://git.gnome.org/browse/pygobject/commit/?id=3e3525e93d852cde0f63e835b774a9b004773c69
(application/x-gzip)    pygobject-3.2.2-3.src.tar.gz (2.9 KiB)
Comment by Fabian Henze (flyser) - Tuesday, 23 October 2012, 07:26 GMT
That package fixes the problem for me.
Comment by lilydjwg (lilydjwg) - Tuesday, 23 October 2012, 08:00 GMT
That package fixes the problem for me, too.
Comment by Damjan Dimitrioski (gnu_D) - Tuesday, 23 October 2012, 10:46 GMT
Not for me :(.
[gnu_d@freedom ~]$ python3 d.py
Traceback (most recent call last):
File "<frozen importlib._bootstrap>", line 1268, in _path_importer_cache
KeyError: 47

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "d.py", line 1, in <module>
from gi.repository.Gtk import Gtk
File "<frozen importlib._bootstrap>", line 1558, in _find_and_load
File "<frozen importlib._bootstrap>", line 1516, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 1470, in _find_module
File "<frozen importlib._bootstrap>", line 1305, in find_module
File "<frozen importlib._bootstrap>", line 1281, in _get_loader
File "<frozen importlib._bootstrap>", line 1270, in _path_importer_cache
File "<frozen importlib._bootstrap>", line 1251, in _path_hooks
TypeError: 'int' object is not iterable
Comment by Jesse Frey (jessef) - Tuesday, 23 October 2012, 18:54 GMT
The packages fixes it for me as well
Comment by Damjan Dimitrioski (gnu_D) - Tuesday, 23 October 2012, 18:59 GMT
Ok, somehow later on, in Eclipse I managed to get it running, dunno why it was working afterwards :).

Loading...