starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Can't load see or load profile after changing bellStyle setting #14892

New Issue
Closed
opened 2026-01-31 04:22:31 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 04:22:31 +00:00
Owner
Copy Link

Originally created by @bcalvery on GitHub (Aug 17, 2021).

Windows Terminal version (or Windows build number)

1.10.1933.0

Other Software

Ubuntu 20.04

Steps to reproduce

I have Ubuntu as my default profile in Windows Terminal. And Windows Terminal configured to start automatically.
Open Settings > Profiles > Ubuntu 20.04 > Advanced > Bell Notification Style
Uncheck "Audible"

My resulting settings.json file looks like this:
image

This setting change works correctly correctly until the next time I restart the computer. After restarting the computer when Windows Terminal opens I get this:
image
and Ubuntu is no longer visible in the new tab or settings menu:
image

If I then go to settings, open the settings.json and delete the line "bellStyle": "none", from the Ubuntu profile, that profile immediately becomes visible again.

Expected Behavior

I expect changing a profile's "Bell Notification Style" (bellStyle) property by unchecking "Audible" (changing value to "none") to not cause the profile to fail to load.

Actual Behavior

Changing a profile's "Bell Notification Style" (bellStyle) property by unchecking "Audible" (changing value to "none") causes terminal to be unable to load that profile.

Originally created by @bcalvery on GitHub (Aug 17, 2021). ### Windows Terminal version (or Windows build number) 1.10.1933.0 ### Other Software Ubuntu 20.04 ### Steps to reproduce I have Ubuntu as my default profile in Windows Terminal. And Windows Terminal configured to start automatically. Open Settings > Profiles > Ubuntu 20.04 > Advanced > Bell Notification Style Uncheck "Audible" My resulting settings.json file looks like this: ![image](https://user-images.githubusercontent.com/15043460/129727408-e65a5c54-0ff2-413a-9c6a-ebce4c9271da.png) This setting change works correctly correctly until the next time I restart the computer. After restarting the computer when Windows Terminal opens I get this: ![image](https://user-images.githubusercontent.com/15043460/129727751-52cc3977-1d1d-4839-b466-3cedf6e238ce.png) and Ubuntu is no longer visible in the new tab or settings menu: ![image](https://user-images.githubusercontent.com/15043460/129729061-91519ec9-549b-4347-87d0-8cf2a88451c7.png) If I then go to settings, open the settings.json and delete the line `"bellStyle": "none",` from the Ubuntu profile, that profile immediately becomes visible again. ### Expected Behavior I expect changing a profile's "Bell Notification Style" (bellStyle) property by unchecking "Audible" (changing value to "none") to **not** cause the profile to fail to load. ### Actual Behavior Changing a profile's "Bell Notification Style" (bellStyle) property by unchecking "Audible" (changing value to "none") causes terminal to be unable to load that profile.
claunia added the Resolution-Duplicate label 2026-01-31 04:22:31 +00:00
claunia commented 2026-01-31 04:22:32 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 17, 2021):

Alright so I think the bell style thing might just be a red herring here. WSL is actually notoriously bad at telling the Terminal in a reasonable period of time what the list of profiles is.

See for example: #6160, #7199, #9905. The "restarting the computer" bit of the repro also is a good givaway that the issue is due to the fact that the first time wsl.exe is launched, it starts up fairly slowly.

/dup #6160

@zadjii-msft commented on GitHub (Aug 17, 2021): Alright so I think the bell style thing might just be a [red herring](https://c.tenor.com/PACZT4i8fEIAAAAC/communism-red-herring.gif) here. WSL is actually notoriously bad at telling the Terminal in a reasonable period of time what the list of profiles is. See for example: #6160, #7199, #9905. The "restarting the computer" bit of the repro also is a good givaway that the issue is due to the fact that the _first_ time wsl.exe is launched, it starts up fairly slowly. /dup #6160
claunia commented 2026-01-31 04:22:32 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 17, 2021):

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!

@ghost commented on GitHub (Aug 17, 2021): 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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14892
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?