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

Bug Report - Windows Terminal doesn't start with some characters #2755

New Issue
Closed
opened 2026-01-30 23:04:13 +00:00 by claunia · 10 comments
claunia commented 2026-01-30 23:04:13 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Jul 14, 2019).

Environment

Windows Terminal version: Microsoft Windows [Version 10.0.18362.239]
Linux subsystem in Windows <a href="https://www.microsoft.com/en-us/p/kali-linux/9pkr34tncv07?activetab=pivot:overviewtab" target="_blank">(you can download it from here!)</a><a href="https://www.kali.org/news/kali-linux-in-the-windows-app-store/" target="_blank">(and the docs here!)</a>
Dual boot with Linux

Steps to reproduce

If i change the settings of the Windows Terminal, create a new profile and set it default with Linux (not powershell or cmd) , modify the property 'fontFace' from 'Consolas' to 'Rubik' (font on fonts.google.com). Close all windows and try to open Windows Terminal it won't open, if i change it back to 'Consolas' and try to open it this time it will start.

Expected behavior

Change the font and work properly.

Actual behavior

App doesn't start.

Originally created by @ghost on GitHub (Jul 14, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows Terminal version: Microsoft Windows [Version 10.0.18362.239] Linux subsystem in Windows <a href="https://www.microsoft.com/en-us/p/kali-linux/9pkr34tncv07?activetab=pivot:overviewtab" target="_blank">(you can download it from here!)</a><a href="https://www.kali.org/news/kali-linux-in-the-windows-app-store/" target="_blank">(and the docs here!)</a> Dual boot with Linux ``` # Steps to reproduce If i change the settings of the Windows Terminal, create a new profile and set it default with Linux (not powershell or cmd) , modify the property 'fontFace' from 'Consolas' to 'Rubik' (font on fonts.google.com). Close all windows and try to open Windows Terminal it won't open, if i change it back to 'Consolas' and try to open it this time it will start. # Expected behavior Change the font and work properly. # Actual behavior App doesn't start.
claunia added the Area-SettingsIssue-BugResolution-DuplicateProduct-Terminal labels 2026-01-30 23:04:14 +00:00
claunia commented 2026-01-30 23:04:15 +00:00
Author
Owner
Copy Link

@gifuthornberkanan commented on GitHub (Jul 14, 2019):

I'm getting the same issue but it seems inconsistent which fonts trigger this.

For me 'Droid Sans Mono for Powerline' does work but 'Droid Sans Mono Slashed for Powerline' and 'Droid Sans Mono Dotted for Powerline' both cause the app to crash.

Also in addition to the OP's description of the problem, I also noticed that if you have the profiles.json open at the same time as the terminal app, and then change the font to a "bad" font and Save, the terminal crashes and closes right away.

Lastly, In addition to wsl.exe, I'm also experiencing this with Powershell 5.1 and cmd.

@gifuthornberkanan commented on GitHub (Jul 14, 2019): I'm getting the same issue but it seems inconsistent which fonts trigger this. For me 'Droid Sans Mono for Powerline' does work but 'Droid Sans Mono Slashed for Powerline' and 'Droid Sans Mono Dotted for Powerline' both cause the app to crash. Also in addition to the OP's description of the problem, I also noticed that if you have the profiles.json open at the same time as the terminal app, and then change the font to a "bad" font and Save, the terminal crashes and closes right away. Lastly, In addition to wsl.exe, I'm also experiencing this with Powershell 5.1 and cmd.
claunia commented 2026-01-30 23:04:15 +00:00
Author
Owner
Copy Link

@gifuthornberkanan commented on GitHub (Jul 14, 2019):

Just did a little more quick testing and if you set the "fontFace" property to a non-existant font, the terminal does not crash.

I tried setting it to 'Draid Sans Mono for Powerline' (which is not a real or installed font on my system) and also 'Courier Old' (also not real) and the terminal didn't crash but the font size did change to what looked like a 1 point font.

So it seems like specific fonts are causing it to crash as opposed to not being set to a real/installed font.

@gifuthornberkanan commented on GitHub (Jul 14, 2019): Just did a little more quick testing and if you set the "fontFace" property to a non-existant font, the terminal does not crash. I tried setting it to 'Draid Sans Mono for Powerline' (which is not a real or installed font on my system) and also 'Courier Old' (also not real) and the terminal didn't crash but the font size did change to what looked like a 1 point font. So it seems like specific fonts are causing it to crash as opposed to not being set to a real/installed font.
claunia commented 2026-01-30 23:04:15 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 14, 2019):

Just did a little more quick testing and if you set the "fontFace"property to a non-existant font, the terminal does not crash.

If you try something that he doesn't like (false settings, non existing fonts, ecc,) the terminal strt with the default settings ("factory default").
that is normal (i think).
Anyway Good job with the Terminal, keep it up :-D

@ghost commented on GitHub (Jul 14, 2019): > > > Just did a little more quick testing and if you set the "fontFace"property to a non-existant font, the terminal does not crash. If you try something that he doesn't like (false settings, non existing fonts, ecc,) the terminal strt with the default settings ("factory default"). that is normal (i think). Anyway Good job with the Terminal, keep it up :-D
claunia commented 2026-01-30 23:04:15 +00:00
Author
Owner
Copy Link

@gifuthornberkanan commented on GitHub (Jul 16, 2019):

I did more testing and I'm not sure if I'm having the exact same issue as the OP.

I'm pretty sure that the cause of my crashing is when I try to save with a font whose name is 32 characters or more.

Evidence:
"fontFace" : "Roboto Mono Light for Powerline" (font name is 31 chars) --> saves and font changes on the terminal (expected behavior)
"fontFace" : "Roboto Mono Light for Powerlinex" (font name is 32 chars) --> terminal immediately crashes

"fontFace" : "Roboto Mono Thin for Powerline" (font name is 30 chars) --> saves and font changes on the terminal (expected behavior)
"fontFace" : "Roboto Mono Thin for Powerlinex" (font name is 31 chars) --> not a real font so font displayed on terminal becomes 1 point
"fontFace" : "Roboto Mono Thin for Powerlinexx" (font name is 32 chars) --> terminal immediately crashes

I'd be interested to see if the OP's font actually has a longer name then just "Rubik". If not, then my problem might be different and I'll start my own issue.

@gifuthornberkanan commented on GitHub (Jul 16, 2019): I did more testing and I'm not sure if I'm having the exact same issue as the OP. I'm pretty sure that the cause of my crashing is when I try to save with a font whose name is 32 characters or more. Evidence: "fontFace" : "Roboto Mono Light for Powerline" (font name is 31 chars) --> saves and font changes on the terminal (expected behavior) "fontFace" : "Roboto Mono Light for Powerlinex" (font name is 32 chars) --> terminal immediately crashes "fontFace" : "Roboto Mono Thin for Powerline" (font name is 30 chars) --> saves and font changes on the terminal (expected behavior) "fontFace" : "Roboto Mono Thin for Powerlinex" (font name is 31 chars) --> not a real font so font displayed on terminal becomes 1 point "fontFace" : "Roboto Mono Thin for Powerlinexx" (font name is 32 chars) --> terminal immediately crashes I'd be interested to see if the OP's font actually has a longer name then just "Rubik". If not, then my problem might be different and I'll start my own issue.
claunia commented 2026-01-30 23:04:15 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 16, 2019):

If you do, make sure you look at #602!

@DHowett-MSFT commented on GitHub (Jul 16, 2019): If you do, make sure you look at #602!
claunia commented 2026-01-30 23:04:15 +00:00
Author
Owner
Copy Link

@gifuthornberkanan commented on GitHub (Jul 16, 2019):

Yup! That's my issue. I did try to look through the backlog but I guess I didn't look hard enough.

@gifuthornberkanan commented on GitHub (Jul 16, 2019): Yup! That's my issue. I did try to look through the backlog but I guess I didn't look hard enough.
claunia commented 2026-01-30 23:04:15 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 16, 2019):

I'd be interested to see if the OP's font actually has a longer name then just "Rubik". If not, then my problem might be different and I'll start my own issue.

As i said in the Original post you can go on https://fonts.google.com/ to 'test' fonts (Copy paste the names), if you want to see the font that i was talking about just go here ---> https://fonts.google.com/specimen/Rubik
[The answer to your question Is no]

@ghost commented on GitHub (Jul 16, 2019): > > > I'd be interested to see if the OP's font actually has a longer name then just "Rubik". If not, then my problem might be different and I'll start my own issue. As i said in the Original post you can go on https://fonts.google.com/ to 'test' fonts (Copy paste the names), if you want to see the font that i was talking about just go here ---> https://fonts.google.com/specimen/Rubik [The answer to your question Is no]
claunia commented 2026-01-30 23:04:16 +00:00
Author
Owner
Copy Link

@aguywithcode commented on GitHub (Aug 7, 2019):

Why is this closed? The OP said the bug wasn't due to font name length.

@aguywithcode commented on GitHub (Aug 7, 2019): Why is this closed? The OP said the bug wasn't due to font name length.
claunia commented 2026-01-30 23:04:16 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 7, 2019):

@mdizzy i don't know

@ghost commented on GitHub (Aug 7, 2019): @mdizzy i don't know
claunia commented 2026-01-30 23:04:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 8, 2019):

I think this is closed because it's a dupe of another issue that's known, but the actual issue wasn't linked here.

From playing around with the font myself, it looks like the bug is one of the following:

  1. Specifying a font name that doesn't actually exist causes the terminal to crash
  2. Rubik might not actually be a monospaced font.
  3. When I was playing with it, I say some artifacts similar to #610

image

  • "Rubik Regular" would not be found, and we'd fallback to Consolas
@zadjii-msft commented on GitHub (Aug 8, 2019): I think this is closed because it's a dupe of another issue that's known, but the actual issue wasn't linked here. From playing around with the font myself, it looks like the bug is one of the following: 1. Specifying a font name that doesn't actually exist causes the terminal to crash 2. Rubik might not actually be a monospaced font. 3. When I was playing with it, I say some artifacts similar to #610 ![image](https://user-images.githubusercontent.com/18356694/62707238-ab431f00-b9b6-11e9-9580-6c6aa2102efe.png) * "Rubik Regular" would not be found, and we'd fallback to Consolas
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 Area-Settings Issue-Bug Product-Terminal 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#2755
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?