bug#44414: xterm has GI_TYPELIB_PATH set when started via gdm via fluxbox

bug#44414: xterm has GI_TYPELIB_PATH set when started via gdm via fluxbox

[Danny Milosavljevic]

[-- Attachment #1: Type: text/plain, Size: 336 bytes --]

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.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

bug#44414: xterm has GI_TYPELIB_PATH set when started via gdm via fluxbox

[Maxim Cournoyer]

Hello,

Danny Milosavljevic <dannym@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.

Just confirming that is still the case on a GDM launched session, with:

--8<---------------cut here---------------start------------->8---
cat /proc/$(grep xterm)/environ | xargs -0 -n1 | grep ^GI_TYPELIB
--8<---------------cut here---------------end--------------->8---

Maxim

bug#44414: xterm has GI_TYPELIB_PATH set when started via gdm via fluxbox

[Maxime Devos]

[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

> Danny Milosavljevic <dannym@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.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]