Re: mozilla-releases-security-updates

[Yamo']

Hi,

Dirk Fieldhouse a tapoté le 21/12/2020 23:55:

> Besides which, some or all of these issues may be in neophile code 
> (Gecko 60+) that has yet to infect the SM codebase.


It is not only gecko60 code, there is an effort to backport the code :

Quoting 
> Additional important security fixes up to Current Firefox 78.4 ESR and a few 
> enhancements have been backported. 




-- 
Stéphane
Sorry for possible mistakes in English!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: mozilla-releases-security-updates

[Dirk Fieldhouse]

On 20/12/2020 00:16, Daniel wrote:

meagain wrote on 20/12/20 05:01:


https://us-cert.cisa.gov/ncas/current-activity/2020/12/16/mozilla-releases-security-updates-firefox-firefox-esr-and 


How to integrate these updates into SeaMonkey?


I would stand-by, meagain, as I'm sure our trusty SM Devs are working 
their holiday bound butts off, trying to get a SM Version (which 
includes these updates) out the door!! ;-P


Besides which, some or all of these issues may be in neophile code 
(Gecko 60+) that has yet to infect the SM codebase.


/df

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

Re: mozilla-releases-security-updates

[Daniel]

meagain wrote on 20/12/20 05:01:


https://us-cert.cisa.gov/ncas/current-activity/2020/12/16/mozilla-releases-security-updates-firefox-firefox-esr-and 



How to integrate these updates into SeaMonkey?


I would stand-by, meagain, as I'm sure our trusty SM Devs are working 
their holiday bound butts off, trying to get a SM Version (which 
includes these updates) out the door!! ;-P

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 
SeaMonkey/2.53.5.1 Build identifier: 20201115194905


Linux User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) 
Gecko/20100101 SeaMonkey/2.49.1 Build identifier: 20171015235623

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

mozilla-releases-security-updates

[meagain]

https://us-cert.cisa.gov/ncas/current-activity/2020/12/16/mozilla-releases-security-updates-firefox-firefox-esr-and

How to integrate these updates into SeaMonkey?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Updates: re: 2.49.5

[Daniel]

Frank-Rainer Grahl wrote on 10/12/20 20:54:



Daniel wrote:

Frank-Rainer Grahl wrote on 09/12/20 07:26:

Ant wrote:

On 12/8/2020 9:42 AM, Frank-Rainer Grahl wrote:


Frank-Rainer Grahl wrote:
If anyone wants to stay on 2.49.5 or prior running Windows 7 and 
up be my guest but don't file any bugs or ask for official support.


A bit misleading. Goes for other OS too but mentioned 7 because 
2.53.1 removed pre Windows 7 support.


Speaking of W7, how much longer with upcoming SM support it?


No plans to discontinue. We were basically the last supporting XP and 
this will hopefully last longer.


FRG


Frank-Rainer (or any other knowledge person), perhaps you could set me 
straight.


I can understand a modern computer (64 bit or 128 bit even) not being 
really happy running an 8 bit (yes, that's were I started), or a 
sixteen bit or even a thirty-two bit OS/Program 



No 128 bit exists. maybe a few gpus but overall none.

But they should be able to run it wouldn't they?? O.K., not very 
efficiently, but still  And maybe as slow as wet weeks seem, but 
still.


Sure, the other bits and pieces (Java/JavaScript/etc) might be a 
problem, but !!


These days you usually use a vm for old stuff. You would need a 
supported OS and nothing that old will boot on modern hardware.



Or am I totally off track!!


Very theoretical without knowing the actual use case. For Intel the 
instruction set was only expanded as far as I know so even an 8088 
assembler program might still run unless I am mistaken.


FRG


Thanks, Frank-Rainer, that's about my understanding as well  just 
seems a bit of a waste!!

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 
SeaMonkey/2.53.5.1 Build identifier: 20201115194905


Linux User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) 
Gecko/20100101 SeaMonkey/2.49.1 Build identifier: 20171015235623

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

Re: Updates: re: 2.49.5

[Frank-Rainer Grahl]

Daniel wrote:

Frank-Rainer Grahl wrote on 09/12/20 07:26:

Ant wrote:

On 12/8/2020 9:42 AM, Frank-Rainer Grahl wrote:


Frank-Rainer Grahl wrote:
If anyone wants to stay on 2.49.5 or prior running Windows 7 and up be my 
guest but don't file any bugs or ask for official support.


A bit misleading. Goes for other OS too but mentioned 7 because 2.53.1 
removed pre Windows 7 support.


Speaking of W7, how much longer with upcoming SM support it?


No plans to discontinue. We were basically the last supporting XP and this 
will hopefully last longer.


FRG


Frank-Rainer (or any other knowledge person), perhaps you could set me straight.

I can understand a modern computer (64 bit or 128 bit even) not being really 
happy running an 8 bit (yes, that's were I started), or a sixteen bit or even 
a thirty-two bit OS/Program 



No 128 bit exists. maybe a few gpus but overall none.

But they should be able to run it wouldn't they?? O.K., not very efficiently, 
but still  And maybe as slow as wet weeks seem, but still.


Sure, the other bits and pieces (Java/JavaScript/etc) might be a problem, but 
!!


These days you usually use a vm for old stuff. You would need a supported OS 
and nothing that old will boot on modern hardware.



Or am I totally off track!!


Very theoretical without knowing the actual use case. For Intel the 
instruction set was only expanded as far as I know so even an 8088 assembler 
program might still run unless I am mistaken.


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

Re: Updates: re: 2.49.5

[Frank-Rainer Grahl]

Ant wrote:

On 12/8/2020 12:26 PM, Frank-Rainer Grahl wrote:

Ant wrote:

On 12/8/2020 9:42 AM, Frank-Rainer Grahl wrote:


Frank-Rainer Grahl wrote:
If anyone wants to stay on 2.49.5 or prior running Windows 7 and up be my 
guest but don't file any bugs or ask for official support.


A bit misleading. Goes for other OS too but mentioned 7 because 2.53.1 
removed pre Windows 7 support.


Speaking of W7, how much longer with upcoming SM support it?


No plans to discontinue. We were basically the last supporting XP and this 
will hopefully last longer.


Thanks FRG. I am doing the same. I hate W8 and W10. :(


Actually I am on 8.1 With open shell menu and the stupid apps and menu gone it 
is usable and much smoother than 7 when it comes to virtual machines. But main 
vm with SeaMonkey mail is on 7 :)


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

Re: Updates: re: 2.49.5

[Daniel]

Frank-Rainer Grahl wrote on 09/12/20 07:26:

Ant wrote:

On 12/8/2020 9:42 AM, Frank-Rainer Grahl wrote:


Frank-Rainer Grahl wrote:
If anyone wants to stay on 2.49.5 or prior running Windows 7 and up 
be my guest but don't file any bugs or ask for official support.


A bit misleading. Goes for other OS too but mentioned 7 because 
2.53.1 removed pre Windows 7 support.


Speaking of W7, how much longer with upcoming SM support it?


No plans to discontinue. We were basically the last supporting XP and 
this will hopefully last longer.


FRG


Frank-Rainer (or any other knowledge person), perhaps you could set me 
straight.


I can understand a modern computer (64 bit or 128 bit even) not being 
really happy running an 8 bit (yes, that's were I started), or a sixteen 
bit or even a thirty-two bit OS/Program 


But they should be able to run it wouldn't they?? O.K., not very 
efficiently, but still  And maybe as slow as wet weeks seem, but still.


Sure, the other bits and pieces (Java/JavaScript/etc) might be a 
problem, but !!


Or am I totally off track!!
--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 
SeaMonkey/2.53.5.1 Build identifier: 20201115194905


Linux User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) 
Gecko/20100101 SeaMonkey/2.49.1 Build identifier: 20171015235623

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

Re: Updates: re: 2.49.5

[Ant]

On 12/8/2020 12:26 PM, Frank-Rainer Grahl wrote:

Ant wrote:

On 12/8/2020 9:42 AM, Frank-Rainer Grahl wrote:


Frank-Rainer Grahl wrote:
If anyone wants to stay on 2.49.5 or prior running Windows 7 and up 
be my guest but don't file any bugs or ask for official support.


A bit misleading. Goes for other OS too but mentioned 7 because 
2.53.1 removed pre Windows 7 support.


Speaking of W7, how much longer with upcoming SM support it?


No plans to discontinue. We were basically the last supporting XP and 
this will hopefully last longer.


Thanks FRG. I am doing the same. I hate W8 and W10. :(
--
Life's so loco! ..!.. *isms, sins, hates, (d)evil, z, tiredness, my old 
body, (sick/ill)ness (e.g., COVID-19 & SARS-CoV-2), deaths (RIP), 
interruptions, issues, conflicts, obstacles, stresses, fires, 
out(r)ages, dramas, unlucky #4, 2020, greeds, bugs (e.g., crashes & 
female mosquitoes), etc. D: Note: A fixed width font (Courier, 
Monospace, etc.) is required to see this signature correctly.

   /\___/\http://aqfl.net & http://antfarm.home.dhs.org
  / /\ /\ \
 | |o   o| |   Axe ANT from its address if shown & e-mailing privately.
\ _ /   Please kindly use Ant nickname & URL/link if crediting.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Updates: General

[Gunther Nikl]

Edmund Wong wrote:
> It is also not likely that we'd set the update system to use
> SSLv3 or TLSv1 (thanks to Heartbleed, Poodle, and whatever
> else) and set to a lower cypher set.

Despite the attacks listed I believe supporting TLSv1 with a very
limited cypher set should be possible. Even SM 1.1.x does support
ecdhe_ecdsa_aes and ecdhe_rsa_aes. Since these cyphers are enabled
by default supporting them with TLSv1 on the server should be fine.

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

Re: Updates: re: 2.49.5

[Daniel]

Frank-Rainer Grahl wrote on 9/12/2020 4:33 am:

Daniel wrote:

Edmund Wong wrote on 08/12/20 10:48:

Edmund Wong wrote:

Hi All,

This is a quick specific mention for version 2.49.5.

There are no updates to this version.  There are updates to 2.49.4.
Just none to 2.49.5.  Users hoping to update to this
version will need to update manually.


Further to my post, I'm currently working on a minor patch
between 2.49.4 to 2.49.5.

Edmund


Can I ask  "WHY??"

Shouldn't you be advising us all to upgrade to SM 2.53.5.1 (or 
whatever) rather than fixing problems associated with a,  what??, 
year or more old version??


(Not that I, and I'm sure a lot of others here, don't appreciated all 
the effort that you, Edmund, and the rest of the SM team put in!! ;-) )


(To be honest, when I saw your 36 line original post in this thread, 
then saw your 13 line reply to yourself, I thought this would be you 
apologising for the OP!! ;-P )


My personal two cents:

Profile upgrade from 2.0 to 2.49.x or whatever will probably fail. I 
think needs to go thru 2.1 at least. Anyone still on pre 2.49 probably 
has a reason if I find it valid or not. Don't care don't want to hear 
it. We are fixing outstanding issues as fast as time permits but not 
enough devs around. Issues with add-ons need to be fixed buy the author 
or a third party. Binary plugins and add-ons are gone and will not come 
back.


Would enable updates from 2.33.1 and up to 2.49.5. Tested these and 
should cause no big problems.


I would not enable updates from 2.49.x to 2.53.1 and up. If a master 
password is set this might result in data loss. Also because of the code 
cleanups and mozilla deprecations older add-ons might not work resulting 
in further unhappy users. If anyone wants to stay on 2.49.5 or prior 
running Windows 7 and up be my guest but don't file any bugs or ask for 
official support.


Updates for 2.53.1 and up should be fully enabled. There are some issues 
in later versions but overall they are stable.



FRG


Thank you! Thank you! Thank you! For all your efforts. ;-P
--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 
SeaMonkey/2.53.5.1 Build identifier: 20201115194905


Linux User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) 
Gecko/20100101 SeaMonkey/2.49.1 Build identifier: 20171015235623

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

Re: Updates: General

[mozilla-lists . mbourne]

Edmund Wong wrote:

Hi All,

I hope all is well with everyone.

I've been spending a lot of time working on the update system.  When I
started this project some time ago,  I had just wanted to use the
old system and update (pun not intended)it.  Gave up that idea and went
for something else.

Now fast forward a few years to 2020 after working on this on-and-off.
With the release process still being half-manually generated (though
the process has gotten a bit faster), I figured I'd tackle this update
issue once and for all.

I had the intention of setting up the new system such that all versions
(2.0 to 2.53.5.1 etc) can update properly.  After getting a simple
working prototype running, I realized that it's no longer possible to
even update anything <= 2.23.


To be honest, I always thought (probably just assumed) that the main 
problem with updating from older versions was that the Mozilla server 
they were hard-coded to check for updates ceased to exist (or at least 
stopped hosting SeaMonkey updates).  So you were having to set up a new 
server to host updates, but even then older versions wouldn't know about 
it so wouldn't pick up any updates.  I hadn't realised there was any 
possibility that new infrastructure might eventually enable those older 
versions to update as well.


There's bound to come a point, though, where an old version is just too 
old to be able to support updating automatically!


--
Mark.

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

Re: Updates: re: 2.49.5

[Frank-Rainer Grahl]

Ant wrote:

On 12/8/2020 9:42 AM, Frank-Rainer Grahl wrote:


Frank-Rainer Grahl wrote:
If anyone wants to stay on 2.49.5 or prior running Windows 7 and up be my 
guest but don't file any bugs or ask for official support.


A bit misleading. Goes for other OS too but mentioned 7 because 2.53.1 
removed pre Windows 7 support.


Speaking of W7, how much longer with upcoming SM support it?


No plans to discontinue. We were basically the last supporting XP and this 
will hopefully last longer.


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

Re: Updates: re: 2.49.5

[Ant]

On 12/8/2020 9:42 AM, Frank-Rainer Grahl wrote:


Frank-Rainer Grahl wrote:
If anyone wants to stay on 2.49.5 or prior running Windows 7 and up be 
my guest but don't file any bugs or ask for official support.


A bit misleading. Goes for other OS too but mentioned 7 because 2.53.1 
removed pre Windows 7 support.


Speaking of W7, how much longer with upcoming SM support it?
--
Life's so loco! ..!.. *isms, sins, hates, (d)evil, z, tiredness, my old 
body, (sick/ill)ness (e.g., COVID-19 & SARS-CoV-2), deaths (RIP), 
interruptions, issues, conflicts, obstacles, stresses, fires, 
out(r)ages, dramas, unlucky #4, 2020, greeds, bugs (e.g., crashes & 
female mosquitoes), etc. D: Note: A fixed width font (Courier, 
Monospace, etc.) is required to see this signature correctly.

   /\___/\http://aqfl.net & http://antfarm.home.dhs.org
  / /\ /\ \
 | |o   o| |   Axe ANT from its address if shown & e-mailing privately.
\ _ /   Please kindly use Ant nickname & URL/link if crediting.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Updates: re: 2.49.5

[Frank-Rainer Grahl]

Frank-Rainer Grahl wrote:
If anyone wants to stay on 2.49.5 or prior running Windows 7 and up be my 
guest but don't file any bugs or ask for official support.


A bit misleading. Goes for other OS too but mentioned 7 because 2.53.1 removed 
pre Windows 7 support.


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

Re: Updates: re: 2.49.5

[Frank-Rainer Grahl]

Daniel wrote:

Edmund Wong wrote on 08/12/20 10:48:

Edmund Wong wrote:

Hi All,

This is a quick specific mention for version 2.49.5.

There are no updates to this version.  There are updates to 2.49.4.
Just none to 2.49.5.  Users hoping to update to this
version will need to update manually.


Further to my post, I'm currently working on a minor patch
between 2.49.4 to 2.49.5.

Edmund


Can I ask  "WHY??"

Shouldn't you be advising us all to upgrade to SM 2.53.5.1 (or whatever) 
rather than fixing problems associated with a,  what??, year or more old 
version??


(Not that I, and I'm sure a lot of others here, don't appreciated all the 
effort that you, Edmund, and the rest of the SM team put in!! ;-) )


(To be honest, when I saw your 36 line original post in this thread, then saw 
your 13 line reply to yourself, I thought this would be you apologising for 
the OP!! ;-P )


My personal two cents:

Profile upgrade from 2.0 to 2.49.x or whatever will probably fail. I think 
needs to go thru 2.1 at least. Anyone still on pre 2.49 probably has a reason 
if I find it valid or not. Don't care don't want to hear it. We are fixing 
outstanding issues as fast as time permits but not enough devs around. Issues 
with add-ons need to be fixed buy the author or a third party. Binary plugins 
and add-ons are gone and will not come back.


Would enable updates from 2.33.1 and up to 2.49.5. Tested these and should 
cause no big problems.


I would not enable updates from 2.49.x to 2.53.1 and up. If a master password 
is set this might result in data loss. Also because of the code cleanups and 
mozilla deprecations older add-ons might not work resulting in further unhappy 
users. If anyone wants to stay on 2.49.5 or prior running Windows 7 and up be 
my guest but don't file any bugs or ask for official support.


Updates for 2.53.1 and up should be fully enabled. There are some issues in 
later versions but overall they are stable.



FRG

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

Re: Updates: re: 2.49.5

[Daniel]

Edmund Wong wrote on 08/12/20 10:48:

Edmund Wong wrote:

Hi All,

This is a quick specific mention for version 2.49.5.

There are no updates to this version.  There are updates to 2.49.4.
Just none to 2.49.5.  Users hoping to update to this
version will need to update manually.


Further to my post, I'm currently working on a minor patch
between 2.49.4 to 2.49.5.

Edmund


Can I ask  "WHY??"

Shouldn't you be advising us all to upgrade to SM 2.53.5.1 (or whatever) 
rather than fixing problems associated with a,  what??, year or more 
old version??


(Not that I, and I'm sure a lot of others here, don't appreciated all 
the effort that you, Edmund, and the rest of the SM team put in!! ;-) )


(To be honest, when I saw your 36 line original post in this thread, 
then saw your 13 line reply to yourself, I thought this would be you 
apologising for the OP!! ;-P )

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 
SeaMonkey/2.53.5.1 Build identifier: 20201115194905


Linux User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) 
Gecko/20100101 SeaMonkey/2.49.1 Build identifier: 2017101523562

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

Re: Updates: General

[Daniel]

Don Spam's Reckless Son wrote on 07/12/20 21:40:

Edmund Wong wrote:

Hi All,

I hope all is well with everyone.

I've been spending a lot of time working on the update system.  When I
started this project some time ago,  I had just wanted to use the
old system and update (pun not intended)it.  Gave up that idea and went
for something else.

Now fast forward a few years to 2020 after working on this on-and-off.
With the release process still being half-manually generated (though
the process has gotten a bit faster), I figured I'd tackle this update
issue once and for all.

I had the intention of setting up the new system such that all versions
(2.0 to 2.53.5.1 etc) can update properly.  After getting a simple
working prototype running, I realized that it's no longer possible to
even update anything <= 2.23.

Our update site uses TLSv1.1 or 1.2 (and a better set of cyphers) which
these versions don't support and it's no longer possible to patch these
versions to support TLSv1.1 or TLSv1.2.

It is also not likely that we'd set the update system to use
SSLv3 or TLSv1 (thanks to Heartbleed, Poodle, and whatever
else) and set to a lower cypher set.

Errors:
   Version 2.1 to 2.23 gets a 'ssl_error_no_cypher_overlap' error.

   Version 2.0x gets a "Data transfer interupted" error.

   I haven't tested version 1.x.  or the Mozilla Suite.


So, I have come to the conclusion that it doesn't seem possible to
update 2.0 to the latest and greatest.

Here's a list of versions and their supported status:

Versions

   o Mozilla Suite, 1.x, 2.0x, <= 2.23  :  Not supported.
 [Related gecko versions: 1.8, 1.8.1, 1.9.1, <= 26

   o versions >= 2.24:   Supported
  [related gecko versions:  >= 27]

This is only considering versions as they are; Not the underlying
operating system support.

That's my update on the updates. [Probably going to be an update to
this update that updates on the update...etc... ad nauseum]
  We're nearly there.  I just need to make sure that the update process
won't update systems that *shouldn't* be updated.  i.e Updating 2.49.5
to 2.53 on a Winxp system or, in the case of Linux distros own compiled
versions, they also won't be updated. [Though I have been told
that Linux distros-own compiled versions won't query the update
server.]

Edmund


Just one question to that: I have an ancient profile which I found on an 
unused machine and where I'd like to at least have access to the emails 
there.
Would a modern Seamonkey be able to understand them; are the profile 
incompatibilities in the email handling, the browser side or in common 
parts such as password handling?  "ancient" certainly means < 2.24 and 
it may even mean < 2.0.


Don, might it be possible to use MozBackup to backup the old profile, 
copy the file to your new(er) computer and then use MozBackup to expand 
the (old) profile into a (new) profile to see if your new(er) SeaMonkey 
can make any sense of it??

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 
SeaMonkey/2.53.5.1 Build identifier: 20201115194905


Linux User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) 
Gecko/20100101 SeaMonkey/2.49.1 Build identifier: 20171015235623

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

Re: Updates: General

[Steve Wendt via support-seamonkey]

On 12/7/2020 4:05 PM, Edmund Wong wrote:


What I do know is that there was never an automatic upgrade
path from < 2.0 to 2.0.   It was always manual.

I think the best way is to backup the profile, and upgrade
SeaMonkey manually from < 2.0 to 2.0, then 2.0 to 2.1..etc
up until 2.24 (while backing up the profile as you go).


The release notes of the various versions should offer some guidance.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Updates: General

[Edmund Wong]

Don Spam's Reckless Son wrote:
> Edmund Wong wrote:
>> Hi All,
>>
>> I hope all is well with everyone.
>>
>> I've been spending a lot of time working on the update system.  When I
>> started this project some time ago,  I had just wanted to use the
>> old system and update (pun not intended)it.  Gave up that idea and went
>> for something else.
>>
>> Now fast forward a few years to 2020 after working on this on-and-off.
>> With the release process still being half-manually generated (though
>> the process has gotten a bit faster), I figured I'd tackle this update
>> issue once and for all.
>>
>> I had the intention of setting up the new system such that all versions
>> (2.0 to 2.53.5.1 etc) can update properly.  After getting a simple
>> working prototype running, I realized that it's no longer possible to
>> even update anything <= 2.23.
>>
>> Our update site uses TLSv1.1 or 1.2 (and a better set of cyphers) which
>> these versions don't support and it's no longer possible to patch these
>> versions to support TLSv1.1 or TLSv1.2.
>>
>> It is also not likely that we'd set the update system to use
>> SSLv3 or TLSv1 (thanks to Heartbleed, Poodle, and whatever
>> else) and set to a lower cypher set.
>>
>> Errors:
>>    Version 2.1 to 2.23 gets a 'ssl_error_no_cypher_overlap' error.
>>
>>    Version 2.0x gets a "Data transfer interupted" error.
>>
>>    I haven't tested version 1.x.  or the Mozilla Suite.
>>
>>
>> So, I have come to the conclusion that it doesn't seem possible to
>> update 2.0 to the latest and greatest.
>>
>> Here's a list of versions and their supported status:
>>
>> Versions
>>
>>    o Mozilla Suite, 1.x, 2.0x, <= 2.23  :  Not supported.
>>  [Related gecko versions: 1.8, 1.8.1, 1.9.1, <= 26
>>
>>    o versions >= 2.24:   Supported
>>   [related gecko versions:  >= 27]
>>
>> This is only considering versions as they are; Not the underlying
>> operating system support.
>>
>> That's my update on the updates. [Probably going to be an update to
>> this update that updates on the update...etc... ad nauseum]
>>   We're nearly there.  I just need to make sure that the update process
>> won't update systems that *shouldn't* be updated.  i.e Updating 2.49.5
>> to 2.53 on a Winxp system or, in the case of Linux distros own compiled
>> versions, they also won't be updated. [Though I have been told
>> that Linux distros-own compiled versions won't query the update
>> server.]
>>
>>
>> Edmund
>>
> 
> Just one question to that: I have an ancient profile which I found on an
> unused machine and where I'd like to at least have access to the emails
> there.
> Would a modern Seamonkey be able to understand them; are the profile
> incompatibilities in the email handling, the browser side or in common
> parts such as password handling?  "ancient" certainly means < 2.24 and
> it may even mean < 2.0.
> 

There will definitely be incompatabilities which could cause either
SeaMonkey to crash or the profile getting corrupted.   This would
definitely apply to anything < 2.0.

As for the differences, unfortunately, I don't know the inner
workings of the profile code to tell which part would work and
which part won't.

What I do know is that there was never an automatic upgrade
path from < 2.0 to 2.0.   It was always manual.

I think the best way is to backup the profile, and upgrade
SeaMonkey manually from < 2.0 to 2.0, then 2.0 to 2.1..etc
up until 2.24 (while backing up the profile as you go).

Again, I apologize for not being too specific or helpful.

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

Re: Updates: re: 2.49.5

[Edmund Wong]

Edmund Wong wrote:
> Hi All,
> 
> This is a quick specific mention for version 2.49.5.
> 
> There are no updates to this version.  There are updates to 2.49.4.
> Just none to 2.49.5.  Users hoping to update to this
> version will need to update manually.

Further to my post, I'm currently working on a minor patch
between 2.49.4 to 2.49.5.

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

Re: Updates: General

[WaltS48]

On 12/7/20 5:34 PM, mozilla-lists.mbou...@spamgourmet.com wrote:

WaltS48 wrote:

On 12/7/20 2:43 PM, Gerry Hickman wrote:

Edmund Wong wrote:

Now fast forward a few years to 2020 after working on this on-and-off.
With the release process still being half-manually generated (though
the process has gotten a bit faster), I figured I'd tackle this update
issue once and for all.


The way it works on Linux distros is really much better than I 
remember on Windows where individual apps had their own updaters with 
their own schedules, installers, and admin rights. On Linux distros, 
you run a simple command and the whole o/s (and all apps) offer their 
updates.


The issue for Edmund is trying to ensure that, when SeaMonkey is built 
by a distro and installed via their package manager, SeaMonkey's 
built-in updater doesn't interfere with that.  The system package keeps 
track of files it installs, so that they can be removed as necessary 
when the package is updated or uninstalled.  If SeaMonkey installed an 
update through its own mechanism, that would be outside the control and 
knowledge of the system's package manager and could break future updates 
and uninstalls.

 > Some applications provide a build-time option to disable automatic
updates.  I don't know if SeaMonkey has such an option, but if it does 
the onus might be on the people building packages for distros to use 
that option to disable SeaMonkey's updates.  Not sure where that would 
leave Ubuntuzilla though, as I think they simply package the official 
builds, so probably wouldn't be compiled with that option.




The Firefox and Thunderbird builds built by Ubuntu have 
"--disable-updater" in the configure options.





Ubuntu doesn't provide SeaMonkey in its main repo anymore.


For SeaMonkey on Ubuntu (and its derivatives such as Mint), there's the 
Ubuntuzilla repository:

https://sourceforge.net/p/ubuntuzilla/wiki/Main_Page/



I'm not interested in adding any other repositories.

I have to download and install each new version over the old. An 
internal app update mechanism would be greatly appreciated.


Even if SeaMonkey's built-in updater did work, personally I'd still use 
Ubuntuzilla since I find it more convenient to manage updates through 
the system's package manager, along with everything else.




I'd rather use the SeaMonkey built-in updater since the system's package 
manager doesn't provide the application.


I actually prefer the Windows way of installing and updating the 
applications from their developers.


--
OS: Ubuntu Linux 18.04LTS - Gnome Desktop
https://www.thunderbird.net/en-US/get-involved/
https://give.thunderbird.net/en-US/


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

Re: Updates: General

[mozilla-lists . mbourne]

WaltS48 wrote:

On 12/7/20 2:43 PM, Gerry Hickman wrote:

Edmund Wong wrote:

Now fast forward a few years to 2020 after working on this on-and-off.
With the release process still being half-manually generated (though
the process has gotten a bit faster), I figured I'd tackle this update
issue once and for all.


The way it works on Linux distros is really much better than I 
remember on Windows where individual apps had their own updaters with 
their own schedules, installers, and admin rights. On Linux distros, 
you run a simple command and the whole o/s (and all apps) offer their 
updates.


The issue for Edmund is trying to ensure that, when SeaMonkey is built 
by a distro and installed via their package manager, SeaMonkey's 
built-in updater doesn't interfere with that.  The system package keeps 
track of files it installs, so that they can be removed as necessary 
when the package is updated or uninstalled.  If SeaMonkey installed an 
update through its own mechanism, that would be outside the control and 
knowledge of the system's package manager and could break future updates 
and uninstalls.


Some applications provide a build-time option to disable automatic 
updates.  I don't know if SeaMonkey has such an option, but if it does 
the onus might be on the people building packages for distros to use 
that option to disable SeaMonkey's updates.  Not sure where that would 
leave Ubuntuzilla though, as I think they simply package the official 
builds, so probably wouldn't be compiled with that option.


SeaMonkey is already in EPEL for example, so it's a ten 
second job to update it. You don't need to run an exe file 
(installer), you just copy a few files, and you can even downgrade.




What is EPEL?


Extra Packages for Enterprise Linux.  It's a non-default repository with 
additional packages for Red Hat (and derivatives such as CentOS).  No 
good for Ubuntu though, as Red Hat uses RPM packages and Ubuntu uses Deb 
packages.



Ubuntu doesn't provide SeaMonkey in its main repo anymore.


For SeaMonkey on Ubuntu (and its derivatives such as Mint), there's the 
Ubuntuzilla repository:

https://sourceforge.net/p/ubuntuzilla/wiki/Main_Page/

I have to download and install each new version over the old. An 
internal app update mechanism would be greatly appreciated.


Even if SeaMonkey's built-in updater did work, personally I'd still use 
Ubuntuzilla since I find it more convenient to manage updates through 
the system's package manager, along with everything else.


--
Mark.

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

Re: Updates: General

[Gerry Hickman via support-seamonkey]

WaltS48 wrote:

What is EPEL?



Ubuntu doesn't provide SeaMonkey in its main repo anymore.

I have to download and install each new version over the old. An 
internal app update mechanism would be greatly appreciated.


EPEL is "Extra Packages for Enterprise Linux", you can add it as a 
repository to either RHEL (Red Hat Enterprise Linux) or to CentOS. The 
packages are in RPM format, (Red Hat Package Manager). The package 
manager is a robust way to manage installed programs, for example 
checking dependencies and preventing conflicts.


Ubuntu uses APT and *.deb packages.

--
Gerry Hickman (London UK)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Updates: General

[WaltS48]

On 12/7/20 2:43 PM, Gerry Hickman wrote:

Edmund Wong wrote:

Now fast forward a few years to 2020 after working on this on-and-off.
With the release process still being half-manually generated (though
the process has gotten a bit faster), I figured I'd tackle this update
issue once and for all.


The way it works on Linux distros is really much better than I remember 
on Windows where individual apps had their own updaters with their own 
schedules, installers, and admin rights. On Linux distros, you run a 
simple command and the whole o/s (and all apps) offer their updates. 
SeaMonkey is already in EPEL for example, so it's a ten second job to 
update it. You don't need to run an exe file (installer), you just copy 
a few files, and you can even downgrade.




What is EPEL?

Ubuntu doesn't provide SeaMonkey in its main repo anymore.

I have to download and install each new version over the old. An 
internal app update mechanism would be greatly appreciated.


--
OS: Ubuntu Linux 18.04LTS - Gnome Desktop
https://www.thunderbird.net/en-US/get-involved/
https://give.thunderbird.net/en-US/

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

Re: Updates: General

[Gerry Hickman via support-seamonkey]

Don Spam's Reckless Son wrote:

Just one question to that: I have an ancient profile which I found on an 
unused machine and where I'd like to at least have access to the emails 
there.

Would a modern Seamonkey be able to understand them


I'd say it's important that you upgrade (and test) any old profiles as 
soon as possible, so they're at least compatible with the current 
version. Make (and keep) a backup before upgrading.



--
Gerry Hickman (London UK)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Updates: General

[Gerry Hickman via support-seamonkey]

Edmund Wong wrote:

Now fast forward a few years to 2020 after working on this on-and-off.
With the release process still being half-manually generated (though
the process has gotten a bit faster), I figured I'd tackle this update
issue once and for all.


The way it works on Linux distros is really much better than I remember 
on Windows where individual apps had their own updaters with their own 
schedules, installers, and admin rights. On Linux distros, you run a 
simple command and the whole o/s (and all apps) offer their updates. 
SeaMonkey is already in EPEL for example, so it's a ten second job to 
update it. You don't need to run an exe file (installer), you just copy 
a few files, and you can even downgrade.


--
Gerry Hickman (London UK)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Updates: General

[Don Spam's Reckless Son]

Edmund Wong wrote:

Hi All,

I hope all is well with everyone.

I've been spending a lot of time working on the update system.  When I
started this project some time ago,  I had just wanted to use the
old system and update (pun not intended)it.  Gave up that idea and went
for something else.

Now fast forward a few years to 2020 after working on this on-and-off.
With the release process still being half-manually generated (though
the process has gotten a bit faster), I figured I'd tackle this update
issue once and for all.

I had the intention of setting up the new system such that all versions
(2.0 to 2.53.5.1 etc) can update properly.  After getting a simple
working prototype running, I realized that it's no longer possible to
even update anything <= 2.23.

Our update site uses TLSv1.1 or 1.2 (and a better set of cyphers) which
these versions don't support and it's no longer possible to patch these
versions to support TLSv1.1 or TLSv1.2.

It is also not likely that we'd set the update system to use
SSLv3 or TLSv1 (thanks to Heartbleed, Poodle, and whatever
else) and set to a lower cypher set.

Errors:
   Version 2.1 to 2.23 gets a 'ssl_error_no_cypher_overlap' error.

   Version 2.0x gets a "Data transfer interupted" error.

   I haven't tested version 1.x.  or the Mozilla Suite.


So, I have come to the conclusion that it doesn't seem possible to
update 2.0 to the latest and greatest.

Here's a list of versions and their supported status:

Versions

   o Mozilla Suite, 1.x, 2.0x, <= 2.23  :  Not supported.
 [Related gecko versions: 1.8, 1.8.1, 1.9.1, <= 26

   o versions >= 2.24:   Supported
  [related gecko versions:  >= 27]

This is only considering versions as they are; Not the underlying
operating system support.

That's my update on the updates. [Probably going to be an update to
this update that updates on the update...etc... ad nauseum]
  We're nearly there.  I just need to make sure that the update process
won't update systems that *shouldn't* be updated.  i.e Updating 2.49.5
to 2.53 on a Winxp system or, in the case of Linux distros own compiled
versions, they also won't be updated. [Though I have been told
that Linux distros-own compiled versions won't query the update
server.]


Edmund



Just one question to that: I have an ancient profile which I found on an 
unused machine and where I'd like to at least have access to the emails 
there.
Would a modern Seamonkey be able to understand them; are the profile 
incompatibilities in the email handling, the browser side or in common 
parts such as password handling?  "ancient" certainly means < 2.24 and 
it may even mean < 2.0.


--
spammo ergo sum, viruses courtesy of https://www.nsa.gov/malware/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Updates: re: 2.49.5

[Edmund Wong]

Hi All,

This is a quick specific mention for version 2.49.5.

There are no updates to this version.  There are updates to 2.49.4.
Just none to 2.49.5.  Users hoping to update to this
version will need to update manually.

Why?

Because 2.49.5 was a difficult version (at least for me) to release
as I hadn't gotten any new release process set properly.  I hadn't
even (still haven't,  really) gotten the whole release automation
working, so IanN and FRG had to manually do that build.

So while I had uploaded the binaries, I had forgotten the updates.
While the Linux and mac updates can still be uploaded (they hadn't
been clobbered),  the windows versions need to be regenerated.
That is my fault, and I do apologize.  It is inconvenient,
especially when I'll have the update system set up properly;
but what's done is done.

Given that regenerating the whole shebang would be difficult(
the build environment requirements are not the same as that
for the latest versions),  it wouldn't be a very efficient
use of a very limited resource group.

If and when the release automation is done and can be set
to use different build environments (a very complicated
task...  imo), I don't quite see it being done.

So, that said, if you are planning to update to 2.49.5,
please do so manually.


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

Updates: General

[Edmund Wong]

Hi All,

I hope all is well with everyone.

I've been spending a lot of time working on the update system.  When I
started this project some time ago,  I had just wanted to use the
old system and update (pun not intended)it.  Gave up that idea and went
for something else.

Now fast forward a few years to 2020 after working on this on-and-off.
With the release process still being half-manually generated (though
the process has gotten a bit faster), I figured I'd tackle this update
issue once and for all.

I had the intention of setting up the new system such that all versions
(2.0 to 2.53.5.1 etc) can update properly.  After getting a simple
working prototype running, I realized that it's no longer possible to
even update anything <= 2.23.

Our update site uses TLSv1.1 or 1.2 (and a better set of cyphers) which
these versions don't support and it's no longer possible to patch these
versions to support TLSv1.1 or TLSv1.2.

It is also not likely that we'd set the update system to use
SSLv3 or TLSv1 (thanks to Heartbleed, Poodle, and whatever
else) and set to a lower cypher set.

Errors:
  Version 2.1 to 2.23 gets a 'ssl_error_no_cypher_overlap' error.

  Version 2.0x gets a "Data transfer interupted" error.

  I haven't tested version 1.x.  or the Mozilla Suite.


So, I have come to the conclusion that it doesn't seem possible to
update 2.0 to the latest and greatest.

Here's a list of versions and their supported status:

Versions

  o Mozilla Suite, 1.x, 2.0x, <= 2.23  :  Not supported.
[Related gecko versions: 1.8, 1.8.1, 1.9.1, <= 26

  o versions >= 2.24:   Supported
 [related gecko versions:  >= 27]

This is only considering versions as they are; Not the underlying
operating system support.

That's my update on the updates. [Probably going to be an update to
this update that updates on the update...etc... ad nauseum]
 We're nearly there.  I just need to make sure that the update process
won't update systems that *shouldn't* be updated.  i.e Updating 2.49.5
to 2.53 on a Winxp system or, in the case of Linux distros own compiled
versions, they also won't be updated. [Though I have been told
that Linux distros-own compiled versions won't query the update
server.]


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

Re: updates

