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 338760 - Segmentation Fault instancing a subclass of gtk.Dialog
Segmentation Fault instancing a subclass of gtk.Dialog
Status: RESOLVED DUPLICATE of bug 96658
Product: pygtk
Classification: Bindings
Component: gtk
2.8.x
Other All
: Normal critical
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2006-04-17 09:02 UTC by Alberto Ruiz
Modified: 2006-04-17 09:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
This is the code example that produces the crash. (372 bytes, text/x-python)
2006-04-17 09:04 UTC, Alberto Ruiz
Details

Description Alberto Ruiz 2006-04-17 09:02:22 UTC
Steps to reproduce:
1. subclassing a gtk.Dialog class without calling the __init__ of the parent
like this:
2. running the application and calling the callback which instance the dialog

Stack trace:


Other information:
Comment 1 Alberto Ruiz 2006-04-17 09:04:17 UTC
Created attachment 63674 [details]
This is the code example that produces the crash.

It is a window with a button as a child, the button has a callback connected to its clicked signal which runs the dialog, and then the segmentation fault occurs.
Comment 2 Alberto Ruiz 2006-04-17 09:05:14 UTC
These are the versions of pygtk and gtk+ that I'm using:

[arc@centauri:~]$ pkg-config --modversion pygtk-2.0
2.8.4
[arc@centauri:~]$ pkg-config --modversion gtk+-2.0
2.8.16
Comment 3 Gustavo Carneiro 2006-04-17 09:50:09 UTC

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