when i try to use "synonimous", the program crash and closes.
I have no idea what "synonimous" might be or how does one use it... Could you tell us what did you do, where you clicked etc., preferably in a few easy-to-follow steps?
(In reply to comment #1)
> I have no idea what "synonimous" might be or how does one use it... Could you
> tell us what did you do, where you clicked etc., preferably in a few
> easy-to-follow steps?
I beg your pardon for my poor english, but here you are:
You open a document in writer.
type some words misspelled.
Select one of these words.
Go to Tools->Language->Synonimous (CTRL+F7)... and you have a beatiful crash..
NOT Reproducible with "LibreOffice 3.3.2RC1 – WIN7 Home Premium (64bit) German UI [OOO330m19 (Build:201 / tag 184.108.40.206)]"
May I ask you to read hints on <http://wiki.documentfoundation.org/BugReport>?
- Attach a sample WRITER document so that we can try to reproduce your problem
- add information
-- concerning your PC
-- concerning your OS
-- concerning your LibO localization (UI language) and installed dictionaries
-- Whether that problem also occurs in CALC
–- Libo settings that might be related to your problems
-- everything else crossing your mind after you read a.m. URL
Ah, thesaurus... I'm pretty sure this is https://bugzilla.redhat.com/show_bug.cgi?id=675806, then. We have fixed it in master, but not in 3.3. Maybe we should, too?
yeah @yahoo.es -> likely this is Spanish, and the known mythes crasher was triggered by a Spanish thesaurus extension
cherrypicked b788f9fc846c0f47d02df02ac6733c0ac21a13c6 to 3-3, need more acks to push to 3-3-2
its a trivial fix: see http://cgit.freedesktop.org/libreoffice/libs-extern/commit/?h=libreoffice-3-3&id=896c49083aec918b0710f9c62f2f775a53f28057
Created attachment 44570 [details]
a spreadsheet used like scheduler
Thank you for your contribution, additional information only will be required if you find out that your problem unexpectedly is different to the one that will be fixed soon, as you can see.
fix will be in 3.3.2
*** Bug 35464 has been marked as a duplicate of this bug. ***