You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Linux AppImage leaks runtime environment into integrated terminal and can conflict with system libraries #10966
On Linux, the T3 Code AppImage appears to leak AppImage runtime environment variables and mount paths into the integrated terminal. This can cause host/system programs launched from the T3 terminal to resolve AppImage-bundled libraries or otherwise behave differently from the same programs launched from a normal terminal.
Programs launched from T3 Code's integrated terminal should use the host system environment and system libraries. AppImage-specific variables and mount paths should not leak into unrelated child processes.
Actual behavior
The integrated terminal can inherit AppImage runtime state such as APPIMAGE, APPDIR, OWD, ARGV0, and LD_LIBRARY_PATH entries pointing into /tmp/.mount_T3-*. AppImage mount paths may also appear in PATH.
This can cause system binaries launched from the T3 terminal to behave differently or potentially load incompatible libraries from the AppImage instead of the host system.
Closing as a duplicate of #1699. Same AppImage launcher env leaking into the integrated terminal (ARGV0 / APPIMAGE / APPDIR / OWD, plus mount paths in PATH / LD_LIBRARY_PATH); #1699 is the canonical thread (also covered #2509).
Activity
juliusmarminge commentedon Sep 9, 2026
Closing as a duplicate of #1699. Same AppImage launcher env leaking into the integrated terminal (
ARGV0/APPIMAGE/APPDIR/OWD, plus mount paths inPATH/LD_LIBRARY_PATH); #1699 is the canonical thread (also covered #2509).