244668 - [trunk] Profile Manager broken in OS X

Status: RESOLVED WORKSFORME

(Toolkit :: Startup and Profile System, defect)

Description

[riscky]

Launching Firefox under OS X with the -p flag fails

Try launching with the terminal using:
Firefox.app/Contents/MacOS/./firefox-bin -p

Firefox launches with an error reading:
"The URL is not Valid and cannon be loaded"

Comment 1

[riscky]

More info... opps
thats with Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a2)
Gecko/20040525 Firefox/0.8.0+

However...
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040525
Firefox/0.8.0+
Firefox.app/Contents/MacOS/./firefox-bin -p
give you:
"Error: argument -P requires a profile name"

Comment 2

[Bruce Davidson]

WFM fine with latest nightly (own build 20040529). Specifying -P without a
profile name isn't valid, but it just causes the profile manager dialog to come
up. Riscky, is this still a problem with a recent nightly?

Comment 3

[riscky]

Trunk build still fails... my own clobber build... Mozilla/5.0 (Macintosh; U;
PPC Mac OS X Mach-O; en-US; rv:1.8a2) Gecko/20040525 Firefox/0.8.0+

Firefox.app/Contents/MacOS/./firefox-bin -P
*** eeeeeeee = [Exception... "Component returned failure code: 0x80520012
(NS_ERROR_FILE_NOT_FOUND) [nsIFile.remove]"  nsresult: "0x80520012
(NS_ERROR_FILE_NOT_FOUND)"  location: "JS frame ::
file:///Firefox.app/Contents/MacOS/components/nsExtensionManager.js ::
ensureExtensionsFiles :: line 217"  data: no]
Firefox.app/Contents/MacOS/./firefox-bin: can't map file:
/Firefox.app/Contents/MacOS/plugins/Default Plugin.plugin ((os/kern) invalid
argument)

As for the branch build... I haven't tested a nightly build... but -P should be
a valid and should require a profile name.. it should bring up the Profile
Manager. See http://www.mozilla.org/projects/help-viewer/docs/firebird/profiles.html

Comment 4

[Hiro]

WFM
-p and -P -- whichever it specifies, there is no problem.

Mac OS X 10.3.4
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; ja-JP; rv:1.8a2) Gecko/20040529
Firefox/0.8.0+

Comment 5

[riscky]

I'm in the process of making a fresh build (new tree & XCode 1.2)... since this
seems to work for everyone else I hope such a move resloves the issues I'm
seeing... however I've been able to reproduce this on three different machines.

Comment 6

[riscky]

It seems pulling a fresh tree sloves my ails... well the ones this bug covers.