Bug 58294 - undefined: certain font crashes writer and calc
Summary: undefined: certain font crashes writer and calc
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected) release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Keywords: regression
Depends on:
Reported: 2012-12-14 14:50 UTC by Jean-Paul Maley
Modified: 2013-03-22 09:47 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Paul Maley 2012-12-14 14:50:10 UTC
Problem description: 
SEGDT.TTF (Solid Edge font) crashes writer and calc
Steps to reproduce:
1. open writer (new empty file opens)
2. scroll through fonts
3. at SEGDT.TTF it crashes

Current behavior:
at SEGDT.TTF it crashes
Expected behavior:
at SEGDT.TTF it doesn't crash
Operating System: Windows 7
Last worked in: release
Comment 1 Jean-Paul Maley 2012-12-14 14:57:23 UTC
when replacing the bugged font in options-fonts you can eliminate the bug
Comment 2 Jean-Paul Maley 2012-12-14 14:58:57 UTC
also in
Comment 3 Julien Nabet 2012-12-15 00:07:13 UTC
Jean-Paul: could you tell where SEGDT.TTF could be retrieved for testing?
Comment 4 Jean-Paul Maley 2012-12-15 10:19:53 UTC
It is a font from Siemens: Solid Edge. Its propriety CAD software so i don't know if i can provide it. I'll ask my software provider.
Comment 5 Julien Nabet 2012-12-15 10:56:06 UTC
2 possibilities too:
1) Get a backtrace from Windows (see http://wiki.documentfoundation.org/BugReport#How_to_get_a_backtrace_.28on_Windows.29)
2) If you have Linux on a workstation, you can install your font in it (just for the test) and retrieve more easily a backtrace (see http://wiki.documentfoundation.org/BugReport#How_to_get_a_backtrace_.28on_Linux.29)
Comment 6 retired 2013-03-22 09:47:39 UTC
No feedback from bug reporter for a very long time.

@Jean-Paul: Could you please test if this issue is still valid when using LO 4? If that is the case, please re-open the bug. It would be great if you could also provide the requested backtrace so this problem can be dealt with.