-
Notifications
You must be signed in to change notification settings - Fork 816
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
A connection attempt failed because the connected party did not properly respond #5459
Comments
Duplicate |
Still it exist after several restart and |
@darkRaspberry - Your logs are empty. Did you start the logs, repro the issue, then stop? |
Ok should i run it again? |
I am having the same issue as above with windows version: Here are my logs: EDIT: Updated to latest Fast ring update |
This issue is back after the WSL Kernel update to 5.4. Some distros can start but some fail. What is common: systemd based distro can't start - they need systemd running as PID 1. They have dozens of units inside rootfs image. There is no option to start them synchronously - it will take forever. My Ubuntu 20.04 with genie worked stable a long time until the upgrade attempt. Without systemd, i.e. D-Bus, network configuration units they can't bootstrap. |
I just wiped whole windows and leaving it forever. Anyone can take the issue further as a owner of this issue GitHub don't allow me to transfer it. I no longer use this platform so the repo owner can close this issue. |
Environment
Steps to reproduce
Just launch the Ubuntu in any way.
Like launch by Windows terminal or Launch by direct app(Ubuntu)
Uploading log failed due to file not supported so renaming file to .log
lxcore_user.log
lxcore_kernel.log
lxcore_service.log
Expected behavior
Launch in normal way
Actual behavior
I am attaching the screenshot
Launch by Ubuntu app.
Launch by Windows terminal
The text was updated successfully, but these errors were encountered: