On 10/12/2016 9:51 AM, NoOp wrote:
> On 10/12/2016 5:23 AM, Chris Ilias wrote:
>> On 11/10/2016 10:23 PM, NoOp wrote:
>>>> On 10/11/2016 07:10 PM, NoOp wrote:
>>>>> I just received update notices for 2.46 (Windows and linux) on the
>>>>> system that I have 2.46 running. (Note: I do not get a notice on those
>>>>> that are still running 2.40). Here is what I get for the upgraded 2.46:
>>>>>
>>>>> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101
>>>>> Firefox/49.0 SeaMonkey/2.46
>>>>> Build identifier: 20160922144825
>>>>>
>>>>> and
>>>>>
>>>>> User agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:49.0)
>>>>> Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
>>>>> Build identifier: 20160922153204
>>>>>
>>>>> Anyone else (that are already running 2.46) get the same?
>>>
>>> Mine are from:
>>> https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-linux64/
>>> and I don't see that they're updated beyond 09/22:
>>> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101
>>> Firefox/49.0 SeaMonkey/2.46
>>> Build identifier: 2016092214482
>>>
>>> Unfortunately I wasn't paying much attention when I updated (baseball
>>> playoffs & cooking)... but update history from
>>> 'Help|Troubleshooting|Show Update History' shows on the Win10 shows:
>>>
>>> SeaMonkey 2.46 (20160922153204)
>>> Security Update
>>> Installed on: Tuesday, October 11, 2016 3:40:50 PM
>>> Status: The Update was successfully installed
>>>
>>> and now it is showing (after restart):
>>>
>>> User agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:49.0)
>>> Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
>>> Build identifier: 20160922153204
>> 
>> According to the last modified column of that directory, those builds 
>> are from September 22. I assume you were using an earlier build. :)
>> 
> 
> Yeah, I was as my download history shows that I downloaded 2.46 on 9/9
> from Adrian Kalla's (wave to Adrian) directory:
> https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/
> (latest-comm-release-<>).
> 
> I was just surprised that the update notice actually worked, however...
> Prior to the update I was running the 32bit version:
> Mozilla/5.0 (Windows NT 6.2; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
> SeaMonkey/2.46
> and the update changed my install to 64bit. I had purposely switched
> back to 32bit because of plugin problems (Shockwave Flash is the only
> plugin that shows up in about:plugins with 64bit. Plus the 64bit update
> borked my Lightning calendar & I had to reinstall to 5.1 to get my
> calendar back. Now I have to go back and download the 32bit version &
> reinstall so that I can get my plugins to work again :-(
> 
> Note: on the linux update all is OK as that was running 64bit and all
> the plugins work.
> 
> I'll post back after I revert back to 32bit...
> 

Added mozilla.dev.apps.seamonkey to this so perhaps Adrian will see
(setting followups to stay here on m.s.s).

OK, I've reinstalled 2.46 32bit so that all of my plugins work again:
User agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:49.0) Gecko/20100101
Firefox/49.0 SeaMonkey/2.46
Build identifier: 20160923004119
I had to reinstall lightning with the 32bit xpi to get calendar to work
again.

  Checked for updates and get:
A security and stability update for SeaMonkey is available
SeaMonkey 2.46

OK so far, but now I check to see where the 'View more information about
this update' goes to and find that it goes to the 64bit version:
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
  That is why my install changed from 32bit to 64bit (wew...thought my
CRS was acting up again).

I'll reinstall the latest from the 32bit directory:
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/
and see if it still prompts me for a security update.


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

Reply via email to