Apache OpenOffice (AOO) Bugzilla – Issue 79369
Writer crashes on Insert Special Character on linux
Last modified: 2007-08-07 16:39:19 UTC
This issue was reported before (76578) but closed. The problem seems not to be fixed. Writer still crashes when trying to Insert | special character and to scroll down the table of characters. I tried under Debian (OOo 2.2.1, German) and OpenSuse 10.2, German and with the official packages. I have also seen it happen in Kubuntu 7.04. Writer crashes reliably when i do that: 1. Open a text document 2. Choose: Insert | Special Character (= Einfügen | Sonderzeichen in German) 3. Choose a (Truetype-?) font with a _lot_ of characters (as Times New Roman, Arial or FreeSans from the debian-package ttf-freefont) 4. Scroll down the table with the characters 5. Writer crashes, usually before I get down to the last characters of the font The problem is not limited to the msttcorefonts. The solution suggested in issue 76578 would be, to set the locales to en_US. But that's not a sensible solution for everybody and it didn't work for me anyway. And even if there was a problem with the locales, OOo shouldn't just crash silently. The problem seems to be limited to the linux version 2.2.0 and up. OOo 2.1 on linux works just fine. On Windows there is no problem at all. When I start OOo from the command line it get the following messages several times before I start the actions described above: (process:5798): GLib-GObject-CRITICAL **: /tmp/buildd/glib2.0-2.12.12/gobject/gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function (process:5798): Gdk-CRITICAL **: gdk_screen_get_font_options: assertion `GDK_IS_SCREEN (screen)' failed There is no message at all when OOo is crashing or immediately before. Regards Martin
Unable to reproduce with OOo-2.2.1 B 9161 Linux i86 RPM de_DE (OpenSuse 10.2, KDE 3.5.5 "release 45.4"; several fonts). koyukuk: Please allow OOo to send the automatic crash report and insert the ID you'll receive via email here.
Thank you for the quick answer first of all. I let OOo send a crash report using the same build you did on OpenSuse 10.2. I used FreeSans from the OpenSuse freefont package. The crash happens with Arial, Times New Roman FreeSerif as well. I had to scroll down all the way and a bit up again, so it seemed better at first. But then it happend again. It took me several crashes for the report program to start though. I something useful arrived. Best regards Martin
koyukuk: If you supplied your email address in the automatic crash report assistant, you should have received an automatic reply containing an ID. Please quote the ID of your automatic crash report here. This will make it possible to associate the crash report with this issue. You might also wish to discuss your problem on the users mailing list of the respective project; for German please see http://de.openoffice.org/about-ooo/about-users-mailinglist.html However, I'm still unable to reproduce your problem. Thus, this issue is likely to be closed as WORKSFORME. - Maybe somebody running OOo under Gnome or so can double-check.
Hello now I got an ID for a crash report: rhvyvc I hope it helps. I still get crashes but it seems to take a bit longer sometimes. I just had to scroll three times up and down (using the mouse wheel). I tried some more fonts, and most work fine. To me it seems the problem is related to the size of the font. FreeMono is fine though. FreeSans, FreeSerif, Arial, Times New Roman crash. Thanks Martin
The report does not contain any stack so no information can be taken from it.
MRU->HI: could you please have a look?
Yesterday I tried again, but didn't manage to get a better crash report. Mostly the crash report program didn't trigger. After the document recovery I get the option to click <continue> (or <Weiter> in my case) to the report assistant, but nothing happens. OOo just starts up without showing the crash report form. When I start crash_report after a crash manually, the assistant appears on the next start of OOo. The result is what I have sent already. If there is anything else I can do, please let me know. Best regards Martin
Verified with suse and given fonts above: No Crash! Set to WFM.
Sorry for disturbing again, but I might have found the reason, why you can't reproduce the crash. It happens only when antialiasing for screen fonts is switched off or set to value so high, that the character table isn't antialiased. (In the German Version the setting is in Extras | Optionen | OpenOffice.org | Ansicht | Bildschirmschriften glätten) If you please could try that one thing, that would be nice. I got a better crash report with the ID rfsnkc. Thanks Martin
When Tools > Options > OOo > View > User Interface > [ ] Screen font antialiasing is switched off, OOo 2.2.1 B 9161 Linux i86 RPM de_DE and OOo-Dev 680_m218 B 9177 Linux i86 RPM en_US crash reproducibly when scrolling (quickly) through the Insert > Special Character dialogue (e.g. with Lucida Sans).
Yep, nice catch.
Yes, that's a good catch: X-Error: BadPixmap (invalid Pixmap parameter) Major opcode: 56 (X_ChangeGC) Resource ID: 0xffffffff It looks like a CreatePixmap call failed for the glyph image => analyzing
I found it: the regression got into milestones >=SRC680_m201 with the fix for issue 73485
@sba: please verify in CWS vcl80
SBA->HI: As discussed, please proceed. Thanks. Reassigned to HI.
Verified with cws vcl80 = ok
Still ok in 680m225_9196