702211 - Couldn't get browser.startup.homepage.1 pref: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch2.getComplexValue]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: chrome://communicator/co

Status: VERIFIED WORKSFORME

(SeaMonkey :: Preferences, defect)

Description

[Philip Chee]

Error: Couldn't get browser.startup.homepage.1 pref: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch2.getComplexValue]"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: chrome://communicator/content/utilityOverlay.js :: GetLocalizedStringPref :: line 194"  data: no]
Source file: chrome://communicator/content/utilityOverlay.js
Line: 196

I normally have two homepages in my home page group. On startup the second one gets deleted but browser.startup.homepage.count is still set to 2 in about:config

After shut down I have:
user_pref("browser.startup.homepage", "about:blank");
user_pref("browser.startup.homepage_override.mstone", "rv:1.9.1.20pre");
user_pref("browser.startup.page", 0);

Possible causes of regression:
Bug 535128 - Additional home page preferences not cleaned up when reducing the home page group
Bug 692423 - Remove "Last page visited" options from Browser preferences, or reimplement functionality.

Comment 1

[rsx11m]

Phil, I'm unable to reproduce this on neither 20111031, 20111105, nor 20111107 trunk (2.7a1) builds, also not on the 20111112 aurora build (using an existing or new profile), thus it seems to be a recent regression after the last merge.

Maybe I'm not using the correct steps to reproduce, do you see this on aurora?

Comment 2

[rsx11m]

So, I don't even see this with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0a1) Gecko/20111110 SeaMonkey/2.8a1 either, both home page entries are retained:

browser.startup.homepage http://forums.mozillazine.org/
browser.startup.homepage.1 http://www.mozilla.org
browser.startup.homepage.count 2
browser.startup.homepage_override.mstone rv:11.0a1

The "rv:1.9.1.20pre" value in your mstone setting looks suspicious and like a remnant entry from a 2.0.x installation, maybe some migration code kicking in despite not being supposed to do so?

Comment 3

[Philip Chee]

> The "rv:1.9.1.20pre" value in your mstone setting looks suspicious and like a remnant
> entry from a 2.0.x installation, maybe some migration code kicking in despite not
> being supposed to do so?
Good point. Haven't been able to reproduce this with todays build. All prefs look normal.