Bug 503515

Summary:	Klipper should be a background process and not tied to the applet
Product:	[Plasma] kwin	Reporter:	Ellie <el>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	xaver.hugl
Priority:	NOR
Version First Reported In:	6.3.4
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Ellie 2025-04-29 10:14:54 UTC

SUMMARY

(My apologies if this isn't handled by KWin, I wasn't sure.)

It seems like even for simple small text items, the clipboard in KDE is no longer available after app that was copied from quits. This seems to be the case even for native Wayland apps, where I thought this legacy problem from X11 was meant to be fixed (wasn't it?). I would like to suggest this behavior is undesired and unexpected for most users, at least as long as the clipboard contents are small enough that there aren't any unreasonable resources being used to keep it available even after the source app has terminated.

STEPS TO REPRODUCE

1. Open any CTRL+C Wayland native app. I tried Brave and an Electron app, both via flatseal forced to use native Wayland.
2. Copy any text inside the app. Leave the app running.
3. Paste the text in e.g. KWrite or gedit to test that the clipboard works.
4. Terminate the source app now.
5. Try to paste again in e.g. KWrite or gedit to test that the clipboard no longer works.

OBSERVED RESULT

Pasting even small contents no longer works after source app quits.

EXPECTED RESULT

At least for native Wayland apps and for reasonably small clipboard contents, the contents should remain available indefinitely until something new is copied.

SOFTWARE/OS VERSIONS

Windows:
macOS:
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: postmarketOS v24.12
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0

ADDITIONAL INFORMATION

Comment 1 Bug Janitor Service 2025-04-29 10:33:42 UTC

Thank you for the bug report!

However Plasma 6.2.4 is no longer eligible for support or maintenance from KDE; supported versions are 5.27. (LTS), and 6.3 (non-LTS) or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one.

If you need support for Plasma 6.2.4, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE.

If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report.

Comment 2 Ellie 2025-05-02 13:18:15 UTC

I just checked, it also happens with 6.3.4.

Comment 3 Zamundaaa 2025-05-02 15:10:22 UTC

Do you have klipper enabled (right click system tray > configure system tray > entires > clipboard)? This is the expected behavior if you turned it off.

Comment 4 Bug Janitor Service 2025-05-17 03:47:09 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Ellie 2025-05-17 07:18:24 UTC

> Do you have klipper enabled (right click system tray > configure system tray > entires > clipboard)? This is the expected behavior if you turned it off.

I did! That's curious, perhaps this should be changed. To explain what I did, I disabled a lot of items in the system tray because the tray is too cluttered and that's apparently the only way to get Plasma to not make them show up again sometimes (and I don't want a clipboard history, beyond the current entry). Perhaps disabling a tray widget shouldn't disable the clipboard remaining persistent? I don't think disabling any other widget has the effect that some system-wide setting is changed or becomes unavailable.

Comment 6 Zamundaaa 2025-05-26 14:18:39 UTC

Yeah, ideally it shouldn't be tied to the applet.

*** This bug has been marked as a duplicate of bug 423625 ***