On Sat, 20 Sep 2014, Paul van der Vlis wrote:

> op 18-09-14 03:14, Patrick Bartek schreef:
> > Anyone else experiencing this?  Haven't found any reports so far.
> > Chrome & Pepper ran fine before update/upgrade a few days ago.
> > Figured I'd check before I started mucking about the system trying
> > to fix it.
> > 
> > Downloaded .deb directly from Google for the install which was about
> > 18 months ago. System always kept up to date.
> > 
> > Wheezy 7.6 (64-bit).  Openbox 3.5.0-7 WM Only.  No other gui
> > environments installed.
> > Chrome 37.0.2062.120 (64-bit)
> > libpepflashplayer.so 15.0.0.152
> 
> The newest pepperflashplugin links against GLIBC_2.14. So don't use
> the lastest version, or you need a newer glibc.

Yes, I discovered this.  Wheezy uses 2.13.  But why PepperFlash was
linked to the library used in Testing instead of Stable, I don't know.
Compulsive-obsessive behavior that one MUST have the newest of
EVERYTHING?  New Toy Syndrome?  Newer is Better myth? ;-)  Something
I've never understood.  If it works, why replace it?  

> This is what I do:
> 
> First install pepperflashplugin-nonfree when it's not installed.
> Then do this as root:
> ----------
> cachedir="/var/cache/pepperflashplugin-nonfree"
> debfile="google-chrome-stable_36.0.1985.143-1_amd64.deb"
> cd /tmp/
> wget https://vandervlis.nl/files/$debfile
> dpkg-deb -x $debfile unpackchrome
> sofile=unpackchrome/opt/google/chrome/PepperFlash/libpepflashplayer.so
> mv -f $sofile /usr/lib/pepperflashplugin-nonfree
> chown
> root:root /usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so
> chmod 644 /usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so mv
> $debfile $cachedir ----------
> 
> Then restart Chromium and flash should work correct.
> Most code comes from: /usr/sbin/update-pepperflashplugin-nonfree

Thanks.  I'll check into this "fix."  Unfortunately, I think, I'll be
stuck with an "old" version of Chrome/Pepperflash forever, since I'll
never be able to upgrade it on my Wheezy system because of the 2.14
problem.  I've read it's possible to run 2.14 and 2.13 on the same
system, but I'm wary of that option.  More research needed.

Thanks, again.

B


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140920090136.52787...@debian7.boseck208.net

Reply via email to