[Bug 20643] New: World of Warcraft patcher tries to change folder permissions

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

Summary: World of Warcraft patcher tries to change folder
                    permissions
           Product: Wine
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

WoW downloaded a new hotfix via its launcher (Launcher.exe).  Download went
fine, but when it tried to apply the patch, it vanished. The World of Warcraft
directory permissions had changed and set owner to not read/write/execute in
that folder.

I reset the permissions and then tried several times, with the same results.

I eventually chown'ed the directory as root's, and then set permissions to
world-writable so the patcher could run as non-root, but would not rewrite
permissions.

The patcher was started as non-root, and I got this error:

"Launcher requires write permission to the Z:\home\xxxxxx\World of Warcraft\
directory to successfully patch the game. Please enable write access to the
directory using an administrator account."

Launching the game using Wow.exe still works. Launcher.exe continues trying to
patch, and therefore complains about permissions.

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

Robert Andersson  changed:

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

--- Comment #1 from Robert Andersson   2009-11-10 03:30:00 ---
Yes, same problem here, started with the hotfix that got downloaded today.

Pretty much makes it impossible to use the Wow launcher.

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

--- Comment #2 from Vitaliy Margolen   2009-11-10 08:25:22 ---
Wine version? Please attach +advapi,+file,+ntdll trace.
Also make sure you running the program properly:
http://wiki.winehq.org/FAQ#run_from_terminal

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

--- Comment #3 from Robert Andersson   2009-11-10 12:40:45 ---
Created an attachment (id=24643)
 --> (http://bugs.winehq.org/attachment.cgi?id=24643)
WINEDEBUG="+advapi,+file,+ntdll" wine Launcher.exe &> /tmp/output.txt

Debug-output as requested.

Wine version 1.1.32

Search for SetFileSecurityW in the debug-output, what follows is likely the
culprit as a bit after the WoW-directory has lost its write-access and all
file-opens start returning errno = 13

Regards, Robert.

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

Juan Lang  changed:

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

--- Comment #4 from Juan Lang   2009-11-11 13:44:00 ---
*** Bug 20665 has been marked as a duplicate of this bug. ***

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

PlaNet Fox  changed:

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

--- Comment #5 from PlaNet Fox   2009-11-11 16:27:51 ---
I have exactly same Problems, since wow patch with the same wine version

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

Erik  changed:

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

--- Comment #6 from Erik   2009-11-12 05:55:56 ---
I see this behaviour as well but after the patch.It seems that the patch
consists of a new version of Launcher.exe that not only tries but succeeds in
changing directory permissions of the WoW directory from drwxr-xr-x into
d---r-x---, which makes the directory completely inaccessible. This makes it
impossible for the launcher tot start WoW,exe. Rumors are that this is intended
by Blizzard to avoid multiboxing (which simply can be avoided by starting
multiple instances of WoW.exe).
A quick and (very) dirty workaround is to restore the permissions by hand while
Launcher.exe is still active.
Strangely when running the program from an NTFS partition directory permissions
are left alone or restored properly...
This behaviour is seen in all Wine versions 1.1.13-1.1.32.

Funny thing is: people running WoW on native Windows platform are reporting
exactly the same problem.
I'm not convinced this is really a Wine bug...it seems to me that Blizzard's
developers could use some education..:-)

Best regards, Erik

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

Sean  changed:

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

--- Comment #7 from Sean   2009-11-12 20:16:58 ---
Here is a dirty workaround that allows me to run the game through the Launcher
for now.

Start the Launcher with this bash script:

#!/bin/bash

nohup env WINEPREFIX="/home/sean/.wine" wine "C:\Games\World of
Warcraft\Launcher.exe" &
sleep 1
chmod 770 -v ~/.wine/drive_c/Games/World\ of\ Warcraft
echo "Exiting"
exit 0

You need to change the directory names to match your own, but this should set
the proper permissions to your WoW folder 1 second after starting the
Launcher(you may have increase this if you have a slow computer), and then exit
the script. This should make the game launchable through the Launcher, and
hopefully allow the installation of future patches through the
launcher(hopefully the future patches fix this)

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

Dmitry Timoshkov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|unspecified                 |1.1.32

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

