For the benefit of users that might find this thread while trying to get rid of this error, here's how to fix it.
If It's All Text dies with an "exited with a status of 1" error in .deb- based flavors of Linux like Ubuntu, here's how to fix that error. To see if this will fix your error, run this command: sudo aa-status If you get output like "14 profiles are in enforce mode" then these instructions will work for you - continue with the following steps. Look in the /etc/apparmor.d/ folder for a file called (or starts with) usr.bin.firefox. Edit that file with your favorite editor using superuser priveleges. You'll need to add a line that points to the editor that you configured It's All Text to use. In my case, that's kate, and the path to kate's binary is /usr/bin/kate. Using the above path, add one or two lines into the middle of usr.bin.firefox, like this: # I added this on 2/17/2012 to allow firefox access to the kate binary for the It's All Text addin /usr/bin/kate ixr, The line that starts with # is just a comment. The /usr/bin/kate portion must point to your editor. The ixr portion gives Firefox permission to run your editor. The comma at the end of the line is required. To make this change be seen by Firefox, either restart your computer, or run this command: sudo /etc/init.d/apparmor restart -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/882125 Title: nsIProcess doesn't work for some executables Status in “firefox” package in Ubuntu: Invalid Bug description: Hello! I'm the author of the Firefox extension "It's All Text!". This extension launches a local editor (like emacs or gvim) with the contents of a textarea to make editing web pages (wikis, etc.) easier. I have discovered a bug in Ubuntu's firefox: https://github.com/docwhat/itsalltext/issues/18 It appears that the nsIProcess run*() methods fail for *some* binaries. In the issue I referenced above, the user was able to use /usr/bin/gedit but not /usr/bin/sublime-text-2. It would fail to launch and return an exit code 1. The user was nice enough to let me screen share with him and we tried runwAsync() (the default), runAsync(), and run() to launch the editor but it failed in all cases. We then downloaded Firefox from the official site (both the Ubuntu one and the official one were 7.0.1) and nsIProcess then worked. I am unable to figure out: * How /usr/bin/gedit and /usr/bin/sublime-text-2 differ that one fails and one succeeds. * How the Ubuntu Firefox and the Official Firefox differ. I haven't a clue about what's going on here. I am unable to reproduce this problem in my VM. I'll ask the user to subscribe to this bug in case you want to ask him additional questions. Ciao! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/882125/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
