wine users - Nov 2009 - New WoW Launcher.exe changes directory permissions

I'm using Wine (1.1.13) for over a year now on openSuSE Linux (11.1);
I'm using a few Windows programs but mostly used is WoW. Never ran Wine as
root, never had a noteworthy problem with any program; WoW was installed,
upgraded and patched without a glitch (now at 3.2.2.10505) and ran just fine.
Until 2 days ago when Blizzard delivered a small update which included a new
launcher. Every time this launcher is started it shows it's screen but it
cannot start WoW.exe anymore. And that's no wonder: The permissions of the
WoW directory are changed from the original drwxr-xr-x into d---r-x---..which
makes it inaccessible quite effectively.....The accusing finger would point to
Blizzard, but the real question is:
How is a Windows program running on Wine capable of messing with these
permissions..?
A workaround is to manually restore the permissions to their original before
pressing the "Play" button, or to use a copy of this entire directory
from an NTFS partition on an USB drive (in this case the permissions are left
alone).
But that's quick and very dirty.....anyone a suggestion..?

Best regards, Erik

On Wed, 2009-11-11 at 16:30 -0600, emn8w8 wrote:
> I'm using Wine (1.1.13) for over a year now on openSuSE Linux (11.1);
I'm using a few Windows programs but mostly used is WoW. Never ran Wine as
root, never had a noteworthy problem with any program; WoW was installed,
upgraded and patched without a glitch (now at 3.2.2.10505) and ran just fine.
Until 2 days ago when Blizzard delivered a small update which included a new
launcher. Every time this launcher is started it shows it's screen but it
cannot start WoW.exe anymore. And that's no wonder: The permissions of the
WoW directory are changed from the original drwxr-xr-x into d---r-x---..which
makes it inaccessible quite effectively.....The accusing finger would point to
Blizzard, but the real question is:
> How is a Windows program running on Wine capable of messing with these
permissions..?
> A workaround is to manually restore the permissions to their original
before pressing the "Play" button, or to use a copy of this entire
directory from an NTFS partition on an USB drive (in this case the permissions
are left alone).
> But that's quick and very dirty.....anyone a suggestion..?
> 
File a bug with Blizzard.


Martin

emn8w8  acl the directory.  I think is the simplest.  I don't think they are
smart enough to nuke that. acl(access control lists) group permissions also look
left alone.

Wine does have the right to be messing with permissions.  Now windows
permissions need to be compared to what wine is spitting out it might be a wine
bug.

Some applications do stunts like that to stop them from being run mult times. 
But that is still pointing to a bug because the application not releasing when
existing.

So try newer wine just in case it some form of bug with 1.1.13 that is fixed.

oiaohm wrote:
> emn8w8  acl the directory.  I think is the simplest.  I don't think
they are smart enough to nuke that. acl(access control lists) group permissions
also look left alone.
According to the bug that won't help:
http://bugs.winehq.org/show_bug.cgi?id=20643

The only thing I can think of - hack Wine and disable that functionality. See if
that works.

You are right....I've seen it too....
Since this is a problem from Blizzard, that can be circumvented even with some 
elegance, and has nothing to do with Wine itself nor is a Wine-bug
I will go back to my state as a happy Wine user....:-) and will just wait when
and how this will be solved....

I thank you all for your time and replies,

Best regards, Erik