Created attachment 187205 [details] Prematurely ended pasted picture. SUMMARY From time to time, trying to paste a picture results in the picture partially pasted and the rest filled with white. Though very rarely, it happens. STEPS TO REPRODUCE 1. Copy a picture to the clipboard 2. Paste it OBSERVED RESULT The pasted picture is sometimes prematurely chopped and it fills the rest with something else EXPECTED RESULT The picture should be integrally pasted 100% of the times SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.5.3 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.0 ADDITIONAL INFORMATION
When this happens, if you press Meta+V to open the clipboard popup, is the copied image cut off in there too? Or does it look complete?
Actually, neither. Pictures don't show at all in the clipboard popup, only text entries. And it never did show images at all, for none of my Plasma setups. And even if it showed up in the clipboard (which it doesn't so once I copy anything else the picture is sent to oblivion and can't rely on clipboard popup to restore it), it would show up complete because the cutoff happens at paste time, so if I get the cutoff, cancel/delete the paste, and paste again, it shows up fine there. It seems like some paste events get prematurely ended but the surface area is still reserved so whatever didn't finish to paste gets filled with transparent, and in turn WhatsApp fills it with white, or maybe it's the opposite.
This all sounds very strange. Can you reproduce any of this in a new clean user account, *with no customization*?
As I said, I can't even manually trigger this behavior. It just happens randomly, I would say that 1 of every 100 paste events the image is cut mid-paste and the rest of the area gets filled of white. I know this isn't the proper way to debug an issue like this, but Plasma not waiting/making sure that the picture was fully pasted before terminating the paste event is my current guess. I might be completely wrong, though, but that's up to you to check and decide.
Yeah, unfortunately this sounds like it's not going to go anywhere unless you can figure out a more concrete set of steps to reproduce the issue. It would be useful to know if it *never* happens in a new clean user account with no customizations, though.