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.

Sign up for GitHub

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

Jump to bottom

Clipboard not working correctly #9

Closed
potatoattack opened this issue Aug 13, 2018 · 5 comments
Closed

Clipboard not working correctly #9

potatoattack opened this issue Aug 13, 2018 · 5 comments

Comments

@potatoattack
Copy link

Copy and pasting from a wine program into a non-wine program does not work. Though it works the other way around.
With a clean wine prefix I run:

wine notepad

then open a native text editor (e.g., kate) and copy and paste text back and forth between them. Sometimes it takes a few copies before it fails.
This happens with esync enabled and disabled.
Please let me know if any logs would be useful.
@zfigura
Copy link
Owner

zfigura commented Aug 13, 2018

I can't seem to easily reproduce this. If you can reproduce this with a +server,+clipboard,+hook log, can you please attach one?

@potatoattack
Copy link
Author

potatoattack commented Aug 13, 2018 •
edited
Loading

Sure, here is a log with it happening a few times.
wine.log.gz
made with:
WINEDEBUG=+server,+clipboard,+hook notepad > wine.log 2>&1

zfigura added a commit that referenced this issue Aug 14, 2018
@zfigura
ntdll, server: Revert to old implementation of hung queue detection.
9b7bb12 
By manually notifying the server every time we enter and exit a message wait.

The hung queue logic keeps breaking. In the case of bug #9 it was breaking
because we were waiting for more than 5 seconds on our queue and then someone
sent us a message with SMTO_ABORTIFHUNG. Just stop fighting against the
server and try to coöperate with it instead. It takes two extra server calls,
but ideally the GUI thread isn't going to be in the same sort of performance-
critical code that this patchset was written for.
@zfigura
Copy link
Owner

zfigura commented Aug 14, 2018

Thanks. I'm not sure why I couldn't reproduce the bug on my machine, but the cause was clear enough. Can you test with the latest master? If necessary I can provide a tarball of the patches.

@potatoattack
Copy link
Author

Yep this has fixed the issue =D

@zfigura
Copy link
Owner

zfigura commented Aug 14, 2018

Thanks; closing then.

@zfigura zfigura closed this as completed Aug 14, 2018
zfigura added a commit that referenced this issue Oct 7, 2018
@zfigura
ntdll, server: Revert to old implementation of hung queue detection.
736cc81 
By manually notifying the server every time we enter and exit a message wait.

The hung queue logic keeps breaking. In the case of bug #9 it was breaking
because we were waiting for more than 5 seconds on our queue and then someone
sent us a message with SMTO_ABORTIFHUNG. Just stop fighting against the
server and try to coöperate with it instead. It takes two extra server calls,
but ideally the GUI thread isn't going to be in the same sort of performance-
critical code that this patchset was written for.
zfigura added a commit that referenced this issue Nov 1, 2018
@zfigura
ntdll, server: Revert to old implementation of hung queue detection.
1a49022 
By manually notifying the server every time we enter and exit a message wait.

The hung queue logic keeps breaking. In the case of bug #9 it was breaking
because we were waiting for more than 5 seconds on our queue and then someone
sent us a message with SMTO_ABORTIFHUNG. Just stop fighting against the
server and try to coöperate with it instead. It takes two extra server calls,
but ideally the GUI thread isn't going to be in the same sort of performance-
critical code that this patchset was written for.
kakra pushed a commit to kakra/wine-proton that referenced this issue Jan 11, 2019
@zfigura @kakra
ntdll, server: Revert to old implementation of hung queue detection.
3ddffdb 
By manually notifying the server every time we enter and exit a message wait.

The hung queue logic keeps breaking. In the case of bug zfigura/wine#9 it was
breaking because we were waiting for more than 5 seconds on our queue and
then someone sent us a message with SMTO_ABORTIFHUNG. Just stop fighting
against the server and try to coöperate with it instead. It takes two extra
server calls, but ideally the GUI thread isn't going to be in the same sort
of performance-critical code that this patchset was written for.
kakra pushed a commit to kakra/wine-proton that referenced this issue Jan 19, 2019
@zfigura @kakra
ntdll, server: Revert to old implementation of hung queue detection.
e5cb7d8 
By manually notifying the server every time we enter and exit a message wait.

