Dale: >This appears to be a Seamonkey issue and I have no clue where to >start. I ran Seamonkey in a console as a user.
To recall. You have renamed ~/.mozilla, SM newly emerged so that it creates a new ~/.mozilla at the next start, not installed any extension and have now only the default plugin in about:plugins. And your SM crashes at http://wireless.att.com/ Interesting. :) >This is what I got for a error: > >/usr/libexec/mozilla-launcher: line 119: 16912 Segmentation fault >$(type -P aoss) "$mozbin" $xulparams "$@" >seamonkey-bin exited with non-zero status (139) > >I can't help but notice xulpaprams in there. Is that related to >xulrunner? That give you any ideas? No, that doesn't help. Before i disabled the crashreporter in my SM2 with ----- ~/.mozconfig ----- ac_add_options --disable-crashreporter --------------- i got a popup window in case of a crash with informations, which could be sent to mozilla.org to automatically generate a meaningful report. But SM1? I don't remember. Too much time. But you had modified your profile and your prefs.js by hand. Was not necessary for testing the URL. Create a new profile with Tools->Switch Profile->Manage Profiles..., switch to it and do nothing else than calling http://wireless.att.com/ in the browser. Crash again? If so, then i would fetch http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/1.1.16/seamonkey-1.1.16.en-US.linux-i686.tar.gz, put it in a new dir in home, e.g. ~/.sm-test, decompress it there, change to the dir seamonkey and issue there ./seamonkey after renaming ~/.mozilla to e.g. ~/.mozilla-old-2. Hm, is 'issue' the right verb? *g* And, you had never run SM with sudo, right? This could severely damage your profile. Hartmut
