Closed Bug 6622 Opened 25 years ago Closed 25 years ago

[PP]GetComponentFolder: No working using 1 parameter form

Categories

(Core Graveyard :: Installer: XPInstall Engine, defect, P3)

Other
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jimmykenlee, Assigned: ssu0262)

References

Details

Build: 5/17/99 SeaMonkey build 1. Use jar at http://jimbob/jars/a_getcomponentfolder.jar 2. Using the form Install.GetComponentFolder(regName+"/"+jarSrc); 3. Trigger jar RESULT: SeaMonkey crashes. The installscript does add a file as expected. However, the crash appears to occur when GetComponentFolder is called. The Install.log shows: --------------------------------------------------------------------------- Acceptance: a_getcomponentfolder --------------------------------------------------------------------------- Starting Installation at 05/17/1999 14:54:09 Installing: C:\Program Files\mozbin517\x86rel\smrtupdt.txt EXPECTED RESULT: No crash. Install.log shows that script ends gracefully. Currently, there is no output to show that GetComponentFolder gets the correct string. This will be added when support is available.
QA Contact: 4395 → 4138
Changing QA Contact from Grace to Jimmy.
jimmy - can you get a talkback report for this?
Summary: GetComponentFolder: Crashes using 1 parameter form → GetComponentFolder: No working using 1 parameter form
Build 6/7/99 Talkback report was not submitted. This is no longer crashing. Removing "Crash" from Summary.
Assignee: dougt → dveditz
setting target milestone to M8 reassign to dveditz
Target Milestone: M8
Assignee: dveditz → ssu
reassign to Sean
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
fixed. I already talked to Jimmy on how this works. Look for the fix in the next build of Seamonkey.
Status: RESOLVED → REOPENED
OS: Windows NT → Linux
Hardware: PC → Other
Summary: GetComponentFolder: No working using 1 parameter form → [PP] GetComponentFolder: No working using 1 parameter form
Build 7/7/99 Adding [PP] to Summary since this is fixed for Windows. However, this fails for Macintosh and Unix. For both Mac and Linux, the Install.log shows that the install script aborts gracefully.
Resolution: FIXED → ---
Clearing Fixed resolution since this is now re-opened.
Depends on: 8311
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Build 7/13/99 This is still a problem for Unix and Macintosh. Windows is fine. The Install.log shows that GetComponentFolder returns "null". This is not correct. For Linux, I am able to see that the the component is properly registered. For Mac, I am unable to view the netscape registry. There is a problem that I am still investigating.
Clearing Fixed resolution due to ReOpen of this bug.
Resolution: FIXED → ---
Target Milestone: M8 → M9
M8 is over...moving to M9. cathleen please move to later milestone if needed.
I have made numberous bug fixes which might cause some of these bugs to go away. I am going to mark them as FIXED so that they may be verified.
Status: RESOLVED → REOPENED
Summary: [PP] GetComponentFolder: No working using 1 parameter form → GetComponentFolder: No working using 1 parameter form
Build 7/27/99 This is still a problem. But now Windows no longer works. Removing [PP] from Summary.
Resolution: FIXED → ---
Clearing FIXED resolution due to Re-open.
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
Fixed.
Status: RESOLVED → REOPENED
Summary: GetComponentFolder: No working using 1 parameter form → [PP]GetComponentFolder: No working using 1 parameter form
Build 8/9/99 But wait there's more... Macintosh and Windows now behave as expected. The Version Registry looks fine on Linux, but the path is unexpectedly being returned as "null". Adding [PP] to Summary. The current Target Milestone is M9, but Sean and I agree that this is not an M9 blocker.
Resolution: FIXED → ---
Clearing Fixed resolution due to reopen.
Status: REOPENED → ASSIGNED
Target Milestone: M9 → M10
moving to M10
Status: ASSIGNED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
My fix to bug 10180 appears to have fixed this.
Status: RESOLVED → VERIFIED
Build 8/27/99 Fine on all platforms.
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall Engine
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.