Bug 439851

Summary:	klipper removes clipboard content on mouse-click when memory size is set to 1
Product:	[Plasma] plasmashell	Reporter:	Hayo Schmidt <bugzilla>
Component:	Clipboard widget & pop-up	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	minor	CC:	kde, nate
Priority:	NOR
Version First Reported In:	5.18.6
Target Milestone:	1.0
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Screenshot of my klipper settings

Description Hayo Schmidt 2021-07-14 20:08:41 UTC

SUMMARY

klipper does not provide the content of the clipboard after Ctrl-C, Mouse click, Ctrl-V.
The trigger is that I have set the clipboard memory size (Größe des Verlaufsspeichers) to 1. If set to two, it works.

STEPS TO REPRODUCE
1. Configure clipboard memory size (Größe des Verlaufsspeichers) to 1.
2. Open (for instance) in LibreOffice Calc a spreadsheet.
3. Mark one line with content.
4. Ctrl-C.
(Now the LibreOffice menu provides the option to Insert).
5. Click with mouse into one of the next rows
(Now the LibreOffice menu does not provide the option to Insert).

OBSERVED RESULT

6. Ctrl-V. Nothing is inserted.

The content is nonetheless available in klipper. If you select it there, it may be pasted again.

EXPECTED RESULT

The copied content must (not just should) be inserted.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Leap 15.2
KDE Plasma Version: 5.18.6
KDE Frameworks Version: 5.71.0
Qt Version: 5.12.7

ADDITIONAL INFORMATION

Let me state that I do not need and do not want any of the features that klipper provides, and never did! In fact this peace of software, which I apparently cannot remove or disable, is a constant annoyance. In general it is a security flaw: I do not want any clipboard content other than the current one available in the system. Old copies of possibly sensitive content are a major security hole.
This is why I had set the size of memory to 1 some months ago, in order to get the original behaviour of Copy&Paste which I am using for more than 35 years. klipper managed to kill one of the most basic functionalities of any OS GUI. Congratulations. You may imagine that this had an big negative impact on my work for those months, because I did not identify the root cause of this effect.
BTW: If I copy the source about five times very quickly, the paste sometimes works again. It's kind of bad magic.

Comment 1 David Edmundson 2021-07-14 20:16:05 UTC

You can disable klipper just remove the applet. Also being overly dramatic won't help your case.

Comment 2 David Edmundson 2021-07-14 20:21:18 UTC

Please can you confirm all the other settings in klipper?

Comment 3 Hayo Schmidt 2021-07-14 20:25:30 UTC

(In reply to David Edmundson from comment #1)
> You can disable klipper just remove the applet. Also being overly dramatic
> won't help your case.

Well, I cannot remove the applet. I can just "deactivate" it. If it helps, it is OK for my personal needs.

An no, I am not overly dramatic. I am sensible for other people running into the same problem.

Comment 4 Hayo Schmidt 2021-07-14 20:38:35 UTC

Created attachment 140061 [details]
Screenshot of my klipper settings

This attachment shows my configuration. I checked that exactly this configuration shows the error.

Comment 5 Hayo Schmidt 2021-07-14 20:42:19 UTC

(In reply to David Edmundson from comment #2)
> Please can you confirm all the other settings in klipper?

Please see my attachment with klipper settings.

When testing that this setting really shows the effect, I saw that Copy&Paste sometimes works also with this setting. In lets say one of five cases.

Comment 6 David Edmundson 2021-07-14 20:52:53 UTC

thanks

Comment 7 Nate Graham 2021-08-03 20:43:27 UTC

I cannot reproduce the issue with those steps. When I make my clipboard history size 1, select a cell in LO writer, and copy it, the text appears as the single item in Klipper, and I can paste it. I made sure all the other settings are the same as in your screenshot too.

If disabling Klipper is good enough for you (and this is a perfectly valid and supported use case), than I think we can close this. :)