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 564740 - configure error on python module detection
configure error on python module detection
Status: RESOLVED FIXED
Product: orca
Classification: Applications
Component: general
2.25.x
Other Linux
: Normal normal
: ---
Assigned To: Orca Maintainers
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-12-16 14:41 UTC by Frederic Peters
Modified: 2009-01-12 20:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
init threads in python test script (305 bytes, patch)
2008-12-16 14:44 UTC, Frederic Peters
none Details | Review

Description Frederic Peters 2008-12-16 14:41:55 UTC
Detection of some python modules now fails with:

** (.:11887): WARNING **: g_thread_init() has not been called. ORBit2 would
like to use threads, so the application should have called g_thread_init(NULL)
before any GLib or GLib-using API. Calling g_thread_init() now here inside the
libORBit-2 library is too late, so instead threads won't be used by ORBit2.
This might have bad side-effects. Fix the application!

GLib-ERROR **: The thread system is not yet initialized.
aborting...
Comment 1 Frederic Peters 2008-12-16 14:44:05 UTC
Created attachment 124797 [details] [review]
init threads in python test script

This fixes the build issue; however I didn't actually run Orca and it may well be this is also needed at runtime.
Comment 2 Willie Walker 2008-12-18 17:12:18 UTC
(In reply to comment #0)
> Detection of some python modules now fails with:
> 
> ** (.:11887): WARNING **: g_thread_init() has not been called. ORBit2 would
> like to use threads, so the application should have called g_thread_init(NULL)
> before any GLib or GLib-using API. Calling g_thread_init() now here inside the
> libORBit-2 library is too late, so instead threads won't be used by ORBit2.
> This might have bad side-effects. Fix the application!
> 
> GLib-ERROR **: The thread system is not yet initialized.
> aborting...
> 

Thanks Frederic!  Do you know which specific modules this fails with?  I'm curious why this hasn't happened before and if a specific module import (e.g., ORBit?) is causing this.  The reason I ask is that I cannot reproduce the problem on my machine, but I notice there are a couple places in acinclude.m4 that we might need to modify in a manner similar to your patch.
Comment 3 Frederic Peters 2008-12-18 20:35:52 UTC
  checking for python module bonobo... ./configure: line 23706:  9228 Trace/breakpoint trap   (core dumped) $PYTHON -c "$prog" 1>&5 2>&5
  no
  configure: error: Could not find python module bonobo - make sure you have gnome-python with support for libbonobo-2.0 >= 2.14.0 installed

The thing is I suddenly got all those g_thread_init() warnings and couldn't find the culprit (as I spent a few days away of my jhbuild environment); and asking other people I couldn't find any body with the same problem; so it may well be something local and not a real issue.

I'll get to rebuild an environment soon, to confirm or invalidate this bug report.
(I'm marking it as NEEDINFO so I remember to get back).
Comment 4 Frederic Peters 2009-01-12 20:32:31 UTC
So the thread init issue was related to a change in ORBit2, that has been reverted; this bug can be closed.