-
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
'fontFace' not working for any profile after system reboot. #3257
Comments
I assume, issue #3250 is the same issue. Just wanted to create a new issue since that one is lacking any information. |
Which font specifically are you using? "Powerline Fonts" isn't terribly descriptive. Does the font work in other applications after rebooting? Can you share a screenshot of it working in Windows Terminal before rebooting? Thanks. |
Roboto Mono for Powerline at first, then Noto Mono for Powerline, DejaVu Sans Mono for Powerline and even with Courier New. It seems that every profile gets the fallback to the default font, no matter the
Outside of the terminal (Using the conhost setting dialogue the fonts work excluding Roboto Mono which is bugged atm (See #295, respectively google/fonts#1832), so that ones off the table for me).
Unfortunately I can't provide a screenshot from before restarting Windows. But I'll go check, if restarting Windows and/or reinstalling Terminal helps. |
Ok, reinstalling the terminal and or restarting Windows didn't work. Next will be another restart or two to see, if it breaks again. |
Ok, same issue after a restart. I've tried to install only a single set: DejaVu Sans Mono for Powerline. It worked, till I've restarted Windows. In short: Reinstalling the font fixes it and restarting Windows breaks it again. Currently I'm too tired to hunt that issue down any more. |
This is really fascinating! I wonder if it reproduces on v0.6? Sorry, I've never seen anything like this before, but we did make some font changes in that release. |
Also, if you install the font "for all users" instead of just plain installing it, does it work after a reboot? This might be something fun for the font team to look at. |
@DHowett-MSFT wrote:
Yes, it reproduces with: Windows Terminal (Preview) Version: 0.6.2951.0
Yes, this works fine after a reboot.
Did a couple more restarts and installing and uninstalling of fonts, what I've found out so far: So the steps to reproduce should be: Steps to reproduce
Expected behaviourBoth fonts always work. Actual behaviorThe globally installed (aka for all users) font works fine, the locally installed font breaks/won't load unless you restart the FontCache or disable the service before restarting Windows. |
Oh and btw: I wonder, if its the FontCache to blame or how Windows Terminal utilizes it. I guess a bit of both, since the issue with the FontCache described above only exists in the Terminal. |
So, Terminal isn't doing anything special with the font cache. We're using DirectWrite, the text rendering API, like most other apps on the system are. Now, I've got one last crazy idea before I escalate this to the fonts team: If you introduce a delay (say, 30-60 seconds) between steps 6 and 7 ... does it work for you? Sorry to make you jump through so many hoops. |
I doubt it does since I usually do a bunch of other thing before restarting the terminal, but I can test it one last time. Gimme a min or ten. |
😁 I'm wrapping this all up to escalate to the team who owns font handling on Windows, since it looks like we're doing "everything we can" here. |
Apparently, reinstalling Windows also fixes this. Just upgraded my GPU from Nvidia to AMD and Windows started crashing periodically. Even after using GPU driver removal tool and reinstalling AMD, so I tried reinstalling Windows. Both issues seem to be fixed. No crashing and No font problems in wt. No idea what causes the issue but, in my case, reinstalling Windows seems have resolved it. That is a horrible solution. I wish someone could have helped debug the cause of the issue. |
Currently in the camp where none of the proposed workarounds remedy the issue for me. Anyone manage to resolve this issue with any of the Iosevka Nerd Fonts in a way not listed above? |
+1 Having this w/ multiple fonts. Victor Mono as of today. |
I seem to have fixed this issue on Windows 11 latest updates as of 7/4/2023: windows key -> services -> services (local) -> Windows Font Cache Service In this window, select tab "Log On", and use "Local System Account", also check "Allow service to interact ..." Click "Ok" Then stop and start service |
Okay so housecleaning time. Internally, this is tracked by MSFT:42103854. After the last couple PRs we did in this area, we're pretty confident there's nothing more that we (the Terminal team) can do on our side here to mitigate this. This is pretty clearly still an issue. I'm bumping the internal thread to see how we can get this fixed in the OS. I've decided that even though there's nothing more we (the Terminal team) can do to fix this on our side, I'm going to leave this one open. Folks have a hard enough time searching for existing open issues, let alone closed ones. This is super painful when it does hit, so I think it warrants being left open regardless of if there's any work we can do to fix it. I have no idea when this'll be fixed, but I'll make sure to share any relevant internal updates here in this thread. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Please use upvotes/reactions if you agree with a post. A lot of people are subscribed to this thread and each confirmation pings everyone every time, so please avoid doing that. I'm collapsing the above comments as off-topic. |
sorry...right click on what? |
On the font you want to install? |
Can confirm I am still having this issue with fonts in Windows Terminal on Windows 11 Pro. |
This superuser answer worked for me on windows 11 |
Interesting. In my case, even if I reinstall the fonts in Settings -> Personalization -> Fonts, I still have the error when I try to use the font in the terminal. What did work for me was to remove the fonts, clear the Windows Font Cache Service, and reinstall the fonts for all:
I verified that after rebooting or shutting down, all the nerd fonts are still available in Settings -> Personalization -> Fonts, and correctly set in my Terminal. |
This works for me. Thanks! |
Environment
Steps to reproduce
fontFace
for various profiles (Tested with powershell, cmd and Ubuntu WSL)Note, that everything was working as intended up to here.
Expected behavior
The font setting being applied:
Actual behavior
After restarting Windows
fontFace
is being ignored:Additional Info
My current profiles.json: profiles.txt
The text was updated successfully, but these errors were encountered: