seamonkey-2.0-bin assert failure: *** buffer overflow detected ***: /usr/lib/seamonkey-2.0.11/seamonkey-2.0-bin terminated

StacktraceTop:
 __kernel_vsyscall ()
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __libc_message (do_abort=2, fmt=0x6c382a "*** %s ***: %s terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 __fortify_fail (msg=0x6c37ab "buffer overflow detected") at fortify_fail.c:32

Workaround: disable "Check spelling as you type"

I found there one bug with buffer size calculation, but seems like original buffer-overflow warn in strcpy() is false-positive for this case.

This patch fix both problems.

Thank you for using filing a bug (with a patch) and helping to make Ubuntu better. Seamonkey was updated to 2.0.13 just after you reported this bug. Can you upgrade to this version and report back if it still has the problem? I checked the source and while your patch would apply I'm not sure the issue wasn't fixed in another part of the code. Thanks!

Yes, bug still here, 2.0.13+nobinonly-0ubuntu1 affected, my custom build with this patch works fine.

I find the same (or similar) defect in 2.0.13. On one hand, the argument might be that I have multiple configurations and that creates problems, but the counter argument to that is that if I download my own instance of Seamonkey (which I did with 2.0.11 and 2.0.13) I do not have this buffer overflow problem, nor do I see it at all if I run it on a non-Canonical distribution. Since the Ubuntu-based .deb packages are the only variable I can discern, I continue to believe that something in the way you build these packages contributes to the buffer overflow condition.

You can close this issue if you wish, but only if you keep another defect open for the same issue for the 2.0.13 build. It's too bad we haven't found the root cause of this problem; it is really the only defect I've discovered in the 11.04 release cycle, which makes me wonder if there isn't some kind of interaction with the kernels being used. I had been using the 2.0.11 release on the 10.10 release of Kubuntu and Ubuntu just prior to this, and did not see any instability whatsoever, so this buffer overflow seems somehow related to infrastructure changes in the 11.04 release stream, but I don't have the tools or the wherewithal to test that conjecture, but it has been my consistent observation.

If the stack traces don't provide enough information, think about my comments and see if they cause you to examine areas of the code that may somehow interact with core components of the environment. If not the kernel, what about changes to the X server?

I have not had success with the 2.0.13 build; get the same buffer overflow crash I reported in the 2.0.11 release. Downloading a Seamonkey binary from Mozilla on the same platform works, so the defect is in something that has been put into this package.

There is a similar, if not the same, bug reported for 2.0.13 now (762905).

A similar thing happens each time when I click Create new mail in Yahoo mail! It is very urgent.

Here is the backtrace:

*** buffer overflow detected ***: /usr/lib/seamonkey-2.0.13/seamonkey-2.0-bin terminated
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(__fortify_fail+0x50)[0x1f5df0]
/lib/i386-linux-gnu/libc.so.6(+0xe4cca)[0x1f4cca]
/lib/i386-linux-gnu/libc.so.6(__strcpy_chk+0x3f)[0x1f405f]
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so(+0x1e005)[0x2ab5005]
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so(+0x1e766)[0x2ab5766]
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so(+0x1e8b6)[0x2ab58b6]
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so(+0x1eaca)[0x2ab5aca]
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so(+0xd75c)[0x2aa475c]
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so(+0x4c75)[0x2a9bc75]
/usr/lib/seamonkey-2.0.13/components/libcomposer.so(+0xc7b2)[0x17dc7b2]
/usr/lib/seamonkey-2.0.13/components/libcomposer.so(+0xd024)[0x17dd024]
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so(+0x94c7)[0x2aa04c7]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x3e0b5c)[0x1d32b5c]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x3df2ab)[0x1d312ab]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x18c6ed)[0x1ade6ed]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0xf725a)[0x1a4925a]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0xf102c)[0x1a4302c]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0xf12ab)[0x1a432ab]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0xfbd81)[0x1a4dd81]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x120a89)[0x1a72a89]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x26ba27)[0x1bbda27]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x260e8d)[0x1bb2e8d]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x260fb3)[0x1bb2fb3]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x261b18)[0x1bb3b18]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x261bc1)[0x1bb3bc1]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x256a8a)[0x1ba8a8a]
/usr/lib/seamonkey-2.0.13/components/libxpconnect.so(+0x482f1)[0x2f5e2f1]
/usr/lib/seamonkey-2.0.13/libmozjs.so(+0x409fa)[0x2b19fa]
/usr/lib/seamonkey-2.0.13/libmozjs.so(+0x46aed)[0x2b7aed]
/usr/lib/seamonkey-2.0.13/libmozjs.so(JS_EvaluateUCScriptForPrincipals+0x99)[0x281e30]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x379f6e)[0x1ccbf6e]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x278e4c)[0x1bcae4c]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x278f96)[0x1bcaf96]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x27a2d7)[0x1bcc2d7]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x2781fd)[0x1bca1fd]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x2e042b)[0x1c3242b]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x2dfb58)[0x1c31b58]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x2f9899)[0x1c4b899]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x2f9aa3)[0x1c4baa3]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x2faa06)[0x1c4ca06]
/usr/lib/seamonkey-2.0.13/components/libhtmlpars.so(+0x10d2b)...

