http://bugs.winehq.org/show_bug.cgi?id=20643
--- Comment #22 from Ben Peddell klightspeed@netspace.net.au 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.