My program has a frontend and backend and I wish to separate the GTK
part completely from the rest, so I don't want to use GDK/GObject
threading in my backend.
Actually I found out what the problem is. It's a common problem in
gnutls which is used by a library I've imported (filed as a bug at
https://bugzilla.redhat.com/show_bug.cgi?id=512350). So it's not a
problem with GTK, luckily.
Thank you for your help anyway ;-)
saeed wrote:
When you use PyGTK and PyGObject, you probably not need to Python's
threading. What's your use of threading?
On 7/16/09, Andreas Sommer <[email protected]> wrote:
Hi,
I'm currently having some problems with the following error:
python: ath.c:193: _gcry_ath_mutex_lock: Assertion `*lock ==
((ath_mutex_t) 0)` failed.
Some info about my system:
Debian lenny 5.0.1 (having apt-get upgrade'd with all stable packages)
Python 2.5.2
libgcrypt 1.4.4-3
python-gtk2 2.12.1-6
For your information, I called gtk.gdk.threads_init() before gtk.main
(actually at the very beginning of my script). I'm getting this problem
when using Python threads derived from threading.Thread.
Is it possible at all to use GTK with Python's threading module? Did
anybody else experience such problems?
Best regards
Andreas
_______________________________________________
pygtk mailing list [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://faq.pygtk.org/
_______________________________________________
pygtk mailing list [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://faq.pygtk.org/
