Since version 6.5.3 the command „Copy” won’t store a (rectangular region) screenshot to the clipboard any more – like it used to do up to now.

After clicking on „Copy” there is a notification at the top of the Spectacle window saying „Screenshot was copied to clipboard”. There is no notification from the clipboard itself.

The subsequent command „Paste”, e. g. in LibreOffice, inserts nothing at all.

When inspecting the contents of the clipboard, there is a new placeholder line that appears at the top of the clipboard contents, but it is black, containing nothing.

The bug lives on in version 6.5.4.

I have to save screenshots to a folder/to desktop in order to be able to use them. They cannot be used directly via the clipboard any more, like in previous versions.

However – I just learned (!): whenever I start Spectacle using the shortcut „Meta + Shift + Print” it will still do the job! In that case, there is no notification inside the Spectacle window. The Spectacle window immediately vanishes after clicking „Copy”, and instantly there is a notification from the clipboard: „Notification from Spectacle: A screenshot was copied to clipboard”. Everything is normal then: the screenshot is listed at the top of the clipboard contents, and it can be pasted e. g. into LibreOffice.

Only it refuses to work when I start Spectacle by clicking on its icon in the task bar.

SUMMARY


STEPS TO REPRODUCE
1. Start Spectacle by clicking on its icon in the task bar
2. Take a screenshot (rectangular region) and choose "Copy"
3. Open a LibreOffice document and give the command "Paste"


OBSERVED RESULT
Nothing is pasted

EXPECTED RESULT
The screenshot should be pasted into the LibreOffice document.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Manjaro KDE
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION
1. See above: it still works when Spectacle is launched by shortcut "Meta + Shift + Print".
2. I read in the bug history that this bug is not unknown, but was fixed in the past, years ago. However, it has surfaced again in version 6.5.3.