https://bugs.winehq.org/show_bug.cgi?id=53277
Bug ID: 53277 Summary: user32:edit - The edit field is sometimes empty after a paste on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs@winehq.org Reporter: fgouget@codeweavers.com
user32:edit - The edit field is sometimes empty after a paste on Windows:
edit.c:3211: Test failed: got 0 edit.c:3240: Test failed: got 0
https://test.winehq.org/data/patterns.html#user32:edit
These two failures can happen independently.
This may be caused by clipboard interference (see bug 47888 and bug 53276), though such interference is supposed to preserve the content of the clipboard.
Furthermore this not only happens with the Radeon driver but also on plain QXL VMs (w1064-1qxl on 2022-05-06 and 2022-05-31) and Nvidia machines (cw-gtx560 2022-04-26).
So this is probably related to the above bugs but it looks as if the clipboard gets cleared after it has been set which means a different workaround would be required (e.g. retrying the whole Copy+Paste multiple times).
https://bugs.winehq.org/show_bug.cgi?id=53277
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase
https://bugs.winehq.org/show_bug.cgi?id=53277
Eric Pouech eric.pouech@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |eric.pouech@gmail.com
--- Comment #1 from Eric Pouech eric.pouech@gmail.com --- I get similar errors on a VirtualBox virtual machine. my understanding is that VB, in order to provide guest <=> host clipboard features listens to clipboard write operation (in guest) to expose it to the host.
the test does: T1: open clipboard T2: write data into clipboard T3: close clipboard T4: send WM_PASTE to wndA T5: check that content put in the clipboard is present in wndA
very likely, the VB app is notified about clipboard change in T3, so opens the clipboard after T3. depending of the order of operation, it may weel be that the WM_PASTE can't do its work as it needs to open the clipboard to get its data, and the clipboard is still opened by the VB app. it seems that in that case the WM_PASTE just silently returns when it cannot open the clipboard
in my testing, it shows that the content of the clipboard is not erased, the WM_PASTE just silently fails (there's no returned value from SendMessage). But resending a WM_PASTE a while after just pastes the expected content