On 9/29/2014 5:20 PM, NoOp wrote: > On 09/29/2014 03:57 PM, David E. Ross wrote: >> Windows 7 (x64) >> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 SeaMonkey/2.26.1 >> >> I have four SeaMonkey profiles, one of which is intended for guests to >> use. When that profile is launched, there is a red bar just above the >> view port with the message "Your copy of SeaMonkey is old and probably >> has known security flaws, but you have disabled automated update checks. >> Please update to a newer version." To the right of that message is a >> Check for Updates button. This occurs whether all 15 extensions I >> installed in that profile are enabled or I launch in Safe Mode. >> >> This happens only with the guest profile and none of the other three >> profiles, all of which are running from the same SeaMonkey version. I >> cannot see what I have configured differently between this guest profile >> and my usual default profile. >> >> Please suggest what I might check to resolve this. No, I do not want to >> upgrade and experience Password Manager problems. >> > > Probably related: > <https://bugzilla.mozilla.org/show_bug.cgi?id=581319> > <http://hg.mozilla.org/comm-central/rev/609b77dd2e8a> > > check about:config for: > app.update.lastUpdateTime.background-update-timer >
>From those links, it appears that users are given a warning if they disable automatic updates and it has been more than 90 days since the last installed update. Given there were 83 days between consecutive SeaMonkey versions 2.26.1 and 2.29, is not 90 days a bit tight? Also, I installed SeaMonkey 2.29 on 7 September. Then I removed it by reinstalling SeaMonkey 2.26 on 9 September, which I then updated to 2.26.1 on 25 September. (See my signature below for why I did this.) Thus, it was less than 90 days since I last installed an update. Suddenly, the problem has disappeared. My guest profile and one other profile now have values for that preference variable that is today, later than the values for the other two profiles. The other two have 24 September and 26 September. Something seems to be broken in how app.update.lastUpdateTime.background-update-timer gets updated. -- David E. Ross I am sticking with SeaMonkey 2.26.1 until saved passwords can be used when autocomplete=off. See <https://bugzilla.mozilla.org/show_bug.cgi?id=1064639>. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
