Yes, fix works for me. I must add though: God! Please rid us of Flash! ;) On Fri, May 7, 2010 at 9:35 AM, Evan Martin <e...@chromium.org> wrote: > I am the Chromium developer who fixed this again. > > Not that anyone cares anymore, but: the problem was that Flash breaks if > GDK_NATIVE_WINDOWS isn't set. > The first fix was to set that in our plugin process before starting Flash. > > However, GTK clears the environment variable after initializing. So > with nspluginwrapper we would set the variable, initialize GTK, and then > call into the plugin (nspluginwrapper), which would then spawn its > helper process which then would run Flash without the variable set. > > So as of today's release of Chrome we set the variable, initialize GTK, > and then immediately set the variable again before calling into the > plugin. > > It seems Firefox may have this second bug as well. > http://defect.opensolaris.org/bz/show_bug.cgi?id=15232 If I remember > tomorrow I will attempt to track down that bug in their bug tracker again. > > ** Bug watch added: defect.opensolaris.org/bz/ #15232 > http://defect.opensolaris.org/bz/show_bug.cgi?id=15232 > > -- > Clicking on items in Flash player does nothing [READ DESCRIPTION] > https://bugs.launchpad.net/bugs/410407 > You received this bug notification because you are a direct subscriber > of the bug. >
-- Clicking on items in Flash player does nothing [READ DESCRIPTION] https://bugs.launchpad.net/bugs/410407 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
