From: Maxime Devos <maximedevos@telenet.be>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Danny Milosavljevic <dannym@scratchpost.org>
Cc: 44414@debbugs.gnu.org
Subject: bug#44414: xterm has GI_TYPELIB_PATH set when started via gdm via fluxbox
Date: Mon, 30 Aug 2021 19:32:03 +0200 [thread overview]
Message-ID: <a36053d592e4b384d585b6c25438dcce798afb2a.camel@telenet.be> (raw)
In-Reply-To: <87a6l2slya.fsf@gmail.com>
[-- 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 --]
prev parent reply other threads:[~2021-08-30 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 9:59 bug#44414: xterm has GI_TYPELIB_PATH set when started via gdm via fluxbox Danny Milosavljevic
2021-08-27 19:54 ` Maxim Cournoyer
2021-08-30 17:32 ` Maxime Devos [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a36053d592e4b384d585b6c25438dcce798afb2a.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=44414@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=maxim.cournoyer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).