User:Skierpage/SM 2.2 update notes

From MozillaWiki
Jump to: navigation, search

bug 666479 Warnings from unsigned SeaMonkey installer

The SeaMonkey Windows installer is not signed, so in Windows Vista you get two alerts.

Windows installer should be signed

Maybe file this, as be a dependency of bug 558460 - [Tracking bug] signing improvements. It sounds like some installers are signed automatically.

Failure to run

"Launch SeaMonkey now" at end of install didn't seem to happen.

Running SeaMonkey from icon failed. From command line failed silently, even with -P and -safe-mode

crashreporter.exe worked. updater.exe, etc. failed.

I saved Windows ProcMon.exe "strace"s of SeaMonkey in XML format.

I tried Firefox, that also failed! Spinning cursor icon for about 20 seconds, then exit.  !??! Also captured ProcMon of that as XML.

Saw nothing in Event Viewer, nothing

Try rebooting... Even that was hard, Start > Shutdown didn't take, had to hold down power key.

Upon restart, SeaMonkey OK!

bug 666495 SeaMonkey upgrade moved the program files' dates back in time

It's confusing that most of the SM 2.0.14 program files were dated 2011-04-30 03:57PM , and the new 2.2b1 version went back in time to 2010-01-01 1:00AM. I confirmed by looking at Windows installer ZIP files, see bug.

bug 666492 - sometimes SM upgrade leaves ChatZilla disabled

Startup warned the following addons are incompatible: ChatZilla 0.97 (roughly), I clicked to find an update and it reported No Compatible Add-ons Found. Then started fine. about:addons > Extensions reports

ChatZilla is incompatible with SeaMonkey 2.2
ChatZilla 0.9.87 (disabled)

But this is the same version as works in a clean profile!

I think I had the same problem updating 2.0x to Linux 2.1. Someone else mentioned the glitch in but no bug filed.

The existing profile from 2.0x has a Chatzilla extension in C:\Users\nnn\AppData\Roaming\Mozilla\SeaMonkey\Profiles\xxx.default\extensions\{59c81df5-4b7a-477b-912d-4e0fdf64e5f2} and it seems that confuses SM 2.1 and 2.2

I clicked Remove in about:addons, the directory still there. Upon restart, the extension is in a new trash subfolder and gone from about:addons. KaiRo on chat suggested "what should help is if you remove the copy from about:addons, then go to about:config, and reset extensions.lastAppVersion and restart SeaMonkey"

That worked great for me, but not for others on IRC.

I noticed the built-in CZ has different em:maxversion than the CZ on , yet they have identical em:versions!? See the bug.

BUG: is out-of-date

There are no chrome/chatzilla* or component/chatzilla* files, not even in omnijar. In SM 2.2 (and 2.1?), the extension is in SeaMonkey/distribution/extensions/{59c81df5-4b7a-477b-912d-4e0fdf64e5f2}.xpi

Unrelated: jar: file type seems to need the about:config override. is only (?) documentation for the jar: URL protocol.

Plugincheck wrong header works well for SeaMonkey, but the title is wrong, says "Firefox Web Browser — Plugin Check & Updates"