From kookoolappai at gmail.com Sun Jul 22 11:44:11 2012 From: kookoolappai at gmail.com (Koo Koolappai) Date: Sun, 22 Jul 2012 14:44:11 +0300 Subject: Fwd: nspluginwrapper + flash-plugin + Firefox 10 [Linux] In-Reply-To: References: Message-ID: Summary: Flash videos of http://areena.yle.fi do not play with nspluginwrapper + Firefox 10 + flash-plugin. Three workarounds: Method #1 - add "libflashplayer*" into the ignore list in /etc/sysconfig/nspluginwrapper Method #2 - remove nspluginwrapper package from the system Method #3 - remove flash-plugin package from the system and libflashplayer.so is in /home/myname/.mozilla/plugins/ Full description of the problem: http://scientificlinuxforum.org/index.php?showtopic=1769 From davidben at mit.edu Sun Jul 22 14:18:36 2012 From: davidben at mit.edu (David Benjamin) Date: Sun, 22 Jul 2012 10:18:36 -0400 Subject: nspluginwrapper + flash-plugin + Firefox 10 [Linux] In-Reply-To: References: Message-ID: Hi, Unless you're on some architecture like arm where Adobe does not have a native version of Flash, I /strongly/ recommend you do not use nspluginwrapper. Your distribution is apparently wrapping every plugin; Firefox wrapping everything on startup is not an upstream behavior. I recommend you file a bug with them to stop doing this. nspluginwrapper is buggy, and it doesn't actually do anything for plugin sandboxing or robustness. Both Chrome and Firefox natively support out-of-process plugins now and, for various technical reasons, nspluginwrapper can't give you something as robust. (If you want sandboxing on top of that, the only solution today is Chrome with their built-in PPAPI Flash.) So, I actually suggest doing one of your workarounds. As for your fixing this in nspluginwrapper (since it is a bug). I actually can't play the videos with or without nspluginwrapper, but it does get further along without it. I did notice that the nspluginwrapper version is actually fetching different URLs that don't exist. So something weird's going on there. I can see if I can maybe figure out what's going on. But again, I do not recommend you use nspluginwrapper for Flash anyway. I've personally been using the native 64-bit version (and now the Chrome PPAPI one) for a while now. David On Sun, Jul 22, 2012 at 7:44 AM, Koo Koolappai wrote: > Summary: > Flash videos of http://areena.yle.fi do not play with nspluginwrapper > + Firefox 10 + flash-plugin. > > Three workarounds: > > Method #1 > - add "libflashplayer*" into the ignore list in /etc/sysconfig/nspluginwrapper > > Method #2 > - remove nspluginwrapper package from the system > > Method #3 > - remove flash-plugin package from the system and libflashplayer.so is > in /home/myname/.mozilla/plugins/ > > Full description of the problem: > http://scientificlinuxforum.org/index.php?showtopic=1769 > > _______________________________________________ > Nspluginwrapper-devel-list mailing list > Nspluginwrapper-devel-list at redhat.com > https://www.redhat.com/mailman/listinfo/nspluginwrapper-devel-list From davidben at mit.edu Sun Jul 22 14:19:54 2012 From: davidben at mit.edu (David Benjamin) Date: Sun, 22 Jul 2012 10:19:54 -0400 Subject: nspluginwrapper + flash-plugin + Firefox 10 [Linux] In-Reply-To: References: Message-ID: On Sun, Jul 22, 2012 at 10:18 AM, David Benjamin wrote: > As for your fixing this in nspluginwrapper (since it is a bug). I Er, that was supposed to say "As for fixing this in nspluginwrapper". :-) > actually can't play the videos with or without nspluginwrapper, but it > does get further along without it. I did notice that the > nspluginwrapper version is actually fetching different URLs that don't > exist. So something weird's going on there. I can see if I can maybe > figure out what's going on. But again, I do not recommend you use > nspluginwrapper for Flash anyway. I've personally been using the > native 64-bit version (and now the Chrome PPAPI one) for a while now. > > David > > On Sun, Jul 22, 2012 at 7:44 AM, Koo Koolappai wrote: >> Summary: >> Flash videos of http://areena.yle.fi do not play with nspluginwrapper >> + Firefox 10 + flash-plugin. >> >> Three workarounds: >> >> Method #1 >> - add "libflashplayer*" into the ignore list in /etc/sysconfig/nspluginwrapper >> >> Method #2 >> - remove nspluginwrapper package from the system >> >> Method #3 >> - remove flash-plugin package from the system and libflashplayer.so is >> in /home/myname/.mozilla/plugins/ >> >> Full description of the problem: >> http://scientificlinuxforum.org/index.php?showtopic=1769 >> >> _______________________________________________ >> Nspluginwrapper-devel-list mailing list >> Nspluginwrapper-devel-list at redhat.com >> https://www.redhat.com/mailman/listinfo/nspluginwrapper-devel-list From davidben at mit.edu Sun Jul 22 18:26:01 2012 From: davidben at mit.edu (David Benjamin) Date: Sun, 22 Jul 2012 14:26:01 -0400 Subject: Future of nspluginwrapper Message-ID: Hi all, So, as you might have noticed, I've stopped doing much work on nspluginwrapper. Adobe released a stable 64-bit version of Flash for Linux some time ago, so there is no more need for the common case of running 32-bit Flash on a 64-bit browser. Not to mention the web moving away from plugins in general. And, while the project is still somewhat interesting to me, I don't appear to have much motivation to work on a tool that I do not personally use. If you are still using nspluginwrapper to run Adobe's Flash on i386 or x86-64 Linux, I recommend against it. I know some distributions will wrap every plugin installed on the system. Please do not do this. It's really only a source of instability. nspluginwrapper has never been a sandboxing solution; you can't actually sandbox a general NPAPI plugin. (If you want sandboxed Flash, I think Chrome's built-in PPAPI Flash is your only option.) It also really doesn't do much against hung or crashed plugins[1]. Of course, there are still uses where nspluginwrapper isn't easily avoidable. The Adobe Reader plugin is only 32-bit[2], and there other less common 32-bit-only plugins. Or if you are running on ARM or BSD, I believe people have used nspluginwrapper with qemu and whatnot. But since none of those uses apply to me, I may not be the best person to maintain the project for them. I have some unreleased fixes (that I mostly forgot I never released...) in git since 1.4.4, so at the least I'll make a 1.4.6 release with them. They're fairly uninteresting, except that one fixes a long-standing browser crash on nspluginwrapper upgrade. Past that, I'll try to fix things as I can, but realistically I'm not likely to do much. These days my attention has been given to other projects. So if there is anyone interested for whom the project is more relevant, I am happy to hand over maintainership. I had a number of plans to improve things, particularly the configuration tool and wrapper generation, and I'll detail them to anyone interested. There are also some unresolved bugs like some issue with Adobe Reader. I doubt I'll get to addressing them myself. It's been a fun, if brief, ride. I hope my tenure has made the project more stable. David [1] It is true that nspluginwrapper pushes the plugin out-of-process and provides some minimal robustness here. However, Chrome, Firefox, and now Opera all provide this feature built-in and are far more robust. Both because their code is much better tested and because nspluginwrapper can't do a lot here. In fact, many of nspluginwrapper changes in my tenure, if anything, decreased its robustness to misbehaving plugins. Many of those tricks result in incorrect behavior in synchronous NPAPI and caused crashes in Flash. Browsers only speak NPAPI on one end and have slightly more flexibility here. If your browser does not do this natively, consider asking them to implement the same feature. Think of it as one of many ways browsers compete with each other. Multiprocess tricks are a pretty standard these days, at least for plugins. [2] Well, you can use Chrome's built-in PDF renderer or download the files. And I think Firefox is getting a Javascript PDF viewer soon. But supposing you specifically want Adobe Reader's plugin. From swt at techie.net Sun Jul 22 23:35:38 2012 From: swt at techie.net (Scott Talbert) Date: Sun, 22 Jul 2012 19:35:38 -0400 (EDT) Subject: Future of nspluginwrapper In-Reply-To: References: Message-ID: On Sun, 22 Jul 2012, David Benjamin wrote: > generation, and I'll detail them to anyone interested. There are also > some unresolved bugs like some issue with Adobe Reader. I doubt I'll > get to addressing them myself. > > [2] Well, you can use Chrome's built-in PDF renderer or download the > files. And I think Firefox is getting a Javascript PDF viewer soon. > But supposing you specifically want Adobe Reader's plugin. For a good while I was trying to fix the bug(s) with the Adobe Reader plugin, but I have since given up after not really getting anywhere and not getting any help from Adobe. You are correct, there is now a Javascript PDF viewer add-on, PDF.js[3], available for Firefox. It is available now as an add-on, but they make eventually make it part of the browser. It seems to work pretty well for me, so I've stopped using the Adobe plugin. [3] https://addons.mozilla.org/en-US/firefox/addon/pdfjs/ From stransky at redhat.com Mon Jul 23 06:28:13 2012 From: stransky at redhat.com (Martin Stransky) Date: Mon, 23 Jul 2012 08:28:13 +0200 Subject: Future of nspluginwrapper In-Reply-To: References: Message-ID: <500CEEFD.20008@redhat.com> On 07/23/2012 01:35 AM, Scott Talbert wrote: > On Sun, 22 Jul 2012, David Benjamin wrote: > >> generation, and I'll detail them to anyone interested. There are also >> some unresolved bugs like some issue with Adobe Reader. I doubt I'll >> get to addressing them myself. >> >> [2] Well, you can use Chrome's built-in PDF renderer or download the >> files. And I think Firefox is getting a Javascript PDF viewer soon. >> But supposing you specifically want Adobe Reader's plugin. > > For a good while I was trying to fix the bug(s) with the Adobe Reader > plugin, but I have since given up after not really getting anywhere and > not getting any help from Adobe. You are correct, there is now a > Javascript PDF viewer add-on, PDF.js[3], available for Firefox. It is > available now as an add-on, but they make eventually make it part of the > browser. It seems to work pretty well for me, so I've stopped using the > Adobe plugin. > > [3] https://addons.mozilla.org/en-US/firefox/addon/pdfjs/ I did a fix for the Adobe Reader plugin/nspluginwrapper, it's tested by our customer now. If it works as expected I'll post the patch here. ma.