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
Install and source vte-2.91.sh for terminal integration #1101
The package libvte-2.91-common provides /etc/profile.d/vte-2.91.sh which is used by the VTE library to provide reliable tracking of thw CWD. We want to use this in the VTE-based Ptyxis terminal (default terminal in Ubuntu Desktop 26.04 and newer) to preserve CWD across workshop shells.
Please consider pre-installing libvte-2.91-common in the base container, and sourcing /etc/profile.d/vte-2.91.sh from bashrc.
The sourcing part already happens from bash in Ubuntu 26.04 containers, but older containers won't source it by default (https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2083705).
Ah, if workshop shell always opens a login shell then the sourcing always happens, for compatible shells. workshop shell --help says that it "launches the login shell", but experimentally it is not a login shell. perhaps the "login" wording here simply means the "default" shell.
Yes we always source /etc/profile.d/*. Currently the mechanism for that is an actual login shell (well, technically bash -l). That may change in future but we'll continue to source the environment variables at least. Similar to how gnome-session works.
As for VTE, I'm not sure we'll be able to include it in the base images since these are the standard Ubuntu cloud images used all over the place, not just in Workshop. But we can probably add a shell script which has the same effect. Does it basically amount to putting something in the PROMPT_COMMAND?
Activity
aleasto commentedon Oct 16, 2026
Ah, if
workshop shellalways opens a login shell then the sourcing always happens, for compatible shells.workshop shell --helpsays that it "launches the login shell", but experimentally it is not a login shell. perhaps the "login" wording here simply means the "default" shell.jonathan-conder commentedon Oct 20, 2026
Yes we always source
/etc/profile.d/*. Currently the mechanism for that is an actual login shell (well, technicallybash -l). That may change in future but we'll continue to source the environment variables at least. Similar to howgnome-sessionworks.As for VTE, I'm not sure we'll be able to include it in the base images since these are the standard Ubuntu cloud images used all over the place, not just in Workshop. But we can probably add a shell script which has the same effect. Does it basically amount to putting something in the
PROMPT_COMMAND?aleasto commentedon Oct 20, 2026
I'm not sure about the implementation details, it is somewhat obscure to read to me: https://gitlab.gnome.org/GNOME/vte/-/blob/master/src/vte.sh.in
But the script also depends on
/usr/libexec/vte-urlencode-cwd