[Bug 46218] New: World of Warcraft A streaming error has occurred. ( WOW51900322) - wine-staging

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=46218

            Bug ID: 46218
           Summary: World of Warcraft A streaming error has occurred.
                    (WOW51900322) - wine-staging
           Product: Wine-staging
           Version: 3.21
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: o.dierick at piezo-forte.be
                CC: leslie_alistair at hotmail.com, z.figura12 at gmail.com
      Distribution: ---

World of Warcraft kicks the player back to the login screen with the error "A
streaming error has occurred. (WOW51900322)" a few seconds after choosing a
character and entering the game world.

The issue has been reported on the AppDB, WineHQ forums and eu/us blizzard
forums. The issue affects Linux players only.

See the How-to / Notes section of
https://appdb.winehq.org/objectManager.php?sClass=version&iId=36961

The workaround is to remove and replace the Cache directory in Program Files
(x86)\World of Warcraft\ by a Windows copy of the cache.

I experience the issue since I upgraded to Debian 9 and got rid of bug 42874.

I made several tests and pin-pointed the issue to the creaturecache.wdb and
gameobjectcache.wdb in World of Warcraft\Cache\WDB\ being corrupt when created.

I compiled a custom wine version : plain wine 3.21 + staged patchset from bug
45349 (with its staging dependencies).

With that custom version the Cache files are NOT corrupt and the issue doesn't
happen.

The 64-bit client requires wine-staging (bug 45349).

I have no knowledge of the issue with 32 bit version of the client and can't
test it myself due to (abandoned) bug 43656.

If the bug is indeed a regression in wine-staging, I guess people using
wine-staging to run the 32 bit game client also have the issue.

I'm currently conducting a regression test in wine-staging to pin-point the
patchset that causes the wrong file creation.

-- 
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.