Closed Bug 307845 Opened 19 years ago Closed 18 years ago

all extensions and themes disappeared when computer is restarted after power failure;

Categories

(Toolkit :: Add-ons Manager, defect)

1.7 Branch
x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 324111

People

(Reporter: gnavmail, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

all extensions and themes disappeared when computer is restarted after  power
failure;  Theme update was running before power failrure.

I think this is due to check disk utility of windows. can't we do anything?

please make it more robust.


Reproducible: Didn't try

Steps to Reproduce:
1.update theme
2.power failure
3.all extensions and themes are gone.

Actual Results:  
all extensions and themes are gone restart after power failure during update
process.

Expected Results:  
extensions and themes should not disappear due to power failure during update
process.
Summary: all extensions and themes disappeared when computer is restarted after power failure; → all extensions and themes disappeared when computer is restarted after power failure;
It is always recommendable to backup your profile first before upgrading or
making other changes. See http://www.mozilla.org/support/firefox/faq
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8) Gecko/20051107 Firefox/1.5

In my experience, a system crash is not necessary for this! I keep having the same problem, but my build is now a few days old. I'll report back as soon as I've had the chance to try it on the newest build.
Confirmed on FF 1.5 final!

Only difference is that I shut down the computer normally.

This has never happened before; I've used FF since before 1.0.

Steps to Reproduce:
1. Uninstall 1.0.7
2. Remove profile data
3. Install 1.5 final
4. Install extensions
5. Restart FF several times (still works)
6. Restart PC
7. Start FF

The contents of extensions.ini are shown below:
[ExtensionDirs]
Extension0=C:\Documents and Settings\vengmark\Application Data\Mozilla\Firefox\Profiles\g4rlpj7m.default\extensions\{34274bf4-1d97-a289-e984-17e546307e4f}
Extension1=C:\Documents and Settings\vengmark\Application Data\Mozilla\Firefox\Profiles\g4rlpj7m.default\extensions\undoclosetab@dorando
Extension2=C:\Documents and Settings\vengmark\Application Data\Mozilla\Firefox\Profiles\g4rlpj7m.default\extensions\{909409b9-2e3b-4682-a5d1-71ca80a76456}
Extension3=C:\Documents and Settings\vengmark\Application Data\Mozilla\Firefox\Profiles\g4rlpj7m.default\extensions\{5a2b4e34-ce62-42e9-a658-06ba4490adf8}
Extension4=C:\Documents and Settings\vengmark\Application Data\Mozilla\Firefox\Profiles\g4rlpj7m.default\extensions\filtersetg@updater
Extension5=C:\Documents and Settings\vengmark\Application Data\Mozilla\Firefox\Profiles\g4rlpj7m.default\extensions\{c36177c0-224a-11da-8cd6-0800200c9a66}
Extension6=C:\Documents and Settings\vengmark\Application Data\Mozilla\Firefox\Profiles\g4rlpj7m.default\extensions\{463F6CA5-EE3C-4be1-B7E6-7FEE11953374}
[ThemeDirs]
Extension0=C:\Program Files\Mozilla Firefox\extensions\{972ce4c6-7e08-4474-a285-3208198ce6fd}

Notes:
- Running Windows XP
- There's only one profile for this user on this machine
- Other profile contents, such as bookmarks and settings, work just fine
Oops!

Firefox 1.5 was overwritten by 1.0.4 (by another installation), and that seems to have overwritten the extensions.rdf file. Reinstalling 1.5 fixed the problem!
naveen, this sounds like Bug 324111 which has been fixed - actually a workaround - for Firefox 2.0.

Over to EM
Component: Startup and Profile System → Extension/Theme Manager
QA Contact: startup → extension.manager
Version: unspecified → 1.0 Branch
Quite sure this is a dupe of Bug 324111.

*** This bug has been marked as a duplicate of 324111 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.