Bug 459335 - Klipper's history is not updated in the Wayland session
Summary: Klipper's history is not updated in the Wayland session
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Clipboard (show other bugs)
Version: 5.26.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-18 16:08 UTC by Ilya Bizyaev
Modified: 2023-09-07 18:45 UTC (History)
11 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ilya Bizyaev 2022-09-18 16:08:00 UTC
SUMMARY
No matter what text I copy, Klipper's history (both in the plasmoid and in the Meta+V dropdown) is not updated. Instead, I see the same list of old entries. Pasting the current entry works, but I'm used to accessing a few last ones, so it breaks my workflow.

STEPS TO REPRODUCE
1. Select any text in Konsole or Firefox
2. Press Ctrl+C to copy it
3. Press Meta+V to view Klipper history

OBSERVED RESULT
The top entry is not what you've just copied

EXPECTED RESULT
The top entry is what you've just have copied

SOFTWARE/OS VERSIONS
Operating System: openSUSE Leap 15.4
KDE Plasma Version: 5.25.90
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.5
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Comment 1 Fushan Wen 2022-09-19 04:21:28 UTC
Cannot reproduce on master. Can you still reproduce the bug in a new user environment?
Comment 2 Fushan Wen 2022-09-21 06:21:44 UTC
Update status
Comment 3 Ilya Bizyaev 2022-09-24 17:57:12 UTC
This problem has magically disappeared with an update and reboot :)
Comment 4 Ilya Bizyaev 2022-10-01 22:05:07 UTC
This is happening for me again, so there's something else in play :/

Previously, I could not reproduce this on a new user, but then I could also not reproduce this on my primary user, so I'm not sure if that's useful.
Comment 5 FedX 2022-10-02 14:37:16 UTC
I have seen this behavior as well, but what's interesting for me is, Klipper appears to think everything I copy is '#FDBC4B`. I do not know where that hex code is comming from, it it's not obviusly marked as anything. I had some success getting history to work if I enabled the action menue to appear on text copy, and cleared my clipboard history. Unfortunatly, systemctl is not reporting any bugs related to Klipper on my system, and there are unfortunatly contless subsystems that could cause behavior like this...
Comment 6 Ilya Bizyaev 2022-10-02 19:38:04 UTC
Interestingly, for me, Klipper's history is also stuck with an HTML color as its last element ("#050505")! I'm also pretty sure that happened last time as well.
Comment 7 Ilya Bizyaev 2022-10-02 19:40:44 UTC
I can confirm the following behavior:
* If I delete the last element (#050505) with a plasmoid action, it disappears from Meta+V
* As soon as I copy any text, #050505 becomes the last element in the history again
Comment 8 FedX 2022-10-24 16:54:59 UTC
I have been using Plasma 5.26 for the last 3 days and since I have not seen this bug arise. I will update this thread if I see it again, but I believe it's safe to say it's been fixed.
Comment 9 Ilya Bizyaev 2022-10-24 19:52:25 UTC
Still happening here with 5.26.
Comment 10 FedX 2022-10-24 20:40:20 UTC
Odd, maybe this is a bug with something completely unrelated to Plasma. I also got an update to WLRoots. 

Unrelated, I was looking at my `~/.config/klipperrc` and Klipper thought it was at version 5.25.5, I doubt that's related, but it's certainly worth looking into.
Comment 11 m.orly97 2022-12-01 18:03:54 UTC
(In reply to FedX from comment #5)
> I have seen this behavior as well, but what's interesting for me is, Klipper
> appears to think everything I copy is '#FDBC4B`. I do not know where that
> hex code is comming from, it it's not obviusly marked as anything. I had
> some success getting history to work if I enabled the action menue to appear
> on text copy, and cleared my clipboard history. Unfortunatly, systemctl is
> not reporting any bugs related to Klipper on my system, and there are
> unfortunatly contless subsystems that could cause behavior like this...

I guess that hex code comes from the color picker Plasma applet. If that's the case for you, I've found a workaround, namely open the settings of the color picker and un-check the "copy automatically in clipboard" option.
In my case this workaround hadn't solved completely the issue, as the "Klipper history not updating" problem still happens (seemingly at random), but at least it happens less frequently.
Comment 12 Ilya Bizyaev 2022-12-04 22:34:32 UTC
Indeed, deleting the Color Picker widget and restarting `plasmashell` made the issue go away :)
I'll keep track and let you know if this workaround is persistent.
Comment 13 Li Desheng 2023-01-07 16:20:50 UTC
I use archlinux, and I met the same problem today. All a day long's searching, finally I found it can be solved by installing "xwayland-protocols" and "xorg-xwayland" these two packages. Hope that can help you.
Comment 14 m.orly97 2023-01-08 12:37:31 UTC
(In reply to Li Desheng from comment #13)
> I use archlinux, and I met the same problem today. All a day long's
> searching, finally I found it can be solved by installing
> "xwayland-protocols" and "xorg-xwayland" these two packages. Hope that can
> help you.

I did not find the package "xwayland-protocols", did you mean "wayland-protocols"? Because I installed the latter but I'm still experiencing the issue with Firefox: the first time I copy something from Firefox, Klipper updates its history correctly, but if I copy again something from Firefox then Klipper does not update its history. It seems to work with other applications though.
Comment 15 Ilya Bizyaev 2023-01-28 12:34:19 UTC
*** Bug 463323 has been marked as a duplicate of this bug. ***
Comment 16 FreeLibre 2023-02-02 12:07:51 UTC
I can reproduce this in Firefox 109.0 installed using dnf but not on Telegram Desktop Flatpak.

Fedora 37 KDE Wayland.
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.6
Kernel Version: 6.1.8-200

Similar to my issue:
https://bugs.kde.org/show_bug.cgi?id=433854
https://bugs.kde.org/show_bug.cgi?id=462673
Comment 17 FreeLibre 2023-09-07 17:47:12 UTC
I'd like to report that I have not reproduced this bug in the last few months. So it seems to be fixed.

Plasma 5.27.7 + Fedora 38.
Comment 18 Ilya Bizyaev 2023-09-07 18:45:56 UTC
Let's close it then, I also can't reproduce it anymore.