firefox segmentation fault - libgail.so: wrong ELF class: ELFCLASS64

[Tremaine Lea]

This happens 100% of the time on the Facebook page where you upload photos

 firefox
Gtk-Message: Failed to load module "gail": /usr/lib/gtk-2.0/modules/libgail.so: wrong ELF class: ELFCLASS64
Gtk-Message: Failed to load module "gail": /usr/lib/gtk-2.0/modules/libgail.so: wrong ELF class: ELFCLASS64
Gtk-Message: Failed to load module "atk-bridge": /usr/lib/gtk-2.0/modules/libatk-bridge.so: wrong ELF class: ELFCLASS64
GCJ PLUGIN: thread 0x1a25c70: NP_Initialize
GCJ PLUGIN: thread 0x1a25c70: NP_Initialize: using /usr/lib/classpath/gappletviewer.
GCJ PLUGIN: thread 0x1a25c70: NP_Initialize return
GCJ PLUGIN: thread 0x1a25c70: GCJ_New
GCJ PLUGIN: thread 0x1a25c70: plugin_data_new
GCJ PLUGIN: thread 0x1a25c70: plugin_data_new return
GCJ PLUGIN: thread 0x1a25c70: plugin_get_documentbase
GCJ PLUGIN: thread 0x1a25c70: plugin_get_documentbase return
gcjwebplugin.cc:978: thread 0x1a25c70: Error: Failed to read line from whitelist file.
GCJ PLUGIN: thread 0x1a25c70: NP_GetValue
GCJ PLUGIN: thread 0x1a25c70: NP_GetValue: returning plugin description.
GCJ PLUGIN: thread 0x1a25c70: NP_GetValue return
GCJ PLUGIN: thread 0x1a25c70: GCJ_GetValue
GCJ PLUGIN: thread 0x1a25c70: GCJ_GetValue: returning TRUE for NeedsXEmbed.
GCJ PLUGIN: thread 0x1a25c70: GCJ_GetValue return

(firefox:4323): Gdk-CRITICAL **: gdk_window_get_user_data: assertion `window != NULL' failed

(firefox:4323): Gtk-CRITICAL **: gtk_container_add: assertion `GTK_IS_CONTAINER (container)' failed

(firefox:4323): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed

(firefox:4323): Gtk-CRITICAL **: gtk_socket_get_id: assertion `GTK_WIDGET_ANCHORED (socket)' failed
Segmentation fault

[Alexander Sack (asac)]

can you try to narrow down which plugin causes this? Is it really the gappletviewer that triggers the crash? Maybe its not plugin related at all and you have a bad extension installed? Try to disable them.

[John Vivirito (gnomefreak)]

I;m assuming it is on firefox-3.0 not 2.0

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!