Bug 132327 - Large clipboard content could not be properly pasted
Summary: Large clipboard content could not be properly pasted
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: bibisected, bisected, regression
Depends on:
Blocks: Paste
  Show dependency treegraph
Reported: 2020-04-22 13:49 UTC by Nolan Beatty
Modified: 2021-01-06 07:53 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:
Regression By:

error message upon paste attempt (402.09 KB, image/jpeg)
2020-04-22 13:49 UTC, Nolan Beatty
example excel spreadsheet (2.56 MB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2020-04-23 15:06 UTC, Nolan Beatty
attaching requested clp file (4.68 MB, application/x-7z-compressed)
2020-07-21 12:44 UTC, Nolan Beatty
CopyQ clipboard content (905.81 KB, application/octet-stream)
2020-09-02 08:35 UTC, Timur

Note You need to log in before you can comment on or make changes to this bug.
Description Nolan Beatty 2020-04-22 13:49:34 UTC
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.
Comment 1 Timur 2020-04-23 14:37:39 UTC
Please attach Excel spreadsheet,so that we have a source to copy.
Comment 2 Nolan Beatty 2020-04-23 15:06:08 UTC
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.
Comment 3 Buovjaga 2020-07-20 16:19:01 UTC
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.
Comment 4 Nolan Beatty 2020-07-20 21:12:50 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2020-07-21 03:48:08 UTC Comment hidden (obsolete)
Comment 6 Buovjaga 2020-07-21 08:20:25 UTC Comment hidden (obsolete)
Comment 7 Nolan Beatty 2020-07-21 12:44:42 UTC
Created attachment 163363 [details]
attaching requested clp file
Comment 8 Buovjaga 2020-08-01 17:37:38 UTC
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
Comment 9 Nolan Beatty 2020-08-08 16:59:03 UTC
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
Comment 10 Timur 2020-09-02 08:34:23 UTC
Bibisected in LO 4.1.
 347b6e59bd05495b43c28ff0596edb3a5d7432fd is the first bad commit
Date:   Fri Sep 18 11:11:28 2015 +0800
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
        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.
Comment 11 Timur 2020-09-02 08:35:55 UTC
Created attachment 165008 [details]
CopyQ clipboard content
Comment 12 Nolan Beatty 2021-01-05 23:47:09 UTC Comment hidden (no-value)
Comment 13 Buovjaga 2021-01-06 07:53:49 UTC
(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.