Open
Bug 37176
Opened 25 years ago
Updated 9 years ago
Executable XPIs not listing the executables in the logfile
Categories
(Core Graveyard :: Installer: XPInstall Engine, defect, P2)
Tracking
(Not tracked)
NEW
People
(Reporter: depman1, Unassigned)
Details
Cross-platform. Used extracted builds 2000-04-25-12-M16. also see bug 37168
1. Go to http://jimbob/trigger3.html.
2. Select any of the executable xpis.
a. on NT, Try a_execute from accpt menu. (should run notepad)
b. on Linux, try a_execute_unix. (should run test_exe)
c. on Mac, try a_execute_mac. (should run simpleText)
3. Trigger. OK.
4. Check logfile.
Result: It indicates that executable is executing, but lists "xpinstall.exe"
Expected: On NT/Win98, should list "notepad", on Linux list "test_exe", on Mac
list "simpleText".
Reporter | ||
Updated•24 years ago
|
Summary: Executables are not listing the executables in the logfile → Executable XPIs not listing the executables in the logfile
Comment 3•24 years ago
|
||
Is this File.execute() or Install.execute()?
Reporter | ||
Comment 5•24 years ago
|
||
File.execute lists out executable fine.
Comment 6•24 years ago
|
||
4.x listed the temp file name we were going to execute, this probably does the
same. Not great, but not going to stop the next release either.
over to dprice.
Assignee: ssu → dprice
Status: ASSIGNED → NEW
Target Milestone: --- → mozilla0.9.8
Comment 8•23 years ago
|
||
dprice is on sabitcal. moving to next milestone.
Target Milestone: mozilla0.9.8 → mozilla0.9.9
Resetting milestone of all nsbeta1-bugs, only nsbeta1+ bugs should have a target
milestone.
Target Milestone: mozilla0.9.9 → ---
Comment 10•23 years ago
|
||
Resetting milestone, only nsbeta1+ bugs can have a milestone on them, these are
niminated, but not yet plussed.
Comment 11•23 years ago
|
||
only nsbeta1+ bugs can have milestones, resetting to ---
Comment 12•19 years ago
|
||
http://lxr.mozilla.org/mozilla1.8/source/xpcom/threads/nsProcessCommon.cpp#253
nsProcessCommon.cpp::CreateProcess returns FALSE for some reason. So retVal is
false, status becomes PR_FAILURE, the function returns
NS_ERROR_FILE_EXECUTION_FAILED, and we unravel.
I'm continuing to investigate.
Assignee: dprice → ajvincent
Comment 13•19 years ago
|
||
I was wrong; .msi files (which are what I'm looking into) are not themselves
executable. They have to be opened by msiexec.
Reassigning back to default owner.
Assignee: ajvincent → xpi-engine
QA Contact: jimmykenlee
Updated•15 years ago
|
Assignee: xpi-engine → nobody
QA Contact: xpi-engine
Assignee | ||
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•