Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | spellcheck crashes, possible dictionary config error | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Infrastructure | Reporter: | johnmcalvert <kayakheaven> | ||||||
Component: | Website general issues | Assignee: | issues@lingucomponent <issues> | ||||||
Status: | CLOSED IRREPRODUCIBLE | QA Contact: | issues@lingucomponent <issues> | ||||||
Severity: | Trivial | ||||||||
Priority: | P3 | CC: | issues | ||||||
Version: | current | Keywords: | oooqa | ||||||
Target Milestone: | --- | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||||
Developer Difficulty: | --- | ||||||||
Attachments: |
|
Description
johnmcalvert
2003-02-07 21:19:42 UTC
Created attachment 4604 [details]
dictionary file
Created attachment 4605 [details]
File in which spellcheck crashes on EN_CA and "marvelous"
Hi, Sorry it has taken so long for me to get back to you but... I have tried under 1.1beta and 1.0.2 and under 1.0.1 and I can simply NOT recreate this error at all with your test document or in any other way. I just looked at your dictionary.lst file that you attached and it looks absolutely fine. Did you by any chance upgrade from 1.0.0 or 1.0.1? If so please simply try the following: 1. delete the "dictionary.lst" file from users/wordbook/ (i.e. there should be only 1 "dictionary.lst" file and that one should be found in share/dict/ooo/ and any in user/wordbook should be deleted (these are sometimes present from old installations) 2. shut down out of Quickstarter and OOo 3. restart Then try recreating your bug report Please let me know if this "fixes" the problem. Thanks, Kevin Hi Kevin, for a while I uninstalled OOO as I was having other unrelated problems with my computer and I wanted to eliminate extraneous issues. When I re-installed OOO, this issue no longer happened. Subsequently, I realized that the first time I installed OOO I was confused by the dictionary setup and did it incorrectly. I manually moved some *.dic files from ~OpenOffice.org\OOO.1.0.2\user\wordbook\ to ~OpenOffice.org\OOO.1.0.2\share\dict\ooo\. Therefore I think that this caused the unrecoverable error. I'm sorry I didn't update the status of the OOO issue report. I kind of last track of it in the intervening month. Although I no longer have the "unrecoverable error", there is still something wrong. When OOO has an error, it should give some information about it, not simply report a generic message. I've had this with other areas of the Write and Calc program and it is extemely frustrating to have no clue and no information about what went wrong. I realize this is a rather amorphous comment. What group within OOO can I re-direct this to? John Hi, I agree that something other than "unrecoverable error" would be nice. The lingucomponent module actually writes an error message to "standard error" which must go into some log file. I see it when I run the soffice command from the command line. That said, lingucomponent was deisgned to give an informational error message and NEVER be the cause of an "unrecoverable error" or segfault that I can work around or ignore. The entire application is a different story. The app should never give an "unrecoverable error" for simple things like missing files or damaged config files, missing dictionaries etc. The Hamburg developers are tyring to implement an automatic stack backtrace mechanism that would produce a more detailed bug report that could be sent to OOo or posted as an attachment in a bug report. So you might want to drop an e-mail to dev@openoffice.org asking for an enhancement or asking how to obain more information from "unrecoverable errors" dialogs under WIN XP. I know under Linux a user can leave that dialog on the screen and "attach" to the still running program with a debugger (such as gdb) and generate a nice backtrace of what caused the error. I just don't know if somehting similar is available under WIN XP. Anyway, given the problem has gone away. I am going to resolve this as "WorksForMe". Thanks, Kevin Yes, you can attach to a running process with a debugger in Windows as well. One just have to have development tools available. So, a more user (especially, lame user) friendly approach to gathering runtime data would be welcome. The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew |