Bug 491672

Summary:	Taking a screenshot, copy to clipboard appears to not work
Product:	[Applications] Spectacle	Reporter:	Phil Rigby <phil.rigby>
Component:	General	Assignee:	Noah Davis <noahadvs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kde, nate
Priority:	NOR
Version First Reported In:	24.05.2
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Phil Rigby 2024-08-13 14:31:11 UTC

***
I've taken several different screenshots, clicked the "Copy" button  to put the screenshot on the clipboard, but when I attempt to paste into anything, the paste does not occur.

Clipboard manager shows there's an image on the clipboard, but it won't open.

Clipboard is working fine with text and images from other sources - just screenshots from Spectacle seem to be a problem.

This did work on KDE 5, I used to use it quite a lot but under KDE 6, it's definitely not working correctly.
***

STEPS TO REPRODUCE
1.  Take a screenshot
2. Copy to clipboard
3. Try to paste into another application/window/whatever it may be, the paste does not work (either right-click/paste or CTRL+V)


OBSERVED RESULT
Nothing is pasted - like there is nothing on the clipboard

EXPECTED RESULT
Image that was grabbed from Spectacle should be pasted.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo Linux 2.15, kernel 6.9.2
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0 
Qt Version:  6.7.2

ADDITIONAL INFORMATION
It seems like the copy part of the process is failing, as nothing can open the image from the clipboard which suggests the image is corrupt/not complete.

Comment 1 Nate Graham 2024-08-13 16:45:20 UTC

Did you by any chance change the default screenshot file format to JPEG?

Comment 2 Phil Rigby 2024-08-13 17:47:06 UTC

In Settings, File Saving it is configured as JPG (without the E) but I haven't changed anything there.  I can do so if you want me to test.

Comment 3 Nate Graham 2024-08-13 18:09:21 UTC

I had a feeling. It's a known bug that's being addressed right now, in fact.

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