Skip to content
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

clipboard copying from server to client doesn't work. #2461

Closed
totaam opened this issue Oct 23, 2019 · 6 comments
Closed

clipboard copying from server to client doesn't work. #2461

totaam opened this issue Oct 23, 2019 · 6 comments
Labels

Comments

@totaam
Copy link
Collaborator

totaam commented Oct 23, 2019

Issue migrated from trac ticket # 2461

component: android | priority: blocker | resolution: fixed

2019-10-23 07:59:07: jiang.qian created the issue


After updating from 3.0 (24095) to 3.0.1(24241), the text clipboard copying from server window to client doesn't work any more.

I am using Ubuntu 18.04 64 bit on both server and client. Before the update, clipboard copying on both directions work. after updating, I can only copy from client to server, but not from server to client. Clipboard was of course selected as "both direction".

This seems to be the bug in client side, because when I run the server as 3.0.1 and client downgraded to 3.0.0, the clipboard copying works again in both directions, though I constantly got message

2019-10-23 02:52:31,514  valid targets: TIMESTAMP, TARGETS, SAVE_TARGETS, MULTIPLE, STRING, UTF8_STRING, TEXT, text/plain
2019-10-23 02:52:31,515  dropping the request

on the client logs, these seems not to affect the copying process.

Needless to say, this is a major blocking issue and it forces me to downgrade the client. Please let me know what more help I can provide to debug this.

@totaam
Copy link
Collaborator Author

totaam commented Oct 23, 2019

2019-10-23 12:34:58: antoine changed status from new to assigned

@totaam
Copy link
Collaborator Author

totaam commented Oct 23, 2019

2019-10-23 12:34:58: antoine edited the issue description

@totaam
Copy link
Collaborator Author

totaam commented Oct 23, 2019

2019-10-23 12:34:58: antoine commented


This is likely to be caused by #2450, you should be able to revert r24231.

@totaam
Copy link
Collaborator Author

totaam commented Oct 23, 2019

2019-10-23 13:23:19: antoine changed status from assigned to closed

@totaam
Copy link
Collaborator Author

totaam commented Oct 23, 2019

2019-10-23 13:23:19: antoine set resolution to fixed

@totaam
Copy link
Collaborator Author

totaam commented Oct 23, 2019

2019-10-23 13:23:19: antoine commented


The commit has been reverted in r24245, and the correct fix applied in r24247.

I will re-issue 3.0.1 with this one fix applied on top.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant