https://bugs.kde.org/show_bug.cgi?id=470677

Pedro V <voidpointertonull+bugskde...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |voidpointertonull+bugskdeor
                   |                            |g...@gmail.com

--- Comment #5 from Pedro V <voidpointertonull+bugskde...@gmail.com> ---
Didn't know about "qdbus org.kde.KWin /KWin org.kde.KWin.showDebugConsole",
that's really handy for looking into this kid of issues.

There are likely multiple issues here:
- Authenticators are supposed to keep the clipboard clean
- There might be an XWayland clipboard problem
- Klipper is not always showing what's actually on the clipboard

First one is not really feasible to check, so just guessing there, but I find
it likely that Authy clears the clipboard on exit which is not a problem on its
own, but it gets tricky combined with the Klipper problem.

XWayland is a bit trickier for me as it's surely riddled with odd issues and
I'm trying to avoid it wherever possible, but I think I could reproduce the
problem. Copied from a program using XWayland, exited, and even though the
debug console didn't show a clipboard change, I could no longer paste the
content even though it works before exiting.

Klipper is definitely misleading as it ignores some entries, mostly secrets and
various attempts to clear the clipboard, resulting in showing stale clipboard
content.
For example:
- Copy some text
- Run: wl-copy ""
- Observe Klippy still showing the copied text while the clipboard is already
empty

I'm not too confident in my limited testing as I heavily prefer Wayland where I
haven't seen this issue since I've realized that Klipper history size needs to
be at least 1 (apparently it can't be even set to 0 anymore), so recommending
attempting to isolate this problem to XWayland first.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to