Diablo® III

Open Issues:

None at this time.

Resolved Issues:

Opened: 06/06/2012 - 19:00 EDT | Closed: 06/07/2012 - 02:45 EDT
Hangs at "Authenticating Credentials"

http://us.battle.net/d3/en/forum/topic/5592457019?page=2#24
Bugzilla link: http://bugs.winehq.org/show_bug.cgi?id=30849#c36

Opened: 06/04/2012 - 18:00 EDT | Closed: 06/06/2012 - 16:00 EDT
"You have been removed from the game"

http://us.battle.net/d3/en/forum/topic/5271607015
Bugzilla link: http://bugs.winehq.org/show_bug.cgi?id=30849

Adding the WineHQ AppDB link for Linux users who happen to find this forum first. It contains info about issues with the installer, patching and a nice FAQ on problems (such as the ubuntu security fix) that have been worked out.

http://appdb.winehq.org/objectManager.php?sClass=version&iId=25953

this should really be a sticky

New issue seems to be refusal to authenticate. Works fine for Windows, but WINE clients are not being allowed past the Authenticating Credentials phase. The last lines of log output before this point indicate that it's reading some DLLs that are downloaded to the Cache directory when attempting to log in:

warn:module:load_builtin_dll failed to load .so lib for builtin L"C:\\users\\Public\\Application Data\\Blizzard Entertainment\\Battle.net\\Cache\\36\\b2\\36b27cd911b33c61730a8b82c8b2495fd16e8024fc3b2dde08861c77a852941c.auth": /home/jjs/.wine/dosdevices/c:/users/Public/Application Data/Blizzard Entertainment/Battle.net/Cache/36/b2/36b27cd911b33c61730a8b82c8b2495fd16e8024fc3b2dde08861c77a852941c.auth: invalid ELF header
warn:module:load_builtin_dll cannot open .so lib for builtin L"36b27cd911b33c61730a8b82c8b2495fd16e8024fc3b2dde08861c77a852941c.auth": /home/jjs/.local/lib/wine/36b27cd911b33c61730a8b82c8b2495fd16e8024fc3b2dde08861c77a852941c.auth.so: cannot open shared object file: No such file or directory
warn:module:load_builtin_dll failed to load .so lib for builtin L"C:\\users\\Public\\Application Data\\Blizzard Entertainment\\Battle.net\\Cache\\8f\\52\\8f52906a2c85b416a595702251570f96d3522f39237603115f2f1ab24962043c.auth": /home/jjs/.wine/dosdevices/c:/users/Public/Application Data/Blizzard Entertainment/Battle.net/Cache/8f/52/8f52906a2c85b416a595702251570f96d3522f39237603115f2f1ab24962043c.auth: invalid ELF header
warn:module:load_builtin_dll cannot open .so lib for builtin L"8f52906a2c85b416a595702251570f96d3522f39237603115f2f1ab24962043c.auth": /home/jjs/.local/lib/wine/8f52906a2c85b416a595702251570f96d3522f39237603115f2f1ab24962043c.auth.so: cannot open shared object file: No such file or directory
warn:module:load_builtin_dll failed to load .so lib for builtin L"C:\\users\\Public\\Application Data\\Blizzard Entertainment\\Battle.net\\Cache\\bc\\fa\\bcfa324ab555fc66614976011d018d2be2b9dc23d0b54d94a3bd7d12472aa107.auth": /home/jjs/.wine/dosdevices/c:/users/Public/Application Data/Blizzard Entertainment/Battle.net/Cache/bc/fa/bcfa324ab555fc66614976011d018d2be2b9dc23d0b54d94a3bd7d12472aa107.auth: invalid ELF header
warn:module:load_builtin_dll cannot open .so lib for builtin L"bcfa324ab555fc66614976011d018d2be2b9dc23d0b54d94a3bd7d12472aa107.auth": /home/jjs/.local/lib/wine/bcfa324ab555fc66614976011d018d2be2b9dc23d0b54d94a3bd7d12472aa107.auth.so: cannot open shared object file: No such file or directory
warn:winsock:wsaErrno errno 115, (Operation now in progress).


The files themselves are downloaded the instant the LOGIN button is pushed.


