[Bug 24771] New: WoW 4.0.1 Cannot Login

http://bugs.winehq.org/show_bug.cgi?id=24771

Summary: WoW 4.0.1 Cannot Login
           Product: Wine
           Version: 1.2.1
          Platform: x86
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: wldap32
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Created an attachment (id=31305)
 --> (http://bugs.winehq.org/attachment.cgi?id=31305)
executing World of Warcraft with WINEDEBUG=+wldap32

After a complete installation of the latest World of Warcraft patch 4.0.1, when
entering information to login it will kick back with an error message saying it
is unable to connect.  When the wldap32.dll from a windows installation is
placed in the folder for WoW and the dll is set to native, builtin, the login
works properly.  Attempted to run on a install from windows at first and had
this issue, so I downloaded and did a fresh installation.  The strange thing
about the fresh installation was that it did work up until the point where the
World of Warcraft Launcher had successfully downloaded and installed everything
up to date and then it stopped letting me log in at that point.  I also did a
fresh install and running the launcher to load wow that worked and I will post
the trace from it as a reply for comparison.

[Bug 24771] WoW 4.0.1 Cannot Login

http://bugs.winehq.org/show_bug.cgi?id=24771

--- Comment #1 from Joshua  2010-10-16 12:18:18 CDT ---
Created an attachment (id=31306)
 --> (http://bugs.winehq.org/attachment.cgi?id=31306)
Running WoW with WINEDEBUG=+wldap32

This is a trace of running a fresh install while the launcher has not
completely finished downloading all available content.  For whatever reasons I
am able to login by using the launcher under these circumstances.

[Bug 24771] WoW 4.0.1 Cannot Login

http://bugs.winehq.org/show_bug.cgi?id=24771

Thomas Spear  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from Thomas Spear  2010-10-16 17:42:49 CDT ---
err:virtual:map_image failed to set 60000020 protection on section .text,
noexec filesystem?

Key words in this error indicate that the filesystem is mounted with the noexec
option. What OS are you running, and what is the output of 'mount' by itself?

Also, try a newer wine version; you may have to build from source. The latest
version is 1.3.5 I believe.

[Bug 24771] WoW 4.0.1 Cannot Login

http://bugs.winehq.org/show_bug.cgi?id=24771

Devin Cofer  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #3 from Devin Cofer  2010-10-18 07:37:33 CDT ---
Install libldap (if you are using a 64-bit distro, make sure you have the
32-bit equivalent).

[Bug 24771] WoW 4.0.1 Cannot Login

http://bugs.winehq.org/show_bug.cgi?id=24771

alphasoup  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #4 from alphasoup  2010-10-18 22:22:10 CDT ---
Similar issue found with Ubuntu 9.10 all patches applied and wine 1.3, and
1.2.1:
err:virtual:map_image failed to set 60000020 protection on section .text,
noexec filesystem?

Error appeared with patch 4.0.1 on a wine and wow installation that used to
work just fine before that patch upgrade.

The following fix that worked in this case --
the disk where wow was installed was mounted from fstab using:

/dev/thedisk /media/themountpoint   ext3    users,relatime,errors=remount-ro 0 
     0

This worked for years without an issue.
Today to get Wow login to work required:
1) sudo umount /dev/thedisk
2) sudo fsck /dev/thedisk
3) sudo mount -o rw /dev/thedisk /media/themountpoint

The assumption is that there was an error during mount and the disk was
remounted ro each time (as this continued across system reboot). There was
however no issue found during fsck and no issue mounting the /dev/thedisk drive
in dmesg nor messages.

Still, after these three steps the wow login worked (finally). The login issue
occurred in wine 1.2 as well as wine 1.3.

[Bug 24771] WoW 4.0.1 Cannot Login

http://bugs.winehq.org/show_bug.cgi?id=24771

Aleksei Kazantsev  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #5 from Aleksei Kazantsev  2010-10-27 15:45:41 CDT ---
(In reply to comment #3)
> Install libldap (if you are using a 64-bit distro, make sure you have the
> 32-bit equivalent).

Thanks, that solved it for me.

[Bug 24771] WoW 4.0.1 Cannot Login

http://bugs.winehq.org/show_bug.cgi?id=24771

--- Comment #6 from alphasoup  2010-10-30 12:14:58 CDT ---
I think there are two threads here with same effect:
-- impossible to login after patch 4.0.1 until <something is done>.

This comment and comment #4 relate to comment #2 part of the thread
and has nothing to do -- in the end -- with wldap32 / ldap library workaround.

(In reply to comment #4)
> Similar issue found with Ubuntu 9.10 all patches applied and wine 1.3, and
> 1.2.1:
> err:virtual:map_image failed to set 60000020 protection on section .text,
> noexec filesystem?
>
> Error appeared with patch 4.0.1 on a wine and wow installation that used to
> work just fine before that patch upgrade.

This issue is not impacted (not fixed) by wldap32.
This also happens on a 32 bit system, there is no wldap32.dll
used in the wow folder, etc. The issue continues over a reboot.

To fix again after reboot, use steps 1 and 3:
> This worked for years without an issue.
> Today to get Wow login to work required:

1) sudo umount /dev/thedisk
> - [Optional] sudo fsck /dev/thedisk (NO EFFECT) -- this step can be ignored

3) sudo mount -o rw /dev/thedisk /media/themountpoint

After the 2 steps (unmount and remount rw) the Wow login works (again).

This recent login issue occurred in wine 1.2 as well as latest wine 1.3.5.

It looks as if something changed in the way Wow (windows) is assessing write
permission via wine/linux to access the drive mounted with the wow
installation.

The drive where Wow is installed can no longer be mounted
as rw by users (e.g. options "users,relatime,errors=remount-rw"),
but needs NOW to be mounted with option rw as root.

This issue would be unnoticed by users who install game on their
main system drive...

[Bug 24771] WoW 4.0.1 Cannot Login

http://bugs.winehq.org/show_bug.cgi?id=24771

Joshua  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED

--- Comment #7 from Joshua  2010-11-15 13:25:59 CST ---
I had been mounting my windows partitions as noexec, along with other various
folders I felt had no need for executables.  After changing my fstab and
removing my noexec option it worked.  Still, quite mysterious if you ask me. 
Everything worked fine up until they released the 4.0.1 patch.

[Bug 24771] WoW 4.0.1 Cannot Login

http://bugs.winehq.org/show_bug.cgi?id=24771

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED
         Resolution|FIXED                       |INVALID

--- Comment #8 from Austin English  2010-11-15 13:58:26 CST ---
Nothing was fixed in Wine. Sounds invalid.