Bug 487179 - spelling mistake in firefox script MOZ_LAUCHER
spelling mistake in firefox script MOZ_LAUCHER
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Jan Horak
Fedora Extras Quality Assurance
http://cvs.fedoraproject.org/viewvc/r...
: EasyFix
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-24 12:20 EST by Michael Ploujnikov
Modified: 2009-02-27 02:33 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-02-27 02:33:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michael Ploujnikov 2009-02-24 12:20:28 EST
Description of problem:
The firefox startup shell script contains a spelling mistake in one of the variable names - MOZ_LAUCHER. It should be MOZ_LAUNCHER.

Version-Release number of selected component (if applicable):
firefox.i386                       3.0.6-1.fc9

How reproducible:
Always

Steps to Reproduce:
1. $ grep -i launcher `which firefox`
2. $ grep -i laucher `which firefox`
  
Actual results:
Only the second command produces output. It is:
MOZ_LAUCHER="$MOZ_DIST_BIN/run-mozilla.sh"
  echo $MOZ_LAUCHER $script_args $MOZ_PROGRAM $MOZARGS "$@"
exec $MOZ_LAUCHER $script_args $MOZ_PROGRAM $MOZARGS "$@"


Expected results:
The first command should output:
MOZ_LAUNCHER="$MOZ_DIST_BIN/run-mozilla.sh"
  echo $MOZ_LAUNCHER $script_args $MOZ_PROGRAM $MOZARGS "$@"
exec $MOZ_LAUNCHER $script_args $MOZ_PROGRAM $MOZARGS "$@"


Additional info:
This appears to be a problem even in f10 and devel:
http://cvs.fedoraproject.org/viewvc/rpms/firefox/F-10/firefox.sh.in?revision=1.33&view=markup
http://cvs.fedoraproject.org/viewvc/devel/firefox/firefox.sh.in?revision=1.33&view=markup

Note You need to log in before you can comment on or make changes to this bug.