Jump to content


Possible permissions fix for games on Leopard


  • Please log in to reply
3 replies to this topic

#1 nagromme

nagromme

    Master Blaster

  • Members
  • PipPipPipPipPipPip
  • 1954 posts

Posted 10 November 2007 - 09:55 PM

Someone at MacRumors thought that in Leopard, repairing permissions would break UT2004 (and for that matter, repairing permissions itself may be broken and in need of an Apple patch). My testing suggests that this is accurate, and I think the problem has to do with the new Access Control Lists used for permissions in Leopard. It's possible it only happens for users who are not admins--that I did not test.

I've found a solution for UT2004, and I suspect it will help other games as well in certain situations. (It's similar to permission problems I've seen in some games pre-Leopard, when playing in an account other than the one that installed the game: other users might lack necessary permissions for certain game files.)

The solution (try at your own risk): In Get Info, make sure the app AND its package contents have you as the owner. I found my account wasn't listed at ALL in the permissions list, and the "everyone" group was not sufficient. So click +, add your account, and then with the newly created entry selected, click the little gear menu and make yourself the owner.

You can then "apply to enclosed items" from the same gear menu. The catch is, you can't use that on a package. So you must manually do this for each item in the package--but if you update ownership for a folder WITHIN the package, you can apply to enclosed items within it.

In this case, I had to make myself the owner of:

a) The app package itself.

b) The Contents folder inside the package, and all enclosed items.

c) The System folder inside the package, and all enclosed items. (Because, I believe, Contents contains an alias to ut-2004.bin inside System.)

I did NOT have to update ownership for any other items in the game package, but that may vary from game to game.

Hope this helps someone. Let us know if it has an effect on other games, or if you notice other permission-related weirdness in Leopard.

#2 nagromme

nagromme

    Master Blaster

  • Members
  • PipPipPipPipPipPip
  • 1954 posts

Posted 11 November 2007 - 03:33 AM

A second thing to look for: aliases turning into real file copies!

The above worked for about 3 launches, then the same old error started happening. The above fix didn't help this time, but I noticed something new: the alias inside Contents (which points to the game binary) had turned to a real COPY of the binary. I deleted it and replaced with an alias of my own creation, to no avail.

I ended up having to restore from backup.

Anyway, there's probably a way to re-build the lost alias so that it works, so maybe this is a useful lead for some games. I'm pretty sure many apps use an alias inside Contents.

Maybe all of this will be resolved in 10.5.1 anyway.

#3 Tesseract

Tesseract

    Unmanageable Megaweight

  • Members
  • PipPipPipPipPipPipPipPip
  • 3512 posts
  • Pro Member:Yes

Posted 11 November 2007 - 02:48 PM

I think it's not an actual alias, but a symlink.

#4 nagromme

nagromme

    Master Blaster

  • Members
  • PipPipPipPipPipPip
  • 1954 posts

Posted 11 November 2007 - 04:35 PM

Ah--Good call! I have a little app somewhere for making those. Next time it breaks I will try that.