[mwiik]

My wife's MBP we set up so that each of us has an account and both are administrator accounts. This seems to be causing some issues. I haven't quite tracked this down yet, but it seems after installing software updates on her account, I am also getting asked to install these when I log in. This seems to work fine but it almost seems like we have different app directories...

I updated Google Earth under her account, and it said it couldn't complete the update. I think this might be because I originally installed it under my account. I did the update with my account and it worked fine.

Even just today I was prompted to install firmware updates for the keyboard - though I did this (under her account) a few days ago.

Does Leopard not like two people having administrator accounts? I'm getting my own MBP in a couple days and would just as soon delete my account of her machine entirely, maybe replacing it with a non-administrator account. Now I'm thinking maybe I need to scan first for any system files owned by me.

Anyone else experiencing such issues or have any clues to what's going on? Perhaps this is discussed in another thread? Thanks...

[Big Mac]

That should not be happening, but you can just downgrade your admin account to a normal account; you don't have to delete it.

[mwiik]

If this in any way helps, we got her MBP just after Leopard came out - so it came with Tiger and we did the normal upgrade path.

[ibook_steve]

Moving to Mac OS X since this is not directly MBP related.

Steve

[dowNNshift]

Does this only occur with 3rd party applications?

It could be permissions related, but you'd need to identify which applications this behavior is happening with. In Leopard, library files are sorted in order of ~/Library, /Library, then lastly /System/Library. So this means that if the particular application is only installing supportive files in the ~/Library (that's the User Library folder) then other users won't have access to the updates, hence your a plausible cause of your error.

I'd first repair permissions using Disk Utility and see if that remedies the problem. If that doesn't work then track down if the particular application puts supportive files in just your ~/Library folder or both ~/Library and /Library