Please attach a test file to this bug report.

To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test?

Status set to NEEDINFO, please set it back to UNCONFIRMED once requested
informations are provided.

Best regards. JBF

Created attachment 143947 [details]
Here's that file which has the problem with vanishing comments.

In essence, do you mean that you have worked with the file, saved, but not closed and reopened. Then, after the shut down / restart cycle, you notice the comments were lost?
So basically, you should be able to reproduce it without any lengthy "shut down, go to sleep, start the next day" -cycle by just doing File - Reload after saving.

(In reply to Buovjaga from comment #3)
> In essence, do you mean that you have worked with the file, saved, but not
> closed and reopened. Then, after the shut down / restart cycle, you notice
> the comments were lost?
> So basically, you should be able to reproduce it without any lengthy "shut
> down, go to sleep, start the next day" -cycle by just doing File - Reload
> after saving.

 Today, I tried out your suggestion. I saved the file, made a change in one cell (so I could see if it actually reloads to file) and then attempted to reload the file. Apparently it doesn't reload if the file is already there.
 I really do not have time to test over and over using different techniques to replicate this problem and I do NOT wish to have this occur again. When I lose the comments, it really messes up what I am doing. I keep notes on the progress of the clocks throughout the day and night so I can see what they are doing each hour. This keeps the display much simpler when it only showing the results twice a day. The in between times are in those comments.
 When I lose those comments, I have much less information to refer to if a problem occurs.
 Quite frankly, I have no idea how this stuff works. I just use the spreadsheet as it is and expect it to work properly. When it doesn't, I do try to gather the circumstance and report it so you folks can attempt to work it out so it won't do that.

(In reply to George from comment #4)
> (In reply to Buovjaga from comment #3)
> > In essence, do you mean that you have worked with the file, saved, but not
> > closed and reopened. Then, after the shut down / restart cycle, you notice
> > the comments were lost?
> > So basically, you should be able to reproduce it without any lengthy "shut
> > down, go to sleep, start the next day" -cycle by just doing File - Reload
> > after saving.
> 
>  Today, I tried out your suggestion. I saved the file, made a change in one
> cell (so I could see if it actually reloads to file) and then attempted to
> reload the file. Apparently it doesn't reload if the file is already there.

No, it does reload, if the file is already there. That is the sole purpose of the reload functionality. With reload, we are able to quickly see for example, if saving to some Microsoft format caused unwanted changes. It is a shortcut for closing and reopening a file.

>  I really do not have time to test over and over using different techniques
> to replicate this problem and I do NOT wish to have this occur again. When I
> lose the comments, it really messes up what I am doing. I keep notes on the
> progress of the clocks throughout the day and night so I can see what they
> are doing each hour. This keeps the display much simpler when it only
> showing the results twice a day. The in between times are in those comments.
>  When I lose those comments, I have much less information to refer to if a
> problem occurs.
>  Quite frankly, I have no idea how this stuff works. I just use the
> spreadsheet as it is and expect it to work properly. When it doesn't, I do
> try to gather the circumstance and report it so you folks can attempt to
> work it out so it won't do that.

Us folks are fellow users trying to figure out a way to reproduce the problem, so developers can step in eventually. We suffer from the same lack of time as yourself, so it is sort of a balancing act.

I tried adding one comment, saving and reloading, but the comment did not vanish.

Arch Linux 64-bit
Version: 6.1.0.3
Build ID: 6.1.0-2
CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded

(In reply to Buovjaga from comment #5)
> (In reply to George from comment #4)
> > (In reply to Buovjaga from comment #3)
> > > In essence, do you mean that you have worked with the file, saved, but not
> > > closed and reopened. Then, after the shut down / restart cycle, you notice
> > > the comments were lost?
> > > So basically, you should be able to reproduce it without any lengthy "shut
> > > down, go to sleep, start the next day" -cycle by just doing File - Reload
> > > after saving.
> > 
> >  Today, I tried out your suggestion. I saved the file, made a change in one
> > cell (so I could see if it actually reloads to file) and then attempted to
> > reload the file. Apparently it doesn't reload if the file is already there.
> 
> No, it does reload, if the file is already there. That is the sole purpose
> of the reload functionality. With reload, we are able to quickly see for
> example, if saving to some Microsoft format caused unwanted changes. It is a
> shortcut for closing and reopening a file.
> 
> >  I really do not have time to test over and over using different techniques
> > to replicate this problem and I do NOT wish to have this occur again. When I
> > lose the comments, it really messes up what I am doing. I keep notes on the
> > progress of the clocks throughout the day and night so I can see what they
> > are doing each hour. This keeps the display much simpler when it only
> > showing the results twice a day. The in between times are in those comments.
> >  When I lose those comments, I have much less information to refer to if a
> > problem occurs.
> >  Quite frankly, I have no idea how this stuff works. I just use the
> > spreadsheet as it is and expect it to work properly. When it doesn't, I do
> > try to gather the circumstance and report it so you folks can attempt to
> > work it out so it won't do that.
> 
> Us folks are fellow users trying to figure out a way to reproduce the
> problem, so developers can step in eventually. We suffer from the same lack
> of time as yourself, so it is sort of a balancing act.
> 
> I tried adding one comment, saving and reloading, but the comment did not
> vanish.
> 
> Arch Linux 64-bit
> Version: 6.1.0.3
> Build ID: 6.1.0-2
> CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
> Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded

 Hah! You are correct! Just now, I did the same thing but went into
"File/Reload" which I rarely use the "File" method. I've been using the "click and hold  on the open folder GUI button. It's quicker.

 I was about to yell at you 'cause I didn't try it that way the other day.
 
  I suppose it would have been nice if you had told me the step by step method and explained to do it EXACTLY that way.
 Think of me as a beginner and I have been doing it "My Way". because I have been doing it "My Way" for two years.

 I suppose, if I can find the time, I try this a few times AFTER saving it under a different name in the hopes of having a good copy. The bugs I have reported so far are extremely intermittent. Trying it just one time will not work. As it says in the title of this bug..."Occasionally, LO Calc loses blocks of comments"

(In reply to Buovjaga from comment #5)
> (In reply to George from comment #4)
> > (In reply to Buovjaga from comment #3)
> > > In essence, do you mean that you have worked with the file, saved, but not
> > > closed and reopened. Then, after the shut down / restart cycle, you notice
> > > the comments were lost?
> > > So basically, you should be able to reproduce it without any lengthy "shut
> > > down, go to sleep, start the next day" -cycle by just doing File - Reload
> > > after saving.
> > 
> >  Today, I tried out your suggestion. I saved the file, made a change in one
> > cell (so I could see if it actually reloads to file) and then attempted to
> > reload the file. Apparently it doesn't reload if the file is already there.
> 
> No, it does reload, if the file is already there. That is the sole purpose
> of the reload functionality. With reload, we are able to quickly see for
> example, if saving to some Microsoft format caused unwanted changes. It is a
> shortcut for closing and reopening a file.
> 
> >  I really do not have time to test over and over using different techniques
> > to replicate this problem and I do NOT wish to have this occur again. When I
> > lose the comments, it really messes up what I am doing. I keep notes on the
> > progress of the clocks throughout the day and night so I can see what they
> > are doing each hour. This keeps the display much simpler when it only
> > showing the results twice a day. The in between times are in those comments.
> >  When I lose those comments, I have much less information to refer to if a
> > problem occurs.
> >  Quite frankly, I have no idea how this stuff works. I just use the
> > spreadsheet as it is and expect it to work properly. When it doesn't, I do
> > try to gather the circumstance and report it so you folks can attempt to
> > work it out so it won't do that.
> 
> Us folks are fellow users trying to figure out a way to reproduce the
> problem, so developers can step in eventually. We suffer from the same lack
> of time as yourself, so it is sort of a balancing act.
> 
> I tried adding one comment, saving and reloading, but the comment did not
> vanish.
> 
> Arch Linux 64-bit
> Version: 6.1.0.3
> Build ID: 6.1.0-2
> CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
> Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded

 this morning, I loaded up the 'puter and LO Calc. This was VERY close to 7am and I barely caught the clock chimes. When I got to the "Banjo", I notice the comments were missing from last night. So I finally got a chance to make a test by using "File/Reload" before the "Auto save kicked in and before I had time to "Save" the file as I usually do. What I got after "Reload" was exactly the same thing. So, it wasn't a failure AFTER I loaded the file, before auto save and before I manually saved it, it loaded without the comments again using "Reload". This indicates it was lost when I saved it last night. It always happened this way before but, I had no definitive proof until now.
 Since this so intermittent, I have no idea how you folks are going to find the time to have this happen to YOU. It took a few days until this happened to me.

 It's aggravating to me and I hate it.

 If we can't find a fix for this and several other problems with the comment section, I will be forced to begin trying alternative solutions such as other spreadsheet programs. So now, I can move on to report other problems with the "Comment" boxes. It seems almost all the bugs I'm experiencing are in the comment boxes.

 I finally found out when LO Calc is losing some or all the comments!
 One day, I had the "Clock" file open all day and I was up late that night and into the next day. When I was ready to retire for the nigt it was time to save the file and shutdown all apps and the computer. Later(after some sleep), I rebooted and loaded up the usual apps including the LO Calc and the clocks pages. I notice the comments were missing from the day before. Then, I thought on this and remembered the late night from before. Hmmm! After midnight!! Of course!
 So since then, if it's after midnight when I shutdown, I save it and then again save it as a different filename. Then I can reload the original filename and see if it has errors. I've seen lost comments twice but I've since learned that if I just save it twice in a row, the lost comments don't occur in the second event of saving it. 
 So now we have a starting point(I think). The trigger that starts the lost comments seems to be if the file was open all day and past midnight, then saved, the file gets corrupted.
George

quick test with Version: 6.3.0.0.alpha0+
Build ID: c7ad7849d54fd3dad67e7779102f65b8b2f04881
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 

open your file, wrote comment, changed system date to tomorrow, save and reload file - comment is not lost.

(In reply to raal from comment #9)
> quick test with Version: 6.3.0.0.alpha0+
> Build ID: c7ad7849d54fd3dad67e7779102f65b8b2f04881
> CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
> 
> open your file, wrote comment, changed system date to tomorrow, save and
> reload file - comment is not lost.

I guess what is implied is a slow memory leak.

Sorry for not reading all. But if there are no reproducible steps, this bug cannot be confirmed. 
I set Needinfo. Please only change with defined steps.

 I was wrong when I said it only happens after midnight. Last night, I lost all comments in one sheet after a save at about 1030p and I was NOT prepared for that so the loss was already set. I then was forced to rebuild that one sheet to get the comment boxes back The loss of these comments is still intermittent and you have only tried it ONE TIME. You then said you couldn't get it to fail THAT ONE TIME!
 I know you are busy as heck and probably don't have the time to test these intermittent problems so I'm at a loss as to how to fix an intermittent problem.
 So, ASAP, I'm going to give up and go back to WinXP and Excel and I will create a dual boot so I can continue with learning Linux OS because I really like Linux. It's these free apps that I can't tolerate.
 So, I expect that when someone else starts using a spreadsheet as extensively as I do, they will begin to notice these intermittent problems and pick it up as I have been doing. Eventually, the problems will be discovered and repaired.
 So, color me gone.

Hello,
LibreOffice 6.2.2.2 is going to be released today, could you please try again
with this version to see if the problem has been resolved meanwhile? Thanks in
advance

Dear George,

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