--- Comment #8 from Erik   2009-11-13 05:16:06 ---
(In reply to comment #7)
> Here is a dirty workaround that allows me to run the game through the Launcher
> for now.
>
> Start the Launcher with this bash script:
>
> #!/bin/bash
>
> nohup env WINEPREFIX="/home/sean/.wine" wine "C:\Games\World of
> Warcraft\Launcher.exe" &
> sleep 1
> chmod 770 -v ~/.wine/drive_c/Games/World\ of\ Warcraft
> echo "Exiting"
> exit 0
>
> You need to change the directory names to match your own, but this should set
> the proper permissions to your WoW folder 1 second after starting the
> Launcher(you may have increase this if you have a slow computer), and then exit
> the script. This should make the game launchable through the Launcher, and
> hopefully allow the installation of future patches through the
> launcher(hopefully the future patches fix this)

Thank you..! I had reached an almost similar solution but yours is definitely
more elegant..:-)
Blizzard has announced they found a bug in the launcher and will fix it in the
next update/patch. A remaining question is: at which point in the launcher's
lifecycle are the permissions changed? If it is at the end it's no problem but
if it's at the start it will make patching the normal way impossible and must
be done by hand...At least I'm happy it's not a Wine bug...:-)

Best regards, Erik

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |canadrian@electricteaparty.
                   |                            |net

--- Comment #9 from [e-mail]  2009-11-13 13:45:21 ---
Experiencing this issue as well. Could a solution be as simple as chowning the
Warcraft directory as a different user so the user using it wouldn't be able to
change the permissions?

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

--- Comment #10 from Sean   2009-11-13 14:15:37 ---
(In reply to comment #9)
> Experiencing this issue as well. Could a solution be as simple as chowning the
> Warcraft directory as a different user so the user using it wouldn't be able to
> change the permissions?

I tried this too, but the game gives an error about not being able to write to
the game directory(I assume it means it can't write permissions, because users
in my group are able to create, execute, and delete files in the WoW folder,
even if it is owned by root.  It seems that the launcher fails if it is unable
to change the permissions on the WoW folder.

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

Richard  changed:

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

--- Comment #11 from Richard   2009-11-13 14:45:30 ---
Blizzard still has work to do on their end. 
See this thread 
http://forums.worldofwarcraft.com/thread.html?sid=1&topicId=21043887128&...
The current status is it is affecting some XP users. So expect the target to
move depending on what bug patch of the Blizzard tools you have. Note that
Blizzard does not seem to give a user trackable version number for the
Launcher.exe file that this is tied to.

The version of the game Wow.exe is still the same as from Sept-25/2009. 
Wow.exe patch 2.2.2a. build 10505. Is still the game version for the tools
patches of 2009-Nov-09 and 2009-Nov-12 that apparently changed the Launcher and
the Patcher.

The dependencies for this appear to be
1) what account is the software installed as
2) does the executable have effective "Administrator" rights on the folder

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

--- Comment #12 from Sean   2009-11-13 16:19:01 ---
So then, it appears that this is not a wine bug, and therefor should be marked
as "closed","invalid"

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

--- Comment #13 from Austin English   2009-11-13 17:36:48 ---
(In reply to comment #12)
> So then, it appears that this is not a wine bug, and therefor should be marked
> as "closed","invalid"

Yes, it should. But let's leave it open until Blizzard releases a fixed
version, so there aren't a bunch of duplicates filed.

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

Ben Peddell  changed:

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

--- Comment #14 from Ben Peddell   2009-11-14 01:11:45 ---
(In reply to comment #13)
> (In reply to comment #12)
> > So then, it appears that this is not a wine bug, and therefor should be marked
> > as "closed","invalid"
>
> Yes, it should. But let's leave it open until Blizzard releases a fixed
> version, so there aren't a bunch of duplicates filed.

If only there were a wine configuration setting to cause
server/file.c::file_set_sd to:
1) leave the owner permissions intact
2) fake the permission change, or
3) use xattrs to fake the permissions.

The last option would also need an appropriate change to
server/file.c::file_get_sd

[Bug 20643] World of Warcraft patcher tries to change folder permissions

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

