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
If I run the command WSLENV='PATH/l' cmd.exe /c echo hello from WSL, I get a bunch of errors printed out on stderr:
<3>init: (13347) ERROR: UtilTranslatePathList:2021: Failed to translate /usr/local/sbin
<3>init: (13347) ERROR: UtilTranslatePathList:2021: Failed to translate /usr/local/bin
<3>init: (13347) ERROR: UtilTranslatePathList:2021: Failed to translate /usr/sbin
<3>init: (13347) ERROR: UtilTranslatePathList:2021: Failed to translate /usr/bin
<3>init: (13347) ERROR: UtilTranslatePathList:2021: Failed to translate /sbin
<3>init: (13347) ERROR: UtilTranslatePathList:2021: Failed to translate /bin
<3>init: (13347) ERROR: UtilTranslatePathList:2021: Failed to translate /usr/games
<3>init: (13347) ERROR: UtilTranslatePathList:2021: Failed to translate /usr/local/games
<3>init: (13347) ERROR: UtilTranslatePathList:2021: Failed to translate /snap/bin
It would be nice to be able to disable these. For example, if we could add a /i option to WSLENV, such that if you use WSLENV='PATH/li' it would suppress those error messages. Either that or another environment variable.
Redirecting stderr is not an option because the Win32 program we call may be printing meaningful information on stderr.
For a single program this is a minor annoyance, but if you are calling a lot of programs in a script (for example a Makefile) you will get this for every Win32 program you call, resulting in a huge amount of output. It also interferes with programmatically parsing stderr in bash scripts (of course we can workaround this but it's not ideal)
Details of my environment:
uname -a
Linux DESKTOP 4.4.0-17763-Microsoft #194-Microsoft Mon Dec 03 17:58:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux
ver
Microsoft Windows [Version 10.0.17763.195]
The text was updated successfully, but these errors were encountered:
This issue prevents my Ubuntu WSL2 from starting. I would like to use some stuff available cross-distro to avoid the building of self-containing packages for every type of distro. I'm looking at the calendar at my screen's right bottom corner and see 20/02/2021. May I hope for a solution?
If I run the command
WSLENV='PATH/l' cmd.exe /c echo hello
from WSL, I get a bunch of errors printed out on stderr:It would be nice to be able to disable these. For example, if we could add a /i option to WSLENV, such that if you use
WSLENV='PATH/li'
it would suppress those error messages. Either that or another environment variable.Redirecting stderr is not an option because the Win32 program we call may be printing meaningful information on stderr.
For a single program this is a minor annoyance, but if you are calling a lot of programs in a script (for example a Makefile) you will get this for every Win32 program you call, resulting in a huge amount of output. It also interferes with programmatically parsing stderr in bash scripts (of course we can workaround this but it's not ideal)
Details of my environment:
uname -a
ver
The text was updated successfully, but these errors were encountered: