[FFe] Update Seamonkey to 2.0.x

I agree whole heartedly! The official 2.0 release was 10-27-09. From what I've read, SeaMonkey 1.1xx will receive bug fixes for a time and then languish into obscurity.

In any event, the most current is 2.0 and I believe it should be included in Ubuntu ASAP. Hopefully I'll be able to get it via Karmic backports.

FYI, a re-branded version of SeaMonkey 2.0 is already available within the Debian Testing repositories:
http://packages.debian.org/squeeze/iceape-browser

It doesn't appear that anyone is keeping the SeaMonkey updated:
https://launchpad.net/ubuntu/+source/seamonkey

Maintainer:
    Ubuntu-Mozilla-Team
<https://launchpad.net/~ubuntu-mozillateam>
<quote>
Ubuntu-Mozilla-Team does not use Launchpad. This page was created on 2007-07-30 when the lightning-sunbird_0.5-0ubuntu1 package was uploaded to gutsy/RELEASE.
Is this a team you run?
</quote>

It seems the Ubuntu-Mozilla-Team has gone walkabout...
https://launchpad.net/~ubuntu-mozilla-security/+archive/ppa

John Vivirito seems to be the only one who was doing any work with SeaMonkey:
https://launchpad.net/~gnomefreak/+archive/ppa
and even that ppa is sorely outdated.

If Ubuntu can't maintain SeaMonkey, then perhaps it should be dropped from the repositories altogether. At least then folks will download and install directly from mozilla.org rather than risk running old security infested versions of SeaMonkey.

Posted from:
Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7pre) Gecko/20091207 Lightning/1.0b1pre SeaMonkey/2.0.2pre

NoOp
Please stop saying that.
You are NOT right.

You were just saying that there IS ONE maintainer.
Your Idea is BAD, Insulting to all Seamonkey and previous Mozilla and Netscape users over years.
Seamonkey 1.1.17 IS CURRENT release (.1.1.18 bring nothing interesting to update).
2.0 is NEW release and our release Cycle is not that fast as Firefox, neither it needs to be!!

I find your proposal insulting, not a good behavior and frankly, i resist to such BAD ideas that tend to undermine
Ubuntu in any way.
Again, please STOP saying such auwfull ideas, you are NOT helping to Ubuntu by making it available with LESS applications.
IF YPU have something against Seamonkey itself, that is your problem.

I am very much interested in acting on having Seamonkey available Forever in Ubuntu.
And I will consult with current maintainer about your BAD proposals.

Upgrading package to SeaMonkey 2 (even in backports) becomes quite urgent because of... Flash!

I don't know for 32-bit, but on 64-bit platforms, Adobe Flash plugin on SeaMonkey 1.1.7 behaves inconsistently. Web pages with embedded flash animations (e.g. adverts) sometimes freeze the browser, sometimes crash it. It's really painful and happens a lot. Firefox 3.5 and SeaMonkey 2.0 seem not (or to a lesser extent) affected by this.

Because of this problem, using 64-bit SeaMonkey 1.1.7 for daily usage (which is the puropse of an internet suite) has become very painful... So upgrade is badly needed.

By the way, SeaMonkey 2.0.1 will be released in the forthcoming days.

I just added a ppa for Seamonkey 2.0.1. I'm a huge fan of Seamonkey and had the same problem with needing the amd64 version. I used the original source code from seamonkey 2.0.1 and just had to add the debian build files. It installs as seamonkey-2.0 and both versions of the browser (1.1.17 and 2.0.1) can exist on the same system.

https://launchpad.net/~joe-nationnet/+archive/ppa-seamonkey2

Wow, that is great Joe Lesko! ;) Great news! :) Thank you! ;)
But as I see there is no orig.tar.gz and separate diff.gz files?

@Nomax, try installing Adobe 64 bit flash player 10 for Linux, from adobe site. Works fine on 1.1.17 on my Hardy 64bit install ;)

@Nikola M: I tried but then SeaMonkey 1.1.17 crashed upon loading any Flash content.

@Joe Lesko: Awesome! It works great!!! Thanks!