When I open Chatzilla, it crashes:

$ seamonkey --chat
cz-service: No windows, starting new one.
*** buffer overflow detected ***: /usr/lib/seamonkey-2.0.13/seamonkey-2.0-bin terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7fd9ebbc21d7]
/lib/x86_64-linux-gnu/libc.so.6(+0xfd0f0)[0x7fd9ebbc10f0]
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so(+0x1e802)[0x7fd9dd7a7802]
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so(+0x1eedf)[0x7fd9dd7a7edf]
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so(+0x1f023)[0x7fd9dd7a8023]
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so(+0x1f27d)[0x7fd9dd7a827d]
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so(+0xfb23)[0x7fd9dd798b23]
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so(+0x793a)[0x7fd9dd79093a]
/usr/lib/seamonkey-2.0.13/components/libcomposer.so(+0xdeab)[0x7fd9cc6efeab]
/usr/lib/seamonkey-2.0.13/components/libcomposer.so(+0xe692)[0x7fd9cc6f0692]
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so(+0xbb55)[0x7fd9dd794b55]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x559e66)[0x7fd9d6776e66]
/usr/lib/seamonkey-2.0.13/libxpcom_core.so(NS_InvokeByIndex_P+0x26b)[0x7fd9ebec9dd7]
/usr/lib/seamonkey-2.0.13/components/libxpconnect.so(+0x3e46b)[0x7fd9dbb1a46b]
/usr/lib/seamonkey-2.0.13/components/libxpconnect.so(+0x43a8f)[0x7fd9dbb1fa8f]
/usr/lib/seamonkey-2.0.13/libmozjs.so(js_Invoke+0x641)[0x7fd9eb40e7a7]
/usr/lib/seamonkey-2.0.13/libmozjs.so(+0x413f5)[0x7fd9eb3ff3f5]
/usr/lib/seamonkey-2.0.13/libmozjs.so(js_Invoke+0x64b)[0x7fd9eb40e7b1]
/usr/lib/seamonkey-2.0.13/libmozjs.so(+0x50960)[0x7fd9eb40e960]
/usr/lib/seamonkey-2.0.13/libmozjs.so(+0x50aa1)[0x7fd9eb40eaa1]
/usr/lib/seamonkey-2.0.13/libmozjs.so(+0x5ca9a)[0x7fd9eb41aa9a]
/usr/lib/seamonkey-2.0.13/libmozjs.so(+0x5cba4)[0x7fd9eb41aba4]
/usr/lib/seamonkey-2.0.13/libmozjs.so(+0x5d1ef)[0x7fd9eb41b1ef]
/usr/lib/seamonkey-2.0.13/libmozjs.so(+0x41bcd)[0x7fd9eb3ffbcd]
/usr/lib/seamonkey-2.0.13/libmozjs.so(js_Invoke+0x64b)[0x7fd9eb40e7b1]
/usr/lib/seamonkey-2.0.13/libmozjs.so(+0x50960)[0x7fd9eb40e960]
/usr/lib/seamonkey-2.0.13/libmozjs.so(JS_CallFunctionValue+0x1a)[0x7fd9eb3d7fdf]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x4fb159)[0x7fd9d6718159]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x506f35)[0x7fd9d6723f35]
/usr/lib/seamonkey-2.0.13/components/libgklayout.so(+0x5071de)[0x7fd9d67241de]
/usr/lib/seamonkey-2.0.13/libxpcom_core.so(+0x69ed7)[0x7fd9ebec1ed7]
/usr/lib/seamonkey-2.0.13/libxpcom_core.so(+0x6a08a)[0x7fd9ebec208a]
/usr/lib/seamonkey-2.0.13/libxpcom_core.so(+0x67a42)[0x7fd9ebebfa42]
/usr/lib/seamonkey-2.0.13/libxpcom_core.so(_Z21NS_ProcessNextEvent_PP9nsIThreadi+0x2b)[0x7fd9ebe95d7f]
/usr/lib/seamonkey-2.0.13/components/libwidget_gtk2.so(+0x415f1)[0x7fd9db0ac5f1]
/usr/lib/seamonkey-2.0.13/components/libtoolkitcomps.so(+0x8758)[0x7fd9d89d2758]
/usr/lib/seamonkey-2.0.13/libxul.so(XRE_main+0x2d52)[0x7fd9ec12d372]
/usr/lib/seamonkey-2.0.13/seamonkey-2.0-bin[0x4018a7]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xff)[0x7fd9ebae2eff]
/usr/lib/seamonkey-2.0.13/seamonkey-2.0-bin[0x401699]
======= Memory map: ========
00400000-0040c000...

