You are here

Crash after autocorrect options and closing application - still there

4 posts / 0 new
Last post
PRHL
PRHL's picture
Offline
Last seen: 6 years 8 months ago
Joined: 2013-07-28 11:04
Crash after autocorrect options and closing application - still there

The known bug that LO crashes after changing autocorrect options and closing the application is active in both versions of portableapps, i.e. the current 5.0.2 and the previous 4.4.5.
The horrible autocorrect makes the writer app nearly unusable, so you must turn off autocorrect before writing and turn it on before closing the app. Otherwise, the app crashes. In any case, it is impossible to start writer without autocorrect enabled.
For the time being, OpenOffice seems to be the only viable workaround. Maybe there should be a LO with autocorrect disabled by default.

John T. Haller
John T. Haller's picture
Offline
Last seen: 1 hour 38 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Fine Here

I'm not sure what you mean as both the local and portable versions work just fine here. What specific steps should I do to reproduce a crash?

Sometimes, the impossible can become possible, if you're awesome!

PRHL
PRHL's picture
Offline
Last seen: 6 years 8 months ago
Joined: 2013-07-28 11:04
Bug 89867

This is a known bug that is reported for several versions of LO.
http://lists.freedesktop.org/archives/libreoffice-bugs/2015-March/261046...
Just deactivate autocorrect (format - autocorrect - during input). It does not matter when you do this, e.g. with an old document opened, immediately after starting or before closing etc. With "autocorrect during input" deactivated, LO crashes when closing - that's it. And after the recovery, autocorrect is again activated. A sad story.
Therefore it would be preferable to have autocorrect deactivated by default.
4.3.5.2 does not have this problem, tested with
http://downloadarchive.documentfoundation.org/libreoffice/old/4.3.5.2/po...

John T. Haller
John T. Haller's picture
Offline
Last seen: 1 hour 38 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Already Fixed, Likely Rare

This was/is likely a rare bug. Not in that it never happens, but that it happens to a small percentage of users due to some conflict. You're just a lucky one. I can't reproduce it here. Both Fresh 5.0.2 and Still 4.4.5, local and portable, work without issue on my machine. And I followed the steps to reproduce to the letter. Note that this is the actual bug link instead of a link to a mailing list post (the mailing list links to this bug):
https://bugs.documentfoundation.org/show_bug.cgi?id=89867

According to that report, it is fixed in both current versions and was fixed specifically in the 4.4.4 release. There may be another regression, but it's not due to us, and is likely not affecting most users. There is no need to deactivate autocorrect by default.

Sometimes, the impossible can become possible, if you're awesome!

Log in or register to post comments