Help, Adobe Air for Linux ate my mimetypes?
**note** - I would have posted this in the bug list, but I can’t find it, the link from the FAQ just goes to the products page?
**fixed** - Ashutosh from Adobe provided a working fix in the comments below, nice one!
After installing the new Alpha of Adobe Air for Linux yesterday on Ubuntu 7.1 the mime types for .zip files seem to be broken and I can’t figure out how to fix them. When I clicked on a standard .zip file it used to open in FileRoller, it now gives me an error that the filename indicates it’s a zip but the contents indicate it’s an Air Application. I need to use ‘Open With’ to select FileRoller. Not the end of the world but a bit of a pain. Also, the files have a zip icon but this changes to a .air icon when I click it.
Poking around a bit I found xdg-mime included in the files installed with Air (side note, why? I’ve already got these installed, isn’t that the point of using the package manager to install this stuff?) and also an accompanying AdobeAir.xml file…
<?xml version="1.0" encoding="UTF-8"?> <mime-info xmlns="http://www.freedesktop.org/standards/shared-mime-info"> <mime-type type="application/vnd.adobe.air-application-installer-package+zip"> <comment>Adobe AIR Application</comment> <glob pattern="*.air"/> <magic priority="100"> <match type="string" value="PK\003\004" offset="0"/> </magic> </mime-type> </mime-info>
…not sure what the magic stuff does but it looks ok? Also testing with xdg-mime seems to point to the mime types being correct?
adam@ubuntu:~$ xdg-mime query filetype ~/Desktop/08_04_02.zip application/zip adam@ubuntu:~$ xdg-mime query default application/zip file-roller.desktop adam@ubuntu:~$ xdg-mime query default application/vnd.adobe.air-application-installer-package+zip AdobeAIR.desktop
There’s also an air.mime file that also looks ok to me..
application/vnd.adobe.air-application-installer-package+zip
ext: air
I’ve also just spotted, the files have been simlinked incorrectly into /usr/share/mime-info/ …
ls -la /usr/share/mime-info/air.* adam@ubuntu:~$ ls -la /usr/share/mime-info/ lrwxrwxrwx 1 root root 54 2008-03-31 20:26 air.keys -> /opt/Adobe AIR/Versions/1.0/xdg-utils/support/air.keys lrwxrwxrwx 1 root root 54 2008-03-31 20:26 air.mime -> /opt/Adobe AIR/Versions/1.0/xdg-utils/support/air.mime
the links should be to /opt/Adobe AIR/Versions/1.0/support/* , no xdg-utils, so I’ve tried …
adam@ubuntu:~$ sudo unlink /usr/share/mime-info/air.keys adam@ubuntu:~$ sudo unlink /usr/share/mime-info/air.mime adam@ubuntu:~$ sudo ln -s /opt/Adobe\ AIR/Versions/1.0/support/air.keys /usr/share/mime-info/air.keys adam@ubuntu:~$ sudo ln -s /opt/Adobe\ AIR/Versions/1.0/support/air.mime /usr/share/mime-info/air.mime
but this doesn’t seem to fix anything. Any other ideas anyone?
———
note to self, may be time to look at a liquid layout for the blog 
April 2nd, 2008 at 5:11 pm
Are you using Gnome or KDE?
I use both, and AIR has dome the same thing with me on my Gnome installation. Archive files as well as OpenOffice files are now, by default, handled by AIR.
I am not having any of these issues with KDE, however.
April 2nd, 2008 at 5:13 pm
Yeah, Gnome here.
April 2nd, 2008 at 5:34 pm
I also get this when trying to open Filezilla :
10:06:11 PM: can’t open file ‘/usr/share/mime-info/air.mime’ (error 2: No such file or directory)
10:06:11 PM: can’t open file ‘/usr/share/mime-info/air.keys’ (error 2: No such file or directory)
April 2nd, 2008 at 5:38 pm
@Dan, yeah, seems like the installer writes the symlinks to the wrong places, you can unlink them and re-link them by hand (see the bottom of the post) but it doesn’t seem to fix the issue for me anyway?
April 3rd, 2008 at 2:16 pm
Hi,
We’re actively looking at this issue for the next drop/release - some other users have also reported this problem on some
distributions.
To fix this, please try the following:
1. Run the following command as root (use the “xdg-mime” at /opt/Adobe AIR/Versions/1.0/xdg-utils/xdg-mime) -
xdg-mime uninstall –novendor “/opt/Adobe AIR/Versions/1.0/support/AdobeAIR.xml”
2. Remove the following three lines from “/opt/Adobe AIR/Versions/1.0/support/AdobeAIR.xml” -
<magic priority=”100″>
<match type=”string” value=”PK0304″ offset=”0″/>
</magic>
3. Run the following command as root (use the “xdg-mime” at /opt/Adobe AIR/Versions/1.0/xdg-utils/xdg-mime) -
xdg-mime install –novendor “/opt/Adobe AIR/Versions/1.0/support/AdobeAIR.xml”
Do let us know if this does not fix the problem (at the AIR Linux forum -
http://www.adobe.com/cfusion/webforums/forum/categories.cfm?forumid=72&catid=677)
- Ashutosh
Adobe Systems Inc.
April 3rd, 2008 at 2:54 pm
@Ash - ahh, so maybe it was the magic lines after all? I’ll give that a try when I get home, thanks.
April 3rd, 2008 at 4:54 pm
The bug tracker is http://bugs.adobe.com/jira
April 3rd, 2008 at 10:54 pm
I can confirm the fix above from Ashutosh worked for me (although there needs to be two ‘-’s before novendor.)
Cheers!
April 4th, 2008 at 12:49 am
The bug tracker for AIR related bugs is at http://www.adobe.com/go/wish.
The jira bug base is only for Flex, Tamarind and BlazeDS.
Cheers,
Arno.
Adobe AIR Team
April 8th, 2008 at 12:53 am
That fix didn’t work for me. I’m using Ubuntu 8.04 and It only happens when I run pgAdmin III.
April 8th, 2008 at 12:58 am
Guess I spoke too soon, I your solution at the bottom of the post fixed my problem.
Thanks
April 9th, 2008 at 1:30 pm
I cannot yet solve the problem in CentOS5.
April 10th, 2008 at 4:21 pm
It worked for Ubuntu 7.10, thanks!
April 14th, 2008 at 1:32 am
@Ashutosh amazing, thanks!!! it worked perfectly
May 10th, 2008 at 4:11 am
No luck with ubuntu hardy, still problems when opening a zip file from firefox’s download dialog…
May 15th, 2008 at 12:03 am
Unfortunately it doesn’t solve the problem on Ubuntu Hardy.
May 22nd, 2008 at 10:57 pm
The unlinking / linking did it for me. Editing AdobeAIR.xml did not.
I am using Kubuntu 8.04.
The affected application is Junglediskmonitor, which was affected when run and whenever one entered the configuration dialog. It is fine now that I have changed those symlinks.
July 11th, 2008 at 4:45 pm
[…] Obviously, this wasn’t the worst thing that could possibly happen to me… but it was rather aggravating! To solve this problem I went scrounging through the depths of the interblags and finally managed to fix it. Lots of help comes from the Dusty Pixels blog, but I figured I would compile what worked for me here. […]