fquinner
commented
4 years ago This actually suggests that the command itself failed. I.e. python attempted to execute
cmd.exe /C echo %USERPROFILE%... and it returned an exit code of 1, and even if the variable in use contains spaces it still seems to work OK (at least at that point).
From a WSL bash environment, what happens when you run this?
cmd.exe /C echo %USERPROFILE%
echo $?If that looks good, you can try actually running what is executed:
$ python 3.8
>>> import subprocess
>>> subprocess.check_output(["cmd.exe", "/C", "echo", "%USERPROFILE%"], stderr=subprocess.DEVNULL)And see if that throws a CalledProcessError on your system?
ringtailedfox
whenever i try running wsl-windows-toolbar as a user from within WSL2 bash prompt, it just sits there for a few seconds, then spits out this odd error:
user@XOTICPC:~$ wsl-windows-toolbar Traceback (most recent call last): File "/home/user/.local/bin/wsl-windows-toolbar", line 5, in
from wsl_windows_toolbar.wsl_windows_toolbar import cli
File "/home/user/.local/lib/python3.8/site-packages/wsl_windows_toolbar/wsl_windows_toolbar.py", line 26, in
WINDOWS_USERPROFILE = subprocess.check_output(
File "/usr/lib/python3.8/subprocess.py", line 411, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.8/subprocess.py", line 512, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['cmd.exe', '/C', 'echo', '%USERPROFILE%']' returned non-zero exit status 1.
I have no idea what would cause that. It used to happen on occasion, but rebooting my machine would usually fix it... what can I do to fix this odd behavior?
is it because my windows user profile has a space in it? (C:\Users\User Name\ instead of C:\Users\UserName\, for example)...