diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2010-10-03 21:45:45 +0200 |
|---|---|---|
| committer | Hans de Goede <hdegoede@redhat.com> | 2010-10-04 11:49:14 +0200 |
| commit | aabca2864d9439bc061feedd8d315b9aaac5c666 (patch) | |
| tree | 96060fe068e9d46e8029fdb125d5a842badf82c7 /python_modules/spice_parser.py | |
| parent | a2492d5ae347941b7a5bc13ad5a4de1c006b4ff0 (diff) | |
| download | spice-aabca2864d9439bc061feedd8d315b9aaac5c666.tar.gz spice-aabca2864d9439bc061feedd8d315b9aaac5c666.tar.xz spice-aabca2864d9439bc061feedd8d315b9aaac5c666.zip | |
spicec-x11: Force processing of ownerchange event when releasing the cb
Make sure we process the XFixesSetSelectionOwnerNotify event caused by
us setting the clipboard owner to none, directly after setting the owner
to none. Otherwise we may end up changing the clipboard owner to none, after
it has already been re-owned because the XFixesSetSelectionOwnerNotify event
to owner none is event is still pending when we set the new owner, and
then changes the owner back to none once processed messing up our clipboard
ownership state tracking.
I saw this happening when doing copy twice in succession inside the guest.
Diffstat (limited to 'python_modules/spice_parser.py')
0 files changed, 0 insertions, 0 deletions