-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
An unexpected profile appearing in dropdown called "Default" #9304
Comments
Any update on this yet?? |
@carlos-zamora, you've been working on the SUI mostly, wanna take a first stab at investigating this?
@Krrishdhaneja FYI we generally don't check our work emails on the weekend, and largely only work M-F, 9-5. We appreciate you patience |
No problem! Btw what is SUI? |
SUI = the Settings UI |
@Krrishdhaneja Since you were using the Settings UI, looks like you were doing this on Windows Terminal Preview. This morning, we just updated preview to 1.7.572.0. I'm not able to get a repro. Do you mind seeing if you're still experiencing this with the new update? If so, could you provide more clear instructions on what's causing it? (changing the default profile and saving isn't causing it for me). Thanks! |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
Reopening and moving to v1.9 |
What can be the possible reason for this behavior to happen? Can you please tell? |
If we knew, we'd tell you! That's what we've got to investigate here. Could you share the contents of your |
Here is my
|
All of a sudden I got this same issue.
Then, i found that Terminal now showed a default profile. When i opened settings.json, i found a stray profile (note that this profile was in addition to the wsl profile) -
Without a "name" property, the name defaulted to Default. It looks like some bug with the code that reads/writes from the SUI to the json file. For some reason, instead of updating a profile, it is creating a new profile with the only property that the user was trying to modify. It might also be related to some wsl handling. |
Any update on this? |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
Environment
Steps to reproduce
When I tried to change the default profile, a new cmd.exe admin profile called "Default" emerged ->
Expected behavior
Expected that it would change the default profile from powershell to fedora(installed using rootfs)
Actual behavior
Another new profile emerged called "Default" which I didn't made!
The text was updated successfully, but these errors were encountered: