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

[Bug]: Can't connect to WSL due to "unable to determine os" after disk repair #1666

Open
1 of 3 tasks
JackTheMico opened this issue Jan 2, 2025 · 5 comments
Open
1 of 3 tasks
Labels
bug Something isn't working triage Needs triage

Comments

@JackTheMico
Copy link

Current Behavior

I have two WSLs but can't connect to any of those through Waveterm.
Here are the error screenshots:
image
image

Expected Behavior

Be able to connect to WSL through Waveterm.

Steps To Reproduce

  1. Install the latest version of Waveterm.
  2. Click connect button to connect to a WSL.

Wave Version

v0.10.4(202412210247)

Platform

Windows

OS Version/Distribution

Windows11 23H2

Architecture

x64

Anything else?

I exported and re-imported those two WSLs before because of a disk repair.

Questionnaire

  • I'm interested in fixing this myself but don't know where to start
  • I would like to fix and I have a solution
  • I don't have time to fix this right now, but maybe later
@JackTheMico JackTheMico added bug Something isn't working triage Needs triage labels Jan 2, 2025
@esimkowitz
Copy link
Member

are you able to connect to these WSL distros normally after your disk repair?

@esimkowitz esimkowitz changed the title [Bug]: Can't connect to WSL due to "unable to determine os" [Bug]: Can't connect to WSL due to "unable to determine os" after disk repair Jan 2, 2025
@JackTheMico
Copy link
Author

are you able to connect to these WSL distros normally after your disk repair?

Yes, I can run wsl or wsl -d kali-linux to connect to distros normally.

@esimkowitz
Copy link
Member

Got it, could you send me your log file? You can find the path to it by running `wsh wavepath configuration. You can send it to [email protected]

@JackTheMico
Copy link
Author

Got it, could you send me your log file? You can find the path to it by running `wsh wavepath configuration. You can send it to [email protected]

Thank you! I have sent the email and attached the log file. BTW, I think the command had been changed to wsh wavepath log.

@esimkowitz
Copy link
Member

Thanks! It hasn't changed, I just shouldn't try to write comments at 2am 😂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage Needs triage
Projects
None yet
Development

No branches or pull requests

2 participants