I also moved/chowned ~/bin over, so they had access to the same stuff in the path, in addition to having the same $PATH set. (Yeah, I really liked that theory, too.) N.B. So it doesn't seem to just be an environment var that's set on one side but not on the other. Program launches fine for one user, crashes for the other. bashrc to the "good" user account, such that printenv shows the same variables set in each user's environment. Environment variables - On the theory that there's something going on with the "bad" user's $PATH, I copied/chowned.It fixed a couple of things, but didn't appear to make a difference. Repair permissions - Just for starters, I ran Disk Utility's "Repair Permissions" a few times on the boot disk.In fairness, I do have a lot of stuff installed (XCode and CLI tools, MacPorts, Homebrew, LaTeX, various releases of Python, etc.) but they are all installed for all users, not to the affected user's homedir. When run from a Guest account or a different user's account, it launches just fine with no suggestion as to what might be going wrong. But I'm open to other thoughts on what it might mean. My interpretation of this is that it's trying to load something from a NIB, possibly from a shared framework, and it's choking. The error that's causing the crash is setObjectForKey: object cannot be nil (key: LibraryPath)' When launched by the "bad" user, the application immediately quits with this crashlog output. So, obviously, the problem is related to that user's account/environment. The problem is that it crashes immediately after launch, with absolute consistency, but only when run from a particular user's account, but not when run from a Guest account or from another user. I look forward to sharing with you in the future.I have a Mac OS X application (Garmin's "VIRB Edit", which lets you download videos from the VIRB series of GoPro-ish cameras) that has turned into a slightly obsessive technical challenge. Thank you, again, everyone who posted to the previous members question. I upgraded without a second thought and NO plans of looking back. I finally got the store to give me a replacement. It was in the shop more than a Fiat Spyder. I had been wanting a Mac for a few years now and finally got this Macbook pro a couple of weeks ago. So I was very pleasantly surprised to find out that Mac did go through this trouble to make life simpler for us. I remember thinking then that this system was flawed because they did not have a Macro written to allow you to drag and drop software into the trash. When I got my first Windows computer, it was shortly after Windows 95 came out. ![]() I was trying to figure out how to remove software and APPs from my Mac. ![]() I just found this sight quite by accident. ![]() There were a couple of responses to another members question. Thanks for the help on removing programs from my Mac.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |