GNU bug report logs - #44414
xterm has GI_TYPELIB_PATH set when started via gdm via fluxbox

Previous Next

Package: guix;

Reported by: Danny Milosavljevic <dannym <at> scratchpost.org>

Date: Tue, 3 Nov 2020 10:00:02 UTC

Severity: important

Full log


Message #13 received at 44414 <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>, Danny Milosavljevic
 <dannym <at> scratchpost.org>
Cc: 44414 <at> debbugs.gnu.org
Subject: Re: bug#44414: xterm has GI_TYPELIB_PATH set when started via gdm
 via fluxbox
Date: Mon, 30 Aug 2021 19:32:03 +0200
[Message part 1 (text/plain, inline)]
> Danny Milosavljevic <dannym <at> scratchpost.org> writes:
> 
> > Hi,
> > 
> > this is one of the bug reports in the aftermath of the problem I had outlined
> > in "GNOME in Guix" thread.
> > 
> > Currently, even when using xterm, started by fluxbox, started by gdm-x-session,
> > the environment variable GI_TYPELIB_PATH is set inside the shell started by
> > that xterm.
> > 
> > Please don't do set GI_TYPELIB_PATH that way.

I took a look at which package or service might be setting GI_TYPELIB_PATH.
xterm and fluxbox don't use wrap-program, so probably not those.
gdm uses glib-or-gtk-build-system, which has a glib-or-gtk-wrap phase,
which wraps programs, setting various environment variables.

It should probably be disabled in this case.  I don't know if GDM uses
GI_TYPELIB_PATH.  If it does, somehow GDM must still find the right
typelibs without setting GI_TYPELIB_PATH ... Or maybe it could simply
unset GI_TYPELIB_PATH between fork(...) and exec(...)? (Requires source
code patching ...)

Greetings,
Maxime.
[signature.asc (application/pgp-signature, inline)]

This bug report was last modified 3 years and 287 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.