https://bugs.winehq.org/show_bug.cgi?id=22521 --- Comment #41 from Anastasius Focht <focht(a)gmx.net> --- Hello, --- quote --- Comment 35 was written over a year go. Since then the bug's status was NEW. Why is that if the bug "has been fixed some time ago" --- quote --- As I said in comment #34 the bug was recycled/badly managed until that point. Yes, it would have been Austin's or my task to re-confirm this as "new" or close the bug for good at that time, creating another one. Small mistakes happen since we do a lot of triaging work (in our spare time FYI), but this kind of is negligible. Analysis and explicit (re)confirmation by commenting were present, only the Bugzilla bug state was inconsistent. --- quote --- So, the "mixing in of unrelated issues" drew your attention to it again. You're welcome! --- quote --- I can't keep attention to every triaged bug on regular basis unless I completely stop triaging new bugs. I manage/triaged a large amount of Wine Bugzilla issues and partially provided analysis/solutions which require magnitudes more time. Revisiting of old/triaged bugs happens on my own schedule/preference. You could have written "still present", just like Austin did and it would have drawn my attention to this too. Upon closure I provided an explanation/trace excerpt to other people why I think this particular issue is fixed and mentioned that your recent comments had nothing to do with the actual issue. To intent was to avoid confusion/questioning of other people who don't understand the technical details. Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.