Comment 27 for bug 1129679

Is #26 an automated message? The bug has been confirmed for the current release, 13.10 (see #25).

Also, the wording of the message is a bit odd. It gives "there hasn't been any activity in [the bug] recently" as a justification for re-checking whether the bug still exists. I don't see why this might be an indication the bug is fixed: it just as likely indicates that the reporter believes they have supplied all requested information, and is now waiting for a fix.

It's reasonable to ask whether a bug still exists in a new release, but it has already been confirmed that it does.