Adobe finally released a 64bit flash, it would be cool to see this available in portage. http://labs.adobe.com/downloads/flashplayer10.html Reproducible: Always Steps to Reproduce:
Adobe considers this release as pre-release for developers and advanced users. Anyway, reassigning to maintainer...
Still, it would be sweet to have it in ~amd64 or at least some overlay. BTW I guess that all Gentoo users are kinda advanced users (in the way that, we are all used to rebuilding stuff and tracking down why things don't work ;]) So, please (please, please) write an ebuild and put it somewhere :)
Indeed, an ebuild for this would be fantastic.
Benn testing the plugin a lot today here on my ~amd64 system: It's fast, a lot faster than nspluginwrappery stuff, and has not crashed my browser so far. The fullscreening doesn't work here (as advertised) and I don't have a camera to test, but I think it should at least get to ~amd64 (maybe with a einfo note): Right now that is the best way for Flash in 64Bit by far.
Should probably add that I tested with www-client/mozilla-firefox-3.0.4.
Wow, great news! I've checked this in (netscape-flash-10.0.20.12_alpha), but p.masked it for now. I haven't done a lot of testing yet, but my basic benchmark (youtube) seems to work properly. Please test it and tell your friends - If I get enough positive feedback on this bug I'll consider unmasking it to ~amd64 soon.
Created attachment 172097 [details] netscape-flash for amd64 systems Until it gets unmasked i wrote a quick ebuild to help other users to test it This version of flash-player works perfect here :) Enjoy!
(In reply to comment #8) > Created an attachment (id=172097) [edit] > netscape-flash for amd64 systems > > Until it gets unmasked i wrote a quick ebuild to help other users to test it > > This version of flash-player works perfect here :) > > Enjoy! > http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-www/netscape-flash/ChangeLog?view=markup :)
Works fine here. Tested in Konqueror 4.2 SVN and Firefox3, using youtube (of course) and THE flash overkill page: http://www.musicovery.com/ If latter one works, flash works.
(In reply to comment #9) > (In reply to comment #8) > > Created an attachment (id=172097) [edit] > > netscape-flash for amd64 systems > > > > Until it gets unmasked i wrote a quick ebuild to help other users to test it > > > > This version of flash-player works perfect here :) > > > > Enjoy! > > > > http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-www/netscape-flash/ChangeLog?view=markup > :) > Ooops missed that :) Please consider to add !net-www/nspluginwrapper as blocked package on DEPEND variable otherwise you will mess up your flash :)
But acrobat's plugin is also 32bit (isn't it?). So this bockage will also block the possibility of using acrobat's plugin. Isn't there a better way to do it?
The source package for this version is only for 64bit systems .Since there is no README file inside the source package , try to use the .so file on an x86 gentoo machine and you ll see that it fails Besides that , another way to see that is the name of the package which is x86_64. According to this article http://labs.adobe.com/technologies/flashplayer10/ it is only for 64bit systems The best way to deal with this is to modify the ebuild to download the appropriate package according to your architecture
Comment on attachment 172097 [details] netscape-flash for amd64 systems Removed since there is already on portage cvs
Have been testing it with Firefox 2.0.0.18 - works almost flawlessly and is definitely faster than nspluginwrapper stuff. Full-screen mode and v4l2 webcam also work fine. One bug I have found so far: it segfaults on closing a tab with this movie running: http://ncannasse.fr/blog/playing_with_3d
(In reply to comment #15) > One bug I have found so far: it segfaults on closing a tab with this movie > running: http://ncannasse.fr/blog/playing_with_3d > same here. anyway the alpha runs "fine" (like 32bit flash) here with firefox 3.0.4.
Confirmed to work on firefox 3.1beta1. Tested on youtube and bubble shooter :)
Youtube works for me but espn.com crashes the browser.
Had to install libflashsupport to get sound working, but this is keyworded only for x86. I'm using oss. Otherwise works great!
(In reply to comment #19) > Had to install libflashsupport to get sound working, but this is keyworded only > for x86. I'm using oss. Otherwise works great! oss? That's crazy! But yes, that reminds me that libflashsupport is now useful for amd64 users as well! Time to keyword it, I guess. -- Everyone with crashes: If you haven't yet already, report them here: http://bugs.adobe.com/flashplayer/
I insist that you need to block this package with nspluginwrapper package since this version of flashplayer is only for amd64 machines. Am I wrong?I cant find any documentation about the supported ~arches
(In reply to comment #21) > I insist that you need to block this package with nspluginwrapper package since > this version of flashplayer is only for amd64 machines. Am I wrong?I cant find > any documentation about the supported ~arches > I'm no expert (read: this is just off the top of my head), but wouldn't nspluginwrapper be used for other 32 bit plugins than just flash? Adding a black could be an issue for people who use it. Shouldn't nspluginwrapper be modified to just not wrap flash if there is a 64 bit version? then you could block older versions of nspluginwrapper.
(In reply to comment #21) > I insist that you need to block this package with nspluginwrapper package since > this version of flashplayer is only for amd64 machines. Am I wrong?I cant find > any documentation about the supported ~arches Let us begin by assuming you meant "suggest" intead of "insist" ;) I don't think a block is the appropriate thing here - There's no reason netscape-flash 64-bit and nspluginwrapper can't both be installed simultaneously - In fact, as Maciej and Murph mentioned, nspluginwrapper is still used for other 32-bit plugins. I can imagine that someone using the 32-bit acroread plugin on amd64 would be very angry if they suddenly couldn't upgrade to the 64-bit flash plugin! Now, I may perhaps consider having a postinstall script remove any old nswrappers for the 32-bit flashplugin.so if it detects them, I'm not sure if this is necessary, since I did this myself manually before I upgraded. Did you have trouble upgrading to the 64-bit version because of nspluginwrapper? What happened? How did you fix it? This is one of the reasons this package is p.masked for now. As for your final question, yes, this particular version of flash is only for amd64 machines. I'm sure that in the future when this software is actually released, the same version will be available for both x86 and amd64. However presently there is no 10.0.20.12_alpha for x86. Just look at the KEYWORDS in the ebuild I checked in. It specifically says: '-* -x86 ~amd64' which means "This CANNOT be used on x86 (or any other arch) and is unstable on amd64". Compare this to the KEYWORDS of 10.0.12.36 -> "-* x86 amd64' This means "This is stable on x86 and amd64 but cannot be used on any other arch". Package managers read these values, so even if you *did* unmask 10.0.20.12 on and x86 machine, you could not accidentally upgrade to it without explicitly overriding the arch check in your package manager.
(In reply to comment #22) > Shouldn't nspluginwrapper be > modified to just not wrap flash if there is a 64 bit version? then you could > block older versions of nspluginwrapper. As I understand things, and I'm not an expert in nspluginwrapper either, it won't wrap native plugins without you explicitly asking it to do so with the '-n' flag. Furthermore, some people may actually *want* to wrap native plugins, since nspluginwrapper separates the plugin out of the main browser execution thread - In theory then a crashing plugin won't bring down the browser.
(In reply to comment #23) > (In reply to comment #21) > > I insist that you need to block this package with nspluginwrapper package since > > this version of flashplayer is only for amd64 machines. Am I wrong?I cant find > > any documentation about the supported ~arches > > Let us begin by assuming you meant "suggest" intead of "insist" ;) Ok sorry about that :) > > I don't think a block is the appropriate thing here - There's no reason > netscape-flash 64-bit and nspluginwrapper can't both be installed > simultaneously - In fact, as Maciej and Murph mentioned, nspluginwrapper is > still used for other 32-bit plugins. I can imagine that someone using > the 32-bit acroread plugin on amd64 would be very angry if they suddenly > couldn't upgrade to the 64-bit flash plugin! > > Now, I may perhaps consider having a postinstall script remove any old > nswrappers for the 32-bit flashplugin.so if it detects them, I'm not sure if > this is necessary, since I did this myself manually before I upgraded. Did >you That is probably the best solution. Call nspluginwrapper script to remove old flash :) ( i am not an expert too )
(In reply to comment #22) > I'm no expert (read: this is just off the top of my head), but wouldn't > nspluginwrapper be used for other 32 bit plugins than just flash? Yes, absolutely it is. I still need this for realplayer since certain sites won't work with realaudio support in the Totem plugin. You don't need to block it, just run "nspluginwrapper -l" to list plugins and "nspluginwrapper -r <path_to_file_in_list>" to remove them. You may need to run as each user and root to remove all copies. This is what I did.
Someone tested this flash with opera? I see it works on ff, but hangs opera 9.62 on my pc.
Works here with www-client/opera-9.62. Tested youtube and could watch video.
(In reply to comment #28) > Works here with www-client/opera-9.62. Tested youtube and could watch video. > +1 :)
Works as intended for me, too. (FF 3.0.4) Hasn't crashed yet which the 32bit version with nspluginwrapper did alot for me...
Regarding nspluginwrapper: To automatically remove any dead plugins, you can just run 'nspluginwrapper -a -u'. Of course this will only work if the 32-bit libs have already been removed, and unfortunately during a normal upgrade the older 32-bit libs are not going to be removed until after the 64-bit version is done installing, since portage does: 1. Install new package 2. Uninstall old package The good news is that I have not see any trouble on my amd64 machine that results from having the old nspluginwrapper stuff around, so even if no one ever sees the message it shouldn't hurt. Please let me know if this is not the case for you! I will add a note into the post-install hook that will notify users that they should run 'nspluginwrapper -a -u' manually to clear out any old wrappers. I just don't think there's a way to actually do this automatically.
youtube works like a charm, FF 3.0.4, feels a lot faster
SeaMonkey 1.1.12 - no crash so far (half a day of videos & some games)
Maybe it should go ~amd64? Looks like it works better than 32 bit version. We know that if someone uses ~ branch he know what he is doing, and more people should test this package.
Firefox 3.x: Works flawlessly and better than 32bit Flash + nspluginwrapper
jim, any news on this one? do you plan to add this to portage? thanks!
Good news everyone! A majority of the comments here have been positive, so I've unmasked this to ~amd64 Enjoy. If you experience any issues from here on out, please add to other bugs or open new bugs.
