SUMMARY I want the clipboard to be as dumb and reliable as possible. Setting clipboard history to 1 entries does not fix the issue STEPS TO REPRODUCE Run plasma 6 and copy-paste different text multiple times OBSERVED RESULT It is utterly unpredictable and completely unreliable. EXPECTED RESULT Setting history to 1 should disable this supposed feature. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.5.2 KDE Frameworks Version: 6.19.0 Qt Version: 6.10.0 Kernel Version: 6.17.7-arch1-2 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Feels like this was never tested.
Please give specific steps about what you are doing and what doesn't work, otherwise this isn't actionable
Like i said: Setting clipboard history to 1 entries does not disable the clipboard manager. HOW do i disable it? Because the clipboard is very unreliable with it active. On Plasma 5 it could be fully disabled and that solved the issue.
Bug reports are intended to report, discuss and fix bugs. A better place to ask howto questions and ask for workarounds are either to reach out to EndeavourOS support, or on the forums: [https://discuss.kde.org/c/help/6](https://discuss.kde.org/c/help/6) Thanks for your understanding.
No, this is a KDE problem. It is reproducible on other distros. And this behavior DOES NOT make sense. It is a BUG and/or an implementation error.
If you are genuinely trying to describe a bug you would like us to fix, we need more details about the behavior you see. A video of the buggy behavior would be very helpful. Without knowing exactly what you see we don't know what to fix. Without more detail this won't be actionable. Thanks.
"Without more detail this won't be actionable" Yes it very much would be. As long as the clipboard manager cannot be disabled you cannot state that.
.
Stick your dot somewhere else. This solves nothing and is just dumb.
*** Bug 512536 has been marked as a duplicate of this bug. ***
You can disable the clipboard manager in the System Tray settings: set "Clipboard" to "Disabled. This may not have the effect you're hoping for, or will come with some unavoidable and undesirable side effects, but you can do it. In the future, please check the attitude at the door. This is a bug tracker, not a complaints department. I understand that you're feeling frustrated, but putting that frustration into bug reports isn't productive. Thanks for understanding.
As someone working with code you should understand the moments when a bug cannot be consistently be reproduced for days sometimes weeks and other times it affects your workflow every single day. I'm at the verge of pulling my hair out here in frustration.
Your feelings are your job to manage, not ours. You've been told how to disable the clipboard manager as you asked. Digging deeper, it would appear that you wanted to do so because of a specific bug you're encountering. If you'd like to report that bug, please do so on a new bug report that uses descriptive and accurate steps to reproduce, and calm, neutral language. That way, the bug report will be actionable and hopefully someone can investigate the issue and fix it. If you're not aware of how to trigger the bug in a reproducible way, it's worth doing some troubleshooting on your own side to try to nail down the circumstances under which it happens. Because without accurate information about when the issue happens, there's very little chance anyone can fix it, and reporting it anyway will be a waste of all our time.
Nate Graham - that's not a place I expected to look. But I believe it will solve the problem. Thank you for taking this seriously. I don't know what the warning is about: "Disabling the clipboard is not recommended, as it will cause copied data to be lost when the application it was copied from is closed. Instead consider configuring the clipboard to disable its history, or only remember one item at a time" --- Clipboard seems fine, even if I copy something, close the application fully and paste it in a newly spawned application, despite the warning so I guess it only applies to some edgecases or specific applications.
(In reply to Nate Graham from comment #13) > If you're not aware of how to trigger the bug in a reproducible way ... That wasn't exactly possible since the problem wasn't really specific to anything. It occurred with most applications, though not every application. There hasn't been a specific pattern to trigger the issues either. It only came and went. Chalk it up to cosmic rays or something. I dunno.
Lastly, I don't know who incorrectly changed the title. BUT the issues was never limited to text.