Description: LibreOffice Version: 6.0.6.2 Build ID: 1:6.0.6-0ubuntu0.18.04.1 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-CA (en_CA.UTF-8); Calc: group PC user@host:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic user@host:~$ uname -a Linux host 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I have a spreadsheet I've been working on/with for 18 months give or take. The last time I used it, yesterday or the day before, everything was fine, as far as I know. The last time I would have seen those sheets directly would be Oct 31 2018 while using ctrl-pgup / -pgdn to cycle past the tabs. I would have noticed them being blank at that time. Today I opened it at lunch, and two of the worksheets are completely blank. All data is gone. The other worksheets are fine. It is as if I had executed this sequence of steps: - group tabs "Losses - Legend" and "Errands" by clicking one sheet and ctrl-clicking the second sheet - ctrl-a to select all - right-click - Clear contents... - check off "Delete all" - press OK Or some equivalent set of steps that takes even longer than that. I can guarantee that I did not do that accidentally. Data and formatting are completely gone, including borders, cell/column/row sizing and fill colours. The sheets look like they have been just-created; default everything for a blank sheet. Steps to Reproduce: No idea how this occurred. Actual Results: No idea how to reproduce this. Expected Results: Spreadsheet does not lose data Reproducible: Didn't try User Profile Reset: No Additional Info: The spreadsheet was created on an Ubuntu 16.04 system with whatever release of LibreOffice was current at the time I created the spreadsheet, around maybe Jul 2017. As a rule, I hibernate when moving my laptop from home to office. I usually use ctrl-s to save before exiting. I don't believe my laptop has encountered a drained battery situation recently, but has in the past and may have since the end of Oct when I last knew with reasonable certainty that the worksheets were ok.
Created attachment 146845 [details] Backup copy I made immediately on noticing the data loss I am pretty sure that I had opened and then performed a couple of ctrl-s saves before noticing the problem, so I don't know how useful the document will be. The copy in $HOME/.config/libreoffice/4/user/backup was equally not helpful (still have it though, just in case).
I did some research before reporting this bug. I couldn't find anything directly relevant. I did find some discussion about an intra-threads bug where the fix went into 5.2.x. This spreadsheet is a native created-with-Calc spreadsheet. It's never been an .xls. It has never been stored on a networked filesystem; always direct local SSD access. I will admit to fat-fingering sometimes in Calc, and having to undo to recover from it. However, the exact specific sequence of actions needed to accomplish a "sheet reset" would be very hard to perform accidentally: - length of sequence of "accidental" actions - some actions are mouse-only; they have no keyboard equivalent I've added a cron job to make nightly backups. If this happens again, I'll have better history to add here and no data loss. I'm unsure whether turning on Track Changes will help, but I've done that as well. I think I recall a couple of times where opening the sheet took a long time, but I'm not certain about that. I'm an embedded C developer; I can drink from the firehose.
I've taken to backing up this spreadsheet, and the problem has recurred, I'll attach a before and after copy.
Created attachment 147565 [details] Last backup before the problem recurrence
Created attachment 147566 [details] First backup after the problem recurrence
You don't say where exactly loss reoccurred, I see that "Losses - Legend" is empty. Sorry for changing to Needinfo but bug report makes sense for reproducible and clear issue. So far, not enough to confirm.
"You don't say where exactly loss reoccurred, I see that "Losses - Legend" is empty." Same tab, "Losses - Legend", completely blank. Although the formatting was intact; column sizes mainly. "Sorry for changing to Needinfo but bug report makes sense for reproducible and clear issue. So far, not enough to confirm." Bug reports make sense for bugs. Which this is, as I have never purposefully performed a "delete all content" action for any tab in this workbook, ever. Thus the loss of data is a bug. Would it be nice if it was demand-reproducible? Yes. I'm a programmer. I am very familiar with debugging. As of right now, it is not demand-reproducible, but, it does occur from time to time, so it is reproducible. So I agree with Needinfo; reproduction steps are required. Since we don't have those, but do have a situation where the bug occurs, suggesting debugging steps would be much appreciated. I tried turning on the Edit -> Track Changes -> Record Changes thing but it produces way too much info that requires user interaction. If it record changes silently, like Google's Sheet's versioning, that would be ideal. I've come to suspect that there is a mouse-based action, perhaps interacting with the worksheet tabs and/or tabs bar, that is in fact "delete all content", but I haven't found any documentation on anything like that. The reason I suspect this is because I'm often mouse-grabbing the horizontal scroll bar, just near the "Losses - Legend" tab, to scroll horizontally, AND, I often miss the scroll bar (because it is way too thin, a different issue) and grab the tabs instead.
This sounds like bug 103625, which was unfortunately automatically closed due to no response from the reporter. To drink from logging firehose, one could use a debug build and SAL_LOG: https://wiki.documentfoundation.org/Development/How_to_debug#Macros_Controlling_Debug_Code https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@86-TDF-dbg/
It could be, although the issue I reported only affects one or two tabs, not the whole workbook. I haven't seen this in some time; I'm okay with closing this bug. If it occurs I can re-file. I tried having logging on but it was way to much. I've been making regular backups to guard against it happening again. Thanks all.
Ok, let's close for now