536347 - Troubles after upgrade to 2.0.1 (bookmarks, home page, navigation arrows, displaying URLs)

Status: RESOLVED INCOMPLETE

(SeaMonkey :: General, defect)

Description

[Tomas Hajny]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; chrome://navigator/locale/navigator.properties; rv:1.9.1.6) Gecko/20091206 SeaMonkey/2.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; chrome://navigator/locale/navigator.properties; rv:1.9.1.6) Gecko/20091206 SeaMonkey/2.0.1

After upgrade from 2.0 to 2.0.1 using the Windows installer provided on official pages (see the URL field above), I observe the following troubles:

- SeaMonkey starts with a blank page instead of the configured home page (I have a static HTML page configured as a home page).

- No bookmarks are shown in the Bookmarks menu (the menu ends with the delimiter below the option "Subscribe to this page"). I can access my bookmarks using the Manage Bookmarks option (they're all there). After I do this (open the Bookmark Manager and possibly close it again), the bookmarks start appearing in the Bookmarks menu properly for the particular session. Nevertheless, opening the bookmarks from the Bookmarks menu is not possible (opening from the Bookmark Manager is OK).

- The navigation arrows are always grayed out as if going back weren't possible. Backspace key works OK though.

- Moving mouse cursor over a link doesn't show the target URL in the status line.

- URLs in the URL field at the top are not updated properly when switching among open tabs (the last typed URL persists there even if I switch to a tab having a completely different URL open and in spite of the fact that I used a different tab when typing the URL).

There may be some other issues, these are those I discovered so far. Everything works properly again after downgrading to one of the previous 2.0.x versions (including betas and RCs), installing 2.0.1 gives the same problematic behaviour again. Starting 2.0.1 in safe mode doesn't help, the behaviour is the same.

Reproducible: Always

Steps to Reproduce:
1. Install 2.0.1 Windows EN under WinXP Professional SP3 using the downloaded installer
2. Start SeaMonkey
3. Choose Bookmarks in the menu
Actual Results:  
No bookmarks shown (see the details above)

Expected Results:  
My bookmarks are displayed

Default theme used

Comment 1

[Serge Gautherie (:sgautherie)]

Are you installing v2.0.1 in a separate directory?
Is there any message in the Error Console?

Comment 2

[Tomas Hajny]

No, installed as an upgrade, i.e. into the same directory as used for previous 2.0.x releases (betas, RCs and 2.0 release).

The Error Console indeed contains quite a few messages already on startup. There are several messages with severity Information (all of them like "Failed to load XPCOM component: D:\INTERNET\MOZILLA_X\components\..." where the last part refers to various DLLs, etc.). More importantly, the following 3 error messages appear at the end:
----------------
Error: uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.clearUserPref]"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: file:///D:/INTERNET/MOZILLA_X/components/smileApplication.js :: pref_reset :: line 733"  data: no]

Error: cmdZoomReduce is null
Source File: chrome://imagezoom/content/overlay.js
Line: 75

Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]"  nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)"  location: "<unknown>"  data: no]
==========================
Once I start doing something (like loading a SquirrelMail page with reference to this Bugzilla record or the Bugzilla page itself), there are quite a few warning lines complaining about various stuff (let me know if you're interested in those). Also the same three error messages appeared again, although I can't tell what was the exact cause (possibly opening a new SeaMonkey window).

Comment 3

[Serge Gautherie (:sgautherie)]

(In reply to comment #2)

> No, installed as an upgrade

Could you try to uninstall your current version then install v2.0.1 in a separate dir, to check if it makes a difference?

> There are several messages with severity Information (all of them like "Failed
> to load XPCOM component: D:\INTERNET\MOZILLA_X\components\..." where the last

Any one other than those listed in bug 527458 comment 6?

> part refers to various DLLs, etc.). More importantly, the following 3 error
> messages appear at the end:

That might be a clue...
(You get these in safe mode too, right?)

Comment 4

[Tomas Hajny]

(In reply to comment #3)
> (In reply to comment #2)
> 
> > No, installed as an upgrade
> 
> Could you try to uninstall your current version then install v2.0.1 in a
> separate dir, to check if it makes a difference?

Well... Sorry for a silly question, but can I do it without loosing my previously installed extensions / plugins and all settings (both for SeaMonkey and those extensions)? If yes, how (complete backup of the whole machine and restore afterwards is not an option for me)? The trouble is that I don't know how much is this just a matter of backing up the installation directory and possibly also the profile directory, or whether there's more (like e.g. Windows registry, some other directories, etc.). Loosing them temporarily for the particular installation for test purposes is certainly OK, but I want to be able to have everything back after reinstalling the correctly working 2.0 version.


> > There are several messages with severity Information (all of them like "Failed
> > to load XPCOM component: D:\INTERNET\MOZILLA_X\components\..." where the last
> 
> Any one other than those listed in bug 527458 comment 6?

All of them are different from those listed there, in fact. Examples include e.g. addrbook.dll, bayesflt.dll, impeudra.dll, mime.dll, msgdb.dll, myspell\en-us.aff, etc.


> > part refers to various DLLs, etc.). More importantly, the following 3 error
> > messages appear at the end:
> 
> That might be a clue...
> (You get these in safe mode too, right?)

Actually, that's a good point, in the safe mode I only get the first one:

Error: uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.clearUserPref]"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: file:///D:/INTERNET/MOZILLA_X/components/smileApplication.js :: pref_reset :: line 733"  data: no]

BTW, I suspect that my response may be somewhat longer in the next days, sorry for that (and Merry Christmas or season holidays whatever matter for you ;-) ).

Comment 5

[Serge Gautherie (:sgautherie)]

(In reply to comment #4)

> Well... Sorry for a silly question, but can I do it without loosing my
> previously installed extensions / plugins and all settings (both for SeaMonkey
> and those extensions)?

Not silly at all. But not one I can answer in Bugzilla.
You should find instructions in documentation or support groups.

The only solution I can suggest, if you know how, is to try the .zip file instead of the installer.

> All of them are different from those listed there, in fact. Examples include
> e.g. addrbook.dll, bayesflt.dll, impeudra.dll, mime.dll, msgdb.dll,
> myspell\en-us.aff, etc.

From what I checked on my computer, all these are v1.1.x files, not v2.0.x.

> Actually, that's a good point, in the safe mode I only get the first one:

At this point, I would assume that either you installed v2.0 over v1.1,
or you have some kind of v1.1 extensions enabled in v2.0 (profile).

> Error: uncaught exception: [Exception... "Component returned failure code:
> 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.clearUserPref]"  nsresult:
> "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
> file:///D:/INTERNET/MOZILLA_X/components/smileApplication.js :: pref_reset ::
> line 733"  data: no]

Does it happen with a new/clean profile too?

Anyway, your (v2.0.1) installation seems rather broken at this point.
Unless you can report reproducible steps and results on specific issue(s), I don't think much more can be done here.

Comment 6

[Serge Gautherie (:sgautherie)]

(1+ months later)

No reply from reporter.

R.Incomplete