There was a time where I think there was an underlying problem in pygtk. If I recall correctly, merely doing an "import gtk" in python and nothing else seemed to elicit this message. As such, there was little a Python application could do to avoid this.
Will On Fri, 2007-08-10 at 22:07 +0800, Li Yuan wrote: > Hi Halim, > > Please refer to my former mail. > Applications need to call g_thread_init before any glib calls. It will > quit applications if applications call it twice. > > In this case, if linphone doesn't call g_thread_init before gtk_init, > CORBA will call. When linphone calls it the second time, linphone > crashed. The fix is to move g_thread_init to the begining (before > gtk_init), or add a check before calling g_thread_init (not perfect). > > So this is applications' bug. Maybe not only in linphone. > > Regards, > Li > > > 2007/8/9, Halim Sahin <[EMAIL PROTECTED]>: > Hello Li, > On Do, Aug 09, 2007 at 04:10:44 +0800, Li Yuan wrote: > > Do we have a bug for this? > > I reported this in > Date: Sun, 27 May 2007 07:53:27 +0000 (UTC) > in the gnome-accessibility list. > > Which versions of gnome are fixing this? > > The application that had this problem is linphone. > But google says that more apps were affected by this problem. > > Thanks > Halim > > _______________________________________________ > Gnome-accessibility-devel mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel > > _______________________________________________ > Gnome-accessibility-devel mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel _______________________________________________ Gnome-accessibility-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
