On Sat, 2013-02-02 at 11:37 -0500, Fred James wrote: > Michael Rasmussen wrote: > > Here's the issue and workaround: > > > > Which version of Chrome? What is your CPU? IIRC, Pepper Flash is > > disabled, by default, on older CPUs. > > > > Very, very similar thread here: Google Chrome - couldn't load plugin - > > shockwave flash and a link to > > code.google.com/p/chromium/issues/detail?id=173790. It's still flagged > > as "unconfirmed" despite several me-toos. > > > > It's now "untriaged" but this comment explains the problem: > > "Unfortunately, 11.5.31.138 was pushed out via the component > > updater, and using plugins from the component updater doesn't work on > > Linux (and breaks stuff, due to the way plugins > > are loaded). :( So deleting ~/.config/google-chrome/PepperFlash should > > fix things (unfortunately falling back to .137) > > ... and since we've stopped pushing .138, it won't reappear." > > > > So if your YouTube / flashcontent is broken rm -rf > > ~/.config/google-chrome/PepperFlash > > will restore your video access. > <rant> We used to joke (at my last job, and I do mean last) that ... > "We don't test!" > "We don't document!"
The noted rm -rf worked for me -- I found the thread yesterday afternoon when I couldn't open a simple puzzle that I wanted to do after work -- (where I'm now testing and documenting the open source implementation of SSO, now OpenAM). Thanks, Mike _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
