Copy paste bug in libre writer

English
, ,
#22

Did GetOpenClipboardWindow report any program had the clipboard open? I’m presuming it didn’t; which is problematic as it would have been far easier to solve if something had kept it open. At this point I don’t think we’ve progressed anywhere, we still don’t know if the problem is with the clipboard, some other program keeping it open, or LibreOffice.

I’ve had a similar problem once or twice since you reported it and I’ve tried and tried and tried to reproduce it but it’s so inconsistent and seemingly random (perhaps the same issue, perhaps not).

Perhaps open a bug report with the info you’ve found here, it does seem to be more than what had been reported before.

#23

@Ash733 - VB program msgbox has always been:
GetOpenClipboardWindow
Sucessfully opened and closed the clipboard. Does not appear to be any problems.
OK

At this point I don’t think we’ve progressed anywhere
I know if ONLY affects LibreOffice Writer & Calc, and has been consistent for me, at least. Is this the correct URL - https://bugs.documentfoundation.org?

Note, for me at least, this is a relatively recent bug, in terms of LO versions. i.e. it never used to happen.

#24

bug URL: 162029 – LibreOffice products don't accept the current clipboard contents for pasting, pastes the previous contents

#25

For links to markdown formatting, see This is the guide - How to use the Ask site? - #6 by erAck

Maybe this post in answers.microsoft has a pointer, keep Windows from sleeping, Clipboard problems (can not copy/paste) in Windows 11

#26

thanks - I removed the multiple msgbox hyphens to fix it.

#27

Seems from bugzilla this bug has been known before April 2022 - 148647 – LO pastes previously copied content instead of what was last copied from other app (Windows 10; see comment 11) and NINE other bug reports.
image

with possible fix even just yesterday - 148647 – LO pastes previously copied content instead of what was last copied from other app (Windows 10; see comment 11)

#28

…which was mentioned above :wink:

But thanks for filing a bug report - in fact, the usually suggested exercise of finding existing bugs before filing an own one is, IMO, a waste of time, and my usual advise is: you see something that, in your opinion, misbehaves - you don’t hesitate, and just file a new bug. For one, you could be intimidated by the huge bug database with hundreds of thousands of issues, where people use all kinds of language to express their problems, and get lost much easier than the triagers who know the usual issues well, and who can find duplicates much easier than you, and in the process of looking for a duplicate, an inexperienced user could loose their incentive to file it - and having a duplicate is so much better than not having it filed at all; and also, duplicates (and CCed people) have own value of indicating the importance and spread of the problem (we use these numbers as a metric of bug importance / severity, even more useful than the bugs’ respective meta fields).

The only pre-requisite to filing bugs must be the proper expectations, where the user does not take closing their bugs as not a bug as a personal insult: closing bugs in such a way is also a positive thing, where the user gets an explanation / reason for the behavior; and filing these (not-a-)bugs is also appreciated as an important contribution.

2 Likes
#29

Very kind of you Mike. I still “try” to see if my bug is a duplicate, and given the # worldwide users, surely most of the time it will be, as I’m making unnecessary work for others to mark as a duplicate & close. You’ve explained why/ why not, so don’t further reply :wink:

1 Like
#30

I’ve not seen this bug again since the github report said it was fixed. Well done Mike.

1 Like

Impressum (Legal Info) | Datenschutzerklärung (Privacy Policy)   Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.