SeaMonkey -new version? (Linux)

[snailcoach]

I use PCLOS KDE5. When I open SM I got this message in a bright red bar -no problem with the bar. I like it-

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.

Then I run 'check for updates but got' There are no updates available. Please check again later . . .

Below is 'About SM' from Help on the menu bar

SeaMonkey
version 2.49.4

You are currently on the release update channel.
See a list of contributors to the Mozilla Project.
Read the licensing information for this product.
Read the release notes for this version.
See the build configuration used for this version.
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4
Build identifier: 20180711183816

This is the only version in the repo. Though I've seen mentions of newer versions in development, is version 2.49.4, safe to keep using until the newer ones reach the repos?

[therube]

I recently got that message too - in some of my Profiles.

I /think ?/ there is a pref that can turn it off?
I'm using a later build, WG9s SeaMonkey 2.49 Builds, but as said, also have the message.
(Hasn't bugged me enough, yet, to look further.)

He also has WG9s SeaMonkey 2.53 Builds.
They should be stable. (Well, they are for me. Happened to have a crash, the other day, surprised the heck out of me.)
If you try 2.53, be sure to do it either with a separate Profile, cause you don't (particularly) want to go back to using 2.49 after having used 2.53 on an "updated" existing Profile. In any case, backup ahead of time.


Oh, & update checks, currently, are ineffectual.


Bug 1074660 - Implementation of Bug #581319 Is Broken
Bug 581319 Warn people on startup if they run an old build with updates disabled

app.updatecheck.override is mentioned. Don't know if it is effectual?

[therube]

app.updatecheck.override is mentioned. Don't know if it is effectual?

Works.
Create the key, as boolean, & set it to 'true'.


Issue is (in part) caused by having app.update.enabled set to 'false'.