GNOME Bugzilla – Bug 621771
SIGSEGV in nspluginscan due to uninitialized gthread
Last modified: 2010-11-16 13:00:20 UTC
As described in bug #606775, recent glib releases (2.24.1 in my case) rely on the gthread subsystem being initialized in gio and gobject. This assumption doesn't necessarily hold for the totem ns browser plugin, causing nspluginscan from KDE 3.5 to crash with a SIGSEGV. The core reason is that aquiring a lock in g_content_type_get_description results in a NULL function call. Detailed information about this crash can also be found in https://bugs.gentoo.org/324237 . I believe that it is now the responsibility of the totem plugin library to ensure that the gthread library is properly initialized before gio functions are called. The application loading the plugin might not have done so.
Created attachment 163824 [details] [review] Initialise the GType system when called into Add calls to g_type_init() in the plugin entry points so that GThread is initialised if not already, so that GIO calls work as expected. Note that this requires GLib 2.24 to work properly, so only done in master (gnome-2-30 depends on GLib 2.22)
Attachment 163824 [details] pushed as dc894da - Initialise the GType system when called into
*** Bug 634934 has been marked as a duplicate of this bug. ***