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

//wsl$/Ubuntu file or resource was not found #5753

Closed
blacklightpy opened this issue Aug 13, 2020 · 5 comments
Closed

//wsl$/Ubuntu file or resource was not found #5753

blacklightpy opened this issue Aug 13, 2020 · 5 comments

Comments

@blacklightpy
Copy link

Environment

Windows build number: 20185
Your Distribution version: Ubuntu 20.04
Whether the issue is on WSL 2 and/or WSL 1: WSL 1

Steps to reproduce

Start a WSL instance
Close the terminal and do something else for a while
a ) Try to access a WSL file from the explorer sidebar or //wsl$/Ubuntu
OR
b) Start a new WSL instance in Windows terminal

Expected behavior

a) Since WSL was booted up once and I hadn't typed wsl --shutdown, the instance should be online and I should be able to access my files
OR
b) WSL should start a terminal instance without starting the distro again because it was started once and not shut down.

Actual behavior

a) Trying to access //wsl/Ubuntu (Linux section in Explorer sidebar) or //wsl$/Ubuntu tells me file or resource was not found
OR
b) WSL starts the distro again, starting at /mnt/c/Users/Blacklight instead of ~ respecting startingDirectory attribute I set in terminal (I have made an issue about it at microsoft/terminal#7272).

This is the exact opposite of microsoft/WSL2-Linux-Kernel/#111, which suggests to add this feature as an option in WSL but this is what I have as default in my system and I don't have an option to turn it off :(

@sr229
Copy link

sr229 commented Aug 13, 2020

IIRC this is intended behavior as to prevent unnecessary usage for portable devices.

@blacklightpy
Copy link
Author

Oh, that makes sense because my device is a laptop. In that case is there any way to turn it off?

@therealkenc
Copy link
Collaborator

therealkenc commented Aug 13, 2020

//wsl$/Ubuntu tells me file or resource was not found

WSL does shut itself down by-design to conserve resources, but that doesn't (ie: shouldn't) prevent WSL from being fired back up on-demand when you access \\wsl$\Ubuntu. Your described behavior does not reproduce here. There is some variable causing your "file or resource was not found" error, but no off-cuff guesses what.

Please collect networking logs and post to feeback hub.

@therealkenc therealkenc changed the title WSL Instance shuts down after not using it for a while //wsl$/Ubuntu file or resource was not found Aug 13, 2020
@blacklightpy
Copy link
Author

Here's the link of the Feedback Hub report: https://aka.ms/AA9at0w

While I was collecting the reports, I noticed that the delay for the //wsl$/Ubuntu path being inactive after closing WSL varies each time. In this instance it wasn't working immediately after I closed the tab, but I tried it once afterwards and it was active for a while more.

Copy link
Contributor

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!

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

No branches or pull requests

4 participants