Re: SeaMonkey v2.0.5 to v2.0.6 update failed -- "The update could not be installed..." [resolved and reported]

2010-07-21 Thread Phillip Pi 

On 7/21/2010 2:01 PM PT, Phillip Jones typed:


I just received the Subject line message.
Caused SM to Quit then a window came up Continue. Then SM opened again
after password entered. then went back and Tried again. This time it
downloaded the entire program took about 10 minutes to download. (1 MB
DSL Line).

This time install took. using 2.0.6 now. I'll have to see whether the
window that open when sending a message stays open and have to dismiss
as previous. or not. Since we have had 7 revisions with no fix I doubt it.


Did you have any process stuck like crashreporter.exe? Check your logs?
--
Phillip Pi
Senior Software Quality Assurance Analyst
Partner Engineering/Internet Service Provider/Symantec Online Services, 
Consumer Business Unit

Symantec Corporation
www.symantec.com
-
Email: phillip...@symantec.comsymc (remove SYMC to reply by e-mail)
-
Please do NOT e-mail me for technical support. DISCLAIMER: The views 
expressed in this posting are mine, and do not necessarily reflect the 
views of my employer. Thank you.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey v2.0.5 to v2.0.6 update failed -- "The update could not be installed..." [resolved and reported]

2010-07-21 Thread NoOp 
On 07/21/2010 02:01 PM, Phillip Jones wrote:
> I just received the Subject line message.
> Caused SM to Quit then a window came up Continue. Then SM opened again 
> after password entered. then went back and Tried again. This time it 
> downloaded the entire program took about 10 minutes to download. (1 MB 
> DSL Line).
> 
> This time install took. using 2.0.6 now.  I'll have to see whether the 
> window that open when sending a message stays open and have to dismiss 
> as previous. or not.  Since we have had 7 revisions with no fix I doubt it.
> 

Dude.. trim! There is no need to post 925 lines for your reply.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey v2.0.5 to v2.0.6 update failed -- "The update could not be installed..." [resolved and reported]

2010-07-21 Thread Phillip Jones 

Phillip Pi wrote:

On 7/21/2010 2:01 PM PT, Phillip Jones typed:


I just received the Subject line message.
Caused SM to Quit then a window came up Continue. Then SM opened again
after password entered. then went back and Tried again. This time it
downloaded the entire program took about 10 minutes to download. (1 MB
DSL Line).

This time install took. using 2.0.6 now. I'll have to see whether the
window that open when sending a message stays open and have to dismiss
as previous. or not. Since we have had 7 revisions with no fix I doubt it.


Did you have any process stuck like crashreporter.exe? Check your logs?


I use the Mac version.

There was no crash just  a message the update didn't take. the an 
continue but which put you back in the application next time you went to 
update, and tried again this time a Full update ensued and took about 10 
minutes (on a 1 mb DSL Connection) to download and install.


As for the problem of the  stuck message after send post the crash 
reporter doesn't show things like this. I never experienced it in SM 1. 
Although I've heard its been a problem as far back as 1.0.4. Evidently 
there is no reporting mechanism for hangs which this problem obviously 
is a type of.


--
Phillip M. Jones, C.E.T."If it's Fixed, Don't Break it"
http://www.phillipmjones.netmailto:pjon...@kimbanet.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey v2.0.5 to v2.0.6 update failed -- "The update could not be installed..." [resolved and reported]

2010-07-21 Thread Ant 

On 7/21/2010 8:08 PM PT, Phillip Jones typed:


I use the Mac version.


Ah, it doesn't have a crash reporter? I didn't know that.



There was no crash just a message the update didn't take. the an
continue but which put you back in the application next time you went to
update, and tried again this time a Full update ensued and took about 10
minutes (on a 1 mb DSL Connection) to download and install.


Weird.



As for the problem of the stuck message after send post the crash
reporter doesn't show things like this. I never experienced it in SM 1.
Although I've heard its been a problem as far back as 1.0.4. Evidently
there is no reporting mechanism for hangs which this problem obviously
is a type of.


