GNU bug report logs -
#44414
xterm has GI_TYPELIB_PATH set when started via gdm via fluxbox
Previous Next
To reply to this bug, email your comments to 44414 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#44414
; Package
guix
.
(Tue, 03 Nov 2020 10:00:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Danny Milosavljevic <dannym <at> scratchpost.org>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Tue, 03 Nov 2020 10:00:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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.
[Message part 2 (application/pgp-signature, inline)]
Severity set to 'important' from 'normal'
Request was from
Ludovic Courtès <ludo <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Thu, 03 Dec 2020 17:11:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#44414
; Package
guix
.
(Fri, 27 Aug 2021 19:55:01 GMT)
Full text and
rfc822 format available.
Message #10 received at 44414 <at> debbugs.gnu.org (full text, mbox):
Hello,
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.
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
Information forwarded
to
bug-guix <at> gnu.org
:
bug#44414
; Package
guix
.
(Mon, 30 Aug 2021 17:33:01 GMT)
Full text and
rfc822 format available.
Message #13 received at 44414 <at> debbugs.gnu.org (full text, mbox):
[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 286 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.