User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/20071127 Firefox/126.96.36.199 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/20071127 Firefox/184.108.40.206 I have been using nsIprocess.run() to launch an exe (which is configured to run as adiminstrator). And it used to launch fine until firefox 220.127.116.11. That is it asked for administrator password and ran without and problem. But when the firefox updated to 18.104.22.168 and onwards, the process.run() stopped working at all it started giving exception. Reproducible: Always Steps to Reproduce: 1.Write an extension with just runs an exe in vista (which is configured to run as administrator) using nsIProcess.run(). 2.Run it in Firefox 22.214.171.124 it run successfully 3.Run it in Firefox 126.96.36.199 it fails to run. Actual Results: It did not launch the process and gave the following exception 0x80520003(NS_ERROR_FILE_EXECUTION_FAILED) [nsIProcess.run] nsresult:0x80520003(NS_ERROR_FILE_EXECUTION_FAILED) Expected Results: Should have launched the process by poping up the UAC dialog. The problem goes away if I configure the Firefox to run as administrator. But this is not exceptable as a browser is never expected to run the administrator context it will be a big security hole (no offense )
This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO. Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles. If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME. This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.
Whiteboard: [CLOSEME 2010-11-15]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.