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 593653 - The function gdk_selection_owner_set_for_display() behaves not correctly
The function gdk_selection_owner_set_for_display() behaves not correctly
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: X11
2.17.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-08-31 11:11 UTC by tigran
Modified: 2018-02-10 03:33 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
This is an example of uncorrect behavior of the function (2.49 KB, text/plain)
2009-08-31 11:11 UTC, tigran 		Details

Description tigran 2009-08-31 11:11:35 UTC 
Created attachment 142117 [details]
This is an example of uncorrect behavior of the function

The function gdk_selection_owner_set_for_display() should send a SelectionClear
event when the send_event parameter is true and the new owner is different from
the current owner, but it doesn't.
Comment 1 tigran 2009-10-01 12:22:57 UTC 
The description of the problem (in English) as well the example demonstrating
it are available at http://linuxtesting.org/results/report?num=D0140 (please
note ".org" instead of ".ru").
Comment 2 tigran 2009-10-08 07:28:45 UTC 
The description of the problem (in English) as well the example demonstrating
it are available at http://linuxtesting.org/results/report?num=D0138 (please
note "138" instead of "140").
Comment 3 Matthias Clasen 2018-02-10 03:33:26 UTC 
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.