The hung queue logic keeps breaking. In the case of bug zfigura/wine#9 it was
breaking because we were waiting for more than 5 seconds on our queue and
then someone sent us a message with SMTO_ABORTIFHUNG. Just stop fighting
against the server and try to coöperate with it instead. It takes two extra
server calls, but ideally the GUI thread isn't going to be in the same sort
of performance-critical code that this patchset was written for.
kakra pushed a commit to kakra/wine-proton that referenced this issue Jan 23, 2019
@zfigura @kakra
ntdll, server: Revert to old implementation of hung queue detection.
c8a3fab 
By manually notifying the server every time we enter and exit a message wait.

The hung queue logic keeps breaking. In the case of bug zfigura/wine#9 it was
breaking because we were waiting for more than 5 seconds on our queue and
then someone sent us a message with SMTO_ABORTIFHUNG. Just stop fighting
against the server and try to coöperate with it instead. It takes two extra
server calls, but ideally the GUI thread isn't going to be in the same sort
of performance-critical code that this patchset was written for.
kakra pushed a commit to kakra/wine-proton that referenced this issue Feb 5, 2019
@zfigura @kakra
ntdll, server: Revert to old implementation of hung queue detection.
b1c8b55 
By manually notifying the server every time we enter and exit a message wait.

The hung queue logic keeps breaking. In the case of bug zfigura/wine#9 it was
breaking because we were waiting for more than 5 seconds on our queue and
then someone sent us a message with SMTO_ABORTIFHUNG. Just stop fighting
against the server and try to coöperate with it instead. It takes two extra
server calls, but ideally the GUI thread isn't going to be in the same sort
of performance-critical code that this patchset was written for.
kakra pushed a commit to kakra/wine-proton that referenced this issue Feb 23, 2019
@zfigura @kakra
ntdll, server: Revert to old implementation of hung queue detection.
b1318cf 
By manually notifying the server every time we enter and exit a message wait.

The hung queue logic keeps breaking. In the case of bug zfigura/wine#9 it was
breaking because we were waiting for more than 5 seconds on our queue and
then someone sent us a message with SMTO_ABORTIFHUNG. Just stop fighting
against the server and try to coöperate with it instead. It takes two extra
server calls, but ideally the GUI thread isn't going to be in the same sort
of performance-critical code that this patchset was written for.
kakra pushed a commit to kakra/wine-proton that referenced this issue Mar 9, 2019
@zfigura @kakra
ntdll, server: Revert to old implementation of hung queue detection.
301b55d 
By manually notifying the server every time we enter and exit a message wait.

The hung queue logic keeps breaking. In the case of bug zfigura/wine#9 it was
breaking because we were waiting for more than 5 seconds on our queue and
then someone sent us a message with SMTO_ABORTIFHUNG. Just stop fighting
against the server and try to coöperate with it instead. It takes two extra
server calls, but ideally the GUI thread isn't going to be in the same sort
of performance-critical code that this patchset was written for.
kakra pushed a commit to kakra/wine-proton that referenced this issue Mar 17, 2019
@zfigura @kakra
ntdll, server: Revert to old implementation of hung queue detection.
c0310c8 
By manually notifying the server every time we enter and exit a message wait.

The hung queue logic keeps breaking. In the case of bug zfigura/wine#9 it was
breaking because we were waiting for more than 5 seconds on our queue and
then someone sent us a message with SMTO_ABORTIFHUNG. Just stop fighting
against the server and try to coöperate with it instead. It takes two extra
server calls, but ideally the GUI thread isn't going to be in the same sort
of performance-critical code that this patchset was written for.
zfigura added a commit that referenced this issue Jul 29, 2019
@zfigura
ntdll, server: Revert to old implementation of hung queue detection.
76d842a 
By manually notifying the server every time we enter and exit a message wait.

The hung queue logic keeps breaking. In the case of bug #9 it was breaking
because we were waiting for more than 5 seconds on our queue and then someone
sent us a message with SMTO_ABORTIFHUNG. Just stop fighting against the
server and try to coöperate with it instead. It takes two extra server calls,
but ideally the GUI thread isn't going to be in the same sort of performance-
critical code that this patchset was written for.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zfigura @potatoattack