Closed
Bug 282011
Opened 21 years ago
Closed 20 years ago
Some preferences reset after installing an update or extension.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: graham.sutherland1, Assigned: bugzilla)
Details
(Whiteboard: [asaP2])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041110 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041110 Firefox/1.0
When I install an Extension, update one, or simply update firefox to the latest
version, a lot of settings get reverted back to their original values. The most
obvious and annoying one is that the download location is reset to "Always to
this location..." which has been set to desktop. Also, the message boxes like
"You are sending this information through an unencrypted page, are you sure?"
start coming up again as if all the "Don't ask me again" values in the settings
were reverted back to false.
This has occured on both of my computers.
Reproducible: Sometimes
Steps to Reproduce:
1. Install a new extension (I used FlashGot for first result, then Linky)
2. Restart the browser.
3. Bug sometimes occurs now.
4. Update the extension to latest version.
5. Restart the browser.
6. Bug sometimes occurs now.
As I stated above, you can also get the same thing happening when you update
Firefox. It's happened twice to me, once ages ago and again when I updated to v1.0
Actual Results:
Nothing changed the first time, but the message box occured the second time when
I went to enter a query into Google. All the settings have been reset.
Expected Results:
Updated the software/extension without losing the settings.
Main PC:
Processor: AMD ATHLON 2000 (1313MHz)
Motherboard: GIGABYTE GA7DXR+
Graphics: ATI RADEON 9200 PRO (Current Resolution: 1024x768x32)
Sound: SOUNDBLASTER PCI128
Hard Disks:
* MAXTOR 80GB (Assigned 'C' on device 'RAID')
* MAXTOR 30GB (Assigned 'D' on device 'RAID')
* IBM 120GB (Assigned 'E' on device 'SCSI')
Second PC:
Processor: AMD ATHLON 1200 (912MHz)
Motherboard: JETWAY 663AS
Graphics: ATI RADEON 7500 (Current Resolution: 1024x768x32)
Sound: None
Hard Disks:
* MAXTOR 80GB (Assigned 'C' on device 'IDE')
* MAXTOR 40GB (Assigned 'D' on device 'IDE')
Bug happened on both computers. They both have a wireless 52MBps LAN card in
them, which connects to my router.
I think the bug can be resolved or worked around by backing up the settings
before the update and restoring them after the update.
Updated•20 years ago
|
Whiteboard: [asaP2]
Comment 1•20 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 2•20 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
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•