[Don Spam's Reckless Son]

Doug Hughes wrote:

Good Morning

I have and use Sea Monkey on two PC's
On this particular PC,2.53.1 Seamonkey says it is up to date and there 
are no available updates.
On my other PC, 2.53.3  Seamonkey and says an update to 2.53.4 is 
available, yet windows wont let me install
because publisher is unknown. One or the other PC I suspect is infected 
with a clone or is there some way

to clarify whats going on here?
any help would be appreciated.
Regards

Doug



The "publisher is unknown" means what it says, Microsoft doesn't know 
who produced it.  You do and - assuming you got it from the correct 
place - it is safe to install.
I read something a couple of years back about a version of Windows 10 
which was "locked in" to the Microsoft Store (or whatever it is called) 
and you would only be able to install products from there.  If that 
exists and you have such a (cheap) version of Windows then you have a 
problem, but since you already have a version of Seamonkey there it 
obviously worked in the past.


--
spammo ergo sum, viruses courtesy of https://www.nsa.gov/malware/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: updates

[Lemuel Johnson via support-seamonkey]

On 9/25/2020 8:12 AM, Doug Hughes wrote:

Good Morning

I have and use Sea Monkey on two PC's
On this particular PC,2.53.1 Seamonkey says it is up to date and there 
are no available updates.
On my other PC, 2.53.3  Seamonkey and says an update to 2.53.4 is 
available, yet windows wont let me install
because publisher is unknown. One or the other PC I suspect is infected 
with a clone or is there some way

to clarify whats going on here?
any help would be appreciated.
Regards

Doug



The warning is bogus.  There's a link on that Windows warning page that 
says something like "Details" or "More Info", etc.  Click that and on 
the next page click on "Install".


Lem Johnson

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

Re: updates

[Nuno Silva]

On 2020-09-25, Doug Hughes wrote:

> Good Morning
>
> I have and use Sea Monkey on two PC's
> On this particular PC,2.53.1 Seamonkey says it is up to date and there
> are no available updates.
> On my other PC, 2.53.3  Seamonkey and says an update to 2.53.4 is
> available, yet windows wont let me install
> because publisher is unknown. One or the other PC I suspect is
> infected with a clone or is there some way
> to clarify whats going on here?
> any help would be appreciated.
> Regards
>
> Doug
>

How are you getting the information about updates?

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

updates

[Doug Hughes]

Good Morning

I have and use Sea Monkey on two PC's
On this particular PC,2.53.1 Seamonkey says it is up to date and there 
are no available updates.
On my other PC, 2.53.3  Seamonkey and says an update to 2.53.4 is 
available, yet windows wont let me install
because publisher is unknown. One or the other PC I suspect is infected 
with a clone or is there some way

to clarify whats going on here?
any help would be appreciated.
Regards

Doug

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

Re: updates

[Ray Davison]

Ken Rudolph wrote:

After all these years (since Netscape 1.0) I've always been scared in
the past when I had to manually do a SeaMonkey version update.
Since Netscape 1.0 I have never "updated" any of the related apps.  I 
get the profiles to a neutral location - preferably a different 
partition, unzip the new app version, and try it.  If I like it better 
than the previous, I delete the previous.


Once when searching for the date/time of a bug insertion I had 20 
versions of SM all on the HDD and using the same profile.


HOWEVER, when SM went from 1X to 2X there was great fanfare; "don't try 
to use a 2X profile with a 1X app".  Now such changes are rather quiet 
and easy to miss.  I currently have 6 recent SM, I know there are 
profile issues, so they are off in "trash space", and my primary SM is 
not effected.


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

Re: updates

[Don Spam's Reckless Son]

Edward wrote:

Don Spam's Reckless Son wrote:

The first (Windows) Seamonkey which offered a 64-bit version 
officially was 2.49.5.  You have 2.49.1, so unless you downloaded an 
unofficial build from a different site - and I'm assuming you'd 
remember doing that - you have a 32-bit version.
That User Agent is a bit weird, I have looked up some old messages 
here and seen:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1


If you do update - download a 64-bit 2.53.3, uninstall your old 
Seamonkey, backup the profile and install the new one.


WOW64 is Windows-On-Windows 64. That is seen when a 32-bit version is 
installed on a 64-bit Windows OS. When I had 64-bit Windows 7 installed, 
SeaMonkey displayed that as the only SM versions at the time were 32-bit.


If a 64-bit version of Sea Monkey is installed on 64-bit Windows, the 
UserAgent will then show 'Win64' and 'x64'.



Which describes his user-agent quite accurately.
To repeat, the only "official" 2.49.1 version was 32-bit - see 
https://www.seamonkey-project.org/releases/2.49.1#official - but his 
user-agent says x64.  This implies an unofficial build, or a manipulated 
user-agent.  I'd go forwards as I suggested anyway - uninstall it before 
installing the current version.


--
spammo ergo sum, viruses courtesy of https://www.nsa.gov/malware/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: updates

[Edward]

Don Spam's Reckless Son wrote:

The first (Windows) Seamonkey which offered a 64-bit version officially 
was 2.49.5.  You have 2.49.1, so unless you downloaded an unofficial 
build from a different site - and I'm assuming you'd remember doing that 
- you have a 32-bit version.
That User Agent is a bit weird, I have looked up some old messages here 
and seen:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 
SeaMonkey/2.49.1
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1


If you do update - download a 64-bit 2.53.3, uninstall your old 
Seamonkey, backup the profile and install the new one.


WOW64 is Windows-On-Windows 64. That is seen when a 32-bit version is 
installed on a 64-bit Windows OS. When I had 64-bit Windows 7 installed, 
SeaMonkey displayed that as the only SM versions at the time were 32-bit.


If a 64-bit version of Sea Monkey is installed on 64-bit Windows, the 
UserAgent will then show 'Win64' and 'x64'.


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

Re: updates

[Don Spam's Reckless Son]

Ken Rudolph wrote:

Don Spam's Reckless Son wrote:

Ken Rudolph wrote:
After all these years (since Netscape 1.0) I've basically given up on 
the SeaMonkey browser, replacing it with Firefox.  However, out of 
habit and utility, I still use SeaMonkey 2.49.1 for e-mail and 
Composer for updating my web site (I have separate links to open only 
those portions of the suite).  This means when I click on an e-mail 
link it opens the SeaMonkey browser in a separate window...which is 
OK by me usually. More often I just ^C the link and then paste it in 
Firefox.


This is working fine for me.  I've always been scared in the past 
when I had to manually do a SeaMonkey version update.  It always did 
work; but I had nervous moments fearful that I'd lose my profile etc. 
Obviously I haven't updated SeaMonkey for a while now.  I see the 
current version is 2.53.3.  So here's my question.  In my situation, 
should I do the SeaMonkey update just for the e-mail and composer 
parts?  Would there be some major advantage to doing the update? 
Everything that I need to do with the SeaMonkey portions other than 
the browser itself is working fine.  Do I need to do the update to 
the entire suite for some reason?


Thank you for Mozilla, however I use it!!



You can't update "just the e-mail and composer parts", it is one 
program.  I have absolutely no idea which Thunderbird fixes have gone 
in since 2.49.1, very little has happened with composer.  Lightning is 
now included, it was not back then.
If you do upgrade - and I see no reason not to - there are a couple of 
things you need to worry about:
- Starting 2.49.5, Seamonkey comes in 32-bit and 64-bit versions.  If 
you are going to move to a 64-bit version, UNINSTALL THE OLD VERSION  
> BEFORE INSTALLING THE NEW ONE.  This is because installing a 64-bit
version will not remove a 32-bit version, something which can have 
fatal side-effects.


I'm not sure if I have the 32 or 64 bit version of SeaMonkey.  I do see 
this in "about":


User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) 
Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1


Does that x64 mean 64 bit version even if it is SM 2.49.1?

I've never worried about that in previous updates to SM.  But now you 
have me thinking that I better know whether to uninstall my current 
version (something that worries me) or not if it is the 32-bit version.


Thank you for the advice!



The first (Windows) Seamonkey which offered a 64-bit version officially 
was 2.49.5.  You have 2.49.1, so unless you downloaded an unofficial 
build from a different site - and I'm assuming you'd remember doing that 
- you have a 32-bit version.
That User Agent is a bit weird, I have looked up some old messages here 
and seen:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 
SeaMonkey/2.49.1
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1


If you do update - download a 64-bit 2.53.3, uninstall your old 
Seamonkey, backup the profile and install the new one.


--
spammo ergo sum, viruses courtesy of https://www.nsa.gov/malware/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: updates

[Ken Rudolph]

Don Spam's Reckless Son wrote:

Ken Rudolph wrote:
After all these years (since Netscape 1.0) I've basically given up on 
the SeaMonkey browser, replacing it with Firefox.  However, out of 
habit and utility, I still use SeaMonkey 2.49.1 for e-mail and 
Composer for updating my web site (I have separate links to open only 
those portions of the suite).  This means when I click on an e-mail 
link it opens the SeaMonkey browser in a separate window...which is OK 
by me usually. More often I just ^C the link and then paste it in 
Firefox.


This is working fine for me.  I've always been scared in the past when 
I had to manually do a SeaMonkey version update.  It always did work; 
but I had nervous moments fearful that I'd lose my profile etc.  
Obviously I haven't updated SeaMonkey for a while now.  I see the 
current version is 2.53.3.  So here's my question.  In my situation, 
should I do the SeaMonkey update just for the e-mail and composer 
parts?  Would there be some major advantage to doing the update?  
Everything that I need to do with the SeaMonkey portions other than 
the browser itself is working fine.  Do I need to do the update to the 
entire suite for some reason?


Thank you for Mozilla, however I use it!!



You can't update "just the e-mail and composer parts", it is one 
program.  I have absolutely no idea which Thunderbird fixes have gone in 
since 2.49.1, very little has happened with composer.  Lightning is now 
included, it was not back then.
If you do upgrade - and I see no reason not to - there are a couple of 
things you need to worry about:
- Starting 2.49.5, Seamonkey comes in 32-bit and 64-bit versions.  If 
you are going to move to a 64-bit version, UNINSTALL THE OLD VERSION  > BEFORE INSTALLING THE NEW ONE.  This is because installing a 64-bit
version will not remove a 32-bit version, something which can have fatal 
side-effects.


I'm not sure if I have the 32 or 64 bit version of SeaMonkey.  I do see 
this in "about":


User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) 
Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1


Does that x64 mean 64 bit version even if it is SM 2.49.1?

I've never worried about that in previous updates to SM.  But now you 
have me thinking that I better know whether to uninstall my current 
version (something that worries me) or not if it is the 32-bit version.


Thank you for the advice!

--
Ken Rudolph

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

updates

[Ken Rudolph]

After all these years (since Netscape 1.0) I've basically given up on 
the SeaMonkey browser, replacing it with Firefox.  However, out of habit 
and utility, I still use SeaMonkey 2.49.1 for e-mail and Composer for 
updating my web site (I have separate links to open only those portions 
of the suite).  This means when I click on an e-mail link it opens the 
SeaMonkey browser in a separate window...which is OK by me usually. 
More often I just ^C the link and then paste it in Firefox.


This is working fine for me.  I've always been scared in the past when I 
had to manually do a SeaMonkey version update.  It always did work; but 
I had nervous moments fearful that I'd lose my profile etc.  Obviously I 
haven't updated SeaMonkey for a while now.  I see the current version is 
2.53.3.  So here's my question.  In my situation, should I do the 
SeaMonkey update just for the e-mail and composer parts?  Would there be 
some major advantage to doing the update?  Everything that I need to do 
with the SeaMonkey portions other than the browser itself is working 
fine.  Do I need to do the update to the entire suite for some reason?


Thank you for Mozilla, however I use it!!

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

Re: UA String Updates - User Agent Switcher

[Rainer Bielefeld]

On 03.12.2019 21:53, Edward wrote:

Unfortunately, all of the User Agent switcher



Hallo,

did you already try "User Agent Switcher" from
https://seamonkeyde.wordpress.com/2019/01/09/classic-add-ons-archive/
after having it converted
https://wp.me/p7kLBG-dI
it for your SM version?

CU

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

Re: UA String Updates

[Daniel]

Ray_Net wrote on 6/12/2019 9:36 AM:

NFN Smith wrote on 04-12-19 23:14:

Ray_Net wrote:

NFN Smith wrote on 04-12-19 00:31:


It's definitely Google's problem.  Showing a stock Firefox UA gets 
around the problem. For some reason, Google doesn't like Seamonkey.


My U.A.String is: User agent: Mozilla/5.0 (Windows NT 10.0; WOW64; 
rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1

but in my pref.js I have this line:
user_pref("general.useragent.override.google.com", "Mozilla/5.0 
(Windows NT 6.1; WOW64; rv:67.0) Gecko/20100101 Firefox/67.0");

And all goes well .


Google has some strange dislike for seeing a Firefox UA string that 
also has "Seamonkey" in it.  I don't know why.  I haven't checked to 
see if that's an issue with other Mozilla forks, such as PaleMoon or 
WaterFox.


OK, so you will tell me that "SeaMonkey" is not in the string ... OK, 
but instead of going to google.com, I go to google.be all goes well 
also - and in that case "SeaMonkey" is in the string, because rhere 
is no override.


When you go the route of prefs, you have to do the spoof on a 
site-by-site basis.  Thus, if you are normally searching at google.be, 
then you need a similar entry for general.useragent.override.google.be .


As I said, this is a test - I don't have a similar entry so, my ua 
string is with seamonkey inside.

anyway, I don't know why it works on my pc and not on other pc's.


Not that it really matters but, a long time ago, I thought some sites 
tested for what browser was mentioned first in the User Agent string, 
whilst some sites tested for which browser was mentioned last in the UA 
string.


So "SeaMonkey Firefox" would work for some sites, whilst others needed 
"Firefox SeaMonkey"!!


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.5 Build identifier: 20190609032134

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

Re: UA String Updates

[Ray_Net]

NFN Smith wrote on 04-12-19 23:14:

Ray_Net wrote:

NFN Smith wrote on 04-12-19 00:31:





It's definitely Google's problem.  Showing a stock Firefox UA gets 
around the problem. For some reason, Google doesn't like Seamonkey.


My U.A.String is: User agent: Mozilla/5.0 (Windows NT 10.0; WOW64; 
rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1

but in my pref.js I have this line:
user_pref("general.useragent.override.google.com", "Mozilla/5.0 
(Windows NT 6.1; WOW64; rv:67.0) Gecko/20100101 Firefox/67.0");

And all goes well .


Google has some strange dislike for seeing a Firefox UA string that 
also has "Seamonkey" in it.  I don't know why.  I haven't checked to 
see if that's an issue with other Mozilla forks, such as PaleMoon or 
WaterFox.



OK, so you will tell me that "SeaMonkey" is not in the string ... OK, 
but instead of going to google.com, I go to google.be all goes well 
also - and in that case "SeaMonkey" is in the string, because rhere 
is no override.


When you go the route of prefs, you have to do the spoof on a 
site-by-site basis.  Thus, if you are normally searching at google.be, 
then you need a similar entry for general.useragent.override.google.be .




As I said, this is a test - I don't have a similar entry so, my ua 
string is with seamonkey inside.

anyway, I don't know why it works on my pc and not on other pc's.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: UA String Updates

[NFN Smith]

Ray_Net wrote:

NFN Smith wrote on 04-12-19 00:31:





It's definitely Google's problem.  Showing a stock Firefox UA gets 
around the problem. For some reason, Google doesn't like Seamonkey.


My U.A.String is: User agent: Mozilla/5.0 (Windows NT 10.0; WOW64; 
rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1

but in my pref.js I have this line:
user_pref("general.useragent.override.google.com", "Mozilla/5.0 (Windows 
NT 6.1; WOW64; rv:67.0) Gecko/20100101 Firefox/67.0");

And all goes well .


Google has some strange dislike for seeing a Firefox UA string that also 
has "Seamonkey" in it.  I don't know why.  I haven't checked to see if 
that's an issue with other Mozilla forks, such as PaleMoon or WaterFox.



OK, so you will tell me that "SeaMonkey" is not in the string ... OK, 
but instead of going to google.com, I go to google.be all goes well also 
- and in that case "SeaMonkey" is in the string, because rhere is no 
override.


When you go the route of prefs, you have to do the spoof on a 
site-by-site basis.  Thus, if you are normally searching at google.be, 
then you need a similar entry for general.useragent.override.google.be .


I don't think there's any way of specifying Google globally.  I could 
guess that showing just "google" rather than full top-level domain could 
work, but that's something you would have to test, and could be disruptive.


Smith

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

Re: UA String Updates

[Ray_Net]

NFN Smith wrote on 04-12-19 00:31:

Edward wrote:

NFN Smith wrote:

There's only a couple of sites that I regularly see that don't like 
the UA string for Seamonkey 2.49.5, especially Google's home page.  
Thus, rather than doing global spoofing, I went to prefs:js and set 
general.useragent.override.google.com to show a standard Firefox 
68.0 UA, while still showing the standard Seamonkey UA (including in 
the mail client) to the rest of the world.


I thought it was a bug in SM causing the Google home page to behave 
as it is, however was told it's the User Agent causing it.


It's definitely Google's problem.  Showing a stock Firefox UA gets 
around the problem. For some reason, Google doesn't like Seamonkey.


My U.A.String is: User agent: Mozilla/5.0 (Windows NT 10.0; WOW64; 
rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1

but in my pref.js I have this line:
user_pref("general.useragent.override.google.com", "Mozilla/5.0 (Windows 
NT 6.1; WOW64; rv:67.0) Gecko/20100101 Firefox/67.0");

And all goes well .
OK, so you will tell me that "SeaMonkey" is not in the string ... OK, 
but instead of going to google.com, I go to google.be all goes well also 
- and in that case "SeaMonkey" is in the string, because rhere is no 
override.

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

Re: UA String Updates

[NFN Smith]

Edward wrote:

NFN Smith wrote:

There's only a couple of sites that I regularly see that don't like 
the UA string for Seamonkey 2.49.5, especially Google's home page.  
Thus, rather than doing global spoofing, I went to prefs:js and set 
general.useragent.override.google.com to show a standard Firefox 68.0 
UA, while still showing the standard Seamonkey UA (including in the 
mail client) to the rest of the world.


I thought it was a bug in SM causing the Google home page to behave as 
it is, however was told it's the User Agent causing it.


It's definitely Google's problem.  Showing a stock Firefox UA gets 
around the problem. For some reason, Google doesn't like Seamonkey.




Unfortunately, all of the User Agent switcher Add-Ons for SeaMonkey, are 
not compatible with the latest SM version.


I run PrefBar in both 2.49.5 on my primary working profile, as well as 
2.53.1 in a virtual machine, and not having any problems, but PrefBar is 
nearly impossible to find, anymore.  The developer removed it from 
addons.mozilla.org, and it hasn't gotten into the git archive of legacy 
extensions.


I just checked, and User Agent Switcher is still in that archive.

As far as I'm aware, as long as Seamonkey continues to support XUL, all 
the old extensions should work.  And I believe that even 2.57 (which is 
based on Gecko 60) is intended to continue supporting XUL, even if 
WebExtensions are also supported.  However, reading the notes from the 
developers' meetings, it seems that we're a long way from seeing 2.57 
released.


Smith

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

Re: UA String Updates

[Ray_Net]

Thomas Pamin wrote on 03-12-19 13:50:
My UA String is Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) 
Gecko/20100101 Firefox/68.0.


Should the NT 6.1 be changed to NT 10.0 for Windows 10? Anything else 
I should update?


Mine is: User agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) 
Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1

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

Re: UA String Updates

[Edward]

NFN Smith wrote:

There's only a couple of sites that I regularly see that don't like the 
UA string for Seamonkey 2.49.5, especially Google's home page.  Thus, 
rather than doing global spoofing, I went to prefs:js and set 
general.useragent.override.google.com to show a standard Firefox 68.0 
UA, while still showing the standard Seamonkey UA (including in the mail 
client) to the rest of the world.


I thought it was a bug in SM causing the Google home page to behave as 
it is, however was told it's the User Agent causing it.


Unfortunately, all of the User Agent switcher Add-Ons for SeaMonkey, are 
not compatible with the latest SM version.



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

Re: UA String Updates

[NFN Smith]

Thomas Pamin wrote:
My UA String is Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) 
Gecko/20100101 Firefox/68.0.


It's certainly workable, although a stock Firefox 68 ESR on Win 7 will 
have "(Windows NT 6.1; Win64; x64; rv:68.0)" in it.  For compatibility 
purposes, it shouldn't make any difference, although what you currently 
have will show up in server logs as being different from a normal 
Firefox UA.


If you really want to verify, go out to portableapps.com, and grab the 
current version of Firefox ESR, then go to Help -> Troubleshooting 
Information.  (With a portable version you can download, launch, and do 
what you need, and then discard, without having to bother with uninstall 
or uninstall.)


Should the NT 6.1 be changed to NT 10.0 for Windows 10? Anything else I 
should update?


My installed copy of Firefox (just updated to 71.0) shows:

  Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 
Firefox/71.0


If you want to show Firefox 68 on Windows 10, you would want:

  Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 
Firefox/68.0


If you're doing spoofing for the purposes of getting around sites that 
are complaining about Seamonkey showing older versions of Firefox, most 
of the time, the only thing that you need is to show Firefox/68.0 at the 
end of the line. It's really unusual to see sites looking at other stuff 
in the UA. I've never seen it, but it probably happens occasionally.


A couple of additional considerations:

When you're spoofing the UA in Seamonkey, that applies to both what the 
browser shows to web sites, but it also turns up in the User-Agent: 
header in your email.  I run the old Display Mail User Agent extension 
(which shows a graphic in all received messages, of what UA the sender 
is using), and with that active, the message I'm replying to shows you 
using Firefox.  My use of that is uncommon, but it definitely stands out 
that you're spoofing, because Firefox doesn't send mail.


If you're sensitive about tracking by uniqueness, on that point, you 
*really* stand out, as much as you do by having a string that's not 
quite standard Firefox for your browsing.


If you don't want your spoofing to be as obvious, you might consider 
showing the string used by Seamonkey 2.53:


  Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 
Firefox/60.0 SeaMonkey/2.53.1


There's only a couple of sites that I regularly see that don't like the 
UA string for Seamonkey 2.49.5, especially Google's home page.  Thus, 
rather than doing global spoofing, I went to prefs:js and set 
general.useragent.override.google.com to show a standard Firefox 68.0 
UA, while still showing the standard Seamonkey UA (including in the mail 
client) to the rest of the world.


Smith

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

UA String Updates

[Thomas Pamin]

My UA String is Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) 
Gecko/20100101 Firefox/68.0.


Should the NT 6.1 be changed to NT 10.0 for Windows 10? Anything else I 
should update?

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

Re: Updates

[WaltS48]

On 5/18/19 12:06 PM, Luis wrote:

Almost one year without updating.


Thanks for the update. ;)

For up to date news see 



Might be time for a new blog post, but ewong is probably very busy 
getting the new infrastructure in shape.




--
OS: Ubuntu Linux 18.04LTS - Gnome Desktop
https://www.thunderbird.net/en-US/get-involved/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Updates

[Luis via support-seamonkey]

Almost one year without updating.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Is it me or are installed extensions not getting updates anymore?

[NFN Smith]

EE wrote:

Ant wrote:

I have these currently installed in my SeaMonkey v2.49.2 web browsers:
* ColorfulTabs 31.1.9 (http://www.addongenie.com/colorfultabs)
* DOM Inspector 2.0.16.1-signed 
(http://www.mozilla.org/projects/inspector/)

* Open With 6.8.6 (https://github.com/darktrojan/openwith)
* PrefBar 7.1.1 (http://prefbar.tuxfamily.org/)
* uBlock Origin 1.13.8 (https://github.com/gorhill/uBlock)

Is it because developers moved onto the new Gecko engine? :( Thank you 
in advnace. :)


I have not seen any updates in themes or extensions for over a year. The 
ones I have still work, however (I did have to add a certain file to my 
themes to get the mail compose window to work).



I've seen a few updates, by developers that are keeping their work going 
as long as Firefox 52.x ESR is still viable.


I have found that in the first couple of months after FF 57 was 
released, there were a few developers doing updates to both WebEx and 
XUL versions, particularly NoScript. I checked, and there's regular 
WebEx updates to NoScript, and it's now been several months since 
there's been an XUL update.


For PrefBar (and I've been enthusiastic about that one for years), if 
you go to the developer's page, it's explicit that that one is dead, and 
there will be no further updates.  The page does indicate that many of 
the functions (but not all) are replicated in various other WebEx 
extensions.


One of the things I did at the time of Firefox 56 is that I installed 
copies of both 56 as well as the beta of 57 (in separate install 
folders, and separate profiles). On 56, I installed all the extensions I 
follow, both for Firefox and for Seamonkey, so that I could see how they 
behave in transition from 56 to 57.  And in the beta (which I continue 
to keep active, now running 60.0 b4) I've been using that for testing, 
to see what WebEx offerings will do what I want.


With the 56 to 57 transition, I found that there were a handful of 
developers that allowed for automatic transition for XUL to WebEx 
versions. For other extensions, I found either new projects, or 
work-alike, and I've found that I can get WebEx to do most of what I 
want, although there's still a couple of things where I'm still 
evaluating options.  Thus, although Seamonkey is still some ways away 
from the transition to WebEx, I'm mostly comfortable with the options. 
The hard part, of course is going to be waiting until Seamonkey makes 
that transition.


For what it's worth, I'm doing the same kind of testing with 
Thunderbird, with a beta of 60.0. A check of Thunderbird documentation 
indicates that Thunderbird is not yet moving to WebEx -- and although TB 
60 will still be XUL based, existing extensions must have tweaking for 
explicit support of TB 60. Thus, if the extension hasn't been tweaked, 
it will not run in TB 60.  From my testing, I follow about 20 TB 
extensions, and in my beta installation, about 3/4 of those extensions 
are disabled because the current versions aren't (yet) updated for 60.


I'm not yet sure what the consequences of this development will be for 
Seamonkey.


I should note that do follow the meeting notes for the Seamonkey 
developers (latest agenda at 
https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2018-04-22), and it's 
a useful insight to see where things stand with development progress. I 
know that there is some interaction with the Thunderbird development 
group (beyond use of Thunderbird code for Seamonkey's mail client), 
including possible coordination between the two projects in shifting 
away from reliance on Mozilla infrastructure for hosting, and there's a 
bit of interaction there, as well, regarding coordinating of add-ons 
structure.


Smith

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

Re: Is it me or are installed extensions not getting updates anymore?

[Ant via support-seamonkey]

On 4/25/2018 11:54 PM, Mason83 wrote:

On 26/04/2018 04:18, Ant wrote:

I have these currently installed in my SeaMonkey v2.49.2 web browsers:
* ColorfulTabs 31.1.9 (http://www.addongenie.com/colorfultabs)
* DOM Inspector 2.0.16.1-signed (http://www.mozilla.org/projects/inspector/)
* Open With 6.8.6 (https://github.com/darktrojan/openwith)
* PrefBar 7.1.1 (http://prefbar.tuxfamily.org/)
* uBlock Origin 1.13.8 (https://github.com/gorhill/uBlock)

Is it because developers moved onto the new Gecko engine? :( Thank you
in advance. :)


SM 2.49 is based on FF 52 ESR.

FF 57 changed the addons APIs : XUL to Webextensions

https://en.wikipedia.org/wiki/XUL

All addons had to be rewritten, some authors just gave up.

Thus, new versions have switched to webext, which SM 2.49
does not support, so no upgrade.

If SM 2.54 or higher is ever released, we can use FF webext
addons again.


Thanks. That is what I thought. :(
--
"Maybe it's like an ant hive..." "Bees man, bees have hives." "You know 
what I mean. It's like one female that runs the whole show." "Yes, the 
queen." "Yeah the mamma. She is bad*ss, man. I mean big." "These things 
ain't ants estupido." "I know that." --Aliens movie
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\   Ant(Dude) @ Personal Web Site http://antfarm.ma.cx
  / /\ /\ \
 | |o   o| |  If crediting, then use Ant nickname and URL/link.
\ _ /  Axe ANT from its address if e-mailing privately.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Is it me or are installed extensions not getting updates anymore?

[EE]

Ant wrote:

I have these currently installed in my SeaMonkey v2.49.2 web browsers:
* ColorfulTabs 31.1.9 (http://www.addongenie.com/colorfultabs)
* DOM Inspector 2.0.16.1-signed 
(http://www.mozilla.org/projects/inspector/)

* Open With 6.8.6 (https://github.com/darktrojan/openwith)
* PrefBar 7.1.1 (http://prefbar.tuxfamily.org/)
* uBlock Origin 1.13.8 (https://github.com/gorhill/uBlock)

Is it because developers moved onto the new Gecko engine? :( Thank you 
in advnace. :)


I have not seen any updates in themes or extensions for over a year. 
The ones I have still work, however (I did have to add a certain file to 
my themes to get the mail compose window to work).

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

Re: Is it me or are installed extensions not getting updates anymore?

[Mason83]

On 26/04/2018 04:18, Ant wrote:
> I have these currently installed in my SeaMonkey v2.49.2 web browsers:
> * ColorfulTabs 31.1.9 (http://www.addongenie.com/colorfultabs)
> * DOM Inspector 2.0.16.1-signed (http://www.mozilla.org/projects/inspector/)
> * Open With 6.8.6 (https://github.com/darktrojan/openwith)
> * PrefBar 7.1.1 (http://prefbar.tuxfamily.org/)
> * uBlock Origin 1.13.8 (https://github.com/gorhill/uBlock)
> 
> Is it because developers moved onto the new Gecko engine? :( Thank you 
> in advance. :)

SM 2.49 is based on FF 52 ESR.

FF 57 changed the addons APIs : XUL to Webextensions

https://en.wikipedia.org/wiki/XUL

All addons had to be rewritten, some authors just gave up.

Thus, new versions have switched to webext, which SM 2.49
does not support, so no upgrade.

If SM 2.54 or higher is ever released, we can use FF webext
addons again.

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

Is it me or are installed extensions not getting updates anymore?

[Ant via support-seamonkey]

I have these currently installed in my SeaMonkey v2.49.2 web browsers:
* ColorfulTabs 31.1.9 (http://www.addongenie.com/colorfultabs)
* DOM Inspector 2.0.16.1-signed (http://www.mozilla.org/projects/inspector/)
* Open With 6.8.6 (https://github.com/darktrojan/openwith)
* PrefBar 7.1.1 (http://prefbar.tuxfamily.org/)
* uBlock Origin 1.13.8 (https://github.com/gorhill/uBlock)

Is it because developers moved onto the new Gecko engine? :( Thank you 
in advnace. :)

--
"The great companies did not know that the line between hunger and anger 
is a thin line. And money that might have gone to wages went for gas, 
for guns, for agents and spies, for blacklists, for drilling. On the 
highways the people moved like ants and searched for work, for food. And 
the anger began to ferment." --John Steinbeck's The Grapes of Wrath
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\   Ant(Dude) @ Personal Web Site http://antfarm.ma.cx
  / /\ /\ \
 | |o   o| |  If crediting, then use Ant nickname and URL/link.
\ _ /  Axe ANT from its address if e-mailing privately.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Issue With Automatic updates and Avast Antivirus

[Ken Kellaher]

We use Avast antivirus and Seamonkey on a few PCs.

It seems a few month ago we started having a problem with Seamonkey not 
being

able to automatically update.  It states it is being blocked.

On one computer Avast is a paid version with the firewall, one computer 
is the free version with

windows firewall.

I contacted Avast and they had me try a few things with Avast... that 
appeared to work for a few days.
The problem appears to be with their Webshield, because when I shut it 
down I have no problems

looking for updates on Seamonkey.

When I contacted Avast again, they suggested contacting you.

Have you heard of this before, is there a solution?   Is there something 
you can help with?



Thank you,

Ken Kellaher

SSHC, Inc.
Westbrook, CT 06498

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

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

Re: Download installer from downloads section, re. updates

[Mort Linder]

Hi Walt,

Thanks a lot for your reassuring reply.

Happy New Year,

Mort



WaltS48 wrote:

On 1/4/18 11:07 AM, Mort Linder wrote:

Hi,

I keep getting an announcement in red letters that I will not get 
SeaMonkey updates,and that I must download the full installer from the 
downloads section. I tried every which way, and keep getting that red 
announcement. I am running Windows 7 Prof. 64 bit.


 How may I get the proper download that will allow me to receive updates?

Thanks,

Mort Linder





You already have the most recent version with SM 2.49.1.

When the SeaMonkey developers fix the updating problem, updates should 
work again.






---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

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

Re: Download installer from downloads section, re. updates

[WaltS48]

On 1/4/18 11:07 AM, Mort Linder wrote:

Hi,

I keep getting an announcement in red letters that I will not get 
SeaMonkey updates,and that I must download the full installer from the 
downloads section. I tried every which way, and keep getting that red 
announcement. I am running Windows 7 Prof. 64 bit.


 How may I get the proper download that will allow me to receive updates?

Thanks,

Mort Linder





You already have the most recent version with SM 2.49.1.

When the SeaMonkey developers fix the updating problem, updates should 
work again.



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

Download installer from downloads section, re. updates

[Mort Linder]

Hi,

I keep getting an announcement in red letters that I will not get 
SeaMonkey updates,and that I must download the full installer from the 
downloads section. I tried every which way, and keep getting that red 
announcement. I am running Windows 7 Prof. 64 bit.


 How may I get the proper download that will allow me to receive updates?

Thanks,

Mort Linder

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

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

Re: Ref Seamonkey Updates

[Lee]

Thanks for your replies, I did know it was up to date but I kept getting 
that warning I showed below.I just wondered if it needed correcting and 
if yes how to do it.  Thanks

again!

> Up date XML File malformed (200)

Lee wrote:

I get the following when I check for updates, any info would be
appreciated.

Software updates

There were problems checking or, downloading, or installling this update
SeaMonkey could not be upgraded because

Up date XML File malformed (200)

Can I correct this?, is there someplace to get the file and where do I
put it.

Thanks!


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

Re: Ref Seamonkey Updates

[Danny Kile]

Lee wrote:

I get the following when I check for updates, any info would be
appreciated.

Software updates

There were problems checking or, downloading, or installling this update
SeaMonkey could not be upgraded because

Up date XML File malformed (200)

Can I correct this?, is there someplace to get the file and where do I
put it.

Thanks!


You could click on Help > About SeaMonkey, this will bring up an About 
Page showing the version you are running. You can click on the SeaMonkey 
logo on this page and it will take you to a download page this will be 
the latest version and you can download in manually.

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

Re: Ref Seamonkey Updates

[WaltS48]

On 4/19/17 10:41 AM, Lee wrote:
I get the following when I check for updates, any info would be 
appreciated.


Software updates

There were problems checking or, downloading, or installling this update
SeaMonkey could not be upgraded because

Up date XML File malformed (200)

Can I correct this?, is there someplace to get the file and where do I 
put it.


Thanks!



SeaMonkey 2.46 is the latest version.

To what version are you trying to update?

--
Go Bucs and Pens!
Coexist <https://www.coexist.org/>
National Popular Vote <http://www.nationalpopularvote.com/>
Ubuntu 16.04LTS

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

Ref Seamonkey Updates

[Lee]

I get the following when I check for updates, any info would be appreciated.

Software updates

There were problems checking or, downloading, or installling this update
SeaMonkey could not be upgraded because

Up date XML File malformed (200)

Can I correct this?, is there someplace to get the file and where do I 
put it.


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

Re: 2.46 Automatically Updates, Breaks Mac OS 10.6.8

[Paul B. Gallagher]

EE wrote:


Disable automatic updating.  In Preferences > Advanced > Software
Installation, under "SeaMonkey" uncheck "Automatically check for
updates".


Not the same thing.

Checking for updates and notifying the user doesn't install anything.

If you want to disable automatic updating, the box to uncheck is 
"Automatically download and install the update."


I concur that wel-behaved installers should check system requirements, 
compatibility, etc. before running. In the real world, developers can't 
think of everything. And the older the user's HW and SW, the more 
initiative he/she should take in this area.


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

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

Re: 2.46 Automatically Updates, Breaks Mac OS 10.6.8

[EE]

Jonathan N. Little wrote:

accordiong...@gmail.com wrote:

This thread has gone in the wrong direction, as it is focusing on whether or 
not I have backed up my profile data.


No you seem to be missing the point. You did not need to create a new
profile and "lose" your data just by uninstalling SeaMonkey and
reinstalling the previous version.

The issue of backing up is just a given! One should always have a backup
strategy. And since the downgrade does not corrupt your whole profile,
only the very limited scope of your browsing history, I mentioned how
your could restore most of that with your backup.


The original (and more important) question is -- is "shouldn't SeaMonkey check 
System Requirements before automatically updating?"



I thought it did. Folks have posted issues where the newest version
would not install on Windows with CPUs sans SSE2. Maybe this is a Mac
quirk...

Disable automatic updating.  In Preferences > Advanced > Software 
Installation, under "SeaMonkey" uncheck "Automatically check for updates".


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

Re: 2.46 Automatically Updates, Breaks Mac OS 10.6.8

[cyberzen]

Le 31/12/2016 à 18:44, WaltS48 a écrit :

Some of us clear browsing history on shutdown.


I do

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

Re: 2.46 Automatically Updates, Breaks Mac OS 10.6.8

[Jonathan N. Little]

accordiong...@gmail.com wrote:
> This thread has gone in the wrong direction, as it is focusing on whether or 
> not I have backed up my profile data.
>
No you seem to be missing the point. You did not need to create a new
profile and "lose" your data just by uninstalling SeaMonkey and
reinstalling the previous version.

The issue of backing up is just a given! One should always have a backup
strategy. And since the downgrade does not corrupt your whole profile,
only the very limited scope of your browsing history, I mentioned how
your could restore most of that with your backup.

> The original (and more important) question is -- is "shouldn't SeaMonkey 
> check System Requirements before automatically updating?"
> 

I thought it did. Folks have posted issues where the newest version
would not install on Windows with CPUs sans SSE2. Maybe this is a Mac
quirk...

-- 
Take care,

Jonathan
---
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 2.46 Automatically Updates, Breaks Mac OS 10.6.8

[accordiongirl]

This thread has gone in the wrong direction, as it is focusing on whether or 
not I have backed up my profile data.

The original (and more important) question is -- is "shouldn't SeaMonkey check 
System Requirements before automatically updating?"

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

Re: 2.46 Automatically Updates, Breaks Mac OS 10.6.8

[Jonathan N. Little]

accordiong...@gmail.com wrote:
> The profile was crippled by SeaMonkey.  Here is a description of this issue 
> from the 2.46 Release Notes.
> 
> "Data loss warning: If you use a profile with this or any later version and 
> then try to go back to SeaMonkey 2.40 or earlier, SeaMonkey will rename your 
> history file to places.sqlite.corrupt and create a new places.sqlite file, 
> effectively resetting your browsing history."
> 
> To avoid all of this, it would be beneficial if SeaMonkey could check System 
> Requirements before automatically updating.
> 

To expand on what Walt said, you will only lose your history[1], but you
can restore all your other settings such as save passwords, site
permissions, browsing preferences, and all your mail accounts with data
if POP! Hardly crippling your profile!

[1]If you had any decent backup, you could restore your places.sqlite db
file from backup before you upgraded. Then you would only lose the
history since that backup.

-- 
Take care,

Jonathan
---
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 2.46 Automatically Updates, Breaks Mac OS 10.6.8

[WaltS48]

On 12/31/2016 12:32 PM, accordiong...@gmail.com wrote:

The profile was crippled by SeaMonkey.  Here is a description of this issue 
from the 2.46 Release Notes.

"Data loss warning: If you use a profile with this or any later version and then try 
to go back to SeaMonkey 2.40 or earlier, SeaMonkey will rename your history file to 
places.sqlite.corrupt and create a new places.sqlite file, effectively resetting your 
browsing history."

To avoid all of this, it would be beneficial if SeaMonkey could check System 
Requirements before automatically updating.


So, you start creating new browsing history.

If you didn't bookmark important sites to you, then that is your mistake.

Some of us clear browsing history on shutdown.


--
Visit Pittsburgh 
Coexist 
Ubuntu 16.04LTS

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

Re: 2.46 Automatically Updates, Breaks Mac OS 10.6.8

[accordiongirl]

The profile was crippled by SeaMonkey.  Here is a description of this issue 
from the 2.46 Release Notes.

"Data loss warning: If you use a profile with this or any later version and 
then try to go back to SeaMonkey 2.40 or earlier, SeaMonkey will rename your 
history file to places.sqlite.corrupt and create a new places.sqlite file, 
effectively resetting your browsing history."

To avoid all of this, it would be beneficial if SeaMonkey could check System 
Requirements before automatically updating.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 2.46 Automatically Updates, Breaks Mac OS 10.6.8

[Jonathan N. Little]

accordiong...@gmail.com wrote:
> SeaMonkey 2.46 has automatically updated itself on my computer running Mac OS 
> 10.6.8.
> 
> This update is not compatible (it requires Mac OS 10.9), and therefore does 
> not run.
> 
> It also cripples my profile.
> 
> And so now I must re-install 2.40, and start over with a new profile.
> 
> Shouldn't SeaMonkey check System Requirements before automatically updating ?
> 

What did you need to create a new profile? The profile and the
application are separate. Just uninstall SeaMonkey and reinstall with
previous version to rollback.

So now you should run profile manager to select your previous profile to
get you stuff back.

-- 
Take care,

Jonathan
---
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

2.46 Automatically Updates, Breaks Mac OS 10.6.8

[accordiongirl]

SeaMonkey 2.46 has automatically updated itself on my computer running Mac OS 
10.6.8.

This update is not compatible (it requires Mac OS 10.9), and therefore does not 
run.

It also cripples my profile.

And so now I must re-install 2.40, and start over with a new profile.

Shouldn't SeaMonkey check System Requirements before automatically updating ?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[pthf1nd3r]

On Saturday, November 19, 2016 at 9:52:07 AM UTC-7, Chris Ilias wrote:
> On 2016-11-17 2:16 AM, pth@gmail.com wrote:
> 
> > My impression is that the microsoft November update rollup makes seamonkey 
> > 2.46 for windows 7 x32 crash.
> 
> Does the Mozilla Crash Reporter come up? If not, it could be because 
> you're not using an official release. If it does,
> 1. Open SeaMonkey.
> 2. Go to Help-->Troubleshooting_Information. That should open a new tab 
> with info about your SeaMonkey setup.
> 3. Under "Crash Reports for the Last 3 Days" click on your latest crash 
> report. That should take you to a web page starting with 
> "https://crash-stats.mozilla.com/report/index/;
> 4. Open a reply to this post and paste the address of your latest crash 
> report.
> We can then look at the data specific to your crash and have a better 
> idea of what is causing the problem.
> 
> -- 
> Chris Ilias 
> Newsgroup moderator

haven't used an official release for awhile now, please see original post in 
this thread/topic for partial explanation. crash occurred using Seamonkey 2.44 
or 2.46 after installing KB3197868. Problem solved by not installing KB3197868, 
and installing KB3197867 instead. now using Seamonkey 2.47 with no problems at 
all.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[pthf1nd3r]

On Friday, November 18, 2016 at 10:15:05 AM UTC-7, Frank-Rainer Grahl wrote:
> ...
> What I meant with crashing the browser is the Windows telemetry which 
> came standard with Windows 10 and is now rolled out by Microsoft for 7 
> and 8.1 users. It can not be disabled but you can uninstall it. 
> Microsoft makes it harder every month to get rid if it. For Windows 7 
> they pushed it with a normal security update KB3197868. You need to 
> deinstall this one and install KB3197867 to get rid of it. If you have a 
> windows\systen32\diagtrack.dll your are infected by it. Slows down the 
> PC especially during logon and transmits sensitive data to MS.
> 
> FRG
> 
this is almost exactly what I did to fix the crashing problem, except I 
reverted to a system backup from before installing KB3107868, then installed 
KB3197867, the "security only" November update rollup for Windows 7. Then I 
installed Seamonkey 2.47  - Seamonkey is not crashing anymore.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[pthf1nd3r]

On Friday, November 18, 2016 at 10:15:05 AM UTC-7, Frank-Rainer Grahl wrote:
>
> 
> What I meant with crashing the browser is the Windows telemetry which 
> came standard with Windows 10 and is now rolled out by Microsoft for 7 
> and 8.1 users. It can not be disabled but you can uninstall it. 
> Microsoft makes it harder every month to get rid if it. For Windows 7 
> they pushed it with a normal security update KB3197868. You need to 
> deinstall this one and install KB3197867 to get rid of it. If you have a 
> windows\systen32\diagtrack.dll your are infected by it. Slows down the 
> PC especially during logon and transmits sensitive data to MS.
> 
> FRG
> 
this is almost exactly what I did to fix the crashing problem, except I 
reverted to a system backup from before installing KB3107868, then installed 
KB3197867, the "security only" November update rollup for Windows 7.. No more 
crashing Seaqmonkey. !!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[Chris Ilias]

On 2016-11-17 2:16 AM, pthf1n...@gmail.com wrote:


My impression is that the microsoft November update rollup makes seamonkey 2.46 
for windows 7 x32 crash.


Does the Mozilla Crash Reporter come up? If not, it could be because 
you're not using an official release. If it does,

1. Open SeaMonkey.
2. Go to Help-->Troubleshooting_Information. That should open a new tab 
with info about your SeaMonkey setup.
3. Under "Crash Reports for the Last 3 Days" click on your latest crash 
report. That should take you to a web page starting with 
"https://crash-stats.mozilla.com/report/index/;
4. Open a reply to this post and paste the address of your latest crash 
report.
We can then look at the data specific to your crash and have a better 
idea of what is causing the problem.


--
Chris Ilias 
Newsgroup moderator
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[Ed Mullen]

On 11/19/2016 at 3:26 AM, Frank-Rainer Grahl's prodigious digits fired off:

Yes but the Windows update catalog is different. If you want to actually
get a kb from it you need to use an MS browser. And KB3197867 for
Windows 7 or KB3197873 for 8.1 are only available there.

FRG

Ed Mullen wrote:


You do NOT need to use IE or Edge to view Knowledge Base atricles.

Just Google the KB number and you can get to it.






Nope, you're still wrong.

Using Firefox:

1.  Google the KB number
2.  Click first link
3.  Scroll down to How to obtain and install ...
4.  Click first link to go to the update catalog
5.  Click the download buttons

--
Ed Mullen
http://edmullen.net/
Do infants enjoy infancy as much as adults enjoy adultery?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[Frank-Rainer Grahl]

You can't do a thing about it in Windows 10. Spying is build so deeply 
into it it can not be removed. Using the privacy options will not fully 
disable it. And it gets worse with every release.
You can hack it but with the Anniversary edition I gave up and just 
wiped the vm. When my other older TH2 vm autoupdates one day I will wipe 
it too.


You would need 10 Enterprise to turn it off.

FRG

Ray_Net wrote:

Frank-Rainer Grahl wrote on 18-11-16 18:14:
Submitting telemetry data is disabled by default in SeaMonkey. 
Telemetry itself is so woven into the gecko engine that you will see 
fragments of it even when disabled. But no data is transmitted.


What I meant with crashing the browser is the Windows telemetry which 
came standard with Windows 10 and is now rolled out by Microsoft for 7 
and 8.1 users. It can not be disabled but you can uninstall it. 
Microsoft makes it harder every month to get rid if it. For Windows 7 
they pushed it with a normal security update KB3197868. You need to 
deinstall this one and install KB3197867 to get rid of it. If you have 
a windows\systen32\diagtrack.dll your are infected by it. Slows down 
the PC especially during logon and transmits sensitive data to MS.
Under my windows10 pro 64bits I have this 
"windows\systen32\diagtrack.dl" So what to do ?


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

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[Frank-Rainer Grahl]

Yes but the Windows update catalog is different. If you want to actually 
get a kb from it you need to use an MS browser. And KB3197867 for 
Windows 7 or KB3197873 for 8.1 are only available there.


FRG

Ed Mullen wrote:


You do NOT need to use IE or Edge to view Knowledge Base atricles.

Just Google the KB number and you can get to it.




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

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[Ray_Net]

Frank-Rainer Grahl wrote on 18-11-16 18:14:
Submitting telemetry data is disabled by default in SeaMonkey. 
Telemetry itself is so woven into the gecko engine that you will see 
fragments of it even when disabled. But no data is transmitted.


What I meant with crashing the browser is the Windows telemetry which 
came standard with Windows 10 and is now rolled out by Microsoft for 7 
and 8.1 users. It can not be disabled but you can uninstall it. 
Microsoft makes it harder every month to get rid if it. For Windows 7 
they pushed it with a normal security update KB3197868. You need to 
deinstall this one and install KB3197867 to get rid of it. If you have 
a windows\systen32\diagtrack.dll your are infected by it. Slows down 
the PC especially during logon and transmits sensitive data to MS.
Under my windows10 pro 64bits I have this 
"windows\systen32\diagtrack.dl" So what to do ?

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

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[Ed Mullen]

On 11/18/2016 at 12:35 PM, Larry S.'s prodigious digits fired off:

So how do I get KB3197867? In Windows Update Catalog I get a brief flash
of the content, then "There is a problem with this site" (or
equivalent). No way to get at the download.

Advice greatly appreciated.

Larry S.


Just Google the KB number then click the first link.

--
Ed Mullen
http://edmullen.net/
Beauty is in the eye of the beer holder.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[Ed Mullen]

On 11/18/2016 at 12:43 PM, Frank-Rainer Grahl's prodigious digits fired off:

You need to use IE. Also close all other browsers. AS siad they make it
hard to get rid of this...

FRG

Larry S. wrote:

Frank-Rainer Grahl wrote:

Submitting telemetry data is disabled by default in SeaMonkey. Telemetry
itself is so woven into the gecko engine that you will see fragments of
it even when disabled. But no data is transmitted.

What I meant with crashing the browser is the Windows telemetry which
came standard with Windows 10 and is now rolled out by Microsoft for 7
and 8.1 users. It can not be disabled but you can uninstall it.
Microsoft makes it harder every month to get rid if it. For Windows 7
they pushed it with a normal security update KB3197868. You need to
deinstall this one and install KB3197867 to get rid of it. If you have a
windows\systen32\diagtrack.dll your are infected by it. Slows down the
PC especially during logon and transmits sensitive data to MS.

FRG


So how do I get KB3197867? In Windows Update Catalog I get a brief
flash of the content, then "There is a problem with this site" (or
equivalent). No way to get at the download.

Advice greatly appreciated.

Larry S.




You do NOT need to use IE or Edge to view Knowledge Base atricles.

Just Google the KB number and you can get to it.


--
Ed Mullen
http://edmullen.net/
If you think nobody cares about you, try missing a couple of payments.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[EE]

Ray_Net wrote:

EE wrote on 17-11-16 19:56:

Frank-Rainer Grahl wrote:

Works fine fro me in x86 and x64 with 2.46 and 2.47. The latest Windows
7 update includes telemetry by default and I have seen at least one
report were this crashed the browser. Monst/any problems you will have
with SeaMonkey you will likely also have with Firefox. Same Engine.


You can disable telemetry.  In about:config, set
"toolkit.telemetry.enabled" to false.


I have this option set by default to false ... but someone could explain
me what is the following option ?
toolkit.telemetry.previousBuildID "user set" "string" 20140203230027


I have no idea.  It looks like a date and time code.  If telemetry 
enabled is set to false, it should not happen anyway.  Just to make 
sure, I blanked the URL setting as well, but that should not really be 
necessary.


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

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[Frank-Rainer Grahl]

You need to use IE. Also close all other browsers. AS siad they make it 
hard to get rid of this...


FRG

Larry S. wrote:

Frank-Rainer Grahl wrote:

Submitting telemetry data is disabled by default in SeaMonkey. Telemetry
itself is so woven into the gecko engine that you will see fragments of
it even when disabled. But no data is transmitted.

What I meant with crashing the browser is the Windows telemetry which
came standard with Windows 10 and is now rolled out by Microsoft for 7
and 8.1 users. It can not be disabled but you can uninstall it.
Microsoft makes it harder every month to get rid if it. For Windows 7
they pushed it with a normal security update KB3197868. You need to
deinstall this one and install KB3197867 to get rid of it. If you have a
windows\systen32\diagtrack.dll your are infected by it. Slows down the
PC especially during logon and transmits sensitive data to MS.

FRG

So how do I get KB3197867? In Windows Update Catalog I get a brief flash 
of the content, then "There is a problem with this site" (or 
equivalent). No way to get at the download.


Advice greatly appreciated.

Larry S.


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

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[Larry S.]

Frank-Rainer Grahl wrote:

Submitting telemetry data is disabled by default in SeaMonkey. Telemetry
itself is so woven into the gecko engine that you will see fragments of
it even when disabled. But no data is transmitted.

What I meant with crashing the browser is the Windows telemetry which
came standard with Windows 10 and is now rolled out by Microsoft for 7
and 8.1 users. It can not be disabled but you can uninstall it.
Microsoft makes it harder every month to get rid if it. For Windows 7
they pushed it with a normal security update KB3197868. You need to
deinstall this one and install KB3197867 to get rid of it. If you have a
windows\systen32\diagtrack.dll your are infected by it. Slows down the
PC especially during logon and transmits sensitive data to MS.

FRG

Ray_Net wrote:

EE wrote on 17-11-16 19:56:

Frank-Rainer Grahl wrote:

Works fine fro me in x86 and x64 with 2.46 and 2.47. The latest Windows
7 update includes telemetry by default and I have seen at least one
report were this crashed the browser. Monst/any problems you will have
with SeaMonkey you will likely also have with Firefox. Same Engine.


You can disable telemetry.  In about:config, set
"toolkit.telemetry.enabled" to false.


I have this option set by default to false ... but someone could
explain me what is the following option ?
toolkit.telemetry.previousBuildID "user set" "string" 20140203230027


So how do I get KB3197867? In Windows Update Catalog I get a brief flash 
of the content, then "There is a problem with this site" (or 
equivalent). No way to get at the download.


Advice greatly appreciated.

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

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[Frank-Rainer Grahl]

Submitting telemetry data is disabled by default in SeaMonkey. Telemetry 
itself is so woven into the gecko engine that you will see fragments of 
it even when disabled. But no data is transmitted.


What I meant with crashing the browser is the Windows telemetry which 
came standard with Windows 10 and is now rolled out by Microsoft for 7 
and 8.1 users. It can not be disabled but you can uninstall it. 
Microsoft makes it harder every month to get rid if it. For Windows 7 
they pushed it with a normal security update KB3197868. You need to 
deinstall this one and install KB3197867 to get rid of it. If you have a 
windows\systen32\diagtrack.dll your are infected by it. Slows down the 
PC especially during logon and transmits sensitive data to MS.


FRG

Ray_Net wrote:

EE wrote on 17-11-16 19:56:

Frank-Rainer Grahl wrote:

Works fine fro me in x86 and x64 with 2.46 and 2.47. The latest Windows
7 update includes telemetry by default and I have seen at least one
report were this crashed the browser. Monst/any problems you will have
with SeaMonkey you will likely also have with Firefox. Same Engine.


You can disable telemetry.  In about:config, set 
"toolkit.telemetry.enabled" to false.


I have this option set by default to false ... but someone could explain 
me what is the following option ?

toolkit.telemetry.previousBuildID "user set" "string" 20140203230027


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

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[pthf1nd3r]

On Thursday, November 17, 2016 at 1:27:07 AM UTC-7, Frank-Rainer Grahl wrote:
> > could anyone explain in plain english, what is happening with Seamonkey for 
> > windows 7 ? Please?
> >
> We are having build problesmw which delayed the next release for a few 
> weeks now. They are in the process of being fixed but it takes time and 
> the devs are all volunters which have a life. For Windows and Linux you 
> can use Adrians unofficial builds which are almost identical to any 
> official build which will be released. Bug reports against these are 
> supported.
> 
> > Is it really time to head over to Firefox and just learn how to use it and 
> > customize it, or is there any hope that seamonkey will be an ongoing 
> > project anything like it used to be?
> >
> 
> Not at this time unless you want to.
> 
> > And what links if any are currently available if we want to stay with 
> > seamonkey and try out current builds at our own peril. Not only that, but 
> > what version or build to look for in the links?
> >
> 
> For Windows x86 pick 2.46 from here:
> 
> https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/
> 
> > My impression is that the microsoft November update rollup makes seamonkey 
> > 2.46 for windows 7 x32 crash.
> 
> Works fine fro me in x86 and x64 with 2.46 and 2.47. The latest Windows 
> 7 update includes telemetry by default and I have seen at least one 
> report were this crashed the browser. Monst/any problems you will have 
> with SeaMonkey you will likely also have with Firefox. Same Engine.
> 
> FRG

to FRG, thank you for answering my questions. for the outsider, there is so 
much mystery about all this.
K
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[Ray_Net]

EE wrote on 17-11-16 19:56:

Frank-Rainer Grahl wrote:

Works fine fro me in x86 and x64 with 2.46 and 2.47. The latest Windows
7 update includes telemetry by default and I have seen at least one
report were this crashed the browser. Monst/any problems you will have
with SeaMonkey you will likely also have with Firefox. Same Engine.


You can disable telemetry.  In about:config, set 
"toolkit.telemetry.enabled" to false.


I have this option set by default to false ... but someone could explain 
me what is the following option ?

toolkit.telemetry.previousBuildID "user set" "string" 20140203230027
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[Pat Connors]

Curious, will version also work on Windows 10 in x64?

For Windows x86 pick 2.46 from here:

https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/ 



My impression is that the microsoft November update rollup makes 
seamonkey 2.46 for windows 7 x32 crash.


Works fine fro me in x86 and x64 with 2.46 and 2.47. The latest 
Windows 7 update includes telemetry by default and I have seen at 
least one report were this crashed the browser. Monst/any problems you 
will have with SeaMonkey you will likely also have with Firefox. Same 
Engine.



--
Pat Connors
http://www.connorsgenealogy.com

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

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[EE]

Frank-Rainer Grahl wrote:

Works fine fro me in x86 and x64 with 2.46 and 2.47. The latest Windows
7 update includes telemetry by default and I have seen at least one
report were this crashed the browser. Monst/any problems you will have
with SeaMonkey you will likely also have with Firefox. Same Engine.


You can disable telemetry.  In about:config, set 
"toolkit.telemetry.enabled" to false.


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

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[Frank-Rainer Grahl]

could anyone explain in plain english, what is happening with Seamonkey for 
windows 7 ? Please?

We are having build problesmw which delayed the next release for a few 
weeks now. They are in the process of being fixed but it takes time and 
the devs are all volunters which have a life. For Windows and Linux you 
can use Adrians unofficial builds which are almost identical to any 
official build which will be released. Bug reports against these are 
supported.



Is it really time to head over to Firefox and just learn how to use it and 
customize it, or is there any hope that seamonkey will be an ongoing project 
anything like it used to be?



Not at this time unless you want to.


And what links if any are currently available if we want to stay with seamonkey 
and try out current builds at our own peril. Not only that, but what version or 
build to look for in the links?



For Windows x86 pick 2.46 from here:

https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/


My impression is that the microsoft November update rollup makes seamonkey 2.46 
for windows 7 x32 crash.


Works fine fro me in x86 and x64 with 2.46 and 2.47. The latest Windows 
7 update includes telemetry by default and I have seen at least one 
report were this crashed the browser. Monst/any problems you will have 
with SeaMonkey you will likely also have with Firefox. Same Engine.


FRG


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

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[Gérard]

On 11/17/2016 08:16 AM, pthf1n...@gmail.com wrote:

On Tuesday, June 21, 2016 at 5:18:49 PM UTC-6, pthf...@gmail.com wrote:

SeaMonkey continues to have some issues,

for example, often when I hit the browser's Back button to go to previous 
webpage, nothing happens. Very frequent.

Is 2.40 the final version, or will there be future updates?

I really don't want to switch to another browser, but it definitely appears 
obvious that Seamonkey doesn't get updated much at all anymore.

Any word on this?
thank you.

long time Mozilla/Seamonkey user, K.


could anyone explain in plain english, what is happening with Seamonkey for 
windows 7 ? Please?

Is it really time to head over to Firefox and just learn how to use it and 
customize it, or is there any hope that seamonkey will be an ongoing project 
anything like it used to be?

And what links if any are currently available if we want to stay with seamonkey 
and try out current builds at our own peril. Not only that, but what version or 
build to look for in the links?

My impression is that the microsoft November update rollup makes seamonkey 2.46 
for windows 7 x32 crash.

thank you to anyone who can shed more light on this.
long time Mozilla/Seamonkey user, K.



do you use windhoos 7 version 2
then you should upgrade to version3
(then you have to have a microsoft licens)

sincerely,

--
Gérard Vinkesteijn-Rudersdorff
http://ciudadpatricia.com
https://facebook.com/gerardjan.vinkesteijn.7

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 
SeaMonkey/2.48a2

Build identifier: 20160923081035

To code the impossible code,This is my quest --
To bring up a virgin machine,   To debug that code,
To pop out of endless recursion,No matter how hopeless,
To grok what appears on the screen, No matter the load,
To write those routines
To right the unrightable bug,   Without question or pause,
To endlessly twiddle and thrash,To be willing to hack FORTRAN IV
To mount the unmountable magtape,   For a heavenly cause.
To stop the unstoppable crash!  And I know if I'll only be true
To this glorious quest,
And the queue will be better for this,  That my code will run CUSPy and calm,
That one man, scorned and   When it's put to the test.
destined to lose,
Still strove with his last allocation
To scrap the unscrappable kludge!
  -- To "The Impossible Dream", from Man of La Mancha
[gérard@gershwin] $
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

[pthf1nd3r]

On Tuesday, June 21, 2016 at 5:18:49 PM UTC-6, pthf...@gmail.com wrote:
> SeaMonkey continues to have some issues,
>  
> for example, often when I hit the browser's Back button to go to previous 
> webpage, nothing happens. Very frequent.
> 
> Is 2.40 the final version, or will there be future updates?
> 
> I really don't want to switch to another browser, but it definitely appears 
> obvious that Seamonkey doesn't get updated much at all anymore.
> 
> Any word on this?
> thank you.
> 
> long time Mozilla/Seamonkey user, K.

could anyone explain in plain english, what is happening with Seamonkey for 
windows 7 ? Please?

Is it really time to head over to Firefox and just learn how to use it and 
customize it, or is there any hope that seamonkey will be an ongoing project 
anything like it used to be? 

And what links if any are currently available if we want to stay with seamonkey 
and try out current builds at our own peril. Not only that, but what version or 
build to look for in the links? 

My impression is that the microsoft November update rollup makes seamonkey 2.46 
for windows 7 x32 crash.

thank you to anyone who can shed more light on this.
long time Mozilla/Seamonkey user, K.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: [Resolved] Re: 2.46 updates?

[Rainer Ullrich]

On 20.10.2016 19:33, Adrian Kalla wrote:

W dniu 10/20/2016 o 11:19 AM, Rainer Ullrich pisze:

The confusing point is:
On a windows 64bit, if you have installed such a *32bit* preview 2.46
SeaMonkey,
and you click on "Help->Check for update", you will be offered a 2.46
update!

If you accept this update, your 32bit SeaMonkey will be replaced with an
*unofficial* preview 2.46 SeaMonkey, but in *64bit*.


As of yesterday, this should not happen on any branch anymore, as I have
ported my update-server-fix from the release branch to all the other
branches. So please check if this behavior still really happens, as this
would be unexpected.


Which version I should try?

Actual I use the (latest?) version from here:
<https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/?C=M;O=D>

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 
Firefox/49.0 SeaMonkey/2.46
Build identifier: 20161016181837

app.update.url is set to 
"https://l10n.mozilla-community.org/~akalla/unofficial/update/3/%PRODUCT%/%CHANNEL%/%BUILD_TARGET%/%LOCALE%/update.xml;

Check for Updates-result:
No Updates Found


Happy computing!
R@iner

--
Universal-Tool für Fritzboxen . http://rukerneltool.rainerullrich.de
Mit Ihrem Samsung TV kommunizieren  http://samsung.rainerullrich.de
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: [Resolved] Re: 2.46 updates?

[Adrian Kalla]

W dniu 10/20/2016 o 11:19 AM, Rainer Ullrich pisze:
> The confusing point is:
> On a windows 64bit, if you have installed such a *32bit* preview 2.46
> SeaMonkey,
> and you click on "Help->Check for update", you will be offered a 2.46
> update!
> 
> If you accept this update, your 32bit SeaMonkey will be replaced with an
> *unofficial* preview 2.46 SeaMonkey, but in *64bit*.

As of yesterday, this should not happen on any branch anymore, as I have
ported my update-server-fix from the release branch to all the other
branches. So please check if this behavior still really happens, as this
would be unexpected.

The Update NoOp saw was just yet another unofficial "nightly" from the
"release" branch - as they don't change version numbers (to e.g. 2.46.1)
as long as the official version number in that branch was not changed.

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

Re: [Resolved] Re: 2.46 updates?

[Rainer Ullrich]

On 20.10.2016 09:13, Daniel wrote:

Yeap!! I'll believe you, NoOp, but on my Win 7 WOW64, when I click
Help->Check for update, I'm still being told my SM 2.40 is the latest
version available!! :-(


2.40 is the latest official version. 2.46 is not finished today and not 
released!

There exists a lot of different *unofficial* beta, preview and release
candidates of 2.46 version. for example here:


The confusing point is:
On a windows 64bit, if you have installed such a *32bit* preview 2.46 SeaMonkey,
and you click on "Help->Check for update", you will be offered a 2.46 update!

If you accept this update, your 32bit SeaMonkey will be replaced with an
*unofficial* preview 2.46 SeaMonkey, but in *64bit*. Installed in the "old"
directory "%ProgramFiles(x86)%\SeaMonkey\". 64bit versions should be installed
in "%ProgramFiles%\SeaMonkey\".

HTH

Happy computing!
R@iner

--
Universal-Tool für Fritzboxen . http://rukerneltool.rainerullrich.de
Mit Ihrem Samsung TV kommunizieren  http://samsung.rainerullrich.de
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: [Resolved] Re: 2.46 updates?

[Daniel]

On 20/10/2016 6:29 AM, NoOp wrote:

On 10/19/2016 01:22 AM, Daniel wrote:

On 19/10/2016 1:00 AM, WaltS48 wrote:

On 10/18/2016 09:23 AM, Daniel wrote:

...



I just went to my SM browser, clicked Help->Check for updates and was
told there were no updates for my WIN7 WOW64 SM!!


What version exactly? Where downloaded from?


Do as Paul suggests or, even easier, have a look at my Sig!! WOW64 SM
2.40 direct from the SeaMonkey Project web page.


Then everything works for you as expected.


But still not being offered any update!



Because there isn't any.

The others are using unofficial versions from Adrian or somewhere else.


Thanks for this, Walt. I had thought that might be the case ... but,
then, upthread, Adrian posted 

"Mozilla recently changed the parameters attached to the update-URL and
it looks like I've configured the update server incorrectly... I hope
I've fixed it now for the RELEASE branch."

So I was thinking it was a genuine release, finally!!



Subject: 2.46 updates?

"I just received update notices for 2.46 (Windows and linux) on the
system that I have 2.46 running."

:-)


Yeap!! I'll believe you, NoOp, but on my Win 7 WOW64, when I click 
Help->Check for update, I'm still being told my SM 2.40 is the latest 
version available!! :-(


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
SeaMonkey/2.40 Build identifier: 20160120202951

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 
SeaMonkey/2.38 Build identifier: 20150903203501

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