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

Default user stopped being respected (only on WSLv1 profiles, WSLv2 are okay) #10874

Closed
1 of 2 tasks
vadimkantorov opened this issue Dec 5, 2023 · 3 comments
Closed
1 of 2 tasks
Assignees

Comments

@vadimkantorov
Copy link

vadimkantorov commented Dec 5, 2023

Windows Version

Microsoft Windows [Version 10.0.22621.2715]

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

No response

Distro Version

Linux version 4.4.0-22621-Microsoft (Microsoft@Microsoft.com) (gcc version 5.4.0 (GCC) ) #2506-Microsoft Fri Jan 01 08:00:00 PST 2016

Other Software

No response

Repro Steps

On my machine I have both WSLv1 and WSLv2 distros and Terminal profiles.

For many years I had it somehow set up that WSLv1 profile in my Terminal logs me in as vadimkantorov by default. I just rebooted the laptop, and somehow WSLv1 logs me into as root. I created a /etc/wsl.conf with

[user]
default=vadimkantorov

but it did not help.

WSLv2 profiles still log me in as vadimkantorov correctly

The ubuntu.exe config --default-user vadimkantorov affects only WSLv2 as it appears

How can I fix my WSLv1 to log me in as vadimkantorov?


UPD: I just fixed it by appending --user vadimkantorov to my wsl.exe command line in Terminal config: https://superuser.com/a/1566031/813257, but it would still be nice to know how to fix it from within the distro, as /etc/wsl.conf appears to have no effect

@vadimkantorov vadimkantorov changed the title Default user stopped being respected Default user stopped being respected (only on WSLv1 profiles, WSLv2 are okay) Dec 5, 2023
@OneBlue
Copy link
Collaborator

OneBlue commented Dec 5, 2023

/logs

@benhillis
Copy link
Member

I was not able to reproduce this. dmesg likely has some errors.

@vadimkantorov
Copy link
Author

vadimkantorov commented Dec 13, 2023

@benhillis If I stumble on this again, I'll add information. For now, it seems to me that it might have coincided with some Windows Update - and this might have been the reason.

I also had spurious keyboard layouts added to Windows (this is a 15-years old Windows bug affecting all non-English layout users, but still not fixed), and this is typically a sign that Windows had installed some update.

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

3 participants