Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 223848 - There is an update available for SeaMonkey.
There is an update available for SeaMonkey.
Product: Fedora
Classification: Fedora
Component: seamonkey (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Martin Stransky
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-01-22 14:13 EST by Kasper Dupont
Modified: 2018-04-11 04:55 EDT (History)
5 users (show)

See Also:
Fixed In Version: seamonkey-1.0.7-
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-14 05:17:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kasper Dupont 2007-01-22 14:13:19 EST
Description of problem:
SeaMonkey says "There is an update available for SeaMonkey.", but "yum
check-update" does not show any updates for SeaMonkey.

Version-Release number of selected component (if applicable):

How reproducible:
Haven't tried.

Steps to Reproduce:
1. Start SeaMonkey
2. Wait a short while
Actual results:

Expected results:
SeaMonkey and yum agrees on whether there is an update available. (This would be
trivial to satisfy, if they used the same source to get the information).

Additional info:
Comment 1 Kai Engert (:kaie) (inactive account) 2007-02-06 22:11:14 EST
Did you manually change the preference "check for updates"?
By default the SeaMonkey package for Fedora has this option disabled.

If you would like to confirm that I'm right, create a new seamonkey profile, and
go to edit/prefs/advanced/software install
and you should see checkbox "check for updates" NOT checked.

If you confirm what I said, there is no bug here.

If you manually enabled that in your profile, you get the report that
Mozilla.org has produced a new release.

This doesn't necessarily mean that Fedora Extras immediately has a new release.
Comment 2 Kai Engert (:kaie) (inactive account) 2007-02-06 22:36:36 EST
Sorry, please ignore my previous comment!
You are not refering to the extras package, but the special FC-5 replacement
Comment 3 Kai Engert (:kaie) (inactive account) 2007-02-06 22:41:05 EST
Martin, in order to fix this bug, we'd have to add this line to

pref("update_notifications.enabled", false);

You might also want to have a look at the other entries in your prefs file and
see whether they are correct. Here is what the seamonkey extras package contains:

pref("browser.display.use_system_colors",   true);
pref("general.smoothScroll",                true);
pref("general.useragent.vendor", "Fedora");
pref("general.useragent.vendorSub", "SEAMONKEY_RPM_VR");
pref("update_notifications.enabled", false);

Should you consider to produce an update package for FC-5, could you please add
a symbolic link from /usr/bin/mozilla to /usr/bin/seamonkey, so former users of
the seamonkey package will still be able to start the program under the name
Comment 7 Fedora Update System 2007-02-13 17:33:37 EST
seamonkey-1.0.7- has been pushed for fc5, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.
Comment 8 Matěj Cepl 2007-02-14 05:17:03 EST
So this should be closed, right?
Comment 9 Kasper Dupont 2007-02-14 13:23:27 EST
As far as I can see 1.0.7-0.6.fc5 is the newest.
Comment 10 Kai Engert (:kaie) (inactive account) 2007-02-14 16:26:38 EST
I can see the Martin built the new package into the updates-testing tree.
I can see the package on the master download server, but not yet on the mirror.
Comment 11 Martin Stransky 2007-02-15 03:09:50 EST
oops, I meant to push it to final. Moved now.
Comment 12 Fedora Update System 2007-02-15 14:46:04 EST
seamonkey-1.0.7- has been pushed for fc5, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.