Here is the problem:

I want to set up a "global" wine directory, so both me and my girlfriend can play games on each others' accounts. Right now, I have wine set up so it can run in my account, but she has to log out and log into my account each time she wants to play a game which is far from ideal.

So, what I did was set up a "global" homeuser group for all user accounts on the system. Then, I moved my ~/.wine folder to /home/wine, and did chown :homeuser /home -R

Then I made a symlink to the /home/wine directory at ~/.wine and did the same for my GF's home directory. It works fine in my account, BUT if I change to my GF's account, I try to run wine and it says

"/home/xxxx/.wine not owned by you"

The directory permissions are 755 so I SHOULD be able to run wine to my knowledge.

... any solutions?

I have no idea whether this will work and no way easily to test it, but I was reading about permissions and the book mentioned the setuid bit. Perhaps setting that would work.

Interesting, I'll test that and let you know how it goes.

I don't think this will work as I want it to - I want the permissions to the shared folder at 755 so other users on my system don't mess up the shared wine directory. Using setuid, this would allow other users full write access to the directory when executing "wine *.exe". This isn't too big of a deal ATM - the most important thing is to get the solution to work (which after looking at the docs for setuid it should work).

Thank you for the help. What I will probably end up doing, is just re-compiling wine from source - I'm sure there are configure flags for this. If not, source diving is always fun.