From: Vincent Untz <[email protected]> > After some discussion with Mike yesterday, and while debugging something > else that I thought was unrelated, we found a rather bad issue in > gnome-panel 2.32, which can be triggered because of libgail-gnome. > > Because libpanel-applet-2 and libpanel-applet-3 share the same symbol > names, we should avoid putting them in the same process. It turns out > that if libgail-gnome is loaded and if there's an in-process > libpanel-applet-3 applet, then it will happen. > > We can work around the issue, though: if we make sure that libgail-gnome > doesn't use any panel_applet_* symbols when it's running inside > gnome-panel, then libpanel-applet-2 won't be used. And the in-process > applets will be able to happily use the right code (ie, > libpanel-applet-3 code). > > This patch for libgail-gnome implements this hack. It's really a bad > hack, but I can't think of a better way to do this. > > Note that doing is this way should keep the bonobo applets accessible. > > Comments?
Well, I don't really know all the details related to that, but based on our last meetings: http://live.gnome.org/Accessibility/GNOME3#libgail-gnome_.28drop_for_GNOME3.29 It seems that we concluded that libgail-gnome was planned to be dropped for GNOME 3.0. Anyway, I have just CCed Li Yuan and Fernando Herrera, as probably they have more details about it, and probably we would require to update that item, in order to ensure the compatibility with the fallback mode (I guess that this is the correct name). BR === API ([email protected]) _______________________________________________ gnome-accessibility-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
