Bug 301065 – www-client/seamonkey-2.0.1 crashes when Javascript is enabled

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Robert Bradbury 2010-01-15 09:09:30 UTC]

Seamonkey-2.0.1 now crashes when attempting to use the Chrome Issues bug database and Javascript is enabled.

Reproducible: Always

Steps to Reproduce:
1. seamonkey
2. First time 2.0.1 comes up, imports settings from 1.X
3. Everything is fine, can browse around (Javascript was imported "disabled")

Actual Results:  
Browsing to specified URL regarding a problem restarting chromium.
Page displays fine.
Attempt to use preferences settings to enable Javascript.  Seamonkey crashes.

Console log (repeatable) is:
~ $ seamonkey

(seamonkey-bin:26406): GLib-WARNING **: g_set_prgname() called multiple times
INTERNAL ERROR on Browser End: Could not get the plugin manager
System error?:: No such file or directory

Errors are deemed poor when they do not specify *what* the file or directory was which was missing!



Expected Results:  
Seamonkey should run fine with Javascript enabled.

Restarting (with stracing) seamonkey with a "new" session using "about: blank" as the home page works fine.  Browsing to the specified page seems to suggest a clone is created that wants to access the plugins but doesn't offer any kind of an open call which would indicate the desired filename.  Strace will be attached.

[Comment 1 Robert Bradbury 2010-01-15 09:40:30 UTC]

Created attachment 216578 [details]
Seamonkey strace with javascript problem

[Comment 2 Robert Bradbury 2010-01-15 09:44:28 UTC]

Created attachment 216579 [details]
emerge --info

It may be worth noting that this seamonkey problem may be due to bad data imported during the 2.0.1 first time startup.  But I have no idea where to go looking for it (perhaps another set of eyes looking at the strace might help).

I have a separate (different user) seamonkey-2.0.1 session which does have Javascript enabled (though I don't think it imported any previous/other browser data) which seems to be able to function properly.

[Comment 3 Jory A. Pratt 2010-01-15 20:16:51 UTC]

(In reply to comment #2)
> Created an attachment (id=216579) [details]
> emerge --info
> 
> It may be worth noting that this seamonkey problem may be due to bad data
> imported during the 2.0.1 first time startup.  But I have no idea where to go
> looking for it (perhaps another set of eyes looking at the strace might help).
> 
> I have a separate (different user) seamonkey-2.0.1 session which does have
> Javascript enabled (though I don't think it imported any previous/other browser
> data) which seems to be able to function properly.
> 

you will need to test with a clean profile, we are unable to ensure a proper migration from one version to the next.

[Comment 4 Martin Mokrejš 2010-01-21 10:25:37 UTC]

Maybe try to get debug info out from seamonkey (either hack the ebuild or configure yourself) with "./configure --disable-optimize --enable-debug='-g3 -O0 -ggdb' --enable-debug-modules=all --enable-debugger-info-modules --enable-detect-webshell-leaks". The first two flags give you debug info in binaries and the other enable extra debug messages printed into the parent xterm.

What I usually do then is:

cd dist/bin
MOZILLA_FIVE_HOME=`pwd` XPCOM_DEBUG_BREAK=trap ./mozilla -g



BTW, the message "GLib-WARNING **: g_set_prgname() called multiple times" I see also with 1.1.18 and must be related to recent updates of some other stuff, let's say within last 1-2 months.

[Comment 5 Lars Wendler (Polynomial-C) (RETIRED) 2010-04-11 14:48:47 UTC]

Does this still happen with seamonkey-2.0.4?

[Comment 6 Lars Wendler (Polynomial-C) (RETIRED) 2010-05-02 16:48:43 UTC]

Please reopen this bug in case it still isn't fixed.