Here is how I installed Flash 10 in Ubuntu. Any reason to do it differently in OpenSUSE 11.2-8?
Reference:
queleimporta.com » Blog Archive » Finally! Adobe releases native 64 bit Flash 10 for Linux
wget http://queleimporta.com/downloads/flash10_x64_en.sh && sudo chmod +x flash10_x64_en.sh && sudo sh ./flash10_x64_en.sh
This script will install Native 64 Bit Flash 10 and will also remove
previous versions of flash and the not needed anymore “nspluginwrapper”
well, I found out the answer: it does not work.
Here are the errors:
libflashplayer.so
cp: cannot create regular file `/usr/lib/mozilla/plugins/': Is a directory
Linking libraries
ln: target `/usr/lib/firefox-addons/plugins/' is not a directory: No such file or directory
ln: target `/usr/lib/xulrunner-addons/plugins/' is not a directory: No such file or directory
What would be the right approach in OpenSUSE?
I grabbed flash from the Adobe site and installed it with the package manager. I do not know if that is technically the correct way but it works just fine.
FWIW, here’s what I did. It worked.
su -
~ # cd /usr/lib64
/usr/lib64 # mkdir mozilla
/usr/lib64 # mkdir mozilla/plugins
/usr/lib64 # cd mozilla/plugins/
/usr/lib64/mozilla/plugins # wget http://download.macromedia.com/pub/labs/flashplayer10/libflashplayer-10.0.32.18.linux-x86_64.so.tar.gz
/usr/lib64/mozilla/plugins # tar zxvf libflashplayer-10.0.32.18.linux-x86_64.so.tar.gz
/usr/lib64/mozilla/plugins # rm libflashplayer-10.0.32.18.linux-x86_64.so.tar.gz
/usr/lib64/mozilla/plugins # ln -sf /usr/lib64/mozilla/plugins/libflashplayer.so /usr/lib64/browser-plugins
/usr/lib64/mozilla/plugins # ln -sf /usr/lib64/mozilla/plugins/libflashplayer.so /usr/lib64/xulrunner-1.9.1.3/plugins
This is how it’s done without creating new folders (that maybe other browsers cannot find):
Download the tarfile and unpack it. Copy libflashplayer.so to /usr/lib64/browser-plugins.
I’m curious a bit about this question. Is not Flash-Player-10.0 available from the openSUSE-11.1 OSS repository as an rpm ? If so, why download and install from a tarball, where such an approach means the files are not tracked by one’s rpm database?
Or am I (again) missing something fundamental?
*** … ahh … ignore the above … this is for openSUSE-11.2 … ] ***
Pondering this some more, I note flash-player-10 is in the factory respository for OSS:
Index of /factory/repo/non-oss/suse
I assume factory will work on openSUSE-11.2 milestone8 ?
So let me ask again … 
… why download and install from tarball (when the files are not tracked by the rpm database), when there is an rpm version available where upon installation the files are tracked by the rpm database.
Or am I (again) missing something fundamental ?
That would depend on whether the 64-bit version is or will be available in the 11.2 repos. If it won’t, I can see one big reason to not use the repo: it will make it possible to ditch the (for me anyway) buggy nspluginwrapper.
oldcpu wrote:
> So let me ask again … … why download and install from tarball
> (when the files are not tracked by the rpm database), when there is an
> rpm version available where upon installation the files are tracked by
> the rpm database.
>
> Or am I (again) missing something fundamental ?
Dunno for this particular case, but sometimes, as times goes by (i. e.,
firefox upgrades), the installed version of the Flash plugin (usually the
rpm one) starts having problems or glitches so people have to try with a
newer version which is no available under standard /non-oss repo so they
are “forced” to install it form Adobe’s site.
In fact, there are some programs that can be easily installed “outside
openSUSE’s policy” (which states that programs are not “upgraded” unless
security holes come up) and I’d say Flash plugin is one of them.
Greetings,
–
Camaleón
OK, flash-player specific for 64-bit. That makes sense. I note 64-bit flash-player is not available yet for 11.2 milestone-8 on the factory OSS.
I confess I have been fortunate with flash-player-10 on my two 64-bit openSUSE-11.1 installs, in that the 64-bit OSS versions (with the wrapper) work for me.
Only 32bit there. 64bit Flashplayer is out, I don’t see the point in not having it in non-oss.
To Sauron: isn’t that a bit over the top, to make it a show-stopper? This is how it works:
Uninstall flashplayer through software installer.
http://download.macromedia.com/pub/labs/flashplayer10/libflashplayer-10.0.32.18.linux-x86_64.so.tar.gz
Open with ark
Unpack in homedir
Open a terminal window and do:
su -c ‘mv libflashplayer.so /usr/lib64/browser-plugins’
(enter rootpassword)
Done
I didn’t mean it’s a show-stopper. I only meant that it’s a reason (for some at least) to use a version not included in the repo.
The 32-bit version with nspluginwrapper works reasonably (although I did have to kill the nspluginwrapper process on a semi-regular basis when I used it due to it hogging the cpu) well, although the 64-bit version works better for me.
I’m surprised nspluginwrapper is no longer required, did they change how this is working and now we can get rid of it and have 64-bits flash?
Cuz when Adobe released their 64-bits .so the procedure I found somewhere (was not in my head :)) to enable 64-bits flash was
- Install latest Flash from http://www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash
- Extract it
- sudo cp libflashplayer.so /usr/lib64/browser-plugins/
then
- sudo nspluginwrapper -i /usr/lib64/browser-plugins/libflashplayer.so
then
- in browser make sure nspluginviewer is selected to handle flash content.
The HTTP address doesn’t exist anymore.
And now we don’t need to use nspluginwrapper and select it in browser? So I can deselect it at OS installation (unless it shows up for some kind of dependencies)?
I’ve never needed it for the 64-bit version, as it should be since the only purpose of it is to be able to use 32-bit plugins in a 64-bit browser.
As long as the 32-bit version has been uninstalled (along with nspluginwrapper unless you have another 32-bit plugin such as adobe reader), all you should need to do is:
Makes sense. That’s the approach I will use. I wonder when they will integrate it in the distro.
The Adobe Reader you mention, is that the “acroread” package (not from opensuse repos I think)? Or might it also apply to other pdf readers like say XPDF? I didn’t know adobe reader was only 32-bits.
Next install (this w-e!) I’ll give a try by not installing nspluginwrapper and see if everything works fine.
That’s the one, yeah (in the non-oss repo IIRC). It’s the only one I know of that provides a webbrowser plugin. Okay, it works with the Konqueror and Okular combination too but not everyone likes Konqueror as a browser so that is not always an option.
It works fine for me. I started using the 64 bit flash and ditched nspluginwrapper a while ago on Ubuntu. And, as I mentioned earlier in this thread, I just installed it the same way on OpenSUSE yesterday and it works perfect (without nspluginwrapper).
As I read the responses here, I see that the only difference in my method is that I put the actual plugin in one directory, and I created a link to it in /usr/lib64/browser-plugins. I also created a link to it in the XULRunner directory (which may or may not have any value).
I find the 64-bit flash to have better performance than 32bit flash + nspluginwrapper. I can play HD youtube video without lag on 64bit flash but not on 32bit flash.
At least this should be the case on slower machines…
Hmmm …
I can play 32bit flash (in Firefox) with no lag on a 32-bit athlon-1100 w/1GB RAM and a nVidia GeForce FX5200 graphic card. Just how old is this 32-bit PC you are referring to ?
In my experience, the performance of 32bit Flash in 32bit Firefox on a 32bit OS is good.
I think what he was referring to is 32bit flash with nspluginwrapper on 64biy Firefox & OS. That’s where the performance will often suck.
And as he said, 64bit flash on 64 bit Firefox/OS has good performance again.
That’s my experience and I’ve seen others say the same thing.