Are you sure v1.x had an updater? I don't recall that. I remember having 
to download the full installer just to upgrade in Mac OS X 10.2.8, 
Windows XP Pro., and Debian/Linux. :(

--
"The life of an ant and that of my child should be granted equal 
consideration." --Michael W. Fox, Vice President, The Human Society of 
the United States, The Inhumane Society, New York, 1990.

   /\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
  / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net
 | |o   o| |
\ _ /If crediting, then use Ant nickname and AQFL URL/link.
 ( ) If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey v2.0.5 to v2.0.6 update failed -- "The update could not be installed..." [resolved and reported]

2010-07-22 Thread Phillip Jones 

Ant wrote:

On 7/21/2010 8:08 PM PT, Phillip Jones typed:


I use the Mac version.


Ah, it doesn't have a crash reporter? I didn't know that.



There was no crash just a message the update didn't take. the an
continue but which put you back in the application next time you went to
update, and tried again this time a Full update ensued and took about 10
minutes (on a 1 mb DSL Connection) to download and install.


Weird.



As for the problem of the stuck message after send post the crash
reporter doesn't show things like this. I never experienced it in SM 1.
Although I've heard its been a problem as far back as 1.0.4. Evidently
there is no reporting mechanism for hangs which this problem obviously
is a type of.


Are you sure v1.x had an updater? I don't recall that. I remember having
to download the full installer just to upgrade in Mac OS X 10.2.8,
Windows XP Pro., and Debian/Linux. :(


I was referring to the stuck message after sending message. Not, 
automatic update.  sorry for confusion.


and while we are at it on the page showing after it updated It says on 
the page there were some bug fixes, performance fixes, and security 
updates.  several people in this thread mentioned why announce if just 
security patches.

--
Phillip M. Jones, C.E.T."If it's Fixed, Don't Break it"
http://www.phillipmjones.netmailto:pjon...@kimbanet.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey v2.0.5 to v2.0.6 update failed -- "The update could not be installed..." [resolved and reported]

2010-07-22 Thread Chris Ilias 

On 10-07-22 12:20 AM, Ant wrote:

On 7/21/2010 8:08 PM PT, Phillip Jones typed:


I use the Mac version.


Ah, it doesn't have a crash reporter? I didn't know that.


Mac versions do have a crash reporter.

--
Chris Ilias 
List-owner: support-firefox, support-thunderbird, test-multimedia
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey v2.0.5 to v2.0.6 update failed -- "The update could not be installed..." [resolved and reported]

2010-07-22 Thread Phillip Jones 

Chris Ilias wrote:

On 10-07-22 12:20 AM, Ant wrote:

On 7/21/2010 8:08 PM PT, Phillip Jones typed:


I use the Mac version.


Ah, it doesn't have a crash reporter? I didn't know that.


Mac versions do have a crash reporter.



The way you have cut you attribute a sentence to me I didn't say.

What I did say was I use a Mac.

Yes Mac's have a Crash Reporter and I've made screenshots frequently to 
post here so people would know what crashes I have.


However; the message window coming up about; message sent and staying on 
screen is not a Crash its a form of hang.


--
Phillip M. Jones, C.E.T."If it's Fixed, Don't Break it"
http://www.phillipmjones.netmailto:pjon...@kimbanet.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey v2.0.5 to v2.0.6 update failed -- "The update could not be installed..." [resolved and reported]

2010-07-30 Thread Phillip Pi 
I did more investigations, and found the culprit! It was from 
crashreporter.exe! I am not sure why the latest Process Explorer didn't 
show that one when I searched "seamonkey".


I found and read 
http://kb.mozillazine.org/Software_Update#Software_Update_not_working_properly 
-- "Another possible solution is to reset the Software Update feature by 
ending all Firefox processes and then removing 'active-update.xml', 
'updates.xml' and the 'updates' folder from the appropriate folder 
locations (see above)..."


So I followed the instructions from my C:\winstuff\SeaMonkey2\. I 
retried downloading updates manually, installing them, and restarting 
SM. Same exact problem. :(


I also found logs that was useful. Here's an update.log after deleting 
updates files:


PREPARE PATCH AccessibleMarshal.dll
PREPARE PATCH MapiProxy.dll
PREPARE PATCH application.ini
PREPARE PATCH chrome/classic.jar
PREPARE PATCH chrome/comm.jar
PREPARE PATCH chrome/en-US.jar
PREPARE PATCH chrome/gloda.jar
PREPARE PATCH chrome/messenger.jar
PREPARE PATCH chrome/newsblog.jar
PREPARE PATCH chrome/pippki.jar
PREPARE PATCH chrome/reporter.jar
PREPARE PATCH chrome/toolkit.jar
PREPARE PATCH components/browser.xpt
PREPARE PATCH components/jar50.dll
PREPARE PATCH components/jsd3250.dll
PREPARE PATCH components/storage-Legacy.js
PREPARE PATCH components/suite.dll
PREPARE PATCH components/xpinstal.dll
PREPARE PATCH crashreporter.exe
PREPARE PATCH defaults/pref/browser-prefs.js
PREPARE PATCH extensions/inspec...@mozilla.org/chrome/inspector.jar
PREPARE PATCH extensions/mod...@themes.mozilla.org/chrome/modern.jar
PREPARE PATCH extensions/mod...@themes.mozilla.org/install.rdf
PREPARE PATCH 
extensions/{59c81df5-4b7a-477b-912d-4e0fdf64e5f2}/chrome/chatzilla.jar

PREPARE PATCH extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}/install.rdf
PREPARE PATCH 
extensions/{f13b157f-b174-47e7-a34d-4815ddfdfeb8}/chrome/venkman.jar

PREPARE ADD freebl3.chk
PREPARE PATCH freebl3.dll
PREPARE PATCH greprefs/all.js
PREPARE PATCH js3250.dll
PREPARE PATCH modules/gloda/datastore.js
PREPARE PATCH mozMapi32.dll
PREPARE PATCH mozcrt19.dll
PREPARE PATCH nsldap32v60.dll
PREPARE PATCH nsldappr32v60.dll
PREPARE PATCH nsldif32v60.dll
PREPARE PATCH nspr4.dll
PREPARE PATCH nss3.dll
PREPARE PATCH nssckbi.dll
PREPARE ADD nssdbm3.chk
PREPARE PATCH nssdbm3.dll
PREPARE PATCH nssutil3.dll
PREPARE PATCH platform.ini
PREPARE PATCH plc4.dll
PREPARE PATCH plds4.dll
PREPARE PATCH plugins/npnul32.dll
PREPARE PATCH seamonkey.exe
PREPARE PATCH smime3.dll
PREPARE ADD softokn3.chk
PREPARE PATCH softokn3.dll
PREPARE PATCH sqlite3.dll
PREPARE PATCH ssl3.dll
PREPARE PATCH uninstall/helper.exe
PREPARE PATCH updater.exe
PREPARE PATCH xpcom.dll
PREPARE PATCH xpcom_core.dll
PREPARE REMOVE chrome/app-chrome.manifest
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/chatzilla.jar
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/debugqa.jar
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/debugqa.manifest
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/installed-chrome.txt
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/abcardWindow.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/abcardWindow16.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/ablistWindow.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/addressbookWindow.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/addressbookWindow16.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/bmPropsWindow.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/bmPropsWindow16.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/bookmark-window.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/bookmark-window16.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/calendar-window.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/calendar-window16.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/chatzilla-window.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/chatzilla-window16.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/chatzilla-window.ico
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/default.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/default16.xpm
file ca

Re: SeaMonkey v2.0.5 to v2.0.6 update failed -- "The update could not be installed..." [resolved and reported]

2010-07-30 Thread Phillip Jones 

Phillip Pi wrote:

I did more investigations, and found the culprit! It was from
crashreporter.exe! I am not sure why the latest Process Explorer didn't
show that one when I searched "seamonkey".

I found and read
http://kb.mozillazine.org/Software_Update#Software_Update_not_working_properly
-- "Another possible solution is to reset the Software Update feature by
ending all Firefox processes and then removing 'active-update.xml',
'updates.xml' and the 'updates' folder from the appropriate folder
locations (see above)..."

So I followed the instructions from my C:\winstuff\SeaMonkey2\. I
retried downloading updates manually, installing them, and restarting
SM. Same exact problem. :(

I also found logs that was useful. Here's an update.log after deleting
updates files:

PREPARE PATCH AccessibleMarshal.dll
PREPARE PATCH MapiProxy.dll
PREPARE PATCH application.ini
PREPARE PATCH chrome/classic.jar
PREPARE PATCH chrome/comm.jar
PREPARE PATCH chrome/en-US.jar
PREPARE PATCH chrome/gloda.jar
PREPARE PATCH chrome/messenger.jar
PREPARE PATCH chrome/newsblog.jar
PREPARE PATCH chrome/pippki.jar
PREPARE PATCH chrome/reporter.jar
PREPARE PATCH chrome/toolkit.jar
PREPARE PATCH components/browser.xpt
PREPARE PATCH components/jar50.dll
PREPARE PATCH components/jsd3250.dll
PREPARE PATCH components/storage-Legacy.js
PREPARE PATCH components/suite.dll
PREPARE PATCH components/xpinstal.dll
PREPARE PATCH crashreporter.exe
PREPARE PATCH defaults/pref/browser-prefs.js
PREPARE PATCH extensions/inspec...@mozilla.org/chrome/inspector.jar
PREPARE PATCH extensions/mod...@themes.mozilla.org/chrome/modern.jar
PREPARE PATCH extensions/mod...@themes.mozilla.org/install.rdf
PREPARE PATCH
extensions/{59c81df5-4b7a-477b-912d-4e0fdf64e5f2}/chrome/chatzilla.jar
PREPARE PATCH extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}/install.rdf
PREPARE PATCH
extensions/{f13b157f-b174-47e7-a34d-4815ddfdfeb8}/chrome/venkman.jar
PREPARE ADD freebl3.chk
PREPARE PATCH freebl3.dll
PREPARE PATCH greprefs/all.js
PREPARE PATCH js3250.dll
PREPARE PATCH modules/gloda/datastore.js
PREPARE PATCH mozMapi32.dll
PREPARE PATCH mozcrt19.dll
PREPARE PATCH nsldap32v60.dll
PREPARE PATCH nsldappr32v60.dll
PREPARE PATCH nsldif32v60.dll
PREPARE PATCH nspr4.dll
PREPARE PATCH nss3.dll
PREPARE PATCH nssckbi.dll
PREPARE ADD nssdbm3.chk
PREPARE PATCH nssdbm3.dll
PREPARE PATCH nssutil3.dll
PREPARE PATCH platform.ini
PREPARE PATCH plc4.dll
PREPARE PATCH plds4.dll
PREPARE PATCH plugins/npnul32.dll
PREPARE PATCH seamonkey.exe
PREPARE PATCH smime3.dll
PREPARE ADD softokn3.chk
PREPARE PATCH softokn3.dll
PREPARE PATCH sqlite3.dll
PREPARE PATCH ssl3.dll
PREPARE PATCH uninstall/helper.exe
PREPARE PATCH updater.exe
PREPARE PATCH xpcom.dll
PREPARE PATCH xpcom_core.dll
PREPARE REMOVE chrome/app-chrome.manifest
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/chatzilla.jar
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/debugqa.jar
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/debugqa.manifest
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/installed-chrome.txt
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/abcardWindow.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/abcardWindow16.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/ablistWindow.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/addressbookWindow.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/addressbookWindow16.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/bmPropsWindow.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/bmPropsWindow16.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/bookmark-window.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/bookmark-window16.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/calendar-window.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/calendar-window16.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/chatzilla-window.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/chatzilla-window16.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/chatzilla-window.ico
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/default.xpm
file cannot be removed because it does not exist; skipping
PREPARE REMOVE chrome/icons/default/default16.xpm
file