Closed Bug 404465 Opened 17 years ago Closed 17 years ago

Homepage is ignored when starting 3.0b1

Categories

(Toolkit :: Startup and Profile System, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 404695

People

(Reporter: cpuidle, Unassigned)

References

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1; FDM) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110904 Firefox/3.0b1 Starting 3.0b1, it opens a customized google search page, but not the custom homepage. Also, clicking the "Home" button shows no effect. Reproducible: Always
WFM on Windows XP.
Doesn't for me and didn't in "inofficial" beta. If it's due to having FF2 already installed this might be an issue more people might be experiencing. Any diagnosis I could do? I've tried starting in safe mode with add-ins disabled. Issue still present.
What homepage do you see in Options -> Main?
I see: When Firefox starts: Show my homepage Homepage: http://www.heise.de/newsticker/ When I start FF, the home page stays blank (safe mode). Clicking "Home" button then shows the customized google page. I believe this issue is related to bug 404467 and bug 404466 that also appear with my installation- I'm suspecting a common, deeper reason for this behaviour.
I've done some further tests (all in safe mode) and found the following: renaming Application Data\Mozilla\Firefox\Profiles to Application Data\Mozilla\Firefox\Profiles.old: - FF3 doesn't start, instead claims "Application already running" renaming Application Data\Mozilla\Firefox to Application Data\Mozilla\Firefox.old: - FF3 now starts and UI _is_ working Conclusion: the problem is within the Mozilla\FireFox folder- probably the profile?
Delete all places.* in your profile and try again. See bug 404695.
Great suggestion- that's it, thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.