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 546149 - gtk.gdk.threads_init() crash
gtk.gdk.threads_init() crash
Status: RESOLVED DUPLICATE of bug 544946
Product: pygtk
Classification: Bindings
Component: gdk
2.12.x
Other All
: Normal critical
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-03 22:30 UTC by Michel Alexandre Salim
Modified: 2008-08-05 18:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Michel Alexandre Salim 2008-08-03 22:30:13 UTC
Steps to reproduce:
1. import gtk
2. gtk.gdk.threads_init()
3. Alternatively, run applications such as deluge, hocr-gtk or Miro


Stack trace:
From IPython:
Traceback (most recent call last):
  • File "<ipython console>", line 2 in <module>
SystemError: error return without exception set

From Miro:
Traceback (most recent call last):
  File "/usr/bin/miro.real", line 118, in <module>
    startapp()
  File "/usr/bin/miro.real", line 95, in startapp
    startup()
  File "/usr/bin/miro.real", line 32, in startup
    Application().run()
  File "/usr/lib64/python2.5/site-packages/miro/platform/frontends/html/Application.py", line 56, in run
    gtk.gdk.threads_init()
SystemError: error return without exception set


Other information:
gtk2 version: 2.13.5 -- looks like an API mismatch.
Comment 2 Paul Pogonyshev 2008-08-05 18:42:40 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

Note that the bug this is duplicate of is technically open, but it is fixed anyway.


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