Bug 90763 - All the contents of comments disappeared.
Summary: All the contents of comments disappeared.
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.3.6.2 release
Hardware: All macOS (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Writer-Comments
  Show dependency treegraph
 
Reported: 2015-04-21 02:04 UTC by farkas.kati
Modified: 2017-06-09 15:46 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
screen shot of what all my comments look like (138.82 KB, image/png)
2015-04-21 02:04 UTC, farkas.kati
Details
two pages of the problematic doc with empty comments (14.37 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2015-04-21 16:41 UTC, farkas.kati
Details

Note You need to log in before you can comment on or make changes to this bug.
Description farkas.kati 2015-04-21 02:04:08 UTC
Created attachment 114978 [details]
screen shot of what all my comments look like

After saving the document and opening it again, all the contents of inserted comments disappeared. Each comment is shown in the text at the appropriate place, but they are all empty. They all look like to attached pic. Lost about 10 hours of work.
Comment 1 V Stuart Foote 2015-04-21 05:26:03 UTC
@farkas.kati

Sorry for your loss. Looks very annoying. 

However, we can't do much with the issue with what you have provided thus far.

Please provide version details of your OS X installation, as well as the version of LibreOffice (for that, just paste the build info from the About LibreOffice menu item).

We might be able to duplicate things then.
Comment 2 Alex Thurgood 2015-04-21 05:59:18 UTC
This looks like a known bug that was present with an older version of LibreOffice.

@farkas.kati : please try with the latest production release of LibreOffice and report your findings here.
Comment 3 farkas.kati 2015-04-21 08:29:40 UTC
(In reply to V Stuart Foote from comment #1)
> @farkas.kati
> 
> Sorry for your loss. Looks very annoying. 
> 
> However, we can't do much with the issue with what you have provided thus
> far.
> 
> Please provide version details of your OS X installation, as well as the
> version of LibreOffice (for that, just paste the build info from the About
> LibreOffice menu item).
> 
> We might be able to duplicate things then.

Hello, thanks a lot for commenting. (I am new to this, so I am just figuring out where I need to reply, I hope I'm getting it right this time). 

Version of LibreOffice: 4.3.6.2
Build ID: d50a87b2e514536ed401c18000dad4660b6a169e

I downloaded it a few days ago.

My OS X is Yosemite Version 10.10.2 (14C109)
Comment 4 farkas.kati 2015-04-21 08:32:25 UTC
(In reply to Alex Thurgood from comment #2)
> This looks like a known bug that was present with an older version of
> LibreOffice.
> 
> @farkas.kati : please try with the latest production release of LibreOffice
> and report your findings here.

Hi Alex, thanks for the comment. I downloaded LibreOffice on Sunday, a few days ago, I assumed it was the latest version...
Comment 5 Adolfo Jayme Barrientos 2015-04-21 09:50:25 UTC
(In reply to farkas.kati from comment #4)
> Hi Alex, thanks for the comment. I downloaded LibreOffice on Sunday, a few
> days ago, I assumed it was the latest version...

As of now it is still, but keep in mind that we release LibreOffice in two channels simultaneously (as major web browsers do). The “Fresh” channel is the very latest version (4.4.x.); you might want to try that one out.
Comment 6 V Stuart Foote 2015-04-21 12:32:08 UTC
OP responded in PM:


Hello, thanks for getting back. My LibreOffice version is

Version: 4.3.6.2
Build ID: d50a87b2e514536ed401c18000dad4660b6a169e

I downloaded it a few days ago.

My OS X is Yosemite Version 10.10.2 (14C109)
Comment 7 V Stuart Foote 2015-04-21 12:49:39 UTC
@Alex,
(In reply to Alex Thurgood from comment #2)
> This looks like a known bug that was present with an older version of
> LibreOffice.

Looking to close this as a duplicate, did you have the number for the "known" BZ issue? Just scrounged around for it but couldn't locate.
Comment 8 farkas.kati 2015-04-21 13:11:12 UTC
(In reply to Adolfo Jayme from comment #5)
> (In reply to farkas.kati from comment #4)
> > Hi Alex, thanks for the comment. I downloaded LibreOffice on Sunday, a few
> > days ago, I assumed it was the latest version...
> 
> As of now it is still, but keep in mind that we release LibreOffice in two
> channels simultaneously (as major web browsers do). The “Fresh” channel is
> the very latest version (4.4.x.); you might want to try that one out.


Thanks a lot, I haven't realized this. I will download 4.4.x.
Comment 9 farkas.kati 2015-04-21 13:47:24 UTC
Oh dear!!!!

I downloaded the newest version I found: 
Version: 4.4.2.2
Build ID: c4c7d32d0d49397cad38d62472b0bc8acff48dd6
Locale: en_

I opened the same document. Fortunately, the comments were still there, but they were a bit messed up. Some of the comments were originally added to a highlighted text. The highlights are now randomly changed. For many comments, they disappeared (ie the comment used to be added to a highlighted sentence, now it is inserted with no highlight). Another comment had the contrary: it was originally added to a highlighted sentence, now the highlight covers 4 pages.

I deleted and re-inserted the messed up comments. Closed the document. Opened it again. The highlights are all messed up again.

Fixed the most offending ones. Closed the doc. Opened it. The previously fixed issue reappeared.

So some problem with the comments persists even in the 4.4.2.2 version. (Or it is somehow affected by the fact that I started to with the doc in the previous version?)
Comment 10 Alex Thurgood 2015-04-21 13:52:39 UTC
(In reply to V Stuart Foote from comment #7)

Hi Stuart,

> Looking to close this as a duplicate, did you have the number for the
> "known" BZ issue? Just scrounged around for it but couldn't locate.

Offhand no, too many to remember all of them, sorry. Possible a DUP of bug 60506, but this hasn't been fixed after all.
Comment 11 Alex Thurgood 2015-04-21 13:53:32 UTC
@kati : there are other comment issues still present and not yet fixed, unfortunately.
Comment 12 V Stuart Foote 2015-04-21 14:27:05 UTC
@farkas.kati

Hi, so is your document a native .ODT Writer creation, or are you doing round trip saves/opens of MS OOXML .DOCX?

Are the corrupt document comments being applied to footnotes/endnotes as in your screen clip? Or is it affecting track changes and comments?

Either case, any chance of replicating a test document (or attaching a redacted original)?
Comment 13 farkas.kati 2015-04-21 16:40:06 UTC
(In reply to V Stuart Foote from comment #12)
> @farkas.kati
> 
> Hi, so is your document a native .ODT Writer creation, or are you doing
> round trip saves/opens of MS OOXML .DOCX?
> 
> Are the corrupt document comments being applied to footnotes/endnotes as in
> your screen clip? Or is it affecting track changes and comments?
> 
> Either case, any chance of replicating a test document (or attaching a
> redacted original)?

@Stuart

I am doing round trip saves/opens on a .docx document written by someone else. 

The corrupt comments apply to the main text. Actually, there was an issue with applying comments to footnotes: while the document allows me to do that, they all completely disappeared after closing and reopening. So I started to insert my comments concerning footnotes in the main text, after the footnote number.

I was also using track changes, but the track changes seemed to be unaffected.

I attach two pages of the version with the empty comments, if that's what you meant
Comment 14 farkas.kati 2015-04-21 16:41:16 UTC
Created attachment 114991 [details]
two pages of the problematic doc with empty comments
Comment 15 QA Administrators 2016-09-20 09:34:08 UTC Comment hidden (obsolete)
Comment 16 Dieter 2017-06-09 15:32:53 UTC
Bug 60506 which is mentioned in comment 10 is now closed as WORKSFORME. There seems to be other related bugs like bug 68604 and 105458, which are fixed in 5.4.0. So perhaps this bug can also be closed?
Comment 17 Timur 2017-06-09 15:46:09 UTC
This bug was not clearly reported from the beginning. 
It may be duplicate of Bug 68604 which is fixed for 5.4. 
I'll close as Invalid since there are no repro steps, it mentions comments, footnotes, highlighting, track changes... 
If you experience it again with 5.4 or later, submit new bug.