Bug 425015 - Copying an image to the clipboard doesn't work on Wayland
Summary: Copying an image to the clipboard doesn't work on Wayland
Status: RESOLVED DUPLICATE of bug 409798
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 20.04.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-05 00:33 UTC by Ricardo Canul
Modified: 2020-08-05 03:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ricardo Canul 2020-08-05 00:33:15 UTC
SUMMARY


STEPS TO REPRODUCE
1. Login to the system using Wayland
2. Take a screenshot
3. copy image to the clipboard
4. paste it on another program like Chrome to send the screenshot over whatsapp or messanger or any other service

OBSERVED RESULT
Spectacle shows a message saying that the image was correctly copied but when traying to paste it, it doesn't do anything.

EXPECTED RESULT
The image should paste correctly anywhere. because in Xorg it works fine, but in Wayland it doesn't

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.72.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
I tried copying another image to the clipboard from another source like an image from the web browser like Chrome and paste it to a messenging service like Messenger in the web browser and it worked fine on wayland, I also tried to paste the same image to another program like Krita to prove that it is not something that only works inside the web browser and it worked fine as well, with all of this I was trying to prove that it is not a problem with wayland. but since copying images to the clibpboard works in other programs I reach the conclusion that the "Copy the image to the clipboard" doesn't work on Spectacle using Wayland
Comment 1 Patrick Silva 2020-08-05 03:17:41 UTC

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