Confirmed. This is related to how gnome-terminal starts up, via dbus / systemd --user. Even if you type "gnome-terminal" in let's say an xterm, it just notifies systemd to fire up the server. During this step, environment variables get lost.
As a workaround, you could manually start up the server, followed by the client (with a tiny pause in between, if doing from a script), as described at https://wiki.gnome.org/Apps/Terminal/Debugging (without the gdb part). Here's my wrapper script I often use while debugging: #!/bin/bash /usr/lib/gnome-terminal/gnome-terminal-server --app-id a.b$$ & sleep 0.2 /usr/bin/gnome-terminal --app-id a.b$$ "$@" Plenty of other env variables that somehow affect the behavior (e.g. GTK_THEME) aren't forwarded either. So it's probably not feasible to start whitelisting and somehow proxying them to the server one by one. I guess other apps that use dbus/systemd to start up are also affected. xfce4-terminal follows a more standard pattern. I'm not sure what the right solution would be, it looks to me that this overall design has this limitation, or at least I'm not aware of the proper approach (maybe configure systemd??). Alas I'm not aware with the rationale and details of this design. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772557 Title: FREETYPE_PROPERTIES environment variable is not respected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1772557/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
