A bug that has been in Calc for some time (past versions of Calc) After LibreOffice programme open for some time and a Calc file opened - attempt to copy - paste results in programme freezing
For the test, could you give a try to last stable LO version 4.3.3?
Downloaded and installed LO Version 4.3.3 Will return to this Bug report if/when the same copy/paste freeze happens. The issue has been happening for some time and with new versions always hoped it had been removed. Am new to this bug reporting thing.
Since updating LO to Version 4.3.3 have experienced freeze of LO Calc using paste (keyboard CTR V)
Would it be possible you attach the file? (have in mind that any attachment is automatically made public so remove any confidential/private part)
(In reply to Julien Nabet from comment #4) > Would it be possible you attach the file? > (have in mind that any attachment is automatically made public so remove any > confidential/private part) File contains confidential information - have created another file with dummy data to try to reproduce the bug.
I have just had an incident where a LO Calc document I was updating froze after repeated copy/pasting of part of a list, in order to make new rows with some columns containing same data. Not the same document as previously and due to the nature of the data cannot share here.
Is there conditional formatting? If yes, could you remove all of it with a backup for the test?
(In reply to Julien Nabet from comment #7) > Is there conditional formatting? If yes, could you remove all of it with a > backup for the test? No conditional formatting. Only formatting is to show dates and some number formatting in one document and date and time formatting in another document. Both documents originally created in version 4.2.6.3 or before.
Thank you for your feedback. Since I don't have more questions for the moment, I put it back to UNCONFIRMED.
(In reply to mymailbox28 from comment #5) > (In reply to Julien Nabet from comment #4) > > Would it be possible you attach the file? > .... > File contains confidential information - have created another file with > dummy data to try to reproduce the bug. what about this dummy text file? can you upload that one, otherwise it will be hard to debug with no test case
Not been able to reproduce the bug in the dummy file so far so have not uploaded here
(In reply to mymailbox28 from comment #11) > Not been able to reproduce the bug in the dummy file so far so have not > uploaded here Summary -> [Hard to reproduce]
I am moving this to NEEDINFO. It's not going to make any progress at all with current information. We need the test document or a test document that we can reproduce the issue - without this it's really impossible for us to do anything. If you can try to strip out the confidential information by randomly replacing #'s and letters that is an option. Once you provide either: 1. A test document with clear instructions on how to reproduce; or 2. A way to reproduce with a blank document please mark the bug as UNCONFIRMED. Thanks
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team This NEEDINFO message was generated on: 2015-07-18
Have been battling this bug since earliest days of LO. Just upgraded to v5 hoping that this got settled. I doubt that though as I've read that this problem existed prior to the LO fork. Generally occurs after multiple copy/paste operations (Ctrl-v) on spreadsheets (ods) where I haven't saved for some time. Maybe that coincidental, IDK. Because I save more frequently now due to data losses. This is a daily occurrence. Hit again last night. There is no easy way to demonstrate this as it might occur after 20+ copy/paste operations. Usually I'm just copying text or very simple add/subtract formulas when the freeze occurs. This is triggered by "Paste" command. Most often I use Ctrl-v so I know that does it. I don't recall if the top menu or context menu paste commands are involved. I've not seen this with "Paste Special" but I do that less frequently.
Version field correspond to the most earliest version when the bug can be encountered.
exnihilo, seems like an annoying bug. Since almost nobody else can reproduce it, only you can help us out. Getting a backtrace is somewhat hard to do and complex, but would be of great help (feel free to ask for help at #libreoffice-qa on freenode): https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
Also giving the exact versions of your software may also help, which version of Windows, 32 or 64-bit, does it happen on other machines or on a clean install?
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID 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 This INVALID Message was generated on: 2016-05-09