$ file **/*.auth
Cache/36/b2/36b27cd911b33c61730a8b82c8b2495fd16e8024fc3b2dde08861c77a852941c.auth: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows, UPX compressed
Cache/8f/52/8f52906a2c85b416a595702251570f96d3522f39237603115f2f1ab24962043c.auth: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows
Cache/bc/fa/bcfa324ab555fc66614976011d018d2be2b9dc23d0b54d94a3bd7d12472aa107.auth: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows



Edit:For clarification, I think the warnings are just WINE's attempts to find native equivalents for the DLL before falling back to it. The gist is that these files are being downloaded and functions inside are being called immediately between the first green checkmark and the (lack of) the second one.

Further interesting behavior is that it seems that in these cases, our friends are actually seeing us come online despite the feedback indicating that we've yet to be authenticated.

Does anyone important even read this?

06/06/2012 08:19 PMPosted by TityBlaster

Does anyone important even read this?

yeh me, the one who opened the bug with wine and has been coordinating this the best that i can for the past 48 hours

06/06/2012 08:22 PMPosted by DancingBear

Does anyone important even read this?

yeh me, the one who opened the bug with wine and has been coordinating this the best that i can for the past 48 hours

On the blizzard side?

06/06/2012 08:23 PMPosted by TityBlaster

yeh me, the one who opened the bug with wine and has been coordinating this the best that i can for the past 48 hours

On the blizzard side?

i wish

I will confirm this bug. I played for an hour after the "Removed from game" issue was corrected but now cannot log back on. Oddly, mine will either hang at authenticating credentials OR retrieving hero list.

I also second the vote for a sticky!

I'm not expecting too much, but I put in a support ticket. Even if it goes nowhere, at least it will be marked with a resolution of "Linux user, Lost sale", and increment that statistic by one.

Here's what I said in my support request (all 1500 characters of it)...

I have the "Starter" edition of Diablo III. I'm enjoying the game so far (when it works), and want to upgrade to the retail version, except it has been mostly unplayable for me since the evening of June 4th.

Some time Monday ev ening, the game began disconnecting me from battle.net after only a few minutes online. The game client would become unresponsive, maxing out on CPU usage. The only way to exit at that point it is to kill the Diablo III task. Starting the game again, I would be able to log in and play a few minutes more, until it did the same thing again. The onset of that issue coincided with Warden signa tures being enabled server-side.

The game was unplayable until I logged in right after the June 6th maintenance. It worked great again for a few hours. Then when I attempted to log in again later this evening, the same problem started happening again -- only this time, I was unable to make it through the authentication process. This appears to be yet again related to Warden, as if Warden had been disabled post-maintenance, then re-enabled several hours later.

Before we go on a wild goose chase with the troubleshooting script, I'm going to cut to the chase. I'm running the game under Wine on Ubuntu 12.04 64-bit. I and the many other such users who are currently discussing this issue on the forum would very much appreciate if the development team would lend some assistance in getting Warden to work properly on our platform, as they would be the best equipped to help.

Until the game is playable, there's no reason for me to upgrade, even though I would love to. I worry that the other Wine users who have already paid for the game will be left with no other choice than to ask for refunds, and that there are others like me with Starter who are waiting for a reason to upgrade, but cannot due to the software not working. I understand that this is not a supported platform, but a little goodwill toward loyal customers goes a long way.

Thank you.

On the blizzard side?

i wish

How do we get them as an audience? Do we all need to create support tickets?

As it seems like it is a Warden issue I doubt we'll get any help/feedback from Blizzard other than them fixing something on their side, silently. Security through obscurity and all that.

we need everyone to click "Request Sticky" for this thread lol

Which game version does you client display? I may be stuck on version 1.02a even thought it says it is up to date... I am on version 1.02.9950, shouldn't it be 1.02.9955?

06/06/2012 08:35 PMPosted by Defenestrate

Which game version does you client display? I may be stuck on version 1.02a even thought it says it is up to date... I am on version 1.02.9950, shouldn't it be 1.02.9955?

I'm on 9950.

OP thank you for helping us fellow Linux users with your thread

DB, you might want to use actual post-level links in the OP. That orange number on the right-hand margin gives a direct link to the post. As it stands, you have both issues linking to the first post of the exact same thread.

Reported for sticky. Also experiencing this.

Seriously Blizzard, if I keep being unable to play I may get a serious amount of work done.

hmm... game login screen shows 1.0.2.9950 for me still as well. launcher did appear to apply the patch, but perhaps not? where can we verify 9955 is latest build?