[SATLUG] SeaMonkey (Mozilla) Browser Crash

Howard Haradon hharadon at gmail.com
Sat Oct 4 13:23:47 CDT 2008

> Message: 6
> Date: Fri, 03 Oct 2008 11:16:12 -0500
> From: Bruce Dubbs <bruce.dubbs at gmail.com>
> Subject: Re: [SATLUG] SeaMonkey (Mozilla) Browser Crash
> To: The San Antonio Linux User's Group Mailing List
>        <satlug at satlug.org>
> Message-ID: <48E6454C.2000501 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Howard Haradon wrote:
>> Hello,  This AM I had 2 unexplained crashes (the
>> window just disappeared) of my internet browser.
>> I have recently installed Puppy 4.0 with kernel
>> and use SeaMonkey 1.1.11, Mozilla/5.0 (X11; U;
>> Linux i686; en-US; rv:  This SeaMonkey
>> version is the newest stable ver. that I installed using
>> the .tar file from their web site.  It did not come thru
>> Puppy's package manager.  BTW, Synaptic or
>> apt seem to be missing in Puppy as well as any
>> complete repository system ??
>> Anyway, I poked around and found only one
>> message after each crash that might point to the
>> problem in /tmp/xerrs.log :
>> /usr/local/seamonkey/run-mozilla.sh: line 131:  2142
>> Segmentation fault      "$prog" ${1+"$@"}
>> EXIT="Ready"
>> Both time the message was the same.
>> At the time of these problems, I was fussing with an
>> email reply in Gmail, fumbling the arrow keys, CTRL,
>> and/or the Ins key on a standard desktop keyboard.
>> I have tried several key combos, but cannot duplicate
>> the crash.  I had some memory problems earlier on this
>> PC, but have done extensive test of its current DRAM,
>> and they *look* solid.

Bruce wrote:
> I have been using seamonkey 1.1.11 since July 22 without problem, but I built it
> from source instead of downloading a binary.  To me, the most likely cause of
> the problem is a plugin or library.  What plugins do you have?
>   -- Bruce

I see these 4 plugins when I do about:plugins.
Shockwave Flash 9.0 r48
Scalable Vector Graphics, as handled by RSVG-2.18.2. Views SVG images.
Java(TM) Plug-in 1.6.0_07-b06

Now, in looking at /tmp/xerrs.log, there are 9 lines like the following:

Flash Player: Warning: environment variable G_FILENAME_ENCODING is set
and is not UTF-8

Perhaps flash player is the culprit?

Thanks,  Howard

More information about the SATLUG mailing list