Comment 3 for bug 598780

To clarify something; I added this as a bug against gtk+ because I think it's the mechanism that's broken not necessarily appmenu-gtk specifically - I think it's doing what the mechanism is expecting, but I really don't think that mechanism is right.

Also this produces a whole stream of errors - this mechanism gets triggered 10s-100s of time for each application start;
besides the fact it can't do anything for performance even when it's working correctly, it's producing tonnes of errors in this case.
It should be checking this at most once on any app startup.

I believe the 'undefined symbol: menu_proxy_module_load (firefox-bin:16169):'

is coming from the code in 043_ubuntu_menu_proxy.patch in ubuntu_menu_proxy_module_real_load
Nothing checks the return value of _gtk_find_module so the call to g_module_open (being passed null) returns the main program as a module - and that's where the symbols get looked up.

The 'Failed to load type module' is probably from 'ubuntu_menu_proxy_module_get' in the same file; the (null) is again coming from an unchecked return from _gtk_find_module.

Dave