Closed
Bug 195265
Opened 22 years ago
Closed 15 years ago
RFE: Mozilla should wipe-out the cached files in ~/.mozilla profiles when using a different version than the one which created the files
Categories
(SeaMonkey :: General, enhancement)
SeaMonkey
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: roland.mainz, Unassigned)
Details
(Whiteboard: bugday0420)
RFE: Mozilla should wipe-out the cached files in ~/.mozilla profiles when using
a different version (or platform - for example when sharing a profile between
Win32 and Linux) than the one which created the files (maybe this helps for
issues like bug 169777 ("Corrupted XUL.mfl / XUL.mfasl / XUL FastLoad File
freezes/hangs (not crashes) Mozilla/MailNews/etc (when opening Edit >
Preferences, or at "random")"), too :)
Comment 1•22 years ago
|
||
the installer should know anything about the profiles. this would be up to the
browser.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 2•22 years ago
|
||
Henrik Gemal wrote:
> the installer should know anything about the profiles. this would be up to the
> browser.
OK, which component would you suggest ?
Status: RESOLVED → REOPENED
Component: Installer → Browser-General
Resolution: INVALID → ---
Updated•20 years ago
|
Product: Browser → Seamonkey
![]() |
||
Comment 4•16 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
![]() |
||
Comment 5•15 years ago
|
||
For fastload files, this works fine for me.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 15 years ago
Resolution: --- → WORKSFORME
![]() |
||
Updated•15 years ago
|
Assignee: asa → nobody
QA Contact: asa → general
Whiteboard: bugday0420
You need to log in
before you can comment on or make changes to this bug.
Description
•