Closed
Bug 289636
Opened 20 years ago
Closed 18 years ago
Warning: unrecognized command line flag -ProfileManager
Categories
(Toolkit :: Startup and Profile System, defect, P3)
Toolkit
Startup and Profile System
Tracking
()
RESOLVED
FIXED
People
(Reporter: djcater+bugzilla, Assigned: benjamin)
Details
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050408 Firefox/1.0+ When starting Firefox with the command-line flag -ProfileManager the Profile Manager is started, but when the Profile Manager closes, the message in this Summary is printed to the terminal. Steps To Reproduce: 1. Start Firefox and the Profile Manager: /$PATH_TO_FIREFOX/firefox -ProfileManager 2. Select a profile and start Firefox. Actual Results: Profile Manager opened. After selecting a profile and starting Firefox the following message was printed to the terminal: Warning: unrecognized command line flag -ProfileManager Firefox then started with the selected profile. Expected Results: Profile Manager should have opened. After selecting a profile and starting Firefox, Firefox should have started with that profile. No warnings should have appeared in the terminal. Using the latest ocean-trunk/ tinderbox build.
Comment 1•20 years ago
|
||
this is from bug 280725 ==> xre startup
Assignee: nobody → benjamin
Status: UNCONFIRMED → NEW
Component: Cmd-line Features → XRE Startup
Ever confirmed: true
Product: Core → Toolkit
Version: Trunk → unspecified
| Assignee | ||
Updated•20 years ago
|
Priority: -- → P3
Updated•19 years ago
|
OS: Linux → All
Hardware: PC → All
Comment 2•18 years ago
|
||
You get Error: Warning: unrecognized command line flag -console .. nsBrowserContentHandler.js Line: 572 with ".. firefox.exe" -console with FF 2.0b1 , but, I get a console.
Comment 3•18 years ago
|
||
I'm unable to reproduce this and I believe it was fixed by the patch for bug 303599
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Component: XRE Startup → Startup and Profile System
QA Contact: startup
You need to log in
before you can comment on or make changes to this bug.
Description
•