--- Comment #15 from Erik   2009-11-14 10:41:49 ---
> If only there were a wine configuration setting to cause
> server/file.c::file_set_sd to:
> - leave the owner permissions intact
> - fake the permission change, or
> - use xattrs to fake the permissions.
>
> The last option would also need an appropriate change to
> server/file.c::file_get_sd

I would appreciate this also....maybe we should move this to the wishlist..:-)

Best regards, Erik

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

Dmitry Timoshkov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|World of Warcraft patcher   |World of Warcraft launcher
                   |tries to change folder      |tries to change folder
                   |permissions                 |permissions (Not a Wine
                   |                            |bug)

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

Paul Chitescu  changed:

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

--- Comment #16 from Paul Chitescu   2009-11-17 05:45:21 ---
(In reply to comment #12)
> So then, it appears that this is not a wine bug, and therefor should be marked
> as "closed","invalid"

I disagree. Even if WoW has a bug it exposes incorrect permission handling in
Wine.

I have WoW installed on a FAT32 partition so the files will always appear owned
by the mounter - in this case root. This arrangement is not uncommon if you
need a simple way of sharing files in a dual boot computer.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

--- Comment #17 from Ben Peddell   2009-11-17 16:07:34 ---
Created an attachment (id=24810)
 --> (http://bugs.winehq.org/attachment.cgi?id=24810)
Take into account owner groups in server/file.c::sd_to_mode()

I have tested this patch (which looks at the user's groups when determining the
permissions of a file or directory), and the World of Warcraft directory is set
to rwx???--- instead of ---???---.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

Ben Peddell  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1

--- Comment #18 from Ben Peddell   2009-11-25 08:36:02 ---
*** This bug has been confirmed by popular vote. ***

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

[e-mail] changed:

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

--- Comment #19 from [e-mail]  2009-11-28 11:12:50 ---
For you gamers out there, you don't need to run launcher.exe - wow.exe works
fine and can properly patch your game in the interim until upstream (Blizzard)
repairs the permissions bugs.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

Urmas  changed:

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

--- Comment #20 from Urmas   2009-12-03 19:06:23 ---
I have a Windows XP OS, and Launcher just resets an ACL for WoW folder to be
Users:(OICI)F, it even doesn't change the owner. So it's definitely a Wine bug.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

--- Comment #21 from Dmitry Timoshkov   2009-12-04 01:14:59 ---
(In reply to comment #20)
> I have a Windows XP OS, and Launcher just resets an ACL for WoW folder to be
> Users:(OICI)F, it even doesn't change the owner. So it's definitely a Wine bug.

There was a report that the WoW Launcher.exe breaks the directiry permissions
for a user without Administator priviledges set under Vista. Comments in this
bug report confirm this. So this is not a Wine bug.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

--- Comment #22 from Ben Peddell   2009-12-04 04:41:18 ---
(In reply to comment #21)
> (In reply to comment #20)
> > I have a Windows XP OS, and Launcher just resets an ACL for WoW folder to be
> > Users:(OICI)F, it even doesn't change the owner. So it's definitely a Wine bug.
>
> There was a report that the WoW Launcher.exe breaks the directiry permissions
> for a user without Administator priviledges set under Vista. Comments in this
> bug report confirm this. So this is not a Wine bug.

If the user is not the owner of the file or directory, and they are not in a
group that is granted the Control Access permission on that file or directory,
then the World of Warcraft launcher will bomb out with the "Launcher requires
write permission" error.

If the user is not in the Users group, then they will be unable to run World of
Warcraft again until they reset the permissions on the directory. If they don't
own the directory, and they don't possess SeTakeOwnershipPrivilege, they will
need to log in as someone who does to fix the permissions.

Not considering that the user may not be in the Users group is a World of
Warcraft bug.  They should use the Authenticated Users group instead, as
Winlogon gives any authenticated user membership in the Authenticated Users
group.

A user not being allowed access to a directory despite the DACL granting access
to one of their groups is Wine bug.  It should at least calculate the file mode
based on the groups the owner is a member of.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

--- Comment #23 from Urmas   2009-12-04 07:28:32 ---
The Users group implicitly includes all users with 'limited' users accouts,
plus BUILTIN\INTERACTIVE and BUILTIN\AUTHENTICATED groups both on XP and Vista.
So all local users, administrators, network users etc. are members of Users
group, and Wine should correctly emulate this behaviour. User not in Users
group isn't a WoW bug, it's abnormal condition.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

--- Comment #24 from Ben Peddell   2009-12-05 06:36:51 ---
Created an attachment (id=25080)
 --> (http://bugs.winehq.org/attachment.cgi?id=25080)
Testcase to list groups present in a process token

(In reply to comment #23)
> The Users group implicitly includes all users with 'limited' users accouts,
> plus BUILTIN\INTERACTIVE and BUILTIN\AUTHENTICATED groups both on XP and Vista.
> So all local users, administrators, network users etc. are members of Users
> group, and Wine should correctly emulate this behaviour. User not in Users
> group isn't a WoW bug, it's abnormal condition.

By default, NT AUTHORITY\INTERACTIVE and NT AUTHORITY\Authenticated Users are
members of the BUILTIN\Users group.  They can be removed from the BUILTIN\Users
group using the Local Users and Groups MMC snapin.  However, doing so will
almost certainly break some assumptions made by Windows programs.

Unless a person creates a new group that permits interactive logins, removing
INTERACTIVE and Authenticated from Users will prevent those not in the Users
group (including Administrators on Vista) from logging on.

Any breakages of the World of Warcraft launcher on Windows are almost certainly
due to administrators breaking their system, World of Warcraft requiring all
users on a system be given full access to its directory, and/or administrators
not fixing the permissions on the World of Warcraft directory.

The attached testcase was used in this investigation.  If it shows the token
containing the BUILTIN\Users group, then the user should be able to access the
World of Warcraft directory with the permissions the launcher sets.

If it shows the token not containing the BUILTIN\Users group, and the
INTERACTIVE and Authenticated groups have not been removed from Users, please
leave a comment with the operating system in use, how the user is logging in,
and the output of the testcase (possibly redacting any non-builtin accounts).

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

--- Comment #25 from [e-mail]  2009-12-05 23:47:19 ---
(In reply to comment #24)
> Any breakages of the World of Warcraft launcher on Windows are almost certainly
> due to administrators breaking their system, World of Warcraft requiring all
> users on a system be given full access to its directory, and/or administrators
> not fixing the permissions on the World of Warcraft directory.

Considering most of us here have stock installs, and wouldn't even know where
to begin to start sludging up registry permissions or faking NTFS ACLs, fake
user groups, etc, on our installation locations, it might be taken as a hostile
response (or worse, a valid response and promptly closed) that end-users are
somehow at fault for this problem.  It is irresponsible to try to blame this on
users as the administrators of their own system or package maintainers for
properly compiling wine.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

--- Comment #26 from Ben Peddell   2009-12-06 15:30:26 ---
(In reply to comment #25)
> (In reply to comment #24)
> > Any breakages of the World of Warcraft launcher __on__ __Windows__

Reword:
Any breakages of the World of Warcraft launcher __on__ __Windows__ where the
user is unable to access the World of Warcraft directory using the permissions
it sets are almost certainly due to the administrator taking all steps to
remove the user from the BUILTIN\Users group.
> Considering most of us here have stock installs, and wouldn't even know where
> to begin to start sludging up registry permissions or faking NTFS ACLs, fake
> user groups, etc, on our installation locations, it might be taken as a hostile
> response (or worse, a valid response and promptly closed) that end-users are
> somehow at fault for this problem.  It is irresponsible to try to blame this on
> users as the administrators of their own system or package maintainers for
> properly compiling wine.

Any breakages of the World of Warcraft launcher __on__ __Wine__ where the user
running the Launcher owns the directory yet is unable to access it are due to
wineserver looking at only the permissions explicitly given to the owner and
everyone SIDs when calculating the unix mode, and neither allowing the owner
access by default nor calculating the mode based on the full permission set
granted or denied to them.

Any breakages of the World of Warcraft launcher __on__ __Wine__ where the user
is not the owner of the directory but has full read/write/traverse access on it
can most likely be attributed to the World of Warcraft launcher trying to "fix"
the permissions on the directory every time it is started.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

Toupeiro  changed:

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

--- Comment #27 from Toupeiro   2009-12-08 23:51:26 ---
I can confirm launcher does this.  I've bypassed the problem by calling the
BackgroundDownloader in a script while launching wow.  works through patches. 
This is not a fix, but at least for me, a proven work-around.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

Masin Al-Dujaili  changed:

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

--- Comment #28 from Masin Al-Dujaili   2009-12-09 12:23:58 ---
(In reply to comment #27)
> I can confirm launcher does this.  I've bypassed the problem by calling the
> BackgroundDownloader in a script while launching wow.  works through patches. 
> This is not a fix, but at least for me, a proven work-around.

I've written this script:

#!/bin/sh
if [ "$WINEPREFIX" = "" ]; then
    WINEPREFIX="$HOME/.wine"
fi
WOWPATH="$WINEPREFIX/drive_c/Programme/World of Warcraft"

chmod 770 "$WOWPATH"

# I need padsp for sound output
padsp wine "C:\Programme\World of Warcraft\Launcher.exe" &

# requieres inotify-tools
inotifywait -e attrib "$WOWPATH"
sleep 2

chmod 770 "$WOWPATH"

This enables normal functionality.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

jim  changed:

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

--- Comment #29 from jim   2009-12-11 13:23:20 ---
Seems to be fixed for me.  I suspect

http://source.winehq.org/git/wine.git/?a=commit;h=b419df1de48609086c7460fdb5...

fixes this.  Can anyone confirm?

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

Ben Peddell  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #24810|0                           |1
        is obsolete|                            |

--- Comment #30 from Ben Peddell   2009-12-11 23:32:25 ---
(From update of attachment 24810)
Obsoleted by commit b419df1de48609086c7460fdb5d8a20d119e47ee

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

--- Comment #31 from Paul Chitescu   2009-12-14 11:10:06 ---
(In reply to comment #30)
> (From update of attachment 24810 [details])
> Obsoleted by commit b419df1de48609086c7460fdb5d8a20d119e47ee

Bug still there if WoW is on a FAT32 partition, directory permissions are
rwxrwxrwx.

WoW tries to set ACL to "D:(A;OICI;GA;;;BU)" which Wine translates to ---rwxrwx
which are not supported on the filesystem.

On Windows the directory would be made R/W (for everybody since FAT knows no
ownership).

The launcher is required to start the downloader for the correct region.
Previously the downloader would download the currently installed version (en_GB
in my case) but since the Battle.net integration it seems to default to en_US
if started alone.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

--- Comment #32 from Ben Peddell   2009-12-15 06:59:19 ---
(In reply to comment #31)
> (In reply to comment #30)
> Bug still there if WoW is on a FAT32 partition, directory permissions are
> rwxrwxrwx.

The FAT32 issue is a separate issue - Windows returns
STATUS_INVALID_DEVICE_REQUEST when attempting to get or set ACLs on a
filesystem that cannot handle them.  Linux at least returns no error as long as
the file or directory belongs to the user.

On a POSIX system, chmod will return EPERM when attempting to change the mode
of a file or directory that does not belong to the user, even with ugo+rwx
permissions.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

--- Comment #33 from Richard   2009-12-19 09:19:06 ---
Appears fixed in 1.1.35 on Ubuntu 9.04, 64bit.
Wow is in std place at ~/.wine/Program\ Files\World...

Launcher works to start the game permissions remain good.
Was failing with the permissions problem with 1.1.34

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

Jason T. Banks  changed:

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

--- Comment #34 from Jason T. Banks   2009-12-22 08:45:10 ---
Confirmed.  Issue Resolved In 1.1.35

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

Alexandre Julliard  changed:

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

--- Comment #35 from Alexandre Julliard   2009-12-22 09:30:07 ---
Fixed.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

--- Comment #36 from Paul Chitescu   2009-12-22 10:08:51 ---
(In reply to comment #35)
> Fixed.

Not fixed for WoW residing on FAT32.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

--- Comment #37 from Alexandre Julliard   2009-12-22 10:40:37 ---
(In reply to comment #36)
> (In reply to comment #35)
> > Fixed.
>
> Not fixed for WoW residing on FAT32.

That's another problem. Please open a new bug for that.

[Bug 20643] World of Warcraft launcher tries to change folder permissions (Not a Wine bug)

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

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #38 from Jeff Zaroyko   2010-01-09 04:49:09 ---
Closing bugs fixed in 1.1.36.