<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Regression since 1.11.4: Corrupt drawing on mingw64 build used with virt-viewer 0.5.5 binaries" href="https://bugs.freedesktop.org/show_bug.cgi?id=61876#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Regression since 1.11.4: Corrupt drawing on mingw64 build used with virt-viewer 0.5.5 binaries" href="https://bugs.freedesktop.org/show_bug.cgi?id=61876">bug 61876</a> from <a class="email" href="mailto:grant@opped.net" title="Grant C. <grant@opped.net>"> Grant C.</a> <pre>Created <a href="attachment.cgi?id=76798" name="attach_76798" title="git bisect log">attachment 76798</a> <a href="attachment.cgi?id=76798&action=edit" title="git bisect log">[details]</a> git bisect log I've attached a partial bisect log. After getting to this point, the individual revisions that built successfully caused a crash with remote-viewer, preventing me from being able to continue as at that point I'd be bisecting a different issue. I can switch focus to finding the next revision that works without causing a crash, but that'd still leave us with a range of revisions that we can't easily build to track down which one is causing the regression..</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>