Adobe Air 1.5 and Fedora 12 x64 – Gnome-keyring/KWallet error

By finndo On April 20, 2010 · 1 Comment

First off, let me say it is not pretty, second the instructions on the Abode website are better suited for trying to get a man on Mars than getting

First off, let me say it is not pretty, second the instructions on the Abode website are better suited for trying to get a man on Mars than getting Air to work in Linux x64, and they are specific for Fedora 9 and 10 x64…  There are also instructions for installing Adobe Air 2 on Fedora 11, but 2 is not an available install from the drop down menu on the install page.  One last important point, then we shall get started… once again Adobe has ONLY MADE A 32bit APPLICATION VERSION, which is why there is an issue in the first place, the second issue is that once again the great big $$$ hungry corporation has no clue how to design an installation for Linux.  I hope someone from Adobe reads this one days and learns that *nux packages can have DEPENDENCIES listed in the package and the system will attempt to download and install them during installation if they are missing from the local system.  This is one of the top reasons why I switched to *nix after being a Microsoft Partner.

Ok, so the first thing in getting an install that does not want to work is to find instructions from someone who has gotten it to work.  I value my time greatly, and do not believe in re-inventing the wheel (when not necessary).

next problem, Adobe Air requires the Gnome-keyring (boo…. bad, hisss…. yuk yuk yuk) or the KWallet (I don’t think they still make this app, it is now “The KDE Wallet” (filename is KDEWallet instead of KWallet) and can be found by going to System Settings –> Advanced –> KDE Wallet.  I went in and setup a default profile, very easy to do, just hunt around as there are only about 7 things to do in the control panel and if you have not done this already you will find a drop down field that is blank.   now I am getting an issue when attempting to install, or I would not have taken time to write this (unfortunately I had the issue yesterday and did my research for getting around it, then started up again today and as the first set of instructions did not work I am consequently writing this post.  so the bad news is I may not get the same error right now when I try again so I can copy it to this post… yeah… it is working right now… sorry about that, but the main part of the error was “Gnome-keyring or KWallet is necessary to install Adobe Air”  Thankfully (for all) this means a shorter post.  I did a bunch of things and not all of them worked.  Here are the 5 steps I followed so you can copy and paste, start out in a terminal window in the directory that you have downloaded the Adobe Air installer to (most likely ~/Downloads).

Step #2 is from the Adobe website (combined from several steps into one command, obviously the guys techs at Adobe are not Linux people), I had lots of error messages here (not found, already installed, conflicts with installed version, copies files already installed from installed package <name-o-package> and maybe one or two more).  I would bet a couple of $$$ that you can skip this line, but as I have already done it, I don’t know.  (the short version: you should be able just skip step 2)  The remaining instructions came from the website that is referenced from the first link in this post

  1. cd ~/Downloads
  2. sudo yum install lib32asound2 lib32gcc1 lib32ncurses5 lib32stdc++6 lib32z1 libc6 libc6-i386 libnss3.so.1d libnssutil3.so.1d libsmime3.so.1d libssl3.so.1d libnspr4.so.0d libplc4.so.0d libplds4.so.0d ld-linux.so.2 gtk2-devel.i386 libxml2.i386 nss.i386 libXt.so.6 gnome-keyring.i386 xterm rpm-libs.i386
  3. touch ~/.airinstall.log ~/.airappinstall.log
  4. sudo chmod +x AdobeAIRInstaller.bin
  5. sudo yum install -y gtk2-devel.i686 nss.i686 nss-softokn.i686 libxml2-devel.i686 libxslt.i686 gnome-keyring.i686 rpm-devel.i686 alsa-plugins-pulseaudio.i686 PackageKit-gtk-module.i686 libXt.i686 gtk2-engines.i686 libcanberra-gtk2.i686 xterm
  6. sudo ./AdobeAIRInstaller.bin

That did it for me, I clicked “install” “accept” “done” and that was a wrap.  now to test it…

oops… the directions on that blog post go on to say “On Fedora 12, you would not be able to install or run any AIR application. This is probably due to SELinux security policy with the certificate in Adobe AIR.”

The good news… there is a solution, the bad news, as displayed in the blog post it will not work due to a syntax error (tried in BASH, SH, KSH, and TCSH all gave the syntax error except TCSH which gave an illegal variable error)  lucky us the blogger posted the reference link for the solution and I went to check it out.  No help there it is letter for letter correct.  I am lucky I do have a small brain that can occasionally come up with solutions to technical based problems.  here is what I did and, yes it did work.

  1. cd ~/Downloads (you can skip this if you are still there from my previous instructions above)
  2. touch crypt
  3. sudo chmod +x crypt
  4. echo ‘for c in /etc/opt/Adobe/certificates/crypt/*.0; do aucm -n $(basename $c) -t true; done’ >crypt
  5. sudo ./crypt

piece of cake! something I learned from an AIX training class I had last year, if it doesn’t work from a command line, then darn it, put it in a shell script file!!!

There are also instructions on that original blog post for installing and uninstalling Adobe Air Apps, the install part is pretty straight forward, go to the website that has the app, click install.  the uninstall instructions have a couple of steps.  when I get around to uninstalling something I’ll add them to this post (probably in the next 2 hours!!)

Tagged with: • • • • • • • • • • • • • • • • • • • • • • • • • • •
 

FreeBSD the next step – update 2

By finndo On April 5, 2010 · Leave a Comment

this may get a bit repetitive with me re-listing everything, so instead I am just going to link to the first post that has the list of things to do… note I have added a couple of things at the bottom so the [...]

this may get a bit repetitive with me re-listing everything, so instead I am just going to link to the first post that has the list of things to do… note I have added a couple of things at the bottom so the numbers now go past 20…

 

1. 75% in progress, troubleshooting and more testing needed.  I have gotten my user added the the “VirtualBox” user group, but I get this error when I try to execute VirtualBox from the command line ”VirtualBox: supR3HardenedExecDir: couldn’t read “”, errno=2 cchLink=-1“  I tried loading VirtualBox from KDE and it was loading for about 12 seconds then nothing happend, also it did not install a manual page.  I’ll have to do some forum surfing to figure this one out.  this exact error is referrenced in the FreeBSD handbook noting that it should only occur if you are using an older version on VirtualBox.

2. 0% not started.  no updates yet, holding off till I get some of these other tasks complete.

3. 100% complete.  everything is automounting at bootup and it is doing it where I want it to.

4. 100% complete.  I am working almost exclusively via ssh now and can connect to it remotely as tested via an Android cell phone ssh client (props to connectbot)

5. 10% in progress, researched only.  Chrome can be installed as a Debian, Ubuntu, openSUSE, or Fedora package, I just need to set my system up to handle RPMs and I might be able to get it to install, hopefully the newest version will work easier than last august when everyone was trying to hack the install to make it work, especially since every forum I went to never had a successful complete port available and there were no posts from 2010 and the maintainer of the hacked port is not doing updates anymore except those that match his specific system configuration.

6. duplicate issue.  going to delete this one, as #19 and #20 pretty much sum it up.

7. 30% in progress, trouble shooting and additional testing required.  as noteded else where VirtualBox is installed but not able to run, and I have not started on VMWare.

8. 100% complete.  Firefox 3.6.2 is installed and operational.

9. 90% in progress, trouble shooting and more testing needed.  self testing shows that a user is able to ssh in and access the drives, but is not able to ftp in and access the drives.  I used “sudo ln -s /mnt/<directory> /home/<user>/<directory>” I haven’t used links much and need to see if the -s (symbolic) is what is preventing the user from accessing the data via ftp.

10. 0% not started.  no updates yet, holding off till I get some of these other tasks complete.

11. 20% in progress, 1 out of 5 drives is currently running with GPT.  the new 1.5TB drive was setup with GPT when installed into the system.  the new 500GB drive (FreeBSD boot drive) is still MBR as the FreeBSD fdisk application did not have an option for setting the drive boot record to GPT, although I have found documentation on converting the FreeBSD boot drive to GPT.

12. 0% in progress, initial research turned up nothing useful.

13. -30% not started, situation worsening, additional packages labeled as “gnome-xxxx” or “xxxxx-gnome” have been added as dependencies during other package installations. 

14. 10% in progress, initial research has turned up useful information; however I am not currently in a possition to proceed.

15. 0% not started.  no updates yet, holding off till I get some of these other tasks complete.

16. 0% not started.  no updates yet, holding off till I get some of these other tasks complete, will require at least one of #’s 1, 2, 7, or 15 to be complete before work can begin.

17. 0% not started.  no updates yet, holding off till I get some of these other tasks complete, not a priority and very near the bottom of the list of things to do.

18. 40% in progress.  Still leaning towards rsync, but I have been researching into using dump and I think it will do what I want it to.

19. 60% in progress, I thought I had it installed, but when I went to the test if you have java installed page of www.java.com it failed to test my java installation (might need to add the plugin for firefox, will check); however the java download page only lists “Windows, Mac OS, and Linux” as OS choices, so I will have to do more research.

********update – I am making a java install page because this was such a pain in the rump to do.***********

20. 40% in progress, I thought I had it installed, but when I went to hulu it told me I need java 10.0.22, also amd.com told me I need the flash plugin installed; however again there is no FreeBSD listing on the download page as a supported OS, so I will have to do more research.

21. 100% complete.  (I know I added this one) get Yakuake working in KDE, well I did a “sudo pkg_add -r yakuake” and it started downloading, it has about 6 dependencies and those had about 150 dependencies, most of which I already had installed.  the problem I saw was it force downloaded KDE 3.5 and all of it’s dependencies, I hope that doesn’t screw anything up.  If I remember correctly from when KDE 4.0 first came out they specifically named the port KDE4 instead of just KDE so that there would not be conflicts on systems that had both versions installed.  after it finished I ran a “sudo pkgdb -F” it found a lot of stale dependencies and fixed them, one thing I noticed fly by was Firefox 3.0.## which tells me I need to check my Firefox and see if it is 3.0 or 3.6…

22. 10% researched only.  Get Picasa installed and working, this will be just like chrome and will require using RPM packages.

23. 100% complete.  as part of #5 and #22 (and because I always install this on FreeBSD, but it failed during initial OS installation for some reason) I am installing the linux compatibility/emulation pack.  I’ll do a brief post on this and link it here.

Tagged with: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
 
16 visitors online now
5 guests, 11 bots, 0 members
Max visitors today: 23 at 12:30 pm PST
This month: 23 at 02-05-2012 05:37 am PST
This year: 29 at 01-11-2012 02:49 pm PST
All time: 1100 at 08-08-2011 08:11 pm PDT
View in: Mobile | Standard