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