Mailinglist Archive: opensuse (3031 mails)

[Tero Pesonen <teropesonen@xxxxxxxxxxxx>]

On Tuesday 05 February 2008, Jonathan Wilson wrote:
> Hello,
>
> Because of the nature of my work I use both Seamonkey and FireFox
> (and sometimes Konqeror) all at the same time. On SuSE 10.2 Seamonkey
> was very stable, I never had problems with it. I'm pretty sure I had
> upgraded seamonkey to 1.1.7 (latest) while still on 10.2.
>
> Recently I've done a fresh reinstall with openSuSE10.3 and Seamonkey
> is pretty unstable. The worse part is that it's unpredictable and I
> can't find the source of the crash.
>
> I've been running it from a terminal window hoping to catch an
> informative
>
> error but I don't get much. Sessions always look more or less like 
this:
> :>seamonkey
>
> Flash Player: Warning: environment variable G_FILENAME_ENCODING is
> set and is not UTF-8
> Flash Player: Warning: environment variable G_FILENAME_ENCODING is
> set and is not UTF-8
> Flash Player: Warning: environment variable G_FILENAME_ENCODING is
> set and is not UTF-8
> Flash Player: Warning: environment variable G_FILENAME_ENCODING is
> set and is not UTF-8
> Flash Player: Warning: environment variable G_FILENAME_ENCODING is
> set and is not UTF-8
> /usr/bin/seamonkey: line 277: 26823 Segmentation fault      $AOSS
> $MOZ_PROGRAM $MOZ_LANG
>
>
> Sometimes it will run for a week and a half before crashing.
> Sometimes for a couple days. Sometimes for 20 minutes. It does not
> seem to be any particular site or action that causes it to crash.
>
> FireFox is not having any of these problems.
>
> Has anyone experience this sort of thing? It was crashing as soon as
> I installed of the DVD, before I installed any updates, or third
> party things. I have since upgraded to the lastest security update
> with YOU, and it's just the same. I've also added the latest flash
> and acroread from packman, but that does not seem to have made the
> situation better or worse either.
>
> Is anyone else having these problems? How can I debug this?

On my 10.3, Seamonkey Composer is anything but stable. Once it crashes 
(the program window simply disappears), Firefox, too, becomes unstable 
and will sooner or later similarly just disappear in the thin air, with 
no crash dialogue, or that wizard thing that normally follows when some 
poor AJAXed site crashes it. 

To avoid this, once Seamonkey has crashed, I have to kill gconfd-2 and 
restart Firefox and Seamonkey. Things are then back to normal. Either 
Seamonkey screws up gconfd-2, or vice versa. Either way, unless I kill 
gconfd-2 after the Seamonkey 1.1.7 crash, GTK apps will become 
unstable.

I now try to use Seamonkey as little as possible. 

Regards,
Tero Pesonen 
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx