http://bugs.winehq.org/show_bug.cgi?id=10693
Summary: Warcraft III no longer displays in-game chat messages Product: Wine Version: 0.9.50. Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P3 Component: wine-net AssignedTo: wine-bugs@winehq.org ReportedBy: d.zlatkov@gmail.com
After upgrading from 0.9.45 to 0.9.50, my WC3 TFT connects to battle net. However, I don't receive in-game chat messages from anyone else but the host. I also don't receive Signals from anyone else but the host. I can send messages and whispers.
Downgrading to 0.9.45 fixes the issue.
http://bugs.winehq.org/show_bug.cgi?id=10693
--- Comment #1 from Lei Zhang thestig@google.com 2007-12-07 11:50:52 --- Can you run a regression test?
http://wiki.winehq.org/RegressionTesting
or at least try the releases of wine between 0.9.45 and 0.9.50 to narrow it down?
http://bugs.winehq.org/show_bug.cgi?id=10693
--- Comment #2 from Austin English austinenglish@gmail.com 2007-12-07 12:27:07 --- Sounds like a dupe of bug 9787.
http://bugs.winehq.org/show_bug.cgi?id=10693
--- Comment #3 from Dimitar Zlatkov d.zlatkov@gmail.com 2007-12-07 13:10:17 --- Lei, I can't try the releases in between because 0.9.46-0.9.49 do not connect to Battle Net due to a partially implemented AcceptEx.
I'll try to do a regression test but this would be a first time for me and I'll do it end of next week (finals, sorry).
http://bugs.winehq.org/show_bug.cgi?id=10693
Dimitar Zlatkov d.zlatkov@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #4 from Dimitar Zlatkov d.zlatkov@gmail.com 2007-12-08 21:00:45 --- Okay, I'm sorry for being too hasty in reporting this. It must have been something with my computer, after rebooting everything works as expected with 0.9.50.
http://bugs.winehq.org/show_bug.cgi?id=10693
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Dan Kegel dank@kegel.com 2008-01-28 05:59:13 --- Closing all RESOLVED INVALID older than four weeks.