Inskape crashes on using Times New Roman

[Alvaro Olmos]

Inkscape crashes on using Times New Roman font.

Windows version: Microsoft Windows [Version 10.0.17134.286]
Inscape version: 0.92.3 (2105546, 2018-03-11)

Steps to reproduce:
1. Open Inkscape
2. Select Font tool (F8)
3. Write text
4. Open Text Tool (Shift + Ctrl + T)
5. Select Font "Times New Roman"

[Patrick Storz (ede123)]

I'm afraid we need more information to be able as this is obviously not a general issue but likely specific to your system.

First of all can you try to reset your preferences [1] and see if it solves your problem?

If that does not help, please launch Inkscape from commandline (cmd.exe). Navigate to Inkscape's installation directory and execute "inkscape.com" (not inkscape.exe!). If any messages are printd to the console please attach them here.

[1] https://inkscape.org/en/learn/faq/#how-reset-user-preferences

[Alvaro Olmos (olmosunreal)]

[1] Didn't solve the problem.

This is the console print:

Warning: Font face with same CSS values already added: Times New Roman Normal (Standaard, Normál)
Warning: Font face with same CSS values already added: Times New Roman Italic (kurzÝva, ╬á╬╗╬¼╬│╬╣╬▒)
Warning: Font face with same CSS values already added: Times New Roman Bold Italic (terminate called after throwing an instance of 'Glib::ConvertError'

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.

[Patrick Storz (ede123)]

Ah, that's interesting. It seems something's choking on the localized versions of "normal/bold/italic".

What locale are you using?

Just to be sure: Did you install any variants of Times New Roman or just the stock font that ships with Windows?

[Alvaro Olmos (olmosunreal)]

Locale: Español (Colombia)

I didn't install any variant, those are Windows' fonts.

[Alvaro Olmos (olmosunreal)]

CurrentCulture : es-CO
CurrentUICulture : es-ES

[Alvaro Olmos (olmosunreal)]

Same error with some other Windows' fonts:

[Selected Arial font]
Warning: Font face with same CSS values already added: Arial Normal (Standaard, ΚαΛοΛικά)
Warning: Font face with same CSS values already added: Arial Italic (kurzÝva, ╬á╬╗╬¼╬│╬╣╬▒)
Warning: Font face with same CSS values already added: Arial Bold Italic (terminate called after throwing an instance of 'Glib::ConvertError'

[Selected Courier New]
Warning: Font face with same CSS values already added: Courier New Normal (Standaard, ΚαΛοΛικά)
Warning: Font face with same CSS values already added: Courier New Italic (kurzÝva, ╬á╬╗╬¼╬│╬╣╬▒)
Warning: Font face with same CSS values already added: Courier New Bold (terminate called after throwing an instance of 'Glib::ConvertError'

[Selected Palatino Linotype font]
Warning: Font face with same CSS values already added: Palatino Linotype Bold (terminate called after throwing an instance of 'Glib::ConvertError'

Other 2428 fonts without error.

[Thomas Wölfer (twoelfer)]

I have the same problem with Inkscape 0.92.3 (2405546, 2018-03-11) on Windows 10 1803, Build 17134.407, german locale.

[Patrick Storz (ede123)]

German locale?

Now I'm wholly confused, I assumed this was a character encoding issue of the font names, but German font names shouldn't contain any non-ASCII characters (or do you happen to see any accents / umlauts / whatever in a font name anywhere?).

[Thomas Wölfer (twoelfer)]

This is what I get at the console after the error occurs:

[...]
(inkscape.exe:12980): Pango-WARNING **: couldn't load font "Xschrift Not-Rotated 9", falling back to "Sans Not-Rotated 9", expect ugly output.
(inkscape.exe:12980): Pango-WARNING **: couldn't load font "Zetadrei Not-Rotated 9", falling back to "Sans Not-Rotated 9", expect ugly output.
Warning: Font face with same CSS values already added: Times New Roman Normal (Standaard, Normál)
Warning: Font face with same CSS values already added: Times New Roman Italic (kurzÝva, ╬á╬╗╬¼╬│╬╣╬▒)
Warning: Font face with same CSS values already added: Times New Roman Bold Italic (terminate called after throwing an instance of 'Glib::ConvertError'

In this case I just selected the text tool and tried to change the font to "Times New Roman"

The "couldn't load font" message before the actual error is printed once for about 90 times. Whereas overall there are 513 fonts installed.

The problem only occurs when I select one of the (original Windows) fonts: Arial, Courier New and Times New Roman. All the other fonts seem to work. I even have a font called "Südspur" with a german umlaut which doesn't make this problems. I just isn't displayd correct instead of the real Südspur inscape just displays it as a generic sans-serif font. But that maybe another problem.

[Patrick Storz (ede123)]

Ah, but you *do* have non-Ascii characters in the font styles (that are obviously not German for some reason).

I'm not sure where it goes wrong unfortunately and wasn't able to reproduce myself so far.

One thing you could try:
- Exit Inkscape
- Open Windows Explorer and go to "%localappdata%\fontconfig"
- Rename the "cache" folder
- Restart Inkscape and check if it still crashes.

In the best case it's only a corruption of the font cache which would help us narrow it down.

[Thomas Wölfer (twoelfer)]

Renaming the cache folder does not solve the problem. Inkscape still crashes and the output I get after the crash stays the same.

[Qantas94Heavy (qantas94heavy)]

Can reproduce with Inkscape 0.92.3 but not 0.92.4 on Windows 10 x64 1803, so marking as fixed.

If this is still an issue, please comment with details and I'll reopen the bug. Thanks!

[Alvaro Olmos (olmosunreal)]

Problem fixed, no crash with:

Inkscape 0.92.4 (5da689c313, 2019-01-14)
Microsoft Windows x64 [Versión 10.0.17134.648]

[Thomas Wölfer (twoelfer)]

With my installation the problem still persists.

Inkscape 0.92.4 (5da689c313, 2019-01-14)
Microsoft Windows 10 Home (x64) Version 10.0.17763 Build 17763

[Bryce Harrington (bryce)]

Hi, this defect appears to have already been registered in our new bugtracker on gitlab, here:

https://gitlab.com/inkscape/inbox/issues/219

Unfortunately, it doesn't look like a full solution is at hand, and work is still needed to understand the problem, but we'll focus efforts on that bug report going forward, and I'll close this one out.

Moved to: https://gitlab.com/inkscape/inbox/issues/219
Closed by: https://gitlab.com/bryceharrington