Closed
Bug 163744
Opened 23 years ago
Closed 22 years ago
error message displayed in terminal during startup from command-line
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.3alpha
People
(Reporter: salim, Assigned: netscape)
References
Details
Attachments
(1 file, 1 obsolete file)
655 bytes,
patch
|
bryner
:
review+
asa
:
approval1.3+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.0) Gecko/20020530
Build Identifier: Mozilla/5.0 (X11; U; HP-UX 9000/785; en-US; rv:1.0.1) Gecko/20020808
Starting Mozilla from the command-line, with the run-mozilla.sh script, produces
the message "md5sum not found." This seems to come from a check performed at
startup for an md5 checksumming program, which is not present on all platforms
or in all environments.
This does not affect mozilla startup; it simply produces an unnecessary piece of
debugging information.
Reproducible: Always
Steps to Reproduce:
1. start Mozilla using the run-mozilla.sh script
% ./run-mozilla.sh
2. the line "md5sum not found." will appear on screen
3. Mozilla continues to start normally
Actual Results:
The ine "md5sum not found." appeared on screen, and Mozilla started normally.
Expected Results:
Not displayed anything, unless, perhaps the -g (or -debug) switch was enabled.
This can be worked around by using an icon; however, users accustomed to
command-line startup, but without an md5 program in their path, will continue to
see the line of error output.
Reporter | ||
Comment 1•23 years ago
|
||
Adding ccs for people who have worked on this file previously.
Assignee | ||
Comment 2•23 years ago
|
||
Comment 3•23 years ago
|
||
Comment on attachment 96131 [details] [diff] [review]
redirect STDERR to /dev/null
r=bryner
Attachment #96131 -
Flags: review+
Assignee | ||
Comment 4•23 years ago
|
||
Patch has been checked in.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•23 years ago
|
Target Milestone: --- → mozilla1.2alpha
Reporter | ||
Comment 5•23 years ago
|
||
the error output (md5sum not found) still appears during startup. This might be
due to bad behaviour on the part of the type command.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Assignee | ||
Updated•23 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: mozilla1.2alpha → mozilla1.3alpha
Comment 6•22 years ago
|
||
The correct fix on AIX (and likely HP-UX from the comments above) is to
redirect the error output from the 'type' command, not the 'md5sum' command.
This prevents the warning from showing up on AIX which does not ship the GNU
md5sum program by default.
Attachment #96131 -
Attachment is obsolete: true
Updated•22 years ago
|
Attachment #110417 -
Flags: review?(bryner)
Updated•22 years ago
|
Attachment #110417 -
Flags: review?(bryner) → review+
Assignee | ||
Comment 7•22 years ago
|
||
*** Bug 184762 has been marked as a duplicate of this bug. ***
Comment 8•22 years ago
|
||
Requesting driver's approval for checkin to Mozilla 1.3. This is a one-line,
zero risk patch which fixes a warning message from being printed on Unix
machines which do not ship with the GNU md5sum program.
Flags: blocking1.3?
Updated•22 years ago
|
Attachment #110417 -
Flags: approval1.3?
Comment 9•22 years ago
|
||
pkw, it's not necessary to use the "blocking1.3?" request to get a patch landed.
Only set that flag if you feel that drivers should block the release for this
particular problem. If you want to request approval for a patch to land, the
patch approval flag is all that's required.
Flags: blocking1.3?
Comment 10•22 years ago
|
||
Comment on attachment 110417 [details] [diff] [review]
Redirect errors from 'type' command
a=asa (on behalf of drivers) for checkin to 1.3 final.
Attachment #110417 -
Flags: approval1.3? → approval1.3+
Comment 11•22 years ago
|
||
Fixed:
/cvsroot/mozilla/build/unix/run-mozilla.sh,v <-- run-mozilla.sh
new revision: 1.45; previous revision: 1.44
done
Status: NEW → RESOLVED
Closed: 23 years ago → 22 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•