Closed Bug 48623 Opened 25 years ago Closed 17 years ago

win installer needs user-friendly error handling

Categories

(SeaMonkey :: Installer, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bugzilla, Unassigned)

Details

(Whiteboard: [xpibug])

Somehow I just got a Error message when installing: "Error ocurred during installation: -207 blablabla" When pressing Ok in this error dialog the installer just quits. The installer should show the user that the installation didn't success and he/she might try again. Just quiting the installer is now very user friendly.
Component: Installer: XPInstall Engine → Installer
Summary: Better error message when getting error → win installer needs user-friendly error handling
This is not the XPInstall engine but the install front end that does this. Changing component and reassigning. "Better error message when getting error" is a pretty vague summary when mixed in a list with general mozilla bugs so I'll change it to mention the installer. I'll also take the liberty of widening the scope, people have complained about the PR2 installer that if they get an error we delete all the .xpi files and they must download them all again. This really pisses people off. I guess we shouldn't just leave junk on their disk taking up space so we should at least announce we're leaving it behind or better give users the choice of saving them. This feels like a duplicate but I'll let Sean sort that out when he gets back.
Oops, forgot the reassign part...
Assignee: dveditz → ssu
QA Contact: jimmylee → gemal
The installer should display some kind of message if the installation didn't success for some reason. The text could be: "The installation was interrupted or generated an error before Mozilla could be completly installed. Your system has not been modified. To complete installation at another time, please run the installer again. Press Close to close the installer."
Depends on: 52052
Status: NEW → ASSIGNED
Priority: P3 → P2
Keywords: nsbeta1
Whiteboard: [xpibug]
Moz 0.9 tasks
Target Milestone: --- → mozilla0.9
Keywords: nsbeta1nsbeta1+
QA Contact: gemal → gbush
Keywords: nsbeta1+nsbeta1-
Just got the following error: "Error occurred during installation - Navigator: -229 SCRIPT_ERROR" Perhaps this could be changed to: "An error occurred during installation! Mozilla Setup is unable to continue. Please try to run installer again or download a new version of the installer. Error details: Module: Navigator Error text: SCRIPT_ERROR Error number: 229
Target Milestone: mozilla0.9 → mozilla0.9.1
Target Milestone: mozilla0.9.1 → ---
No longer depends on: 52052
I just ran into this with a -214 DOES_NOT_EXIST error. Ugh.
In general, wording of errors should be: | | <foo could not be done>, because <bar was wrong>. <suggestion for fixing the | problem or avoiding it in future>. | E.g.: `Mozilla could not be installed, because the folder ?Program Files? could not be changed. Check that the folder is not locked and that the disk is not write-protected, and try again.' Extra text, such as `No changes have been made to your installation disk', should be given in a separate paragraph below the main error message. So, the first step to fixing this bug is to make a three-column table: error number, error fragment text (in en-US, this would be the bit after `because'), and suggestions for fixing the error. Make provision in the error fragment text for a relevant file or folder name to be inserted.
Keywords: nsbeta1-
over to Curt.
Assignee: ssu → curt
Status: ASSIGNED → NEW
Target Milestone: --- → mozilla1.0
Resetting milestone of all nsbeta1-bugs, only nsbeta1+ bugs should have a target milestone.
Target Milestone: mozilla1.0 → ---
Resetting milestone, only nsbeta1+ bugs can have a milestone on them, these are niminated, but not yet plussed.
only nsbeta1+ bugs can have milestones, resetting to ---
*** Bug 108026 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
Assignee: curt → nobody
Priority: P2 → --
QA Contact: agracebush → general
Seamonkey and Firefox are using a new NSIS based installer. resolving this old bug, please reopen if you still get this with the new installer
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.