Apache OpenOffice (AOO) Bugzilla – Issue 11302
spellcheck crashes, possible dictionary config error
Last modified: 2013-02-24 20:34:24 UTC
This issue is very likely identical or related to #10694, but as a newbie I couldn't figure out how in Issuezilla to append to #10694, or link my new report, other than with this preamble. I am running MS Windows XP SP1 on a Dell 8250 P4 2.5G 500Mb machine. Using Open Office 1.0.2 with almost all settings still at default. I attempted to install EN_CA dictionary using Dictionary Installer but the latter uses ~/user/workbook/ and not ~/share/dict/ooo/ so the files went in the wrong folder. I then manually installed files in the correct place and tweaked the dictionary.lst file. _How can I attach this file as part of this bug report?_ I had a document previously edited when only EN_US dictionary was installed. I opened this document, selected all the text, changed Tools | Options | Language Settings | Languages | Default Languages for Documents | Western = English (Canada); and For the current document only. Then when I run Tools | Spellcheck | Check, part way through the spell checking I get an error: OpenOffice.org 1.0.2 An unrecoverable error has occurred. All modified files have been saved and can probably be recovered at program start. OK If I re-open my document and use the same steps to change the language back to English (USA), and run the spell check, there is no error. The spell check finishes normally. If I change one word in my document from "marvelous" to "marvellous" this solves the crash with English (Canada). I consider there to be two main errors here: a) Open Office reports the bug in the most general way possible leaving me with essentially no clue what happened nor where to start searching for a solution. At the least can Open Office indicate which module caused the error, or better yet, log the details to a crash dump file and refer to this in the error dialog? b) Something is causing the spell checker to choke on "marvelous" with one "l" And as a precursor to the main errors, the following addition problems occurred: c) Dictionary Installer program did not recognize Open Office v1.0.2 even though it behaves incorrectly with v1.0.2 and incorrectly reported that it had successfully installed the dictionaries, even though I might want the dictionaries to be shared, i.e. in ~/share/dict/ooo/. d) Since Dictionary Installer requires that Open Office be closed, and that the OO Quick Starter be closed, shouldn't it enforce this which it doesn't, rather than warning about it in the readme file? As a result not being familiar with the Quick Starter, I ended up doing a reboot cycle to make the manually installed language stick.
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