Apache OpenOffice (AOO) Bugzilla – Issue 2417
Writer crashes with font: MSLineDrawPSMT
Last modified: 2002-05-16 10:20:17 UTC
Any attempt to use this font with the menu: "Format => Character" results in a crash. When scrolling through the fonts with the toolbar window, just before I get to this font, Writer crashes.
Reassigned to Ulf.
Reassigned.
Please attach the font. Thanx.
I very much doubt it's MS Linedraw. I knock heads with a very similar bug, where the cursor gets stuck on the font dropdown when it comes somewhat down the L... fonts. I started deleting TT fonts one by one, thinking they were the culprit, and at first I also thought it was MS Linedraw. After having deleted my way through linedraw.ttf mapsym.ttf and outlook.ttf I could see further down in the font dropdown in Write than before, now all the way to "Luxidux Serif" (?) and now it got stuck there. I see no crash however - just the "stuck in selection mode" thing. Result is very much the same of course - i have to killall soffice-bin to get out of the situation. Not so tempted to delete more fonts, but can this be some oddity with the NUMBER of fonts available?
this one, issue 2143 and issue 2423 may be the same.
Reassigned to Herbert Duerr.
Looks related 2143. Can you please do: strace -f 2>&1 soffice | tee strace.out fgrep open strace.out | tail and copy the results here? Also a dozen lines after the last open() in strace.out would be very interesting.
Since this seems related to 2143 probably a version with debug info would help. Since the 1.6MB file is too big to attach to this bug, can I send it to you via email?
No installation of OpenOffice I tested has ever discovered my truetype fonts. Even if they are configured for X, work in all other apps, and reside in /usr/X11R6/lib/X11/fonts/TrueType/ This also goes for OO-641. I thus follow the hint from issue 1348 and add the path to SAL_FONTPATH_PRIVATE in /program/soffice The syntax I use is valid, and after new start, OpenOffice suddenly sees TT fonts, and even antialias the whole UI.. Mentioning this just in case OpenOffice somewhere "backstage" may see the tt fonts after all...just not "revaling" them in the font dropdown box in writer before i add to private path, and the extra path per chance can cause some "collision". As far as i remember, Draw will see TT fonts without the extra path added. I'm running a default RH7.1 install + errata. No extra installations here should affect font rendering in any way.
Background info: Writer defaults to Printing-layout mode where it only displays fonts it also knows how to print. It knows how to print fonts when it can access the font files are. It didn't find the font files because they are not in the font path but hidden behind a font server. In the newest CVS versions also the font server's paths are analyzed so this problem will be fixed. Draw defaults to Online-layout so you could see the fonts. You can also switch Writer to this mode in the View menu. Does it still crash with the font, now that you are using SAL_FONTPATH_PRIVATE? Did it antialias before? Can you provide a stack trace? You can do this by attaching gdb when it hangs and executing the bt command.
>Does it still crash with the font, now that you are using >SAL_FONTPATH_PRIVATE Personally i don't crash - i just get a hang where the mouse cursor stays forever in "select" position. X becomes useless so i have to escape to console with ctrl+alt+F2 to kill it from there, and then return to the X session with ctrl+alt+F7. >Did it antialias before? It doesn't antialias untill i add the SAL_PRIVATE_FONTPATH for my tt fonts. On next start, ALL is antialiased, also the fonts in the UI. >Can you provide a stack trace? You can do this by attaching >gdb when it hangs and executing the bt command. I haven't figured out how to save the output from an attached gdb from console, which is where i would have to do it since X is "locked off" at this point. But i did discover something else interesting: A line in soffice startup script reads: # uncomment line below to disable anti aliasing of fonts #SAL_ANTIALIAS_DISABLE=true; export SAL_ANTIALIAS_DISABLE I found that if I uncomment that line, the hang does NOT occure, and I still have access to all the TT fonts, allthough now un-aliased and not so pretty looking. I can scroll all i want to in the dropdown though, with no badness occuring. I'd like to add that i'm not the original reporter here - i just attached myself to this bug ;) The crash may or may not be another issue.
Moving from SW to GSL
There is an in my opinion related issue 2423 that just got resolved. Would you like to test if the fixes there also solve the problems you experienced? Since the 1.6MB file is too big to attach it here can I send it to you via email?
Mail is fine: dark@c2i.net
> That worked just great: Re-adding antialiasing and I can now scroll > through the whole font dropdown fine - back and forth. I'm glad the fixes for issue 2423 fixed this problem too. I'm wondering if they work for the original reported Mr. Tyrer too. > However: It now turns out that of the fonts i have installed, a > handfull doesn't display with name in the dropdown, only the AA > icon indicates there is a font there. > Fontname appear in the name-box when i select the font, however > - so it may be a sizing issue. Names of the mysterious fonts in > clear text are >... > > Typical for these are that they are all "decorative" fonts. > > I can mail you the offending font-files if you wish. > The fonts.dir file (and .scale) I use is the "default" generated > version under RH7.1 however - no tweaking done. By default names in a font list are displayed in their own font style. Symbol font names are displayed in the UI font style. If the fonts.dir does not identify them as symbol fonts there is a problem. Also decorative fonts often cannot display their own name so we have to fall back to Andale Sans UI. For OOo there is no fallback font, see issue 1990.
Unless the original reporter of the bug disagrees by reopening the issue I'm setting the status to fixed.
closing.