desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #42512
[Bug 882125] Re: nsIProcess doesn't work for some executables
This is unlikely to be a bug with the Ubuntu specific binaries, as we
don't change anything there at all. It's more likely that the reporter
set the Firefox apparmor profile to enforce mode, so that accesses to
some binaries are blocked (/usr/bin/gedit is one binary which is
explicitly enabled in the profile)
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
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:
Incomplete
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
References