Closed
Bug 267423
Opened 20 years ago
Closed 19 years ago
Download prefs not saving for unpriviliged users (not administrators)
Categories
(Firefox :: Settings UI, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: lindsay, Assigned: bugzilla)
Details
Which version of Firefox? Which user group? (Power Users, Users, special) What for file attributes and permissions are set on prefs.js in your FF profile?
Comment 1•20 years ago
|
||
What is this? Resolving INVALID, refile if there is an actual issue.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Comment 0 was in fact from me, although it seems to be from the reporter. I guess it is so because the reporter didn't put a comment in it.
(In reply to comment #0) > Which version of Firefox? Which user group? (Power Users, Users, special) > What for file attributes and permissions are set on prefs.js in your FF profile? I filled in all this plus a longish descritpion of the problem and the steps to replicate it - where the hell did it all go ? Firefox : RC1 Download prefs not saving for unpriviliged users (not administrators) When running a a unpriviliged user under windows 2000 (Power user group), changes to the download prefs are not saved. Tools|Options|Downloads: - "Ask me where to save every file" - "Save all Files to This Folder" 1. Log in as a unpriviliged user on Windows 2000 (either guest or Power User group) 2. Start Firefox 3. Set the Tools|Options|Downloads:"Ask me where to save every file" option 4. Exit Firefox 5. Start Firefox 6. The Above setting will be unset (off) The Tools|Options|Downloads:"Ask me where to save every file" option was turned off Tools|Options|Downloads:"Ask me where to save every file" option should have been turned on.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Version: unspecified → 1.0 Branch
a) Check the file permissions (Can you modify?) and the attributes (Is it write-protected?) of the prefs.js file in your Firefox profile. Normally you have as (Power) User the sufficient rights, because the FF profile is in your own user profile. b) Do you have an user.js file in your FF profile? Does this file contains these prefs (like browser.download.*)? All entries here overwrite the prefs.js and default prefs.
Assignee: bugs → firefox
Component: Download Manager → Preferences
QA Contact: bmo → mconnor
Comment 5•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 6•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 19 years ago
Resolution: --- → EXPIRED
Comment 7•18 years ago
|
||
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
You need to log in
before you can comment on or make changes to this bug.
Description
•