Seamonkey-2.38 has random segmentation faults. See upstream Mozilla Bug 1216765, "Random Segmentation Fault with Seamonkey" And, somebody removed the last stable version www-client/seamonkey-2.35 ebuild from the main tree. (I'll attach the seamonkey-2.35.ebuild to this bug for other users who may have synced their tree, removing the 2.35 version.) Reproducible: Always
Created attachment 416878 [details] seamonkey-2.35.ebuild Last known stable version of Seamonkey, in reference to Mozilla Bug 1216765, "Random Segmentation Fault with Seamonkey"
Sorry but seamonkey-2.35 won't come back into portage. It has way too many security bugs which am unwilling to backport from later versions. Users can still choose to use seamonkey-2.39 which will be stabilized soon.
Wonderful. Now we're all screwed. See Bug #562930, "www-client/seamonkey-2.38: random crashes with segmentation fault" See my upstream Mozilla Bug 1216765, "Random Segmentation Fault with Seamonkey" I'll revert to Dillo before I have to resorting to pulling my hair-out over trying to use Firefart!
Well that's weird, now I'm seeing the seamonkey-bin package available once again. Maybe I can further narrow this issue to a local build problem, versus other problems.