http://bugs.winehq.org/show_bug.cgi?id=29505
--- Comment #5 from Lawrence E Toal let02do@earthlink.net 2012-01-02 16:24:41 CST --- Thanks Austin English, I don't know why I didn't git your result the first time, but this time through the process it ended with:
let01@arc:~/wine-git$ git bisect bad 82e1a4616cd4802e2c14c057732f6296be73580b is first bad commit commit 82e1a4616cd4802e2c14c057732f6296be73580b Author: Alexandre Julliard julliard@winehq.org Date: Sat Dec 10 13:27:16 2011 +0100
gdi32: Make sure that biSizeImage always contains the correct size in internal BITMAPINFO structures.
:040000 040000 64bcef12ed66371734d56f4b6a49ca923e0c6e6d a2fe84b5ea43ea2958855328ce06dff8ffcf3ba8 M dlls
just as yours did.
I did notice that after this bisect:
let01@arc:~/wine-git$ git bisect good Bisecting: 100 revisions left to test after this (roughly 7 steps) [3e1af081c02b01b513137d33b3972fb0d34e811d] include: Remove unneeded extern "C" directives.
The Bug symptoms changed slightly to a more graceful crash that did not freeze the partly drawn UI on the desktop. Wine closed by itself after the crash.
At this point, I went to the "git bisect bad" branch, and the original freezing symptoms returned. Following that branch led to our similar results. Would it be useful to reset the bisect to that step and try the "git bisect good" branch? I.E. are two different bugs happening?