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

My WSL starts up very slowly, and every time I enter my password with sudo or su, it takes a long time to respond. #12075

Open
1 of 2 tasks
THEBO666 opened this issue Sep 25, 2024 · 10 comments
Labels

Comments

@THEBO666
Copy link

THEBO666 commented Sep 25, 2024

Windows Version

Microsoft Windows [版本 10.0.22631.4037]

WSL Version

2.3.14.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

6.6.36.3-1

Distro Version

Ubuntu 22.04.4 LTS

Other Software

No response

Repro Steps

Yesterday, after executing the 'sudo apt get install xubuntu desktop' command, I closed the terminal midway to terminate it, and then encountered the problem of slow startup and inability to install.

Expected Behavior

I hope to solve the problem

Actual Behavior

Yesterday, after executing the 'sudo apt get install xubuntu desktop' command, I closed the terminal midway to terminate it, and then encountered the problem of slow startup and inability to install. After booting up, the terminal showed the following content:
Welcome to Ubuntu 22.04.4 LTS (GNU/Linux 6.6.36.3-microsoft-standard-WSL2 x86_64)

Expanded Security Maintenance for Applications is not enabled.

25 updates can be applied immediately.
To see these additional updates run: apt list --upgradable

29 additional security updates can be applied with ESM Apps.
Learn more about enabling ESM Apps service at https://ubuntu.com/esm

1 updates could not be installed automatically. For more details,
see /var/log/unattended-upgrades/unattended-upgrades.log

This message is shown once a day. To disable it please create the
/home/junmoxiao/.hushlogin file.
image

Diagnostic Logs

No response

Tasks

No tasks being tracked yet.
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'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@THEBO666
Copy link
Author

/question

Copy link

Diagnostic information
Found '/question', adding tag 'question'

@THEBO666
Copy link
Author

I don't know why I can't collect it
image

@THEBO666
Copy link
Author

WSL 团队需要审核日志

如果这是功能请求,请回复 '/feature'。如果这是一个问题,请回复 '/question'。 否则,请按照以下说明附加日志,除非添加日志,否则您的问题将不会被审核。这些日志将帮助我们了解您机器中发生的情况。

如何收集 WSL 日志

查看类似问题

请查看下面的问题,看看它们是否解决了您的问题,如果该问题描述了您的问题,请考虑关闭此问题并点赞另一个问题,以帮助我们确定其优先级!

已关闭类似 issue:

注意:您可以通过竖起大拇指或竖起大拇指来为我提供反馈。

I don't know why I can't collect it

@THEBO666
Copy link
Author

Copy link

No logs.etl found in the archive. Make sure that you ran collect-wsl-logs.ps1 as administrator and that the logs.etl file is in the archive.

Diagnostic information
.wslconfig found
Detected appx version: 2.3.14.0
No logs.etl found in archive.
Error while parsing the logs. See action page for details

@THEBO666
Copy link
Author

Copy link

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information
.wslconfig found
Detected appx version: 2.3.14.0
Found no WSL traces in the logs

@THEBO666
Copy link
Author

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

.wslconfig found
Detected appx version: 2.3.14.0
Found no WSL traces in the logs

image

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

No branches or pull requests

1 participant