Closed
Bug 314970
Opened 20 years ago
Closed 17 years ago
prefs.js is executable
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 461322
People
(Reporter: mnordhoff, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051102 Firefox/1.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051102 Firefox/1.5
prefs.js is executable (permissions 755), even though it, well, shouldn't be.
Reproducible: Always
Steps to Reproduce:
1. Go to in <program>/defaults/profile or <profile>/.
2. Look down at prefs.js.
Actual Results:
prefs.js is executable.
Expected Results:
prefs.js isn't executable.
Please don't hurt me for filing a totally stupid bug. :( Especially if it already has been filed.
If prefs.js has to be executable, it should do something cool like printing a secret message or auto-configuring everything, instead of just spouting errors that don't make sense:
$ ./prefs.js
./prefs.js: line 3: /KNOPPIX: is a directory
./prefs.js: line 4: bookmarks.html: command not found
./prefs.js: line 5: bookmarks.html: command not found
./prefs.js: line 6: bookmarks.html: command not found
./prefs.js: line 7: bookmarks.html: command not found
./prefs.js: line 8: bookmarks.html: command not found
./prefs.js: line 9: bookmarks.html: command not found
./prefs.js: line 10: chrome/: is a directory
Comment 1•19 years ago
|
||
There are many files in Fx distribution itself that are executable without a reason I know: *.so, *.xml, *.png, *.xpm. Is there a bug for that?
Comment 2•19 years ago
|
||
Same with Thunderbird version 2 beta 1 (20061121)
Updated•19 years ago
|
Status: UNCONFIRMED → NEW
Component: Preferences → Build Config
Ever confirmed: true
Product: Firefox → Core
Version: unspecified → Trunk
Updated•19 years ago
|
QA Contact: preferences → build-config
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Updated•8 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•