2 Mar
2014
2 Mar
'14
8:45 p.m.
http://bugs.winehq.org/show_bug.cgi?id=30849
--- Comment #94 from Michael DeVore medv4380@yahoo.com --- You may want to wait until confirming an all clear for the issue. Several times just after a patch it would work flawlessly only to come back after Blizzard enabled scan that is believed to cause the issue. It may just mean that the check that causes the issue isn't currently enabled.
--
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.