Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Do you really need to bother with a deb package and add an external repository just to get a single libflashplayer.so file from Adobe, also considering flash is more and more useless ???
fireflashupdate.sh works perfectly and can be added as a weekly cron task even at user level (assuming the user is declared as sudoers). https://github.com/cybernova/fireflashupdate [ see README.md ]
i fixed that link.
can't stress this enough.
if a site still uses flash, one should very strongly consider if it is really necessary (or even advisable) to use that particular resource.
tried gnash a few years ago, and then again recently (as a standalone offline player) - it felt just as buggy and almost useless as then, and certainly not lighter on resources compared to adobe's.
I think it would work OK if you added the MX 17 repo to Debian, but only enabled the non-free section, since we don't have very much in it at all.
I recommended only adding the main MX repo and only the non-free section so you wouldn't get overwhelmed by the number of backports we have in the rest of the repo. You can add the others later if you want to experiment and have a system backup. 99.9% of the time you wouldn't need the antiX repo--that only provides some scripts that some of the MX-specific tools use, such as the system-snapshot tool (which probably won't work in pure Debian).
Back when Adobe wasn't updating the NPAPI version, only the PPAPI one, some one wrote a wrapper that let one use PPAPI in a Mozilla browser and it made it into Debian, but it doesn't have much point now that they update both versions in sync.
stevepusser wrote:Chrome downloads its own PPAPI flash the last I heard, but you may have to go into the settings and enable sites to use it.
Firefox was also still using NPAPI Flash instead of PPAPI the last I heard...you can try installing our MX Linux deb that installs both NPAPI and PPAPI packages and set up Chromium compatibility; it works really well: (edit: fixed link) http://mxrepo.com/mx/repo/pool/non-free ... ashplugin/
The mx17 packages are Stretch compatible.
gdebi reports dependency not satisfiable. Please help.
stevepusser wrote:Chrome downloads its own PPAPI flash the last I heard, but you may have to go into the settings and enable sites to use it.
Firefox was also still using NPAPI Flash instead of PPAPI the last I heard...you can try installing our MX Linux deb that installs both NPAPI and PPAPI packages and set up Chromium compatibility; it works really well: (edit: fixed link) http://mxrepo.com/mx/repo/pool/non-free ... ashplugin/
The mx17 packages are Stretch compatible.
gdebi reports dependency not satisfiable. Please help.
Is it so much of an extra effort to tell us what dependency it says is not satisfiable? Jeesh! Why must we pry it out of you?
Of course somebody's gonna complain that's a cranky answer, but for Pete's sake, why make it so hard for someone to help you?
Hi,
I am a curmudgeon too, don't worry about that.
I will tell you which dependency is not satisfiable if you are so kind as to tell me which package should I download, there are several listed under that link.
FYI, I commented out the mxrepo from my sources, because I want to use exclusively the Debian repos, and I am now struggling with unsatisfied dependencies preventing me to complete a dist-upgrade. so I guess that I will have to purge those packages and re-install form the Debian repos (stable + backports).
Thank you for all the great work and prompt and consistent help.
