Closed wenzler closed 2 years ago
Seems an issue. Once in this state, could you please send the result of the following command:
module config --dump-state
Send it to me directly by email if you do not want these information to be publicly available on this ticket.
Nevermind - we are missing to emulate module clear properly
The content of the __MODULES_LMTAG
variable in the output is inconsistent. If by any chance you could describe how the krb5/krb5 module is loaded to end up in this state, it could be interesting.
module clear
is available and should also clear the __MODULES_*
variables.
As said - we dont do module clear but an old style env variable clearing vbuild/init has a krb5/krb5 module load statement - thats the trigger the rest is just about desktops having a SHLVL > 1
According to changelog the aL tagging was introduced
Changed in version 4.7: Output items for module tags auto-loaded (aL), forbidden (F), hidden and hidden-loaded (H), loaded (L), nearly-forbidden (nF), sticky (S) and super-sticky (sS) added
Yet, with 5.0.1 we see that there is a repeated tagging for modules export TERM=xterm export MODULES_COLOR=never module list Currently Loaded Modulefiles: 1) krb5/krb5 2) vb/init
....
I suppose this isnt as intended, or?
Thanks!