Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | "Insert > Special Character" Crash | ||
---|---|---|---|
Product: | Writer | Reporter: | jacksquat <tea.squat> |
Component: | editing | Assignee: | eric.savary |
Status: | CLOSED IRREPRODUCIBLE | QA Contact: | issues@sw <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | guido.ostkamp, issues, yoshimit |
Version: | OOo 2.0 | Keywords: | oooqa |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux, all | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
jacksquat
2005-11-14 01:04:10 UTC
Reassigned to US. When recovering the document OO.o offers to submit a crash report. When allowing "Sun may contact me" it also returns the report ID by mail to you. The report and the ID would be valuable information for us in order to reproduce your problem. Pls. submit a crash report and allow Sun to contact you. Pls. put the report ID in here. Thx. Additionally the document you are creating especially the glyphs you are inserting and the font used could be of some interest in order to reproduce the prob. Pls. additionally attach the document. Thx. in advance. > When recovering the document OO.o offers to submit a crash report. When > allowing"Sun may contact me" it also returns the report ID by mail to you. No. The ID is only returned when the report is sent using StarOffice. OpenOffice.org users only get a "Thank you for your error-report" mail without any further information. You need to query the database for the email/description. If you want, you can have a look at a sample-response I attached to issue 31065. Maybe some of the header-info allows identification of the Report (I doubt so) Verification failed with OOo 2.0.1 final on SuSE Linux 10.0 (I checked with some documents of the english documentation project with several images etc.) Inserting special characters worked without problems. Suggest to close bug with WORKSFORME as the original author has not supplied any document for reproduction and the bug was reported against version 2.0.0. Could the cause of the crash be linked to Issue 61076? Regards, Andrew have to reassign issue. Can't reproduce with OOo-dev m173. Closing for now. Feel free to reopen if necessary. Hwoarang . This issue exists in 2.2.0-6+b1 (Debian) The special characters dialog crashes after some scrolling if Arial or Times font is selected (from msttcorefonts package). Maybe the other ms fonts are also affected. I suggest a reopen. |