Apache OpenOffice (AOO) Bugzilla – Issue 2758
641C crashes when scrolling through list of available fonts
Last modified: 2003-09-08 16:56:16 UTC
641C crashes when scrolling through list of available fonts. OO has been configured with additional truetype fonts (default Windows TT fonts). Crash occurs whether additional fonts are linked or copied into OO font directory (using spadmin.) When scrolling through the list of fonts in the toolbar, OpenOffice will crash. Does not occur with build 641.
Reassigned to Ulf.
Probably you have made a corrupt font available for OO. Try to isolate the font file which causes the crash and attach it to this issue.
I'm using the same fonts when running release 641 and I don't observe this problem. All fonts display fine in release 641. These are a set of core TT fonts that I've been installing in all releases for the past year. I've never observed this problem in any prior release. Anyways... I performed a clean install of 641C and installed NO additional truetype fonts. 641C still crashes. Crash occurs when font 'Goth' appears at bottom of font list (scrolling on line at a time by clicking on down buttom of scrollbar). The only Adobe font metric files that I could find were for font 'Gothic'. Looks like we have a winner. How/where do you remove 'internal' fonts?
I experience the exact same with 641c, and RH Linux 7.2 with RH's 2.4.17-1custom kernel. I also installed M$ fonts. If it does not crash attempting to Display it also crashes attempting to display the Microsoft Sans Serif font. If I change the font name to zzMicrosoft Sans Serif (using spadmin as root), the I sometimes can scroll the whole list, or sometimes the program will crash when Goth . . is reached.
I see this problem as well. Linux RH7.2 with MS tt fonts installed. But I don't believe that has anything to do with it. I scrolled through the list of fonts very quickly trying to get down to Verdana. The font list was only partially drawn - the first entry was partially drawn and the rest of the dropdown list was empty and then the program crashed.
Hmmm, I've been playing with this some more. In my case I can walk through every font in the dropdown until Verdana. It displays Verdana but after that soffice crashes. So, I went to Gnome and ran the Font Selector. The list matched what I remember from the dropdown in soffice. The next font after Verdana (microsoft) in font selector is Verdana (ult1 mo) and it says at the bottom of the font selector that "the selected font is not available". However, several other fonts in font selector have that status as well - alexandria for example, and this does not show up in the soffice font dropdown. The next one after Verdana (ult1 mo) in font selector is webdings and the next is zapf chancery. Back to soffice, I can type in Verdana as a font name and not use the font dropdown list. That works. I can type in webdings and that works, although nothing I type is displayed but the code points are recorded. I can type in zapf chancery and that works also. I hope all this is helpful.
reassigning - is that the way this works? what is the process?
1. Reassigning the bug is correct, because YOU have to find out exactly which font is corrupt on your system.(Pls. don't tell me "should be the font after font xyz in the list of tool abc. That does not help anybody. Font lists are individual on each Linux system.) To do so, please create a dummy text in the wordprocessor, select it and test with each font you'll find in the context menu (mouse button 3). This way you can isolate exact that font that causes the trouble. Pls. attach corrupt fonts to this bug. You may further investigate corrupt fonts by using the tool gfontview. 2. The fact, that you didn't encouter this problem in previous binary snapshots is due to the following: in previous OO snapshots, we weren't able to acces fonts on Linux systems which were provided by fontservers, as e.g. xfs (on RedHat an it's derivates). Therefor you should see an increased list of available fonts in OOo's wordprocessor in current versions.
*** Issue 2157 has been marked as a duplicate of this issue. ***
Look, when it comes to what we're discussing here - I'm an end user. But, I want to help. This is a very important cause IMHO. Looking at the font list seemed like it would be helpful. If I'd known about the right-click on text to and then select Font - I'd have told you about it. Ok, so there are two fonts that cause the crash. Wadalab Gothic and Watanabe Mincho. They don't show up in the gnome font selector (gfontview is not on my system). I searched to find them and they are in /usr/share/fonts/ja/TrueType. There are other fonts in that directory as well but they are OK. I'm attaching Wadalab Gothic only to this. The fonts are ~2.5MB each! If it's ok to make attachments of 5MB or so, then let me know and I can attach the other font as well. Thanks for the step-by-step instructions. It made gathering this info for you easy.
Created attachment 1028 [details] Wadalab Gothic fontthat causes crash
OK, finally had some time to play with the fonts being served up by xfs to determine which fonts and or families are causing OO 641C to crash. If I modify my xfs config file (under RedHat 7.2) to EXCLUDE the following directories: /usr/share/fonts/ja/TrueType (which is set by default in RedHat 7.2), then OO 641C nolonger crashes. My guess is OO doesn't like jis character sets, but I haven't verified. Now a follow-on question. Why does OO 641C LOOK so bad (screen rendering) compared to 641? Font rendering appears lousy compared to 641.
>Now a follow-on question. Why does OO 641C LOOK so bad (screen >rendering) compared to 641? Font rendering appears lousy compared to 641. Pls refer to the OO ng for discussion! This tool is for bug tracking. Back to the issue. Thanks for isolating the problem. It was already fixed in late november (thought the fix was already in the latest build of OO. Sorry.) Pls. refer to http://gsl.openoffice.org/source/browse/gsl/vcl/unx/source/gdi/gcach_xpeer.cxx?rev=1.19&content-type=text/x-cvsweb-markup In case you need that fix urgently you have to build the libvcl. If not, you can simply wait for the next binary snapshot of OO, where the problem will be fixed. As a first workaround you may wish to disable Watanabe Mincho and Wadalab Gothic in your Linux box. Simply exclude the files from being used by xfs.
Fixed.
*** Issue 3107 has been marked as a duplicate of this issue. ***
*** Issue 3197 has been marked as a duplicate of this issue. ***