Closed
Bug 45721
Opened 24 years ago
Closed 23 years ago
No trigger info from install.log after initial launch after wizard install
Categories
(Core Graveyard :: Installer: XPInstall Engine, defect, P3)
Core Graveyard
Installer: XPInstall Engine
Tracking
(Not tracked)
VERIFIED
WORKSFORME
mozilla0.9.8
People
(Reporter: jimmykenlee, Assigned: slogan)
References
Details
Build: 2000-07-17-09-M17(WIN), 2000-07-17-08-M17(MAC) 1. Install Netscape 6 using the install wizard 2. After the initial launch after installation, open http://jimbob/trigger3.html, and trigger any test case such as a_adddelregfile 3. Verify installation RESULT: Both directory and file is installed. Install.log has no record of this xpi every being run. On Windows, the install.log is not even created. If several other xpis are triggered, they too do not appear from the install.log. So it's not just one xpi. It is whatever is triggered after that initial launch. EXPECTED RESULT: Log information exists from triggering this test archive. This was the behavior many months ago. NOTE: Subsequent sessions appear to be fine (ie info is found in install.log after triggering xpis). This appears to only affect the very first launch after a successfuly installation from the wizard.
Comment 1•24 years ago
|
||
this is also happening on linux. Need to quit & relaunch seamonkey.
OS: Windows NT → All
Hardware: PC → All
Summary: No trigger info from install.log after initial launch after wizard install (Win and Mac) → No trigger info from install.log after initial launch after wizard install
Nominating. This may already be fixed.
Assignee: dveditz → syd
Keywords: nsbeta1
Is it fixed? If so, please mark it FIXED.
Keywords: nsbeta1
QA Contact to Grace. Please check on trunk.
QA Contact: jimmylee → gbush
Comment 5•23 years ago
|
||
fixed on all platforms including OS X - trunk builds 200112030x
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
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
•