Closed Bug 136478 Opened 23 years ago Closed 23 years ago

Installer check for running process is failing

Categories

(SeaMonkey :: Installer, defect)

x86
Windows NT
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: agracebush, Assigned: curt)

Details

Attachments

(1 file)

steps to reproduce: 1. run commercial trunk build for 4/1 with QuickLaunch enabled 2. File/exit to install todays version
steps to reproduce: 1. run commercial trunk build for 4/1 with QuickLaunch enabled 2. File/exit to install todays version 3. Run installer - will attach screen shots to show task manager with N6 and N6setup processes running as well as turbo icon in tray 4. installer finishes and launches (showing build id of 4/9) 5. review regedit and see reg key set to 4/1 build 6 close app and warning comes up to exit any open apps 7. kill process and install starts over again and performs normally expected: that Installer will detect N6 process and warn user before any installing takes place
the other screen shots of regedit and prefs are not clear after being changed from bmp to jpg files
QA Contact: bugzilla → gbush
to curt, nominating
Assignee: dveditz → curt
Keywords: nsbeta1
Looks like the "NetscapeMessageWindow" we were looking for is gone -- Bill, do you know anything about that?
No, but I want to, since that's got to be the cause of bug 136181, too. I will investigate.
The resources are screwed up in commercial builds due to bugscape bug 12226 http://bugscape.mcom.com/show_bug.cgi?id=12226 I've attached a patch there. Hopefully we'll fix this tomorrow. See also bug 136181, which this one could be a dup of.
dupe of bug 132858 rite?
No, that one predates the problem here and seems to be something else entirely.
The fix for the root cause of 136181 has been fixed on the trunk in today's build and will be fixed in branch builds as of tomorrow. This bug should be cleared up, also.
According to Bill, this has been fixed. Needs verified.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
yes this was fixed by fix to bug 12226
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: