Bug 502680

Summary: Previous entries in the clipboard pop-up are not pastable when selected multiple times under certain conditions
Product: [Plasma] plasmashell Reporter: Huanyu Liu <1293660441>
Component: Clipboard widget & pop-upAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: kdedev, nate, qydwhotmail
Priority: NOR Keywords: regression
Version First Reported In: 6.3.4   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=502444
Latest Commit: Version Fixed In: 6.3.5
Sentry Crash Report:

Description Huanyu Liu 2025-04-11 14:15:29 UTC 
SUMMARY
Previous items in the clipboard pop-up are not pastable when selected multiple times under certain conditions. See below for a reliable way to reproduce (which takes me half an hour to find out).

STEPS TO REPRODUCE
1. Launch Kate
2. Clear your clipboard history
3. Input "abc", select it, and press Ctrl+C to copy
4. Press Ctrl+V to paste "abc"
5. Input "def", select it, and press Ctrl+C to copy
6. Press Meta+V to open the clipboard pop-up, but do nothing and press Esc to quit
7. Press Ctrl+V to paste "def"
8. Press Meta+V to open the clipboard pop-up, and select the "abc" entry
9. Press Ctrl+V to paste "abc"
10. Press Meta+V to open the clipboard pop-up, and select the "abc" entry again
11. Press Ctrl+V

OBSERVED RESULT
Nothing is pasted

EXPECTED RESULT
The "abc" entry should be pasted

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.13.8-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
This bug is only reproducible with the clipboard pop-up, not the widget.
Comment 1 TraceyC 2025-04-11 19:46:32 UTC 
Thank you for all the time you took to narrow down the reproduction steps. I'm able to reproduce this in Plasma 6.3.4
The good news is that I'm not able to reproduce this with git-master. It looks like recent work with the clipboard has fixed this particular bug, and should be reaching your system when it updates to 6.3.5. 

Please reopen this report if you can reproduce the same bug with 6.3.5. Thanks!