https://bugs.winehq.org/show_bug.cgi?id=40460
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1|d8599db40ada552cecf11235cf7 |df77e490d89a0582fde621d54f8 |70112b33fdf6a |34acfd9588ef9
--- Comment #2 from Austin English austinenglish@gmail.com --- (In reply to Sebastian Lackner from comment #1)
Could you please double-check that the regression test was done correctly? I cannot reproduce the issue here with wine-git and latest winetricks. Also please note that the regression commit only affects Win 3.1 applications, and I doubt that dotnet2.0 is such an executable. Are any special steps required to reproduce the issue?
Well, you're right that it wasn't that commit, it was: austin@austin2:~/wine-git$ git bisect bad df77e490d89a0582fde621d54f834acfd9588ef9 is the first bad commit commit df77e490d89a0582fde621d54f834acfd9588ef9 Author: Sebastian Lackner sebastian@fds-team.de Date: Tue Apr 5 16:20:05 2016 +0200
advapi32: Fix return value of RegNotifyChangeKeyValue for pending events.
Signed-off-by: Sebastian Lackner sebastian@fds-team.de Signed-off-by: Alexandre Julliard julliard@winehq.org
:040000 040000 92dd6b353e53d65eeff6d6769d707d2503a3ed3d 2db7099d0afc07f305b8ebb22e25cedf9f410bc3 M dlls
I can reproduce in wine-1.9.7-225-g1ccc521, and reverting your patch works around it for me.
Nothing special I can think of. I was testing on a remote machine over ssh with X11 fowarding, but I can also reproduce locally, so it's not that.