<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - wine still deadlocks using libxcb1.9" href="https://bugs.freedesktop.org/show_bug.cgi?id=56441#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - wine still deadlocks using libxcb1.9" href="https://bugs.freedesktop.org/show_bug.cgi?id=56441">bug 56441</a> from <a class="email" href="mailto:fracting@gmail.com" title="fracting <fracting@gmail.com>"> fracting</a> <pre>Created <a href="attachment.cgi?id=69141" name="attach_69141" title="Log: Backtrace of deadlock threads">attachment 69141</a> <a href="attachment.cgi?id=69141&action=edit" title="Log: Backtrace of deadlock threads">[details]</a> Log: Backtrace of deadlock threads Hello, I'm one of lucky people who reproduce the "new deadlock" bug :) I reproduce the deadlock about 1/20, on Ubuntu 11.10, 3.0.0-26-generic-pae, libxcb 1.9, wine-1.5.15 However, as Erich E. Hoover point out in a private email, my deadlock doesn't seem to related with libxcb. I collect the backtrace here, and hopefully that helps, maybe there are more than one deadlock bugs, some people hits on a libxcb bug and some other people hits on another unknown bug like me. Cheers.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>