https://bugs.kde.org/show_bug.cgi?id=480448
--- Comment #2 from php4...@gmail.com --- > Can you reproduce that it always fails to copy/paste while the notification > is open, but always succeeds to copy/paste after the notification has > disappeared on its own after 5 seconds? I don't know how to make sense of your question, unless when you say "copy/paste" you mean just "paste". If that is the case, if what you meant is "paste", then the answer is no, I cannot reproduce that. The sequence of events is: - I hit the keyboard shortcut for capturing a rectangular region - the tool shows up allowing me to select a region of the screen to capture - when I'm happy with the selection I hit Enter. => This is when the screenshot is taken and this is the moment when it's supposed to be copied to clipboard (because that's how it's configured in the settings) - and NOW the notification shows up saying the screenshot has been copied. As I said, it usually works as expected, but there was this instance where it stopped working, and nothing would be copied. To copy after the notification is gone is impossible, because the notification appears exactly when (or immediately after, from a logical standpoint) the screenshot is supposedly copied to clipboard (that's what the notification says: that the screenshot has been copied to the clipboard). When this started happening, it was reproducing consistently, meaning I took several screenshots repeating the steps above and none of them was ever copied to the clipboard. I can't say with 100% certainty whether I was pasting before or after the notification had disappeared, but given that I am not particularly quick in my movements, I can bet money that at least some of the screenshot I took, I attempted to paste after the notification had gone. And now that it's working as expected, I have tested making sure I paste quickly before the notification vanishes, and it pastes as expected, so the copying is correctly done at the moment of taking the screenshot, as expected. After I once copied manually by using the button in the tool, then not only it worked, but also the issue stopped happening and I haven't observed it again, so there's no reproducible pattern that I know of. I hope that answers your question. -- You are receiving this mail because: You are watching all bug changes.
