Bug 426787

Summary: unable to erease
Product: [Applications] klipper Reporter: viniciusbr <viniciusbrbio>
Component: plasma-widgetAssignee: Plasma Bugs List <plasma-bugs>
Severity: grave CC: bugseforuns, kde, nate
Priority: NOR    
Version: 5.19.90   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: trying to clear klipper

Description viniciusbr 2020-09-21 00:03:24 UTC

I can't erase the klipper history pressing the "clear history" icon in the applet. How can I debug it for better help?

Many thanks
Comment 1 David Edmundson 2020-09-23 16:27:47 UTC
Do you see a prompt when you try to clear?
Comment 2 viniciusbr 2020-09-23 16:48:09 UTC
Created attachment 131886 [details]
trying to clear klipper

No. I made a video showing it.
Comment 3 Bug Janitor Service 2020-10-08 04:33:13 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 viniciusbr 2020-10-08 11:00:35 UTC
Comment 5 Patrick Silva 2020-11-19 23:21:39 UTC
could your issue be a duplicate of bug 336053 viniciusbr?
Comment 6 viniciusbr 2020-11-19 23:57:08 UTC
I'm not sure. The bug 336053 seems to be related with the dialog option, witch is not my case.
Comment 7 Nate Graham 2021-04-01 20:03:06 UTC
Almost 100% chance this is 336053.

To fix it, open the file ~/.config/plasmashellrc and remove the line containing "really_clear_history=[something]"

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