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 775631 - Emit owner-change signal once per clipboard content change
Emit owner-change signal once per clipboard content change
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Wayland
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: wayland 774975
 
 
Reported: 2016-12-05 12:33 UTC by Tomas Popela
Modified: 2018-05-02 17:49 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
test case (971 bytes, text/x-csrc)
2016-12-05 12:35 UTC, Tomas Popela 		Details

Description Tomas Popela 2016-12-05 12:33:55 UTC 
Right now if the clipboard content is changed than the owner-change signal as emitted twice: for the first time when the previous content is destroyed and for the second time for the new content. On X11 the signal was emitted only once - for the new content.
Comment 1 Tomas Popela 2016-12-05 12:35:51 UTC 
Created attachment 341393 [details]
test case
Comment 2 Jean-François Fortin Tam 2017-02-10 01:40:51 UTC 
Just to highlight/explain the relevance of this bug, as it turns out to be my #1 productivity blocker bug related to Wayland:

the broken clipboard interaction with Evolution (blocked bug #774975) is the main factor preventing me from using a Wayland-based GNOME to do my daily work, which is heavily email-based and requires tons of copy-pasting. It's a dealbreaker for me.
Comment 3 Matthias Clasen 2017-11-26 23:50:38 UTC 
I don't think it is wrong that the signal is emitted twice. Can you perhaps track down where this is causing problems ?
Comment 4 GNOME Infrastructure Team 2018-05-02 17:49:54 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/715.