Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

I am trying to create a new profile, but I cannot open profile manager in Mac OS 10.5.8. I get the following error: "dyld: unknown required load command 0x80000022 Trace/BPT trap".

more options

Hello,

I am trying to repair my Firefox profile, but I cannot open profile manager in Mac OS 10.5.8. When I follow the directions for opening profile manager in my Terminal utility, I get the following error: "dyld: unknown required load command 0x80000022 Trace/BPT trap".

At this point, Firefox (v 5.0 or previous versions), is not running.

Thanks.

Hello, I am trying to repair my Firefox profile, but I cannot open profile manager in Mac OS 10.5.8. When I follow the directions for opening profile manager in my Terminal utility, I get the following error: "dyld: unknown required load command 0x80000022 Trace/BPT trap". At this point, Firefox (v 5.0 or previous versions), is not running. Thanks.

All Replies (4)

more options

Here's an Explanation. Basically you need to add "arch -i386 " at the beginning of the command because 10.5 is 32-bit only and more recent versions of Firefox default to 64-bit.

more options

I was a little confused by "at the beginning of the command" (I wasn't sure if that meant as a command argument or literally *before* the command) and learned from trial/error that this is literally updated command line to use:

arch -i386 /Applications/Firefox.app/Contents/MacOS/firefox-bin -ProfileManager

Modified by Tantek Çelik

more options

/Applications/Firefox.app/Contents/MacOS/firefox-bin -profilemanager

Profile Manager

Check and tell if its working.

more options

@mha007 no that command doesn't work in these cases - that's the very command that causes the problem noted in the original problem report for some folks: "dyld: unknown required load command 0x80000022 Trace/BPT trap"

The point is, if you get that error from that command, you have to use the updated command line I posted above in my previous reply.

Modified by Tantek Çelik