[Bug 24771] WoW 4.0.1 Cannot Login

[wine-bugs at winehq.org]

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

--- Comment #6 from alphasoup <o.eclarisse at gmail.com> 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
> 2) [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...

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.