wine users - Mar 2009 - about re-opening a bug

Hi,
I reported a bug [http://bugs.winehq.org/show_bug.cgi?id=17774] a while ago and
since it didn't crash after a fresh system restart, I proposed to close it,
which was done (by Austin English). But recently I got a crash after restart and
finally I compiled the source code for 1.1.17 to get useful info at the
backtrace.

I found out and the crash (with 1.1.17) happens exactly at the same spot as with
1.1.11. So, although wine is more solid at 1.1.17, it is less solid (for Fable)
than it was at 1.1.10.

I'm inclined to ask to reopen the bug but since I've no experience with
these situations, I would like to have advice on how to proceed.

I also found out someone else reported a crash with Fable
[http://bugs.winehq.org/attachment.cgi?id=20123&action=edit], and although
the backtrace doesn't contain all the debug info, it has the same call stack
until level it reaches 3.[/url]

fcmartins wrote:
> I'm inclined to ask to reopen the bug but since I've no experience
with these situations, I would like to have advice on how to proceed.
Just ask in the bug report to have it reopened as the problem appeared again in
wine-1.1.17 (or really never went away).