To test, just point Seamonkey at a page which always crashes. For example this one: http://www.google.se/language_tools?hl=sv

Wow, this is true. But why?

2011/4/30 Anonymous <email address hidden>

> To test, just point Seamonkey at a page which always crashes. For
> example this one: http://www.google.se/language_tools?hl=sv
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/723830
>
> Title:
> seamonkey-2.0-bin assert failure: *** buffer overflow detected ***:
> /usr/lib/seamonkey-2.0.11/seamonkey-2.0-bin terminated
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/seamonkey/+bug/723830/+subscribe
>

@#15: Because that page contains a multi-line textarea. The default in seamonkey is to enable spellchecking for multi-line textareas, so as long as the spellchecking is broken seamonkey will crash as soon as you visit a page with a multiline textarea on it.

SeaMonkey also crashes when you try to watch a YouTube video (eg: http://www.youtube.com/watch?v=XFSVnEYp6gU ).

But it does not crash on all Flash content.

Ok sorry, this is only caused by the spell checker because of YouTube's text boxes.

Disabled spell checking (as told above) in Edit > Preferences > Languages > Spelling and no more crash.

Thanks!

This bug was also reported to Mozilla's Bugzilla:
https://bugzilla.mozilla.org/show_bug.cgi?id=653914

Since it is a bug in Ubuntu's Seamonkey package, and not in Seamonkey itself, the bug rightfully got an "invalid" state. However, the person who marked it as "invalid" also gave a possible reason for the bug:

> Invalid => Downstream problem. Probably Ubuntu are shipping a newer version of
> the Hunspell libraries which SeaMonkey 2.0.x isn't designed to work with.

Not sure if this helps.

Confirmed in Chatzilla also. Disabling spell checking in Chatzilla Preferences -> Global -> Spellcheck the inputbox, Chatzilla crashed no more.

I think this is fixed upstream by http://hg.mozilla.org/releases/mozilla-2.0/rev/c5b3d7beca8c#l17.29 . The problem was that struct hentry ended with a single char that was used as a variable-length array, and writing multiple chars into the space allocated for a single char triggered fortify checks (even though there was enough space after the end of the struct). Now it ends with a char[1], which fortify recognizes as represending a flexible array.

The original hunspell patch (for the fortify check) was
  http://sourceforge.net/support/tracker.php?aid=2812045
and I just forwarded the other half of Konstantin’s patch from comment 6 (the incorrect descl computation) to
  http://sourceforge.net/support/tracker.php?aid=3304798

Based on the change in hunspell that Anders referenced, I think the attached patch should fix the issue without disabling the _FORTIFY_SOURCE checks.

I'm currently running a test build in my PPA (https://launchpad.net/~broder/+archive/ubuntu-tests), so we'll see what falls out.

Well, that didn't work.

I think you also need to update mozilla/extensions/spellcheck/hunspell/src/htypes.hxx to use char[1] word instead of char word (a la http://hg.mozilla.org/releases/mozilla-2.0/rev/c5b3d7beca8c#l17.29), which probably also means that other files using hentry need to get updated (csutil.hxx in particular, at the very least)

I can't spend any more time on this now, but I don't think this patch is ready to go yet, so I'm going to unsubscribe ~ubuntu-sponsors. If somebody else comes up with a patch that they think works, feel free to resubscribe.

Incidentally, micahg pointed out on IRC that he would be shortly
updating seamonkey to 2.1 shortly:

 [9:59 AM] <micahg> broder: regarding seamonkey, we'll need to push
2.1 when it's released to the stable releases, so idk if an SRU is
worthwhile
 [10:00 AM] <micahg> 2.1 uses the newer hunspell

...which should independently fix this bug, so I'm not planning to
spend any more time on it.

SeaMonkey 2.1 is now out. Is anyone working on adding it to Ubuntu? It would be nice to get this spellchecker bug fixed once and for all...

I am also having the same problem.

I removed this file.
/usr/lib/seamonkey-2.0.11/components/libspellchecker.so

Before removing, I have kept a copy of it in case it is required later.

At the moment, error is not coming now.

Seems to solve the problem.
I updated the package. My versions is now 2.0.13.
This version is still buggy, but removing
/usr/lib/seamonkey-2.0.13/components/libspellchecker.so
seems to solve the problem.

2011/6/27 rajhanschinmay <email address hidden>

> I am also having the same problem.
>
> I removed this file.
> /usr/lib/seamonkey-2.0.11/components/libspellchecker.so
>
> Before removing, I have kept a copy of it in case it is required later.
>
> At the moment, error is not coming now.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (775160).
> https://bugs.launchpad.net/bugs/723830
>
> Title:
> seamonkey-2.0-bin assert failure: *** buffer overflow detected ***:
> /usr/lib/seamonkey-2.0.11/seamonkey-2.0-bin terminated
>
> Status in Hunspell:
> Unknown
> Status in SeaMonkey: all-in-one Internet application suite:
> Invalid
> Status in “seamonkey” package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: seamonkey
>
> Seamonkey has consistently crashed since I started using the Alpha
> builds in the 11.04 series. Previous versions of Seamonkey with
> Kubuntu or Xubuntu were quite reliable; since Alpha testing, even
> accessing a few Web pages has been difficult. Looks like a buffer
> overflow is the culprit. Until the debugger came up, I had no
> diagnostic information to provide; otherwise I would have sent it in
> much sooner.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 11.04
> Package: seamonkey-browser 2.0.11+build1+nobinonly-0ubuntu2
> ProcVersionSignature: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5
> Uname: Linux 2.6.38-4-generic i686
> NonfreeKernelModules: wl
> Architecture: i386
> AssertionMessage: *** buffer overflow detected ***:
> /usr/lib/seamonkey-2.0.11/seamonkey-2.0-bin terminated
> Date: Wed Feb 23 12:16:55 2011
> ExecutablePath: /usr/lib/seamonkey-2.0.11/seamonkey-2.0-bin
> InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
> ProcCmdline: /usr/lib/seamonkey-2.0.11/seamonkey-2.0-bin
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> Signal: 6
> SourcePackage: seamonkey
> StacktraceTop:
> __kernel_vsyscall ()
> raise () from /lib/libc.so.6
> abort () from /lib/libc.so.6
> ?? () from /lib/libc.so.6
> __fortify_fail () from /lib/libc.so.6
> Title: seamonkey-2.0-bin assert failure: *** buffer overflow detected ***:
> /usr/lib/seamonkey-2.0.11/seamonkey-2.0-bin terminated
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hunspell/+bug/723830/+subscriptions
>

Hopefully SeaMonkey 2.1 will be added fast to the repository because having no spell checker is quite annoying. I didn't realized how much I rely on it...

SeaMonkey 2.2 is out now... It will this error. Hope it's added fast!!!

*will fix this error

You can install Seamonkey 2.2 from Launchpad PPA.
Have a look at https://launchpad.net/~seamonkey2/+archive/seamonkey2-pre

Cool! Thanks!

I do not know is related to the same bug, but disabling spell checking all work well, but I cannot send emails.
I can compose the messages, fill the address, but pressing Send button, Seamonkey crash.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.18) Gecko/20110412 SeaMonkey/2.0.13

@efa
Your problem sending email seems unrelated to this bug. To get help with it, I recommend posting a question (https://answers.launchpad.net/ubuntu/+source/seamonkey/+addquestion).

Have you enabled the "Check spelling before sending" option in
Preferences->Composition?

On 30 July 2011 07:11, efa <email address hidden> wrote:
> I do not know is related to the same bug, but disabling spell checking all work well, but I cannot send emails.
> I can compose the messages, fill the address, but pressing Send button, Seamonkey crash.
> Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.18) Gecko/20110412 SeaMonkey/2.0.13
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/723830
>
> Title:
>  seamonkey-2.0-bin assert failure: *** buffer overflow detected ***:
>  /usr/lib/seamonkey-2.0.11/seamonkey-2.0-bin terminated
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hunspell/+bug/723830/+subscriptions
>

worked, disabling "Check spelling before sending", now I can send, thank you

another crash that seems related:
Opening google language tools always crash.
(www.google.com, follow the link at the right of text entry search box, below advanced search)
I cannot find what to disable to continue use Seamonkey 2.0.13

Hello!

 It` s time to move to the present and install Seamonkey 2.2..if U use Ubuntu it will adopt personal data from 2.013. and not crash in gtranslator ( donno how other operating system `ll act).

