Bug 47551 - EDITING: Bad interaction with other WINDOWS tool "Clipboarder" (and may be others)
Summary: EDITING: Bad interaction with other WINDOWS tool "Clipboarder" (and may be ot...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected)
Master old -3.6
Hardware: Other Windows (All)
: medium minor
Assignee: Not Assigned
Depends on:
Reported: 2012-03-20 01:05 UTC by Rainer Bielefeld Retired
Modified: 2015-11-01 09:49 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Rainer Bielefeld Retired 2012-03-20 01:05:30 UTC
Steps how to reproduce the bug with "LibreOffice German UI/Locale [Build-ID: dc9775d-05ecbee-0851ad3-1586698-727bf66] on German WIN7 Home Premium (64bit) and with this
sample document you find here: <https://bugs.freedesktop.org/show_bug.cgi?id=40958#c18>

First I thought "Bug 40958 - EDITING: Copy row to clipboard incomplete ... or: pasting copied row to other rows, makes that data in that row is repeated until the last column" might have reappeared, but it's only similar, not identical.

Currently I only see the problem on 1 PC with all various 3.5 installations already with Master builds from July 2011.
LibO 3.3 and LibO 3.4 are not affected.

The problem is not dependent to the User Profile.

Launching LibO 3.5 in WIN7 Protected Mode heals the problem, so it seems to be some interaction with other programs, drivers, ... . It seems that 3.5. has a particular vulnerability 

Any ideas how to find the evildoer?

It seems the problem appears during the Copy process: 
I did some tests with 3.4.5 and 3.5.1 spreadsheet each containing "x" in B2, copying complete row to row 10 or later in same spreadsheet and to other version, always after havinb selected now rew by click on row header before paste.

3.5.1 source 
to 3.5.1: "x" in each cell of new row (NOT correct)
to 3.4.5: "x" only in first cell (NOT correct)

3.4.5 source 
to 3.5.1: "x" only column B cell of new line (correct)
to 3.4.5: "x" only column B cell of new line (correct)
Comment 1 Stephan Hennig 2012-03-20 03:17:52 UTC

Win XP SP3
Build-ID: dc9775d-05ecbee-0851ad3-1586698-727bf66


1. Download and open file <URL:https://bugs.freedesktop.org/attachment.cgi?id=58690>.

2. Click row header of row 5.

3. Press Ctrl+C.

4. Click row header of row 20.

5. Press Ctrl+V.

In step 4, alternatively clicking just cell A20 then continuing with step 5 works fine, too.  Cell B20 contains 'Grape' while all other cells of row 20 remain empty.
Comment 2 Markus Mohrhard 2012-03-20 09:01:18 UTC
Can you please check with 3.5.2 RC1 and/or up-to-date master builds.  Normally there should now be no way to produce such a bug with my latest fixes.
Comment 3 Rainer Bielefeld Retired 2012-03-20 11:07:21 UTC
Still [Reproducible] with parallel installation of "LOdev 3.5.2rc0+  [Build ID: ec752de-73cb0b8-f269e46] Win-x86@6-fast pull time 2012-03-19 11:08:23 – WIN7 Home Premium (64bit).

I doubt that that is a simple "LibO bug", but some kind of LibO vulnerability concerning interference from other software.

May be my PC is the only one in the Universe suffering from that, but I would like to find the reason, you never know. Can you help me with ideas how to use my result that the problem disappears in WIN Protected Mode?
Comment 4 Stephan Hennig 2012-03-20 16:04:12 UTC
The graphics driver comes to mind.  Could you check if it's not a rendering problem, i.e., if single cells from the copied row are indeed non-empty?
Comment 5 Rainer Bielefeld Retired 2012-03-20 22:35:26 UTC
@Stephan Hennig:
The cells are really with contents, <control+end> leads to column AMJ, and in sample document you see "fruit" until end.
Comment 6 Rainer Bielefeld Retired 2012-03-21 10:01:48 UTC
I found the evildoer: <http://nes.bplaced.net/Features.html>
(I had used it for my tests for 
>Bug 45533 - EDITING: Pasting TABLE as RTF from SPSS fails>

After elimination of that tool LibO now works without problems
Comment 7 Rainer Bielefeld Retired 2012-03-21 10:43:14 UTC
I sent a feedback to tool's creators with reference to this Bug.
It remains a strange thing that there was no problem with 3.4.
Comment 8 Rainer Bielefeld Retired 2012-03-21 22:19:24 UTC
I got some feedback of the developer of the Clipboarder tool, I believe LibO 3.5 vulnerability concerning bad interaction should be checked, because there was no problem with 3.4

Author's feedback:

I'm the author of that program and I'm afraid it's your bug anyway. Clipboarder retrieves all clipboard data when the clipboard is changed. Since you obviously use delayed rendering your program recieves a WM_RENDERFORMAT message for every format as soon as it sets the clipboard and then somehow screws up your internal data structures while processing that message. It may look like it's the fault of clipboarder, but in fact any program can read the clipboard at any time. It's just kind of unusual that clipboarder reads out all clipboard formats, but I can't fix it on my side without using dirty hacks...
(BTW your clipboard data loses information when restarting the application and you have some high-dpi scaling bugs.)

Comment 9 retired 2013-12-22 12:46:11 UTC
This bug is very old. I have no windows nor have I ever heard of Clipboarder.

Is this bug still valid / reproducible with the latest LO release?  Currently http://www.libreoffice.org/download/

Should this be still reproducible for you with the latest LO release please set this bug back to NEW. Should this issue be solved set it to WORKSFORME.

Setting to NEEDINFO until more detail is provided.
Comment 10 QA Administrators 2014-07-08 17:28:53 UTC
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: 

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
Comment 11 QA Administrators 2014-08-04 16:14:59 UTC
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 FDO