On 6/24/17, Curt <cu...@free.fr> wrote: > On 2017-06-24, Maureen L Thomas <silver...@verizon.net> wrote: >> >> Are there no fixes to this problem? I have tried everything that I know >> how to do. Still nothing and it doesn't matter which browser I use. It >> worked just fine in Jessie and I am really sorry it upgraded to Stretch. >> > > Have you verified that 'update-alternatives --list flash-mozilla.so' > > returns > > /usr/lib/flashplugin-nonfree/libflashplayer.so > or > /home/user_maureen/.mozilla/plugins/libflashplayer.so > > ?
Maureen, I was wondering the same (not so "simple") thing: Did libflashplayer.so eventually and ultimately install in the right place in your file hierarchy? In years past, I've gone so far as to put it everywhere I thought rational until it would work. My method of operation was/is to target any sub-directories with the name "plugins" for each and every browser I used. Eventually I picked one higher profile location for the "real", original libflashplayer.so file. I then symlinked everywhere else so that I only had to replace that one primary file on upgrades. It never caused me noticeable conflicts, but that might not be the same experience for others. The only caveat I've faced so far is that I have to remember to repeat that process when I start from scratch with each new, regular debootstrap (full operating system install) attempt. Another thing is there is at least one related "toggle" usually available in a browser's preference settings. It would be about plugins if it exists. It would be about enabling/disabling/deleting and is something that it never hurts to check off on a debug list. Just thinking out loud... :) Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with duct tape *
