Bug 138044 - Loss of one eighth of manuscript!
Summary: Loss of one eighth of manuscript!
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.5.2 release
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-06 17:45 UTC by choosethebest
Modified: 2021-06-09 03:48 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description choosethebest 2020-11-06 17:45:53 UTC
I discovered that whereas the Word doc had been at 95,875 words last time I further polished it in Libre on Nov. 3rd, the word count on it had dropped to 83+++. I'm beyond perplexed (loss of more than 12, 000 words). I am extremely careful about how I handle the novel and others I have started (and everything), and cannot comprehend what happened.

Perhaps the problem is with EDITING or FILESAVE.
Comment 1 Timur 2020-11-09 12:38:05 UTC
See https://wiki.documentfoundation.org/QA/BugReport and submit proper minimal sample and steps to reproduce. 
If you cannot and have only a result, no use of this report.
Comment 2 QA Administrators 2021-05-09 03:51:29 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2021-06-09 03:48:44 UTC
Dear choosethebest,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp