FS#63760 - [gnome-shell] Copying screenshots to clipboard doesn't always work in Wayland

Attached to Project: Arch Linux
Opened by Laurențiu Nicola (lnicola) - Saturday, 14 September 2019, 10:30 GMT
Last edited by freswa (frederik) - Saturday, 22 February 2020, 16:00 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Taking a screenshot with the "Copy a screenshot to clipboard" command doesn't always work, at least in Wayland sessions. Logging out and back in sometimes fixes this.
The screenshot app always works.

Additional info:
* gnome-shell 1:3.34.0+94+g3d86e6e79-1

Steps to reproduce:

1. Open Settings, go to Keyboard shortcuts, and map one of Copy a screenshot {,of a window,of an area} to clipboard.
2. Use the mapped shortcut.
3. Paste into GIMP or another editor. If it works, log out and try again.
This task depends upon

Closed by  freswa (frederik)
Saturday, 22 February 2020, 16:00 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.34.1+1+ge1fc4599-1
Comment by Laurențiu Nicola (lnicola) - Saturday, 14 September 2019, 10:53 GMT
Repro:

1. Start gedit and GIMP
2. Take screenshot of gedit, paste to GIMP, it works
3. Type some text in gedit, copy to clipboard, take screenshot, paste to GIMP (it doesn't work), paste to gedit (the old text is still in clipboard).
4. Select part of an image in GIMP, copy to clipboard, now screenshots work again.

Maybe it's a mutter bug (not gnome-shell), though?
Comment by Laurențiu Nicola (lnicola) - Saturday, 14 September 2019, 11:06 GMT Comment by Andrea (Dea1993) - Thursday, 24 October 2019, 08:59 GMT
i've the same problem
on gnome 3.34.1+5+g072a9a484-1 on wayland, i can't use ctrl-stamp to copy a screen to clipboard if i've already copied a text.

Steps to reproduce:
1) start a gnome shell wayland session
2) ctrl stamp (or ctrl alt stamp, or ctrl shift stamp)
3) paste somewhere (it works)
4) copy a text
5) paste somewhere (it works)
6) take again a screenshot
7) paste it somewhere (still paste the text, not the image)

using this command to clean the clipboard before taking a screen, "fix" the problem "echo -n | xclip -selection clipboard"
Comment by Laurențiu Nicola (lnicola) - Thursday, 24 October 2019, 09:06 GMT
@Dea1993 I wanted to write that this is now working for me, but you're right, there are still issues with screenshots.

These clipboard issues have been such a pain :-( (there were some other bugs you might have missed).
Comment by Andrea (Dea1993) - Thursday, 24 October 2019, 09:27 GMT
mmmm this is strange, i've everything updated but i still have this bug.
for now this is the only bug wich i noticed
when i've time i'll try to create a new user to see if there is a dirty config problem.
i don't know
Comment by Andrea (Dea1993) - Thursday, 24 October 2019, 09:35 GMT
i want also report that i've this problem only using shortkeys.
because if i use the graphic tool gnome-screenshot, take a screen and then i click on "Copy to clipboard" this works.

for example, i've tried this:
copy text from terminal
paste it on telegram (text pasted correctly)
than i've used ctrl stamp to take a screen, pasted it on telegram (still pasting the previous text)
take screenshot with gnome-screenshot tool, click on copy to clipboard, then paste on telegram (it works correctly)
Comment by Andrea (Dea1993) - Thursday, 24 October 2019, 18:26 GMT
i've tried downgrading gtk3 from version "1:3.24.12+32+g39e28ab933-1" to "1:3.24.12-1".
the problem of the screenshot seems solved, but with this version when i want to copy a text using ctrl-c,
i must hit several times ctrl-c to copy the text
Comment by Laurențiu Nicola (lnicola) - Thursday, 24 October 2019, 18:28 GMT
Yeah, that's what I meant in https://gitlab.gnome.org/GNOME/mutter/issues/789#note_631293. Please post there, not in both places.
Comment by Andrea (Dea1993) - Friday, 25 October 2019, 07:47 GMT
this seems an upstream bug, maybe this bug report could be closed?
Comment by Laurențiu Nicola (lnicola) - Friday, 25 October 2019, 08:08 GMT
I don't know what the Arch policy is -- other distributions often track issues in their packages.

It made sense to have this while Carlos was working on a fix, but now I'm not even sure that 3.36 will include one (and that's in five months anyway).
It also makes sense to keep it open so others can see it and not file new issues.
Comment by Andrea (Dea1993) - Thursday, 07 November 2019, 11:54 GMT Comment by Laurențiu Nicola (lnicola) - Friday, 22 November 2019, 11:28 GMT
Actually, I don't think this is fixed in the Arch package.
Comment by Andrea (Dea1993) - Friday, 22 November 2019, 11:33 GMT
on my system the last update of gnome-settings-daemon 3.34.1+1+ge1fc4599-1 (upstream commit e1fc4599764c9b10e086317164267c78f9338883) from repo's arch has fixed
Comment by Laurențiu Nicola (lnicola) - Friday, 22 November 2019, 11:35 GMT
I've been running into this for the past few weeks, so I'm not sure. Oh well.

Loading...