SilverWav's Journal

The best is yet to come…

Note: Ubuntu Lucid 10.04 Flash

with 3 comments

Buttons not working on iPlayer, Flash.

gksudo gedit /usr/lib/nspluginwrapper/i386/linux/npviewer

Add this line:

export GDK_NATIVE_WINDOWS=1

Before this line:

. /usr/lib/nspluginwrapper/noarch/npviewer

Example:

#!/bin/sh
TARGET_OS=linux
TARGET_ARCH=i386
export GDK_NATIVE_WINDOWS=1
. /usr/lib/nspluginwrapper/noarch/npviewer

______________________________

Advertisements

Written by SilverWav

March 21, 2010 at 9:38 pm

3 Responses

Subscribe to comments with RSS.

  1. That did the trick for me!

    Coops

    April 13, 2010 at 9:08 pm

    • Glad to help :-)

      Just surprised that this is still needed tbh, it was the same in 9.10!

      [EDIT]
      Looked into this a little more and the issue is that only Adobe can change libflashplayer.so and they haven’t.

      SilverWav

      April 13, 2010 at 9:19 pm

  2. Some background on this issue.
    ______________________________

    Comment 225 for bug 410407
    pablomme wrote on 2010-03-02: #225

    > Is it a problem with GTK+ or ia32-libs?

    The big picture here is that GTK+ changed the way it does certain things, intentionally and as an improvement. What should happen then is that every piece of software that relies on GTK+ would be updated to cope with/take advantage of the new stuff. And so it has happened with all FOSS projects using GTK+. However, nobody but Adobe can change libflashplayer.so, and they haven’t. That is THE problem, and THE solution lies with Adobe.

    Now, for workarounds. The GTK+ change came with the ability to revert to the old behaviour via environment variables. A possible workaround would be to modify web browsers (and everything else that uses libflashplayer.so) to set up their environment so that the GTK+ calls made from within the Flash player stick to legacy behaviour. Chromium (if the reports above are correct) has done this, others haven’t. Remember that this situation is supposed to be temporary – one would expect Adobe to *eventually* fix libflashplayer.so – so it might not be worth for browsers to go through this.

    Another workaround is applicable to 64-bit systems, where a 32-bit libflashplayer.so is used (this is sub-optimal, and again nothing can be done because of Flash being proprietary). The interface between the 64-bit browser and the 32-bit plugin is nspluginwrapper. The 32-bit plugin then uses 32-bit libraries (including GTK+), which are gathered in this thing called ia32-libs. By modifying the nspluginwrapper scripts, one can directly modify the environment under which libflashplayer.so is run, without need to modify the browser itself.

    To answer your question, there is no problem with GTK+, there is a problem with Flash not being updated to cope with updates to GTK+. And ia32-libs simply mirrors the current versions of common libraries, it’s not to be blamed either.

    ______________________________

    SilverWav

    April 13, 2010 at 11:11 pm


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: