[Bug 636372] Re: pygtk-2.16.0 causes python-2.7 to segfault if warning settings are changed from default to "error"

[Bug Watch Updater]

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=621887.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2010-08-06T11:58:31+00:00 Michal wrote:

Description of problem:

Gajim crashes on startup in F-14. A minimal reproducer points to a bug
either in pygtk2, gtk2, or python:

$ python
Python 2.7 (r27:82500, Jul 26 2010, 18:19:48) 
[GCC 4.5.0 20100716 (Red Hat 4.5.0-3)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import warnings
>>> warnings.filterwarnings('error', module='gtk')
>>> import gtk
python: /builddir/build/BUILD/Python-2.7/Objects/dictobject.c:759: PyDict_SetItem: Assertion `value' failed.
Aborted (core dumped)

Version-Release number of selected component (if applicable):
pygtk2-2.17.0-7.fc14.x86_64
gtk2-2.21.5-2.fc14.x86_64
python-2.7-7.fc14.x86_64

How reproducible:
always

Steps to Reproduce:
1. execute the 3 lines in python
  
Actual results:
assertion failure

Expected results:
no crash

Reply at: https://bugs.launchpad.net/pld-linux/+bug/636372/comments/0

------------------------------------------------------------------------
On 2010-08-09T09:35:05+00:00 Michal wrote:

Added dmalcolm to CC.
David, could this be a bug in the warnings module itself?

Reply at: https://bugs.launchpad.net/pld-linux/+bug/636372/comments/1

------------------------------------------------------------------------
On 2010-08-09T14:52:02+00:00 Dave wrote:

This is a bug in pygtk2's initialization - it uses the deprecated
PyCObject API.  See bug 620216 and bug 620842.

Reply at: https://bugs.launchpad.net/pld-linux/+bug/636372/comments/2

------------------------------------------------------------------------
On 2010-08-12T15:31:30+00:00 Dave wrote:

Upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=623965

Reply at: https://bugs.launchpad.net/pld-linux/+bug/636372/comments/3

------------------------------------------------------------------------
On 2012-08-16T21:20:07+00:00 Fedora wrote:

This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at: https://bugs.launchpad.net/pld-linux/+bug/636372/comments/16


** Changed in: fedora
       Status: Unknown => Won't Fix

** Changed in: fedora
   Importance: Unknown => Medium

-- 
You received this bug notification because you are subscribed to PLD
Linux.
https://bugs.launchpad.net/bugs/636372

Title:
  pygtk-2.16.0 causes python-2.7 to segfault if warning settings are
  changed from default to "error"

Status in PyGTK:
  Confirmed
Status in Fedora:
  Won't Fix
Status in PLD Linux:
  Fix Released

Bug description:
  python-pygtk-2.16.0 causes python-2.7 to segfault if warning settings are changed from default to "error".
  Because PyGTK-2.10+ throws only warnings applications which use PyGTK change warning settings to catch an exception while importing gtk module and X display is not available.

  [kiesiu at beth ~]$ python -c "import warnings; warnings.filterwarnings('error', module='gtk'); import gtk"
  python: Objects/dictobject.c:759: PyDict_SetItem: Assertion `value' failed.
  Aborted

  [kiesiu at beth ~]$ rpm -q python-pygtk-gtk
  python-pygtk-gtk-2.16.0-2.i686

  It's a known bug for upstream
  (https://bugzilla.gnome.org/show_bug.cgi?id=623965) and downstream
  (https://bugzilla.redhat.com/show_bug.cgi?id=621887).

To manage notifications about this bug go to:
https://bugs.launchpad.net/pygtk/+bug/636372/+subscriptions