GNOME Bugzilla – Bug 385120
should GTK_MODULES be unset ?
Last modified: 2009-04-29 11:45:10 UTC
When trying to build GNOME with jhbuild the configure script of deskbar-applet give me the following: checking for gnomeapplet module... ./configure: line 22332: 1200 Aborted ( $PYTHON -c ' try: import gnomeapplet except ImportError, e: if str(e).find("gnomeapplet") >= 0: raise except: pass ' ) 2>&5 no configure: error: gnomeapplet Python module required to build deskbar I looked in the config.log and find this usefull: configure:22301: checking for gnomeapplet module configure:22311: $PYTHON -c ' try: import gnomeapplet except ImportError, e: if str(e).find("gnomeapplet") >= 0: raise except: pass ' GTK Accessibility Module initialized ** (-c:1200): CRITICAL **: AT_SPI_REGISTRY was not started at session startup. ** (-c:1200): WARNING **: IOR not set. ** ERROR **: Could not locate registry aborting... configure:22322: $? = 134 configure:22327: result: no configure:22329: error: gnomeapplet Python module required to build deskbar Appear that something is wrong with the accessibility support when running jhbuild. I tried the same test program in the system python interpreter (the jhbuild uses the one installed by it, that is in my home folder) and everything executed fine. I don't get the CRITICAL, WARNING and ERROR messages. Any advice on this? Thanks!!!
Sounds like your environment includes $GTK_MODULES... or the build is trying to run one of the executables it's built. Running a built executable without a session instance is causing the problem. Upgrading to at-spi HEAD should fix the crash though, since it makes the failure to find the at-spi-registry non-fatal.
Yes, both :-) The $GTK_MODULES are setted to "gail:atk-bridge" and the python interpreter was built by jhbuild. at-spi was checkout with the following command: cvs -z3 -q -d :ext:carlosd@cvs.gnome.org:/cvs/gnome checkout -P -A at-spi What I think that gives me the HEAD sources. I also noticed that inside jhbuild environment $SESSION_MANAGER have the same value as outside. I guess this is related with the session instance that you talked about.
Unset the GTK_MODULES variable before execute the jhbuild script resolved the issue. Thanks Bill. Could you explaim me the influence of this variable?
GTK_MODULES is how apps that don't use gnome_program_init load the accessibility support code, i.e. libatk-bridge and libgail (and libgail-gnome, if the app uses embedded components).
Decreasing severity and updating title, I don't know if unsetting GTK_MODULES in jbhuild is a good idea, so I'll keep this open.
Also I guess now the problem was deskbar-applet didn't declare properly the jhbuild pygtk sys.path, which is a problem I found on another occasion and fixed. commit 645fdac15ccbe6c56465ca04d1e7da4fd1f90838 Author: Sebastian Polsterl <sebp@src.gnome.org> Date: Tue Dec 16 18:47:58 2008 +0000 Fixed bug #564726: configure doesn't detect pygtk in alternative directories (patch by Frederic Peters) svn path=/trunk/; revision=2503 As recent at-spi won't cause a problem anyway, and deskbar-applet will properly set its sys.path, I believe there are no more problems keeping GTK_MODULES set, keeping a11y and other settings the user could have set.