Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wslvar v3.2.3-1 no longer works after upgrading WSL to 2.4.4.0 #12295

Closed
1 of 2 tasks
felipecrs opened this issue Nov 19, 2024 · 8 comments
Closed
1 of 2 tasks

wslvar v3.2.3-1 no longer works after upgrading WSL to 2.4.4.0 #12295

felipecrs opened this issue Nov 19, 2024 · 8 comments

Comments

@felipecrs
Copy link

Windows Version

10.0.26100.2314

WSL Version

2.4.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 24.04

Other Software

$ wslvar --version
wslu v3.2.3-1; wslvar v03

Repro Steps

wslvar, which used to work just fine, isn't working anymore (see Actual Behavior).

Expected Behavior

To work as it did before.

Actual Behavior

$ wslvar USERPROFILE
The string is missing the terminator: ".
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : TerminatorExpectedAtEndOfString

Diagnostic Logs

Please let me know if you need more details.

Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

@felipecrs
Copy link
Author

Note this issue doesn't happen with wslu v4.1.3-1. But I'm reporting anyway in case it's a regression that needs to be fixed.

@felipecrs
Copy link
Author

Also, I'm not sure why but the logs collector simply hangs and doesn't do anything.

Image

@felipecrs felipecrs changed the title wslvar no longer works after WSL 2.4.4.0 wslvar v3.2.3-1 no longer works after upgrading WSL to 2.4.4.0 Nov 19, 2024
Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

@benhillis
Copy link
Member

wslu / wslvar is not maintained by Microsoft. I suggest following up with the owner of that project. Happy to help debug if we broke something, but I don't even know where to start here.

@felipecrs
Copy link
Author

Well, my point was that WSL 2.4.4.0 broke it.

@justus-camp-microsoft
Copy link
Collaborator

We don't maintain the tool and don't make any guarantees about not breaking it between releases. I would recommend opening an issue against the tool's repo.

@felipecrs
Copy link
Author

Alright. Since it's not broken in the tool's latest version, I will not open an issue there.

For posteriority, since even the newest Ubuntu on WSL still packages wslu v3, the solution is to install their PPA to have wslu upgraded to v4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants