Also, users may not understand the bug is caused by footnotes. Any document
with more than one footnote or endnote in a paragraph will crash every time,
from what I understand. But to diagnose the bug, you have to Google and
Nabble and Bug search on "recovery" or "lock file" because you have no idea
it is the footnotes causing the crash. In fact, if you only have one
document open, it does not even seem like a crash. The only evidence of the
crash is that you do not return to the Libre Office main screen, but that
would be normal in MS Word, for example. You are left with a lock file, and
on restart you have a confusing choice about Recovery - it may actually be
best NOT to do the recovery, assuming you saved your file before the crash.
So how could people complain about this bug, if they do not know it is
caused by footnotes? I was a very diligent bug hunter, so I found it.
--
View this message in context:
http://nabble.documentfoundation.org/Always-starts-in-Recovery-mode-when-footnotes-endnotes-tp3255590p3262874.html
Sent from the Users mailing list archive at Nabble.com.
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.