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. ** Patch added: "seamonkey_2.0.13+nobinonly-0ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/seamonkey/+bug/723830/+attachment/2153563/+files/seamonkey_2.0.13%2Bnobinonly-0ubuntu1.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
