Hey, fellow Krita artists.

I have switched to Krita more than 3 years back and never seriously considered other software ever since. There were some minor glitches that the dev team quickly eradicated down the road. But this bug appeared on my system beginning with version 4.2.8 and persists until now. The point is whenever I try to scroll through the fonts in the text tool menu - all fonts suddenly are reduced to tiny dots or just empty placeholders. And outside Krita all fonts disappear for like 5 minutes after I close the program. I first suspected the custom fonts. But getting rid of them did not help. Maybe someone else has this bug, or this is just my glitchy Win 10?

I am afraid this is a glitchy windows 10. The only thing we do is load the fonts, then make a little dropdown where we draw a preview of the font. If that is messed up, then Krita (via qt framework) is unable to load the fonts right, which implies windows is having a hard time.

TheraHedwig wrote:I am afraid this is a glitchy windows 10. The only thing we do is load the fonts, then make a little dropdown where we draw a preview of the font. If that is messed up, then Krita (via qt framework) is unable to load the fonts right, which implies windows is having a hard time.

Thanks, man.
Yeah, I have already grown accustomed to pick a font without opening the font list. Let's hope the devs will eventually find a workaround to that issue

If we could find a way to reproduce this... Can you make a bug report with a screenshot or screen recording, adding the contents of help->system information for bug reports to it?

boudewijn wrote:If we could find a way to reproduce this... Can you make a bug report with a screenshot or screen recording, adding the contents of help->system information for bug reports to it?

Sure.
Here's the short video on how it looks on my desktop https://www.youtube.com/watch?v=c9zYhnV ... e=youtu.be
And here I created a bug report best I could.
https://bugs.kde.org/show_bug.cgi?id=423166

I think boud meant a bug report at bugs.kde.org

TheraHedwig wrote:I think boud meant a bug report at bugs.kde.org

Thanks, I corrected that.
Not really familiar with that bug tracking system, so I beg pardon if I did something wrong.

Case closed. Windows 10 cannot tell the bad fonts from normal ones and crashes. So the font error is system-related. Krita is ok. False alarm.

kritzien wrote:Case closed. Windows 10 cannot tell the bad fonts from normal ones and crashes. So the font error is system-related. Krita is ok. False alarm.

Curious... Back in the Windows NT 3.0 days, you could crash windows with a special truetype font (like the one HP installed with its printer drivers) -- just select it in Word, and poof. That's because a TTF contains a complete programming language (for kerning), and the code for that would be run in RING 0, that is, the most privileged part of the OS. Apparently that's still the case...