Description: Consider this .ods (Calc) file: C:\fakepath\problem_1.ods When trying to copy and paste the green cell into the cells below, the neighboring cells get damaged. When trying to Undo, the previous state of the document isn't restored - thus Undo fails. Could this bug please be fixed? My only workaround currently is to copy and paste only one cell at a time which is quite annoying. Here is a series of screenshot images that illustrates the problem: (See screenshot images) Steps to Reproduce: 1. Open the attached file problem_1.ods 2. Try to copy and paste the green cell into the cells below 3. Examine the damage 4. Try to Undo 5. Examine the damage Workaround: Copy one cell at a time does not destroy the other cells. Workaround is very cumbersome and not a practical solution. Undo not working is especially concerning... Actual Results: a) Combined cells get destroyed. b) An Undo does not repair the cells (by returning to the previous state). Expected Results: a) Combined cells stay the way they are. b) An Undo does at least restore the previous state. Reproducible: Always User Profile Reset: No Additional Info: a) The thing that every normal user would expect. b) The thing that every normal user would expect. NOTE: I have a series of screenshots that illustrates the problem. I have a Calc file problem_1.ods that contains the problem. See the attachment for this bug.
Created attachment 143325 [details] Calc file that contains a simple testcase. I would like to add four .png images (screenshots) too. Hope that I can add more than one file?
Created attachment 143326 [details] first screenshot
Created attachment 143327 [details] 2nd screenshot
Created attachment 143328 [details] 3rd screenshot
Created attachment 143329 [details] 4th screenshot
"User Profile" problem checked by restarting in safe mode. Does not change anything.
Not reproducible with Version: 6.0.5.2 (x64) Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 CPU threads: 4; OS: Windows 10.0; UI render: GL; Locale: es-ES (es_ES); Calc: CL Please test with a newer version.
Still persists in this latest 5.4.7.2 version: Version: 5.4.7.2 (x64) Build-ID: c838ef25c16710f8838b1faec480ebba495259d0 CPU-Threads: 8; BS: Windows 6.19; UI-Render: GL; Gebietsschema: de-DE (de_DE); Calc: group Installing the version 6.0.5 now and will be reporting back in a few minutes...
Tested with 6.0.5 with following results: Aspect a) (the destruction of neighboring cells) still persists: Reproduced. Aspect b) (the ineffectiveness of Undo) was fixed: Can't be reproduced anymore. So, the bug is half fixed and half not fixed. Version: 6.0.5.2 (x64) Build-ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 CPU-Threads: 8; BS: Windows 10.0; UI-Render: GL; Gebietsschema: de-DE (de_DE); Calc: group
I can't reproduce any issue on the copied cell.
Thank you for reporting the bug. Could you please create and attach a screencast showing the steps? There are various free screencast software available for use, including Camstudio (Windows), Jing (Mac), Simple Screen Recorder (Linux) or screencast-o-matic.com (Web). I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested screencast is provided.
Created attachment 143359 [details] after the copy-paste you can see the damage in neighbor cells Here you can see the damage in the neighbor cells (right next to the copied green cells). I just copied the cell C21 into the cells below. I won't do a screencast, but thanks for pointing me to that software. I provided four screenshots that show the simple action and what happens. You can see the screenshots here: https://ask.libreoffice.org/en/question/159774/found-bug-that-also-breaks-undo/
Created attachment 143360 [details] screenshot It seems to me that the borders are not correct set, see screenshot. but when copy the green cell and then pasting to C22:C33; then it will undo in the next column, the merged cells. Pressing ctrl+z will reset to the normal state. Version: 5.3.7.2 Build ID: 6b8ed514a9f8b44d37a1b96673cbbdd077e24059 CPU Threads: 8; OS Version: Linux 4.14; UI Render: default; VCL: kde4; Layout Engine: new; Locale: nl-BE (en_US.UTF-8); Calc: group Version: 6.2.0.0.alpha0+ Build ID: df8589bd49d7eb1bb42ae78abcb91d33cf9255ce CPU threads: 8; OS: Linux 4.14; UI render: default; VCL: kde4; Locale: nl-BE (en_US.UTF-8); Calc: group threaded
Yes, Undo works (Aspect b). But the cells get destroyed (Aspect a). Thus, the bug is 50% fixed and 50% not fixed. Only workaround to prevent the damage is to dopy one cell at a time (C21 -> C22, C21 -> C23, C21 -> C24) which works but is very painful. Note, that it's not just the borders, but also the combination (joining) of the cells which breaks - instead of 1 combined cell you get 5 non-combined cells. That's what I call "damage" since it ruins not only the layout (border lines) but also breaks 1 combined cell into 5 smaller cells which has many negative effects.
Hm, that online
Hm that online screencast website asks me to install an executable (.exe) file. Not trustworthy enough. Can we please set this to UNCONFIRMED? It's really easy to understand how to reproduce this bug and what goes wrong. I don't think that a video/screencast is necessary. Also, I would like to know if this bug is NEW or a DUPLICATE.
Created attachment 143386 [details] screenshot confirm the problem when copying and pasting, see attachment Version: 6.2.0.0.alpha0+ Build ID: df8589bd49d7eb1bb42ae78abcb91d33cf9255ce CPU threads: 8; OS: Linux 4.14; UI render: default; VCL: kde4; Locale: nl-BE (en_US.UTF-8); Calc: group threaded
I can't reproduce it in Version: 6.2.0.0.alpha0+ Build ID: 67f3063b7c334d4d5c59132d90b938671aad09f0 CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded @Xavier, Could you please share the specific steps to reproduce it ? Do you use paste or paste special?
Hello, may I? Actually, paste or paste special doesn't matter. How to reproduce: Using the file (from the first attachment)... - select the cells H22 and H23 and observe: they are combined cells - now select cell C21 - copy (CTRL+C) - now select cells C22 to C39 - paste (CTRL+V) - select the cells H22, I22, H23, I23 and observe: cells not combined anymore Forget about the "Undo broken" part of this bug - that got fixed in 6.0 of LO. It's now only about the breaking apart of random neighboring cells.
@Xisco I only used the past option not past special retested it with past special still can reproduce the problem
@Xisco see comment13 and followed the description from the reporter
Dear marcusman, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear marcusman, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This bug is not present in the current version: Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: hr-HR (en_US); UI: en-US Calc: threaded Neither present in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 105f057f5b994b7d79a55ca719240839c2d45b54 CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: hr-HR (en_US); UI: en-US Calc: CL threaded
Comment 24 did not mention reproducing with an older version and now I tested with 6.3, couldn't repro, so I think we need to hear from marcusman and Xavier. Setting back to NEW.
Following comment 19 on MS Windows using attachment 143325 [details] from comment 1, for me this is repro up to LO 7.0, and solved since LO 7.1. I have not tested under other OSes.
Great, thanks ady. In that case we can confidently close.