It shouldn't re-enable itself. That's a regression. (#150596)zer0ed wrote:I'm wondering if something in the plugin list is "pushed" from the google end of things. Maybe it's something that they changed upstream today.
I just noticed it stopped working in the afternoon here (eastern standard time).
$ ls -alh .config/google-chrome/PepperFlash/
... Feb 1 20:41 188.8.131.52/
$ grep chrome /var/log/dpkg.log.1
2013-01-30 22:31:39 status installed google-chrome-unstable:amd64 26.0.1397.2-r179372
zer0ed wrote:Apparently it's a problem for many users of different distros. I've just checked the official Chrome forum and there is a few posts all recent today.
One solution is to delete the pepperflash directory in ~/.config/google-chrome
av8r0023 wrote:I'm also having this problem. I disabled the libpepflashplayer and everything seems to be working again, but... Now it's running an older version of flash, 184.108.40.206. The only reason I switched to Chrome over Firefox is flash updates. So confused? Guess I'll have to take up my beef with Google.
Adobe Flash Player (2 files) - Version: 220.127.116.11
Shockwave Flash 11.5 r31
Users browsing this forum: No registered users and 12 guests