Red Hat Bugzilla – Bug 223159
Mangled Cross-Blending of Mozilla & SeaMonkey and Splitting Up of SeaMonkey
Last modified: 2018-04-11 11:17:12 EDT
Description of problem:
OK, technically, this is a problem with seamonkey, experienced in FC5, only
you don't list a seamonkey component, and, anyway, this is partly due to
seamonkey being drafted willy-nilly as the new mozilla component. Also, it
appears now that mozilla is no longer recognized as a component (product).
Basically, people running mozilla are getting seamonkey, and mostly without
mail functionality. See actual results for details.
Version-Release number of selected component (if applicable):
Replacing previous unitary seamonkey package and previous mozilla package.
Install FC 5 with or without the previous version of seamonkey from extras.
Run yum update.
Different varieties of hell break loose depending on which starting state you
had and whether you really want to run seamonkey or mozilla.
I *think* this is what is happening:
If the old seamonkey (1.0.4, 1.0.5?) from extras was installed and you run yum
update, you end up with an executable called /usr/bin/mozilla, but
not /usr/bin/seamonky, that invokes seamonkey 1.0.7, and there is no mail or
chat, etc., accessible anywhere - not in the menus, not in the footer icons,
not by command line parameter.
If you then get a glimmering and run yum install seamonkey-\* you get all the
new subcomponent packages, but the mozilla executable is not aware of them.
Same situation as before, but more packages.
If you then delete seamonkey-* and everything that depends on it and reinstall
them all, you end up with an executable called mozilla that has icons and a
windows menu that knows about mail, etc., but mozilla -mail still doesn't
If you have a system with no seamonkey on it and you run yum install seamonkey-
\* you end up with a setup in which mail is functional everywhere, but, of
course, the executable is still called mozilla. Anyway, it can see mail and
mozilla -mail works. It's not clear if it sees the same mail directories it
Of course in all cases, the mozilla package is uninstalled for you. Thanks, I
I would expect updating of seamonkey - now split into sub packages - to result
in installing the subpackages, too. Or maybe in would install a stub that
told me to start from scratch with the new model. Or it would never update
and I would eventually realize I needed to install seamonkey-newsetup-\*. I
wouldn't expect mail to go away, causing users with custom setups that run
seamonkey -mail &s to be unable to access mail.
I would expect the principle executable to retain its usual name, seamonkey.
(Still there in the tarball for 1.0.7.)
I would expect mozilla to remain intact, or to be deleted by some sort of
mozilla update that installed either a link to seamonkey or something that
explained that mozilla was gone, please remove this package and switch to
- Crossbreeding the two packages by interrelating their updating behavior was
- Renaming the seamonkey executable was wrong.
- Not installing all the subdivided elements of seamonkey was wrong.
On the bright side, it ought to be easy to fix. Harder to explain, maybe. :-)
Incidentally, I was really pleased to see that Xft is now compiled in. So at
least it is now easier to see MathML pages. And that nasty SELinux problem
that caused the old seamonkey to crash unless some file properties were hand
changed is gone, too.
This is essentially the same as 223157. I had difficulties submitting it.
*** Bug 223157 has been marked as a duplicate of this bug. ***
*** Bug 223158 has been marked as a duplicate of this bug. ***
Fedora Core 5 is no longer supported, could you please reproduce this with the
updated version of the currently supported distribution (Fedora Core 6, or
Fedora 7, or Rawhide)? If this issue turns out to still be reproducible, please
let us know in this bug report. If after a month's time we have not heard back
from you, we will have to close this bug as CANTFIX.
Setting status to NEEDINFO, and awaiting information from the reporter.
Thanks in advance.
This set of problems was resolved by a modification of the SeaMonkey packages
subsequent to the complaint, back when Fedora 5 was still supported. I
assumed you were responding to the bug, but perhaps something else prompted
the corrections. Anyway, I withdraw the bug.