registry team mailing list archive
-
registry team
-
Mailing list archive
-
Message #28003
[Bug 538796] Re: cannot open Firefox/Chromium/Google Chrome when libmoon is installed
Just to add to the stack trace in comment #37, I installed the dbg
packages and generated the same segfault. The important extra
information is:
Attempting to load the system libmoon
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb4eaab70 (LWP 10083)]
0xa9b50cfc in __static_initialization_and_destruction_0 () at /build/buildd/openjdk-6-6b20-1.9.1/build/../plugin/icedteanp/IcedTeaNPPlugin.cc:237
237 /build/buildd/openjdk-6-6b20-1.9.1/build/../plugin/icedteanp/IcedTeaNPPlugin.cc: No such file or directory.
in /build/buildd/openjdk-6-6b20-1.9.1/build/../plugin/icedteanp/IcedTeaNPPlugin.cc
(gdb) bt
#0 0xa9b50cfc in __static_initialization_and_destruction_0 () at /build/buildd/openjdk-6-6b20-1.9.1/build/../plugin/icedteanp/IcedTeaNPPlugin.cc:237
#1 global constructors keyed to IcedTeaNPPlugin.cc(void) () at /build/buildd/openjdk-6-6b20-1.9.1/build/../plugin/icedteanp/IcedTeaNPPlugin.cc:2439
#2 0xa9b6f68d in __do_global_ctors_aux () from /usr/lib/jvm/java-6-openjdk/jre/lib/i386/IcedTeaPlugin.so
#3 0xa9b4fb68 in _init () from /usr/lib/jvm/java-6-openjdk/jre/lib/i386/IcedTeaPlugin.so
... rest of backtrace snipped.
Of particular interest is that the segfault seems to actually be
happening in the icedtea plugin. Like everyone else that's posted above,
this only occurs when libmoon is installed. At least there's a file/line
number to look at now.
--
cannot open Firefox/Chromium/Google Chrome when libmoon is installed
https://bugs.launchpad.net/bugs/538796
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Chromium.