Bug 90920 - Dataloss: Calc Search can Clone contents of cell to another sheet
Summary: Dataloss: Calc Search can Clone contents of cell to another sheet
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86-64 (AMD64) All
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: dataLoss
Depends on:
Blocks: Find-Search
  Show dependency treegraph
 
Reported: 2015-04-29 06:01 UTC by Dan Loomis
Modified: 2025-05-27 03:12 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Small spreadsheet to reproduce the problem. (12.82 KB, application/vnd.oasis.opendocument.spreadsheet)
2015-04-29 06:01 UTC, Dan Loomis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Loomis 2015-04-29 06:01:57 UTC
Created attachment 115169 [details]
Small spreadsheet to reproduce the problem.

Download and open the attached document
Click on sheet1
Position the cursor on a blank cell in column c. Note the line number.
Enter some data in the cell.   
control f to bring up the search menu. 
Click the icon to go to full search
Make sure search entire document is checked.
Enter "sam" in the search window and start the search.
The data you entered will be moved from the cell on sheet1 to the same cell on the sheet where the string is found.
+++
Click on sheet1
Position the cursor on a blank cell in column c. Note the line number.
Enter some data in the cell. Click on another cell, then double click back into the cell you modified. Add something to the cell.
control F to bring up the search menu. Make sure search entire document is checked.
Enter sam in the search window and start the search.
The data you entered will be copied from the cell on sheet1 to the same cell on the sheet where the string is found.

This was originally reported in Open Office in May of 2010.  It is a data corruption bug and should receive more attention than it has.  Detection of the problem is difficult because users may not realize that row 1000 of their spreadsheet was overlaid because the search stopped at row 500.  It took me months to recognize how this was happening.  

I noticed with 4.4.2.2-4.fc22 (Fedora 22 Beta) that the data in the source cell disappears now as well.   The bug is worse then when I originally discovered it.  

Workaround.   Click out of the cell being modified before initiating the search dialogue.
Comment 1 raal 2015-04-29 09:02:13 UTC
I can confirm with LO 4.2.2, win7.
Dataloss, this silently rewrite data.

please could you post link from AOO bugzilla? Thank you.
Comment 2 Dan Loomis 2015-04-29 16:11:35 UTC
AOO Forum thread
https://forum.openoffice.org/en/forum/viewtopic.php?f=9&t=30248

User acknak opened the bug report 
http://qa.openoffice.org/issues/show_bug.cgi?id=109084
Comment 3 QA Administrators 2016-09-20 09:36:41 UTC Comment hidden (obsolete)
Comment 4 Dan Loomis 2016-09-21 04:58:13 UTC
Confirmed using the attached bugtest.ods spreadsheet.

Modified a cell on sheet one.  From the modified cell searched for "hive" 

Data from the starting cell was copied into the same line on sheet three.  

Please fix this.  It's nearly invisible data corruption that users may not see for days.   It took me a year to narrow down what was happening.
Comment 5 Dan Loomis 2016-09-21 05:00:06 UTC
PS:  Using the following version on Fedora 24 now.   
Version: 5.1.5.2
Build ID: 5.1.5.2-6.fc24
Comment 6 Xisco Faulí 2017-09-29 08:47:57 UTC Comment hidden (obsolete)
Comment 7 eisa01 2019-11-03 16:10:03 UTC
This is still present

Version: 6.4.0.0.alpha1+
Build ID: 80109586e6cb6d3e2e0a53a9079c3125ec9b8368
CPU threads: 4; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded
Comment 8 QA Administrators 2021-11-03 04:31:28 UTC Comment hidden (obsolete)
Comment 9 ady 2023-05-27 14:02:56 UTC
Still repro as of 7.6.alpha.
Comment 10 QA Administrators 2025-05-27 03:12:40 UTC
Dear Dan Loomis,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug