Created attachment 159815 [details] error message upon paste attempt Attempted to copy a large amount of data from an itunes library and paste that data into a Calc spreadsheet. The data copied consisted of around 58000 records (song data). After I copied from the itunes library, i attempted to paste this data into Calc. At first, it appeared that it would be successful. But after a few seconds, I received an error message (see attached) saying the contents of the clipboard could not be pasted. Yet, even though this error was encountered, it still managed to paste a good number of those records. For comparison purposes, I attempted the same copy/paste action using Excel and discovered that no error was encountered and was able to paste my entire itunes library into an excel spreadsheet.
Please attach Excel spreadsheet,so that we have a source to copy.
Created attachment 159862 [details] example excel spreadsheet attaching requested excel spreadsheet. you will find that, if you copy the data directly from the excel spreadsheet into the calc spreadsheet, you will encounter no issues. however, my specific example outlined in this reported issue deals with not being able to paste from another buffer source (in this case, the entire contents of my iTunes library). to create this specific issue, i copied itunes content (over 58000 song data) using CTRL-C. Then i opened up a blank Calc spreadsheet and used CTRL-V (paste) to paste that content into a Calc spreadsheet. That's when i got the error identified in this issue. it successfully pasted most of the records but only got so far in the process before displaying the error message. However, that same process worked when pasting into excel. Attaching the excel file that you requested will probably be of no help to you because we already know copying directly from the excel spreadsheet into calc will indeed work.
Nolan: please run this InsideClipboard software: https://www.nirsoft.net/utils/inside_clipboard.html It will allow you to save the copied iTunes data from your clipboard as a .clp file. You can then hopefully attach it here.
would like to help out with your request for attaching a .clp file to this ticket, however I am unable to do so. The file attachment is over 80MB and bugzilla won't let me attach a file over 30MB.
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to Nolan Beatty from comment #4) > would like to help out with your request for attaching a .clp file to this > ticket, however I am unable to do so. The file attachment is over 80MB and > bugzilla won't let me attach a file over 30MB. Options: 1. Compress it as a .zip or .7z archive 2. Upload to a file host such as https://gofile.io/ and I will figure out the rest
Created attachment 163363 [details] attaching requested clp file
Thanks for the file, I was able to reproduce (sorry for the delay, I was away). This is already seen in the oldest commit of Windows 4.4 bibisect repository, but not yet in version 3.5.0
ok - thanks. i do not understand your last comment regarding the bibisect repository, etc. that doesn't mean much to an end user but probably is meaningful to the folks working on your team. i believe my only interest here is knowing if you could tell me which upcoming release of libreoffice might contain a fix for this particular defect. thank you
Bibisected in LO 4.1. 347b6e59bd05495b43c28ff0596edb3a5d7432fd is the first bad commit Date: Fri Sep 18 11:11:28 2015 +0800 source-hash-a883783c2a1b0e7a8ee5b46387d1e1e3bc5e19bd Previous source-hash-708cab47c4457637f87815750a026168b3f10c84 so single commit. commit a883783c2a1b0e7a8ee5b46387d1e1e3bc5e19bd Author: Eike Rathke <erack@redhat.com> AuthorDate: Tue May 14 13:39:27 2013 +0200 Commit: Eike Rathke <erack@redhat.com> CommitDate: Tue May 14 14:16:02 2013 +0200 resolved fdo#60468 no special tab case workaround for CSV import This reverts 322cbc3818b0553254aab2dfb3c5b196fe814097 "Import mal-formed csv files gracefully." (code now moved to a different location) which was a workaround for a specific situation that breaks things with other documents. With the rework of CSV import for 3.6 the import of the one failing document https://bugzilla.novell.com/attachment.cgi?id=294589 from https://bugzilla.novell.com/show_bug.cgi?id=507322 works almost fine without this workaround, with one difference in row 1805 where data is completely broken and parts of two rows end up in one cell P1805. That row wasn't correct with the workaround either, see also cell P1805 in earlier versions. As a result now without that workaround there is one data row less for the broken document but correct data for correct documents. Adding Eike to CC. Bug is easily seen. When clipboard is pasted, normally it has around 60.000 rows, but with the bug it pastes around 50.000 row and given an error. Only issue is that Nirsoft is Windows only clipboard, we should use multi-platform clipboard tool, I guess CopyQ may do.
Created attachment 165008 [details] CopyQ clipboard content
i see some comments have been added by various team members, and it appears that the development team seems to know what the issue is and how to correct this defect. is the status of NEW still correct for this defect? but i still do not see any indication or discussion of when the end user community can expect to see the resolution (and in which release). any information you have that could help me understand when we might see the fix in an upcoming release of libraoffice would be greatly appreciated. thank you
(In reply to Nolan Beatty from comment #12) > i see some comments have been added by various team members, and it appears > that the development team seems to know what the issue is and how to correct > this defect. is the status of NEW still correct for this defect? NEW is still correct. > but i still do not see any indication or discussion of when the end user > community can expect to see the resolution (and in which release). any > information you have that could help me understand when we might see the fix > in an upcoming release of libraoffice would be greatly appreciated. This is natural. If you did not pay anyone for fixing a bug, you can't expect to know a date of delivery for a fix.
Dear Nolan Beatty, 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
attempted the same procedure as before - copied a large amount of music (approximately 60,000 songs) directly from itunes and successfully pasted all records into a calc spreadsheet - no errors were encountered. this issue seems to have been resolved.