User:Skierpage/SM 2.2 update notes - Revision history

Skierpage: /* ChatZilla woes */ bug filed

2011-06-23T04:19:14Z

ChatZilla woes: bug filed

Skierpage: /* Bug: dates confusing */ bug filed

2011-06-23T04:16:38Z

Bug: dates confusing: bug filed

← Older revision		Revision as of 04:16, 23 June 2011
Line 25:		Line 25:
	Upon restart, SeaMonkey OK!		Upon restart, SeaMonkey OK!

	== Bug: dates ~~confusing~~ ==		== {{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.		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.

	== ChatZilla woes ==		== ChatZilla woes ==

Skierpage: /* Warnings from unsigned SeaMonkey installer */ update, list bug

2011-06-23T03:23:06Z

Warnings from unsigned SeaMonkey installer: update, list bug

@@ Line 1: / Line 1: @@
-== Warnings from unsigned SeaMonkey installer ==
+== {{bug|666479}} Warnings from unsigned SeaMonkey installer ==
-In Windows Vista you get two alerts.  First
+The SeaMonkey Windows installer is not signed, so in Windows Vista you get two alerts.
 == Failure to run ==

Skierpage at 00:39, 23 June 2011

2011-06-23T00:39:53Z

← Older revision		Revision as of 00:39, 23 June 2011
Line 66:		Line 66:

	http://download.oracle.com/docs/cd/E19253-01/819-0913/author/jar.html#jarprotocol is only (?) documentation for the jar: URL protocol.		http://download.oracle.com/docs/cd/E19253-01/819-0913/author/jar.html#jarprotocol is only (?) documentation for the jar: URL protocol.


			== Plugincheck wrong header ==
			http://www.mozilla.com/en-US/plugincheck/ works well for SeaMonkey, but the title is wrong, says "Firefox Web Browser — Plugin Check & Updates"

Skierpage: update notes

2011-06-23T00:25:26Z

update notes

New page

== 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.

← Older revision		Revision as of 04:19, 23 June 2011
Line 28:		Line 28:
	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.		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.

	== ChatZilla ~~woes~~ ==		== {{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.		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		Then started fine. about:addons > Extensions reports
Line 42:		Line 42:
	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.		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"		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 addons.mozilla.org , yet they have identical em:versions!? See the bug.

	=== BUG: http://chatzilla.hacksrus.com/faq/ is out-of-date ===		=== BUG: http://chatzilla.hacksrus.com/faq/ is out-of-date ===
	There are no chrome/chatzilla* or component/chatzilla* files, not even in omnijar.		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		In SM 2.2 (and 2.1?), the extension is in SeaMonkey/distribution/extensions/{59c81df5-4b7a-477b-912d-4e0fdf64e5f2}.xpi


	== Unrelated: jar: file type ==		== Unrelated: jar: file type ==