After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 784549 - copy and paste not working if source application is closed
copy and paste not working if source application is closed
Status: RESOLVED DUPLICATE of bug 775313
Product: gnome-shell
Classification: Core
Component: general
3.22.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-07-05 13:45 UTC by dr.nukular
Modified: 2017-09-14 19:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description dr.nukular 2017-07-05 13:45:36 UTC 
The clipboard using copy and paste is not working properly.

The copied element is lost if the source application is closed. As long as the application is running, the content remains in the clipboard. This applies to any application. terminal, gedit, firefox, nautilus etc.

Steps to Reproduce:
1. Open gedit.
2. Type some text.
3. Copy some text.
4. Paste some text into another application.
5. Close gedit.
6. Paste same text again into another application.

The copied element is lost after source application is closed.

Fedora 25. Wayland. kernel 4.11.7-200.fc25.x86_64. gnome-shell 3.22.3.
Comment 1 André Klapper 2017-07-05 17:13:44 UTC 
It is working properly. 
When the application is closed, its buffer is destroyed.
I don't see how gnome-shell is involved here?
Comment 2 dr.nukular 2017-07-05 17:43:30 UTC 
If this issue is not related to gnome-shell, what else could it be? Wayland?

Do you mean that this is how it was intended to work? Why would that be an feature? To me it looks more like a bug.
Comment 3 Strangiato 2017-07-05 22:30:54 UTC 
I can confirm this problem under Wayland.
I think there is a bug report about it but I cant find it now.
Comment 4 Strangiato 2017-08-22 16:50:55 UTC 
3.26 beta has this same problem.
Comment 5 André Klapper 2017-09-14 19:39:59 UTC 
See bug 775313

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