Nikola M: I posted the orig.tar.gz and diff.gz files for hardy, jaunty, karmic and lucid. I have tried the stable release on all by hardy as I don't have a hardy system available at this time. Launchpad built all the packages for each of the releases. I even put some daily files out there that are more beta builds. I hope the stable release can be picked up for lucid as I really like what Mozilla did with the 2.0 series and it's been very stable for me.

Now the next step is what I need to do with the files so they can get included in the distro.

It would be also great to add SM2.0 as an alternative to x-www-browser
SM1.1 did that. Now I have to do it by hand. like :
update-alternatives --install /usr/bin/x-www-browser x-www-browser /usr/bin/seamonkey-2.0 130

I am downloading it (at a slow rate, something is wrong at me with downl. speed from ppa) after i test , I will post findings

Wladimir Mutel: Thanks. Sounds like a great idea. I'll add update-alternatives today.

Testing
http://ppa.launchpad.net/joe-nationnet/ppa-seamonkey2/ubuntu/pool/main/s/seamonkey-2.0/
[[ ] seamonkey-2.0_2.0.2+nobinonly-0ubuntu4-joe1~karmic_amd64.deb]
and all appears to be working, including java (Version 6 Update 18) and flash 10.0 r42).

Picked up my bookmarks & add-ons/plug-in's, including Lightning 1.0b1 from my standard SM 2.0.3pre (64bit from the mozilla nightlies) w/o issues. I'll run on the 64bit, and test on the 32bit over the next few days and report back. Had some issues with the Applications|Internet menu items (the install screwed up my standard SM menus that I'd set up for running /home/<username>/seamonkey2/ items, but not an issue at this point). I'll also test tomorrow on hardy as well; I can test on jaunty as well, but at this point I think that jaunty will be going away soon so it's not a priority (for me).

Overall: Well done & thanks!

Note: I have been using SeaMonkey daily since it's inception. I test on linux (Ubuntu) & Windows (Win2K, WinXP, and Win7) regularly.

@ Nikola M: I've been testing SeaMonkey from a user and in business/corporate environments from the first release of SeaMonkey. I've insulted no one & suggest you update your knowlege regarding SeaMonkey and Mozilla releases in general.

Installs from the PPA to hardy, jaunty & karmic (32bit) all went w/out issue. I'll test the hardy & karmic's with the standard Mozilla litmus tests: https://litmus.mozilla.org/run_tests.cgi?test_run_id=7 - only thing I can't test is w/imap as I do not have an imap account. Again, thanks for these builds!

Ran the litmus tests for hardy, jaunty & karmic (32bit), and karmic 64bit without issues. Note: I did not post the tests on the litmus site, but instead ran them individually. I've also been using the karmic 32 & 64bit builds on my daily work machines w/o issue.

Any possibility that these ppa builds can be made official?

Seamonkey 2.0.3 is being released next week and Mozilla.org was nice enough to have the source files tagged in revision control, so I rebuilt Seamonkey 2.0.3 without much effort. There are something like 22 security fixes and 100+ bug fixes, I think the way the package builds is the way it should work and it is easy to rebuild when the next release comes out. The new packages are in my PPA area. I don't know what the next steps are for getting the package into one of the repos. I was hoping that Seanonkey could make it into Lucid, but I can understand the pressure on the Ubuntu Mozilla Team in being short on time and needing to get a lot done to be able to help get this moving.

Would it be better if Seamonkey got moved under Universe? I would be happy to maintain it, but I need help with the process to go from package to repo.

Thanks again NoOp for all your testing. That's a lot of builds to keep straight.

So far, I have tested 2.0.2 that I got previously fropm your PPA and it works just fine on Hardy/8.04LTS/64-bit.
Maybe you could bring it back inside PPA since it is Ok?

Also I am eager to see 2.0.3 and to finally switch to SM2 from 1.1.17.
There is now "officialy contributed" Seamonkey 2.0.3 Linux 64-bit binary on main download Seamonkey page.

As an FYI:
http://www.seamonkey-project.org/news#2010-03-16
</quote>
March 16, 2010
Support For SeaMonkey 1.x Dropped

In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a year later. Another three years later, the SeaMonkey project is discontinuing support for the SeaMonkey 1.x series today in favor of SeaMonkey 2.0, which is not only more modern, but also maintained for stability and security problems.

As the SeaMonkey 1.x series no longer receives security updates, due to resource constraints, the SeaMonkey team strongly urges users of that series to upgrade. Additionally, the team continues to strongly urge people still using the old Mozilla Suite or Netscape 4, 6 or 7 to upgrade to the new SeaMonkey 2.0 version. All these older software packages suffer from a large, and steadily increasing, number of security vulnerabilities because they are no longer being maintained.

Everyone on reasonably modern operating systems is urged to switch to the newest release available for free download from the open source project's website at www.seamonkey-project.org, providing the familiar suite functionality in a remodernized application with additional features and fully up to date security.
For the few who can't afford that, a last 1.x release is available. SeaMonkey 1.1.19 does fix a few security issues, but not all known security vulnerabilites, some of which may even be grave. Those are only fixed in the new SeaMonkey 2.0, which will continue to be maintained for quite some time and updated for any security issues as they might arise, while the team is working on evolving the well-known suite even further in future versions.
<quote>

Given that lucid is still showing 1.1.17 (https://launchpad.net/ubuntu/+source/seamonkey):
The Lucid Lynx (pre-release freeze)
SeaMonkey 1.1 series
Show details 1.1.17+nobinonly-0ubuntu1

it would seem that the package maintainers are still asleep at the switch. I've been running Joe's ppa:
Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100208 Lightning/1.0b1 SeaMonkey/2.0.3
(also the 64bit version) and it's been rock solid. Thanks Joe!

As I allready wrote in #542750

Since SM 2.0 is out since month, lucid definitly should ship the newer version!
 -SM 1.1.17 isn't up to date. The last 1.1 is 1.1.19
 -SM 1.1 at all is completely outdated since at least 1/2 year. There are many unfixed security issues and we won't see any fixes.
 -SM2 is technically much closer to FF. So maintenance should be much easier
 -Is it a good idea to ship such an old software like SM 1.1 for the next 2-3 years? (lucid is a LTS version)

I hate to say this: If we can't ship with SM 2.x, SM 1.1 should be removed for security, image and maintanance reasons.

Grettings

Not going to happen just on your will. It's Ubuntu, and Process is the King there.
Use the above mentioned PPA and don't try to demand anything from the mainline.

What won't happen? SM 2.0 in lucid?
Yes I know there is nearly now chance because feature freeze is reached. But what is the alternative? Shipping SM 1.1.x for the next 3 years? I think it's better not shipping SM at all. That's my point.

Both ones not going to happen: SM 2.0 in lucid , as well as SM 1.1 out of lucid.
Wait till Lucid release at the end of April so you could check by yourself.
Then read comment #20 again - it's truth.

Wladimir: Also I'm afraid you're right saying 1.1.17 is going to ship with lucid, just saying "process is King" without any further arguments isn't enough to solve a problem.
And "it's the truth" that there is a problem with SM in Ubuntu:

- SM 2.0.0 was released on 27. oct 09, 2 days before carmic was released. So SM 2 was available from the first day of lucid development
- This bugreport was filled at the same day SM 2 was released.
- There is a debian package since 4. nov 09 like correctly stated from suspicous1 at the end of november.
- Lucid is still shipping with SM 1.1.17 which was released on 22.06.2009. The Update to 1.1.18 from 3.09.09 is still missing.

My question is: What's going wrong here with the "process", and is there something we can do to fix it?
And that's the way my posting should be read: As a suggestion for a fix (add SM 2) or workarround (remove SM 1.1.x) for a bug i found when i was playing arround with Lucid Beta1.

Well, seems we will need to do something to see SM 2.x in Ubuntu in 10.10 release, anyway.
So clock is ticking for 10.10 from now on. Lets `hop in` and do something.
Rechner-Tester, if you want do do something about it, i am willing to also do something about it and to work with Joe Lesko.

PPA release works great , there su currently Seamonkey 2.0.4 available (Also made by Joe Lesko), for 8.04LTS (hardy), 9.10(karmic) and 10.04LTS(lucid), 32 and 64bit:
Seamonkey PPA releases for ubuntu: https://launchpad.net/~seamonkey2/+archive/seamonkey2
Seamonkey PPA testing for Ubuntu: https://launchpad.net/~seamonkey2/+archive/seamonkey2-pre

Only problem I see for now is that not any _plugin_ from mozilla site would not install, with this messages:

"Enigmail" could not be installed because it is not compatible with your SeaMonkey build type (Linux_x86_64-gcc3). Please contact the author of this item about the problem.
and for Lightning:
"Lightning" could not be installed because it is not compatible with your SeaMonkey build type (Linux_x86_64-gcc3). Please contact the author of this item about the problem.

@ Nikola M: It's because Mozilla website only host 32-bit versions of those plugins. For Lightning, you have to use this build: http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/1.0b1/contrib/linux-x86_64/lightning.xpi

FFe granted; we definitely don't want to stay with the old 1.x seamonkey for Lucid.

Am I getting this right? There is a chance for SM 2 in lucid? That would be great news ^_^

Nikola M: Yes, I thought about "doing something". But since I have to do an internship (May be I should write to canoical?) and write my diploma thesis this year I'm very cautious with this.

BTW: What does the tag [FFe] stands for?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Feature Freeze exception. If I can get it done this weekend, it'll
get in, otherwise, it'll have to be dropped for Lucid.

On 04/15/2010 04:42 AM, Rechner-Tester wrote:
> BTW: What does the tag [FFe] stands for?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkvG5pAACgkQTniv4aqX/VlvGwCdEV6JCcA4XE2ro1ZFSU4sz+yW
CHEAnj8tfbBWKtcLg7/zEYF8g+aLmQYq
=BS7T
-----END PGP SIGNATURE-----

I know nothing about the release process so I'm just crossing fingers here!

Micah would have to clarify this but it is not looking like 2.0 will land in Lucid. I had looked at someones build however it is not ready and needs a lot of love to get it ready.

Please test Seamonkey 2 from my PPA for Lucid. E-Mail me directly with any issues. Please backup your profile first.

https://launchpad.net/~micahg/+archive/mozilla-test/

On 04/23/2010 05:35 PM, Micah Gersten wrote:
> Please test Seamonkey 2 from my PPA for Lucid. E-Mail me directly with
> any issues. Please backup your profile first.
>
> https://launchpad.net/~micahg/+archive/mozilla-test/
>

Sorry, doesn't work properly.

1. Doesn't maintain mozilla prefbar display
[http://prefbar.mozdev.org/]
2. Doesn't respect startup options such as '-no-remote -mail -browser'
3. Bookmarks are missing from existing profile.
4. Passwords are missing from existing profile.
etc., etc.

Only tested on 32bit & have not had time to test further or test on 64bit.

What was that quote from John Vivirito? "it is not ready and needs a lot
of love to get it ready."

BTW: loading up the standard SeaMonkey from mozilla, or reinstalling Joe
Lesko's 2.0.4 PPA version
(https://launchpad.net/~seamonkey2/+archive/seamonkey2) and using the
same ~/.mozilla profile restores all of 1-4.

Since 1.1.17 is the current package for Ubuntu and all projects derived from it, I don't think it should be removed, but the 2.0.x series of released could be offered as well through the packaging system as an optional testing package in unsupported or unofficially supported status.

This would still allow 1.1.17 to be the official Ubuntu release, but allow users the option to try out 2.0.4 without official support.

Does anyone know what security issues were fixed between 1.1.17 and 2.0.4?

@Jim: > Does anyone know what security issues were fixed between 1.1.17 and 2.0.4?

http://www.mozilla.org/security/known-vulnerabilities/seamonkey11.html
http://www.mozilla.org/security/known-vulnerabilities/seamonkey20.html

@Jim

1.1.17 is very old and the 1.1.x branch is no longer receiving Security updates. In fact 1.1.19 is the latest release. The choices are the drop Seamonkey from Lucid or upgrade the package to 2.0.x
I will try to fix the issues noted by NoOp before we push to the archive.

This bug was fixed in the package seamonkey - 2.0.4+nobinonly-0ubuntu1

---------------
seamonkey (2.0.4+nobinonly-0ubuntu1) lucid; urgency=low

  * New upstream release v2.0.4 (SEAMONKEY_2_0_4_RELEASE) (LP: #461864)

  [ Fabien Tassin <email address hidden> ]
  * Add conditional support for system Cairo, NSS, NSPR
    - update debian/rules
  * Update icons from xpm to png
    - update debian/seamonkey-*.{install,links,menu}
  * We no longer need dynamic -lsoftokn, disable NSS_DYNAMIC_SOFTOKN
    - add debian/patches/no_dynamic_nss_softokn.patch
    - update debian/patches/series

  [ Micah Gersten <email address hidden> ]
  * Use versioned install directory
    - update debian/rules
  * Bump minimum versions of system libs; cairo to 1.8.8; NSPR to 4.8;
    NSS to 3.12.6
    - update debian/rules
  * Update .install files for latest release
    - update debian/seamonkey-browser.install
    - update debian/seamonkey-mailnews.install
  * Refresh patches
    - update debian/patches/cleaner_dist_clean.patch
    - update debian/patches/fix_installer.patch
    - update debian/patches/seamonkey-fsh.patch
  * Drop cairo FTBFS patch after upstream landing
    - drop debian/patches/fix_ftbfs_with_cairo_fb.patch
    - update debian/series
  * Install gnome components in -browser package so that it works out of the box
    - update debian/seamonkey-browser.install
    - update debian/control
    - update debian/rules
  * Move mozclient to be in source
    - add debian/mozclient/compare.mk
    - add debian/mozclient/seamonkey-remove.binonly.sh
    - add debian/mozclient/seamonkey.conf
    - add debian/mozclient/seamonkey.mk
    - update debian/rules

  [ Chris Coulson <email address hidden> ]
  * Ensure the symlinks are installed correctly. File name expansion
    doesn't work in the .links files, so call dh_link explicitly in
    debian/rules instead
    - drop debian/seamonkey-browser.links
    - drop debian/seamonkey-mailnews.links
    - update debian/rules
  * Only the seamonkey-gnome-support package should have dependencies on GNOME
    libraries - ensure that seamonkey-browser doesn't have the GNOME components
    installed when dh_shlibdeps is run
    - update debian/rules
    - update debian/seamonkey-browser.install
 -- Micah Gersten <email address hidden> Mon, 26 Apr 2010 14:30:57 -0500

Working for me on lucid 32bit & 64bit as of this morning. I'll try on karmic & hardy later.

1. Maintained mozilla prefbar display
[http://prefbar.mozdev.org/]
2. Respects startup options such as '-no-remote -mail -browser'
3. Bookmarks are available from existing profile.
4. Passwords are available from existing profile.
5. Java, flash, and other existing profile settings working.

One issue that I found somewhat confusing; to install via Synaptic I used 'seamonkey'. However, to uninstall if 'seamonkey' is selected you need to uninstall each individual package (mailnews, etc). I did find that if I select 'seamonkey-browser' for uninstall it then selects all the appropriate bits (seamonkey, seamonkey-chatzilla, seamonkey-mailnews, seamonkey-browser). For consistency, one should be able to uninstall the same way that they installed. And from the cli:

$ sudo apt-get install -s seamonkey
Reading package lists... Done
Building dependency tree
Reading state information... Done
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  seamonkey-browser seamonkey-chatzilla seamonkey-mailnews
Suggested packages:
  libkrb53 seamonkey-dom-inspector
The following NEW packages will be installed:
  seamonkey seamonkey-browser seamonkey-chatzilla seamonkey-mailnews
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Inst seamonkey-browser (2.0.4+nobinonly-0ubuntu1 Ubuntu:10.04/lucid)
Inst seamonkey-mailnews (2.0.4+nobinonly-0ubuntu1 Ubuntu:10.04/lucid)
Inst seamonkey (2.0.4+nobinonly-0ubuntu1 Ubuntu:10.04/lucid)
Inst seamonkey-chatzilla (2.0.4+nobinonly-0ubuntu1 Ubuntu:10.04/lucid)
Conf seamonkey-browser (2.0.4+nobinonly-0ubuntu1 Ubuntu:10.04/lucid)
Conf seamonkey-mailnews (2.0.4+nobinonly-0ubuntu1 Ubuntu:10.04/lucid)
Conf seamonkey (2.0.4+nobinonly-0ubuntu1 Ubuntu:10.04/lucid)
Conf seamonkey-chatzilla (2.0.4+nobinonly-0ubuntu1 Ubuntu:10.04/lucid)

$ sudo apt-get remove -s seamonkey
[sudo] password for lucid:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  seamonkey-chatzilla seamonkey-mailnews
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  seamonkey
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Remv seamonkey [2.0.4+nobinonly-0ubuntu1]

I think this is the case with any metapackage. If you want, file another
bug against Seamonkey and I'll try to find the appropriate place/dupe
for the bug. Thanks for testing!

On 04/28/2010 11:35 AM, NoOp wrote:
> <snip />
> One issue that I found somewhat confusing; to install via Synaptic I
> used 'seamonkey'. However, to uninstall if 'seamonkey' is selected you
> need to uninstall each individual package (mailnews, etc). I did find
> that if I select 'seamonkey-browser' for uninstall it then selects all
> the appropriate bits (seamonkey, seamonkey-chatzilla, seamonkey-
> mailnews, seamonkey-browser). For consistency, one should be able to
> uninstall the same way that they installed. And from the cli:
>

On 04/28/2010 09:55 AM, Micah Gersten wrote:
> I think this is the case with any metapackage. If you want, file another
> bug against Seamonkey and I'll try to find the appropriate place/dupe
> for the bug. Thanks for testing!
...

I'll try to get to that tomorrow. However, you're now aware of the
problem, and no, the issue is not the same for other metapackages; you
install via a metapackage, you should be able to uninstall via the same
metapackage. The installation/uninstallation issue should be fixed
regardless of whether a separate bug is filed or not.

Wishlist (yes I can file a new wishlist issue on this tomorrow if
necessary):
Can the packages now _please_ be built for Hardy & Karmic? Neither will
install with the lucid packages due to dependency issues.
  Hardy is a supported LTS that will be around for some time. Karmic
will also be around for some time before folks make transitions to
10.04. Continuing to run on 1.1.17 is a security issue. Of course
you'll need to contend with complaints regarding the form filling issues
in the transition from 1.x to 2.x, but that will happen in lucid as
well. I'd vote for updated security vs old form filling methods anyday.

NoOp, we'll probably backport 2.0.5 when it's released next month. There needs to be some testing done first. The packages will probably hit the Ubuntu Mozilla Security PPA first. I'm not sure what you mean by Form Filling. Feel free to ping me in #ubuntu-mozillateam to discuss further.

@ Micah: I've been getting unexplained crashes in 2.0.4. This build apparently doesn't support the mozilla crash reporter & no trace of a crash in /var/crash (SeaMonkey just disappears/quits). As a result I've had to fall back to my standard SeaMonkey (mozilla) to finish working today. However, before I begin troubleshooting so that I can file a new issue report, can you please advise if the following instructions are valid for this build (modified from Firefox of course):

https://wiki.ubuntu.com/MozillaTeam/Bugs#Obtain%20a%20backtrace%20from%20an%20apport%20crash%20report%20(using%20gdb)

Do I also need seamonkey-gnome-support installed?

The wiki page is out of date. I would suggest using apport to get a
one time crash:
https://wiki.ubuntu.com/Apport
If you don't want to upload it, you can retrace it locally.

seamonkey-gnome-support is only needed for the gnome dependencies.

On 04/30/2010 02:41 PM, NoOp wrote:
> @ Micah: I've been getting unexplained crashes in 2.0.4. This build
> apparently doesn't support the mozilla crash reporter & no trace of a
> crash in /var/crash (SeaMonkey just disappears/quits). As a result I've
> had to fall back to my standard SeaMonkey (mozilla) to finish working
> today. However, before I begin troubleshooting so that I can file a new
> issue report, can you please advise if the following instructions are
> valid for this build (modified from Firefox of course):
>
> https://wiki.ubuntu.com/MozillaTeam/Bugs#Obtain%20a%20backtrace%20from%20an%20apport%20crash%20report%20(using%20gdb)
>
> Do I also need seamonkey-gnome-support installed?
>

Finally decided to use the Ubuntu 2.0.4 again today... crashed while browsing a help.ubuntu.com page. apport used & bug report filed:

https://bugs.launchpad.net/ubuntu/+source/seamonkey/+bug/576082