Steps: 1. Copy 3 different random texts for testing, for now you should see 3 textual items saved in Klipper widget, 2. Open Kate editor (or any app like Firefox) 3. Press Meta+V and select 2nd item 4. Press Ctrl+V to paste it into Kate 5. Press Meta+V, then without selecting any item from Klipper, click outside the floating window to cancel the operation 6. Press Ctrl+V into Kate Observed result: Nothing is pasted into Kate Wanted result: First item (previously second one) should be copied into Kate 7. Press Meta+V then re-select the first item 8. Press Ctrl+V inside Kate Observed result: Nothing is copied into Kate Wanted result: The first item should be copied into Kate Note: If I select any item different from the first one, Ctrl+V will paste it into Kate, but after cancelling Meta+V window the problem reappears again. Operating System: Manjaro Linux KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.9.0 Kernel Version: 6.14.2-1-MANJARO (64-bit) Graphics Platform: Wayland
Can reproduce
*** Bug 498341 has been marked as a duplicate of this bug. ***
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5398
*** Bug 502444 has been marked as a duplicate of this bug. ***
*** Bug 443265 has been marked as a duplicate of this bug. ***
Another scenario which needs to be repeated several times to result the same behavior: 1. Meta+V then select an item different from the first one 2. Paste it into Kate 3. Meta+V then select the first item (the same one currently copied) 4. Paste it into Kate 5. Repeat steps from 1 to 4 until you get nothing when you paste the copied text.
I can reproduce, and it seems Wayland specific
note that the items are not lost from the clipboard history, they are just lost from the current clipboard, ctrl+V doesn't work anymore, but the history is intact
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5526
Created attachment 181884 [details] Issue on Plasma 6.3.91 (6.4 Beta 2) Operating System: Arch Linux KDE Plasma Version: 6.3.91 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version: 6.14.7-arch2-1 (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-11300H @ 3.10GHz Memory: 9 GB of RAM (8.1 GB usable) Graphics Processor 1: NVIDIA GeForce GTX 1650 Graphics Processor 2: Intel® Iris® Xe Graphics Manufacturer: LENOVO Product Name: 82MG System Version: IdeaPad Gaming 3 15IHU6
Got the bug again in Plasma 6.4.2. Seems like that fix for 6.4 didn't work.
Yeah, the merge request contains a note: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5398#note_1223327 that explains why it did not work. I can still reproduce it every siungle time it seems. I often use clipboard to check what is in the clipboard without selecting anything, so this is quite severe for me :-(.
*** Bug 512889 has been marked as a duplicate of this bug. ***
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kguiaddons/-/merge_requests/191
Git commit b71af4e1afcf72b8c9da315dc8d728db70d753c0 by David Edmundson, on behalf of David Redondo. Committed on 15/12/2025 at 10:16. Pushed by davidedmundson into branch 'master'. ksystemclipboard: Dispatch read events in another thread WaylandClipboard wraps ext_data_control if an application tried to read the clipboard using QClipboard whilst it owns the data control we would deadlock. This was previously being solved by trying to transfer mimedata to the regular clipboard upon gaining focus. However this never worked reliably and efforts to fix this only made it more complicated. To solve the original deadlock all ext_data_control classes now live on another thread which dispatches events on a separate queue. A recursive mutex allows the main thread to read mimedata and no wayland events which change the mimedata process until this is complete. Related: bug 480448, bug 496029, bug 505281, bug 506467, bug 507792, bug 509065, bug 509689, bug 511736 FIXED-IN: 6.22 M +116 -14 src/systemclipboard/waylandclipboard.cpp M +3 -0 src/systemclipboard/waylandclipboard_p.h https://invent.kde.org/frameworks/kguiaddons/-/commit/b71af4e1afcf72b8c9da315dc8d728db70d753c0
The issue haven't been fixed after update Frameworks to 6.22 Operating System: EndeavourOS KDE Plasma Version: 6.5.4 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 Kernel Version: 6.18.4-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 32 GiB of RAM (30,7 GiB usable) Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: MINIPC PN52
It seems like i face this only in my main account and only clear desktop screenshot gives me blank element in clipboard new account almost everything seems to be fine
I'm having this issue exactly as shown in the attachment. Operating System: CachyOS Linux KDE Plasma Version: 6.5.4 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 Kernel Version: 6.18.3-2-cachyos (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-11300H @ 3.10GHz Memory: 9 GB of RAM (8.1 GB usable) Graphics Processor 1: Intel® Iris® Xe Graphics Graphics Processor 2: NVIDIA GeForce GTX 1650 Manufacturer: LENOVO Product Name: 82MG System Version: IdeaPad Gaming 3 15IHU6
Actualy for me, it is fixed, I cannot reproduce it (either the original description of the one from comment 6). I wonder what is different on our systems: Operating System: Fedora Linux 43 KDE Plasma Version: 6.5.4 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 Kernel Version: 6.18.3-200.fc43.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × Intel® Core™ i9-9880H CPU @ 2.30GHz Memory: 64 GiB of RAM (62.5 GiB usable) Graphics Processor 1: Intel® UHD Graphics 630 Graphics Processor 2: NVIDIA GeForce GTX 1650 with Max-Q Design
Fernando, are you experiencing the exact issue described in the original report, and are you experiencing it in a new clean user account on the same computer? If not, then your issue is something different, and let's get a new bug report about it.
(In reply to Nate Graham from comment #20) > Fernando, are you experiencing the exact issue described in the original > report, and are you experiencing it in a new clean user account on the same > computer? > > If not, then your issue is something different, and let's get a new bug > report about it. Yes, I'm now using CachyOS on the same notebook since November. I was using Arch Linux before.
And are you experiencing the exact issue described in the original report in a new clean user account on the same computer?
(In reply to Nate Graham from comment #22) > And are you experiencing the exact issue described in the original report in > a new clean user account on the same computer? I'm experiencing the exact same issue in a new clean user account on the same computer from my Bug 498341 that was marked as a duplicate of this one. Should I reopen my bug report instead?
(In reply to Fernando Marcelino Muniz from comment #23) > I'm experiencing the exact same issue in a new clean user account on the > same computer from my Bug 498341 that was marked as a duplicate of this one. > Should I reopen my bug report instead? Let's leave that other bug closed, since it was one of the developers who marked it as a duplicate of this one, which is open. I'm not able to reproduce this on Plasma built from git-master or on Neon Testing What would be really helpful is exact steps to reproduce currently, even if it seems redundant
From reading that other bug, it however does not deep like a duplicate of this one.
Created attachment 188490 [details] Issue on Plasma 6.5.5 I've just noticed that after rebooting an empty copy appears. I don't know if it's related to the failed pasting that lead me to reopen this bug.
Please don't report issue Y in a bug report for issue X; it just ends up confusing everyone. In such a circumstance, open a new bug report for issue Y. Thanks!
Created attachment 188656 [details] Issue on Plasma 6.5.5 Managed to get it on video. Operating System: CachyOS Linux KDE Plasma Version: 6.5.5 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 Kernel Version: 6.18.6-2-cachyos (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-11300H @ 3.10GHz Memory: 9 GB of RAM (8.1 GB usable) Graphics Processor 1: Intel® Iris® Xe Graphics Graphics Processor 2: NVIDIA GeForce GTX 1650 Manufacturer: LENOVO Product Name: 82MG System Version: IdeaPad Gaming 3 15IHU6
It really seems to me your bug is not a duplicate of this one. In the other bug, you say: > Nope, I cannot paste anything after copying a link sometimes, and then I check and link it indeed there, like the attachment shows. Also no, I didn't manually changed the order of copied links, as you can see in the attachment; there's only one link, making it technically the first link. Here, the crucial thing is that opening klipper and not selecting anything causes pasting stop working. For you, pasting sometimes does not work after copying something WITHOUT using klipper first (meaning opening its window to check on clipboards content). Am I correct? If so, your bug should be deduplicated and kept open.
The same conclusion was reached by TraceyC here: https://bugs.kde.org/show_bug.cgi?id=498341#c49 By the way, it is rather unclear if the other duplicates are indeed duplicates of this bug or your bug (BUG 498341). I, on the ot her hand, never experiences your issue. I have to invoke klipper, and that has indeed been fixed. I am a bit hesitatnt to close this bug and deduplicate Fernando since it has been already closed and reopened - maybe Nate can do it authoritatively?
Sorry for the confusion, folks. I've unmarked bug 498341 as a duplicate of this bug, since they do describe two different things. The older bug has been marked FIXED since fixes were merged. Reproduction steps from the video taken with 6.5.5 from comment #28 Clipboard is pinned. There are two entries, a URL and a number. The URL is highlighted Opened Kate Right click, select paste Nothing is pasted I'm keeping this bug open for now, since there are quite a few duplicates. I'm not able to reproduce the originally reported bug from this report on git-master. Is anyone else aside from Fernando experiencing the bug from the first comment, with a new clean user account, on Plasma 6.5.5 with Frameworks 6.22.0?
(In reply to TraceyC from comment #31) > I'm not able to reproduce the originally reported bug from this report on > git-master. Is anyone else aside from Fernando experiencing the bug from the > first comment, with a new clean user account, on Plasma 6.5.5 with > Frameworks 6.22.0? Sorry to speak for Fernando, but according to comment 23, he does and has not (I think) experienced this issue at all, he already said so :-). His bug is different, it seems.
(In reply to tomashnyk from comment #32) > Sorry to speak for Fernando, but according to comment 23, he does and has > not (I think) experienced this issue at all, he already said so :-). His > bug is different, it seems. Let's let Fernando speak for himself. Fernando, if you're experiencing something other than what is described in the original message, a new bug report is the appropriate thing to do at this time. Thanks.
🐛🧹 ⚠️ 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!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.