-
-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
avoid clipboard loops when running nested / sharing sessions #1312
Comments
2016-09-17 06:27:26: antoine uploaded file
|
Done in r18229 (see commit message): we use a token which is never forwarded, then check for its presence at the other end. Still TODO:
|
Notifications and more done in r18230. Keeping this ticket assigned to me as I have seen shadow server hangs in the clipboard code, which may be caused / made worse / related to this. |
Crashes and other problems should be gone as of r18248. @maxmylyn: this ticket should ensure that we can coexist with other clipboard synchronization tools (ie: virtualbox, synergy, etc) and deal with it much more gracefully: disabling the clipboard and showing a notification to the user. Feel free to close. |
2018-02-02 17:04:23: maxmylyn commentedExcellent - noted. Closing |
Hit a clipboard loop which was not detected: #1814 |
2018-04-25 13:34:11: antoine commented
|
Another interesting data point is that switching to |
Meh. |
Related to #41.
Create a UUID for each clipboard helper and add it to a root window property. Clients and servers forward their list of UUIDs to the other end, which then adds those to the root window property.
If any duplicates are found, we have a loop.
Another way of dealing with this is to set a random token on startup, prevent this token from ever being sent across, then looking for it at the other end. Any other clipboard synchronization tool will copy it, then we know we have a loop.
The text was updated successfully, but these errors were encountered: