Bug 117047 - Inter-process localc cut-and-paste pastes into wrong area
Summary: Inter-process localc cut-and-paste pastes into wrong area
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.4.5.1 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-16 17:38 UTC by mwelinder
Modified: 2019-11-28 04:09 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mwelinder 2018-04-16 17:38:51 UTC
Description:
When one localc process does a paste to another, the wrong target area
is sometimes used.

This simulates what would happen if pasting from a non-localc spreadsheet
to localc.


Steps to Reproduce:
1. Start two localc processes.  That likely involves running on a different
   machine not sharing home directory or setting HOME=/tmp/me

   NOTE: if the second process exits immediately, only one process is running.

2. Enter 11,21,12,22 into C7:C8.  (I.e., a 2x2 area.)

3. Select B6:D9 (I.e., a 3x3 area.)

4. Copy

5. Switch to other localc

6. Select A5.

7. Paste

Actual Results:  
A 2x2 data area is pasted into A5:B6.  Ie., the data gets shifted up one
row and one column to the left.  With expressions in the source area it
is possible to get them corrupted.

Expected Results:
A 3x3 data area is pasted into A5:C7


Reproducible: Always


User Profile Reset: No



Additional Info:
This does not happen when doing the cut-and-paste all in one process.

The mini-ods file created and sent via the clipboard simply does not seem
to have any information about the source area.  It would appear that the
bounding box of the non-empty cells is being used as a proxy.

It is possible that the correct area could be deduces from settings.xml

-      <config:config-item config:name="VisibleAreaTop" config:type="int">2709</config:config-item>
-      <config:config-item config:name="VisibleAreaLeft" config:type="int">4515</config:config-item>
-      <config:config-item config:name="VisibleAreaWidth" config:type="int">4516</config:config-item>
-      <config:config-item config:name="VisibleAreaHeight" config:type="int">903</config:config-item>



User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Comment 1 Xisco Faulí 2018-10-19 10:59:20 UTC
Thank you for reporting the bug.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 2 mwelinder 2018-10-19 13:16:25 UTC
Still there in 6.0.5.2
Comment 3 Xisco Faulí 2019-04-30 08:42:56 UTC
A new major release of LibreOffice is available since this bug was reported.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 4 QA Administrators 2019-10-28 03:30:41 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2019-11-28 04:09:22 UTC
Dear mwelinder,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA 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

MassPing-NeedInfo-FollowUp