Your message dated Mon, 28 Apr 2008 23:10:22 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#376003: wine: cannot do "followup" in Forte Agent
has caused the Debian Bug report #376003,
regarding wine: cannot do "followup" in Forte Agent
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
376003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=376003
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: wine
Version: 0.9.14-1
Severity: normal
When using the "Followup-To" function of the Usenet reader Forte
Agent, running on wine, by hitting "F" on a displayed article, the
process freezes: An hourglass is displayed, and nothing happens any
more.
The log file written to /tmp says something like:
wine: Unhandled exception 0xc0000090 at address 0x7f76f011 (thread 0009),
starting debugger...
Usage:
winedbg [ [ --gdb ] [ prog-name [ prog-args ] | <num> | file.mdmp |
--help ]
Going back to 0.9.12 from testing solved the issue for me.
Greetings
Marc
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.1-zgsrv
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
--- End Message ---
--- Begin Message ---
Marc Haber skrev:
I still see the bug once in a while, so if somebody else experiences
the same and finds the issue, it is at least shared pain and can
probably help in debugging.
Unlikely, there's no actual information for anyone in this report,
neither users suffering from the bug nor developers interested in fixing it.
If I were the maintainer, I'd leave the bug open, marked as
unreproducible. But that's of course not my decision.
I'm not seeing much point. Besides not being informative or useful,
there'd be no way to know when it's appropriate to close some vague,
unreproducible bug. A lot of stability fixes are done all the time, any
of them could apply to this problem, but with this kind of report, you'd
never know one way or another.
But if it happens again and you get a backtrace of it or something, feel
free to open a new report (or reopen this one if you prefer).
--- End Message ---