Kind Regards
Me

in my case, I prefer to keep always the software updated to the last stable version, I'll do on all OS but Linux Debian and Ubuntu.
The problem is that Mozilla fundation do not ufficially release the package in standard Debian format, and installing the tar.gz create problem to the package manager.
I do not know why they do not release the software for Linux in .deb and .rpm, but I think this keep lot of Linux users out of last version of Mozilla software.

Yo

  I don`t have other distro experience, sorry, recently had fun with test of Seamonkey 2.3 as it didn`t recognise adobe flash player plugin, some good man advised me to change symlink, but couldn`t find it, am sort of linux consumer with little developer ambition..

Kind Regards

This bug was fixed in the package seamonkey - 2.4.1-0ubuntu1

---------------
seamonkey (2.4.1-0ubuntu1) oneiric; urgency=low

  [ Joe Lesko <email address hidden> ]
  * New upstream release v2.4.1 (SEAMONKEY_2_4_1_RELEASE) (LP: #832791, #723830)
  * Revise build system based on thunderbird
  * Only build seamonkey and seamonkey-gnome-support binary packages
    - update debian/control
  * Allow Seamonkey to build on lucid because of the old yasm library
    - update debian/rules
  * Changed MOZ_BUILD_UNOFFICIAL to 0 so the Seamonkey name would show up in
    seamonkey.desktop
    - update debian/rules
  * Drop old patches
    - update debian/patches/series
  * Clean up some of the lintian warnings
    - add debian/seamonkey.lintian-overrides.in
  * Add Vcs-Bzr
    - update debian/control{,in}

  [ Micah Gersten <email address hidden> ]
  * Add patches from Thunderbird to prevent FTBFS on armel/powerpc
    - add debian/patches/build-fix-for-no-ENABLE_YARR_JIT.patch
    - add debian/patches/compile-pldhash-as-C++.patch
    - add debian/patches/only-add-ENABLE_JIT-to-CXXFLAGS-if-jit-is-enabled.patch
    - add debian/patches/printf-fix.patch
    - update debian/patches/series
  * Add Conflicts on old Seamonkey packages so they are removed from the system
    - update debian/control{,in}
  * Fix Vcs-Bzr location
    - update debian/control{,in}
  * Add Homepage to control file
    - update debian/control{,in}
 -- Joe Lesko <email address hidden> Tue, 11 Oct 2011 03:49:30 -0500

Getting error

/usr/lib/seamonkey-2.0.13/components/libspellchecker.so

Check this article:
https://answers.launchpad.net/ubuntu/+source/seamonkey/+question/156671

Possible solution:
Keep a backup of the following file by using command.

sudo cp /usr/lib/seamonkey-2.0.11/components/libspellchecker.so /usr/lib/seamonkey-2.0.11/components/libspellchecker.so.back

Then remove this file using
sudo rm /usr/lib/seamonkey-2.0.11/components/libspellchecker.so

At the moment, error is not coming now.
See if this one works.

Thank you.

Hello can any give the solution to the problem given below.

when i try to run the ns file, example1b.tcl , from Ns tutorial in ns2.34 installed on ubuntu 11.04,
as " ns example1b.tcl " i get the following error

*** buffer overflow detected ***: nam terminated
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(__fortify_fail+0x50)[0x650df0]
/lib/i386-linux-gnu/libc.so.6(+0xe4cca)[0x64fcca]
/lib/i386-linux-gnu/libc.so.6(__strcpy_chk+0x3f)[0x64f05f]
nam[0x814ccd0]
nam[0x815189e]
nam[0x813e48b]
nam[0x81695ee]
nam[0x816d75d]
nam[0x8140e55]
nam[0x81512c9]
nam[0x813e48b]
nam[0x8140379]
nam[0x814069c]
nam[0x8141256]
nam[0x808b0e7]
nam[0x808b0b9]
nam[0x808c02b]
nam[0x8061f81]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x581e37]
nam[0x804eb11]
======= Memory map: ========
00110000-00127000 r-xp 00000000 08:07 1055097 /usr/lib/i386-linux-gnu/libxcb.so.1.1.0
00127000-00128000 r--p 00016000 08:07 1055097 /usr/lib/i386-linux-gnu/libxcb.so.1.1.0
00128000-00129000 rw-p 00017000 08:07 1055097 /usr/lib/i386-linux-gnu/libxcb.so.1.1.0
001d3000-001d5000 r-xp 00000000 08:07 1054949 /usr/lib/i386-linux-gnu/libXau.so.6.0.0
001d5000-001d6000 r--p 00001000 08:07 1054949 /usr/lib/i386-linux-gnu/libXau.so.6.0.0
001d6000-001d7000 rw-p 00002000 08:07 1054949 /usr/lib/i386-linux-gnu/libXau.so.6.0.0
001fd000-00221000 r-xp 00000000 08:07 5899110 /lib/i386-linux-gnu/libm-2.13.so
00221000-00222000 r--p 00023000 08:07 5899110 /lib/i386-linux-gnu/libm-2.13.so
00222000-00223000 rw-p 00024000 08:07 5899110 /lib/i386-linux-gnu/libm-2.13.so
00249000-00265000 r-xp 00000000 08:07 5899060 /lib/i386-linux-gnu/ld-2.13.so
00265000-00266000 r--p 0001b000 08:07 5899060 /lib/i386-linux-gnu/ld-2.13.so
00266000-00267000 rw-p 0001c000 08:07 5899060 /lib/i386-linux-gnu/ld-2.13.so
00268000-0026c000 r-xp 00000000 08:07 1054957 /usr/lib/i386-linux-gnu/libXdmcp.so.6.0.0
0026c000-0026d000 r--p 00003000 08:07 1054957 /usr/lib/i386-linux-gnu/libXdmcp.so.6.0.0
0026d000-0026e000 rw-p 00004000 08:07 1054957 /usr/lib/i386-linux-gnu/libXdmcp.so.6.0.0
00359000-00373000 r-xp 00000000 08:07 5899101 /lib/i386-linux-gnu/libgcc_s.so.1
00373000-00374000 r--p 00019000 08:07 5899101 /lib/i386-linux-gnu/libgcc_s.so.1
00374000-00375000 rw-p 0001a000 08:07 5899101 /lib/i386-linux-gnu/libgcc_s.so.1
00480000-0055f000 r-xp 00000000 08:07 1055080 /usr/lib/i386-linux-gnu/libstdc++.so.6.0.14
0055f000-00563000 r--p 000de000 08:07 1055080 /usr/lib/i386-linux-gnu/libstdc++.so.6.0.14
00563000-00564000 rw-p 000e2000 08:07 1055080 /usr/lib/i386-linux-gnu/libstdc++.so.6.0.14
00564000-0056b000 rw-p 00000000 00:00 0
0056b000-006c5000 r-xp 00000000 08:07 5899073 /lib/i386-linux-gnu/libc-2.13.so
006c5000-006c6000 ---p 0015a000 08:07 5899073 /lib/i386-linux-gnu/libc-2.13.so
006c6000-006c8000 r--p 0015a000 08:07 5899073 /lib/i386-linux-gnu/libc-2.13.so
006c8000-006c9000 rw-p 0015c000 08:07 5899073 /lib/i386-linux-gnu/libc-2.13.so
006c9000-006cc000 rw-p 00000000 00:00 0
00782000-00784000 r-xp 00000000 08:07 5899083 /lib/i386-linux-gnu/libdl-2.13.so
00784000-00785000 r--p 00001000 08:07 5899083 /lib/i386-linux-gnu/libdl-2.13.so
00785000...