-
Notifications
You must be signed in to change notification settings - Fork 821
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
Cannot start Ubuntu on build 19033.1 #4725
Comments
@kpeters-cbsi - It looks like you are hitting a timeout waiting for the VM to start. Is this a very slow machine by chance? Does this hit 100% of the time or only sometimes? |
@kpeters-cbsi - if you install a new distro (like debian) does this still reproduce? |
Interesting... I wonder if there was something about your old VHDX that was causing mounting the VHD to take a long time. |
The only weirdness I can think of is that I had an SSHFS mount in fstab that I haven't since restored. |
Ah interesting... that could definitely cause issues if your ssh server isn't responding. |
@benhillis I had meet the same issue NO VMware or VirtualBox, and How can I get the useful log, like lxcore_user.etl etc. |
Windows build number: 19035.1000 (Yesterday I've been stuck in #4731, today I've upgraded to 19035.1, the network issue has been gone, but it's now horrible slow at startup) |
yeah, same issue. Take about 40 seconds to start a bash shell (Ubuntu 18.04). It started happening with slow ring build 19035. Noticed if you press ctrl+c it kills whatever is hanging and takes you to the command prompt. Running on the latest Surface Laptop 3, 16GB, i7. I think WSL CPU usage is up too, I noticed my laptop is constantly hot... |
I'm using WSL with 19035, no issue. |
probably related #4738 |
I uninstalled Ubuntu 18.04 and reinstalled. I worked as expect until I did an apt update/upgrade of the distro and now it's back to the slow start again... |
Same issue and it was on a new build and straight after an apt update/upgrade. Before the apt it was fine. |
This was happening to me too in Ubuntu, but i remembered the last package that was updated (wslu). I uninstalled it and it works great again (sudo apt autoremove --purge wslu). |
Thanks! This fixed it. |
Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.
If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.
Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues. Please direct all Windows crashes and security issues to [email protected]. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".\
See our contributing instructions for assistance.
Please fill out the below information:
Your Windows build number: 19033.1
What you're doing and what's happening: When I type "bash" at the Windows command prompt, I get "The Windows Subsystem for Linux instance has terminated"
What's wrong / what should be happening instead: bash / Ubuntu should start.
Strace of the failing command, if applicable: N/A
Logs: bash logs.zip
The text was updated successfully, but these errors were encountered: