Closed Bug 247779 Opened 21 years ago Closed 20 years ago

Exit and Start Firefox buttons disappear after creating very first profile

Categories

(Toolkit :: Startup and Profile System, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 248648

People

(Reporter: jwatt, Assigned: benjamin)

Details

I tested firefox 0.9 without an initial profile, and used the Choose User Profile dialogue that subsequently showed to create the first profile. Once I had finished creating this profile the Exit and Start Firefox buttons disapeared. This did not happen when I restarted and created a second and third profile. This happens consistantly for me. After creating the first profile firefox can still be started by double clicking on the profile name, but this problem will likely confuse the average user. I should say that I was using the SVG enabled milestone build uploaded to http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/0.9/contrib/firefox-0.9-win32-svg-GDI.zip but since the only difference between it and the official milestone is the use of --enable-svg and --enable-svg-renderer-gdiplus, this problem will almost certainly be present for the official milestone.
Actually I wasn't quite right. The SVG enabled build doesn't use --enable-codesighs and --enable-official-branding when the official build does, and it does use --enable-strip and --enable-plaintext-editor-only when the official milestone doesn't.
Someone with a none-SVG build of Firefox confirmed this for me (I forget who) but I forgot to mark the bug as NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Exit and Start Firefox buttons disapear after creating very first profile → Exit and Start Firefox buttons disappear after creating very first profile
maybe dupe of Bug 248648 and bug 273415.
This has the same root cause as 248648, and roc fixed it recently. *** This bug has been marked as a duplicate of 248648 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.