Confirm
396
edits
Changes
update notes
== Warnings from unsigned SeaMonkey installer ==
The SeaMonkey Windows installer is not signed.
In Windows Vista you get two alerts. First
Open File - Security Warning
"The publisher could not be verified. Are you sure you want to run this software.
Publisher: Unknown Publisher
From: \path\to\download\SeaMonkey Setup 2.NNN.exe
This file does not have a valid digital signature. ...
Then if you click [Run], after extracting you get a Windows UAC alert.
User Account Control
An unidentified program wants access to your computer.
...
setup.exe
Unidentified Publisher.
Click Allow to this one.
== 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: dates confusing ==
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.
== ChatZilla woes ==
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 http://forums.mozillazine.org/viewtopic.php?f=6&t=2013041 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"
=== BUG: http://chatzilla.hacksrus.com/faq/ 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 ==
https://developer.mozilla.org/en/Security_and_the_jar_protocol seems to need the about:config override.
http://download.oracle.com/docs/cd/E19253-01/819-0913/author/jar.html#jarprotocol is only (?) documentation for the jar: URL protocol.
The SeaMonkey Windows installer is not signed.
In Windows Vista you get two alerts. First
Open File - Security Warning
"The publisher could not be verified. Are you sure you want to run this software.
Publisher: Unknown Publisher
From: \path\to\download\SeaMonkey Setup 2.NNN.exe
This file does not have a valid digital signature. ...
Then if you click [Run], after extracting you get a Windows UAC alert.
User Account Control
An unidentified program wants access to your computer.
...
setup.exe
Unidentified Publisher.
Click Allow to this one.
== 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: dates confusing ==
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.
== ChatZilla woes ==
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 http://forums.mozillazine.org/viewtopic.php?f=6&t=2013041 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"
=== BUG: http://chatzilla.hacksrus.com/faq/ 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 ==
https://developer.mozilla.org/en/Security_and_the_jar_protocol seems to need the about:config override.
http://download.oracle.com/docs/cd/E19253-01/819-0913/author/jar.html#jarprotocol is only (?) documentation for the jar: URL protocol.
