<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - CLIPBOARD target request after PRIMARY request times out. GDK_SELECTION_NOTIFY has wrong selection id" href="https://bugzilla.gnome.org/show_bug.cgi?id=768177#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - CLIPBOARD target request after PRIMARY request times out. GDK_SELECTION_NOTIFY has wrong selection id" href="https://bugzilla.gnome.org/show_bug.cgi?id=768177">bug 768177</a> from <a href="page.cgi?id=describeuser.html&login=carlosg%40gnome.org" title="Carlos Garnacho <carlosg@gnome.org>"> Carlos Garnacho</a> <pre>Created <a href="attachment.cgi?id=330600&action=diff" name="attach_330600" title="wayland: Separate selection buffers and other per-selection atom data">attachment 330600</a> <a href="attachment.cgi?id=330600&action=edit" title="wayland: Separate selection buffers and other per-selection atom data">[details]</a> <a href='review?bug=768177&attachment=330600'>[review]</a> wayland: Separate selection buffers and other per-selection atom data This has most notably impact in selection buffers, because those were shared across all selection atoms. This turned out wrong on 2 situations: - Because the selection atom was set at SelectionBuffer creation time, the GDK_SELECTION_NOTIFY events generated will have unexpected info if the buffer is attempted to be reused for another selection. - Anytime different selections imply different stored content for the same target. This is better separated into per-selection buffers, so it's not possible to get collisions if a same target is used across different selections.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>