On Thu, 18 Sep 2014, Stephen Allen wrote: > On Wed, Sep 17, 2014 at 06:14:43PM -0700, Patrick Bartek wrote: > > 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 > > Correct me if I'm wrong, but isn't pepperflash purpose to give > Chromium users an updated Flash since the Flash version for Linux has > been halted?
It's for Chrome, too. Same reason. FWIW: Chrome is based off Chromium code. Or so, I've read. Don't know how "close" the two are codewise. > AFAIK Google-Chrome contains it's own Flash internally, which Google > updates as necessarily automatically on ones machine. Pepperflash in Google-Chrome isn't "internal." The libpepflahplayer.so is here: /opt/google/chrome/PepperFlash. My updates/upgrades are 100% manual, but if there is a new version number of Google-Chrome-Stable and/or PepperFlash, they get upgraded like anything else would on the system. 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/20140918154040.515a5...@debian7.boseck208.net
