I am trying to adapt the instructions from here, here, and here to install the debug version of the flash player on my Ubuntu 13.04 installation such that Chrome 30.0.1599.66 can use it.

Interestingly, it appears that I already have the official Adobe flash plugin installed and useable by Chrome, so the problem changes from "installing flash" to "replacing regular flash with the debugger version".

enter image description here

So I need to replace libflashplayer.so with the one downloaded from Adobe. Sounds simple.

I selected this file (Linux Flash Player 11.2 Plugin content debugger), decompressed it and installed the Flash Player Local Settings configurations files as directed.

I then replaced /usr/lib/flashplugin/installer/libflashplayer.so with the version included in the debugger install, and restarted Chrome. To my surprise, the second Adobe Flash Player listing in chrome://plugins just disappeared!

enter image description here

It's as if Chrome doesn't like the debugger plugin for some reason. I tried various things to get the debugger plugin to appear but to no avail:

  • chmod +rx libflashplayer.so
  • nspluginwrapper -i libflashplayer.so (Results in error no appropriate viewer found for libflashplayer.so)
  • mkdir /opt/google/chrome/plugins; mv libflashplayer.so /opt/google/chrome/plugins

How can I get Chrome to recognize the Flash debugger plugin?

  • 64-bit. Linux ckleinlx 3.8.0-31-generic #46-Ubuntu SMP Tue Sep 10 20:03:44 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
    – Cory Klein
    Oct 3, 2013 at 19:20

2 Answers 2


I finally figured it out while trying to get it to work for Firefox! This is based from the direction I found here.

sudo apt-get install ia32-libs nspluginwrapper
sudo mkdir /usr/lib/flash-plugin/
wget http://fpdownload.macromedia.com/pub/flashplayer/updaters/11/flashplayer_11_plugin_debug.i386.tar.gz
tar xzvf flashplayer_11_plugin_debug.i386.tar.gz
sudo cp libflashplayer.so /usr/lib/flash-plugin/
sudo chmod 775 /usr/lib/flash-plugin/libflashplayer.so
cd /usr/lib/mozilla/plugins
rm -rf npwrapper.libflashplayer.so # Not sure if this part is necessary or not
sudo ln -s /usr/lib/flash-plugin/libflashplayer.so .
sudo chmod 777 libflashplayer.so
sudo nspluginwrapper -i /usr/lib/flash-plugin/libflashplayer.so
#                       ^ Use the full path here as a relative path won't work!

Now restart Chrome and Firefox. Both should be using the debug version of the flash plugin!

  • Still testing, but I think what I needed was to install libnss3:i386, since ia32-libs isn't available in ubuntu 14.04
    – isaaclw
    May 22, 2014 at 22:17
  • I also needed to install firefox:i386. Since it looks like I'll be using 32 bit firefox for a while, I installed p11-kit:i386 and libpam-pkcs11:i386 to help squash some warning/errors.
    – isaaclw
    May 23, 2014 at 17:56
  • Also note: the only thing in my /usr/lib/mozilla/plugins/ folder is the 'npwrapper.libflashplayer.so' file that nspluginwrapper created.
    – isaaclw
    May 23, 2014 at 17:58

Chromium doesn't allow you since it's a 32-bits library:

$ file /usr/lib/flashplugin-installer/libflashplayer.so /usr/lib/flashplugin-installer/libflashplayer.so.bk
/usr/lib/flashplugin-installer/libflashplayer.so:    ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped
/usr/lib/flashplugin-installer/libflashplayer.so.bk: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped

(Obviously, the .bk is my backup)

I would use the 32-bit system to debug Flash.

(I don't have a 32-bit system right now, will update later)

  • It doesn't have to be that way, Braiam: file /opt/google/chrome/chrome -> /opt/google/chrome/chrome: ELF 64-bit LSB shared object and .mozilla/plugins/libflashplayer.so: ELF 64-bit LSB shared object.
    – goldilocks
    Oct 3, 2013 at 21:12
  • @goldilocks sorry, what?
    – Braiam
    Oct 3, 2013 at 21:41
  • You've said that the problem has something to do w/ 32 vs 64 bit binaries, and I'm just pointing out both things (chrome and flash) are available in both versions. The only clue Cory has provided is a link to the 32-bit debugger version. You may be right, but in that case, Cory obviously does not understand the difference and you didn't explain it. What? What? Who knows? Why bother? Do you see the point I am vaguely hinting at? ;/ You've perhaps intuited the real problem! But you did not actually say what you intuited. What is it? ;/ ;/
    – goldilocks
    Oct 4, 2013 at 0:06

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .