Closed
Bug 399530
Opened 18 years ago
Closed 16 years ago
Forced update-lost extensions,bookmarks;can't restore backup of extensions?
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: dalexander43, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; http://www.winwax.com (V1.5.0.917); .NET CLR 2.0.50727; .NET CLR 1.1.4322)
Build Identifier: 2.0.0.7
Yesterday it has been forced by reboot un FF update to 2.0.0.7 which was ALREADY installed for 1 months and with lots of customized extensions.add-ons.
I could restore the bookmarks from backup, there are the extensions on the backup but can't reinstall them into new page. How can I restore my old extensions from backup?
Regards
Daniel
Reproducible: Always
Steps to Reproduce:
1.Forced update without warning or notice>I've gort forced reboot
2.I've got an empty 2007 home page, without old bookmartks & extensions/add-ons
3.I restore upon my latest backup, I can seein directory extensions the jp files
but I don't find any way to reattach them with lost cusyomization which sholud be saved in the backup somewhere.
Actual Results:
Lost extensions/uninstalled
It should haave kept EXISTING bookmarks & extensions like when I was running 2006 and I WAS INFORMED about the new ver 2007, which I have installed openly, not like a Trojan as it happened now! Was this an update on THE SAME VERSION or a trojan code similar to FF?? That's my question. What shall I do now to recover my extensions and be sure is not a phishing thing!
Comment 1•18 years ago
|
||
Not a security sensitive bug report. You should try getting support using one of the options listed at http://www.mozilla.com/en-US/support/ .
Group: security
| Assignee | ||
Updated•17 years ago
|
Product: Firefox → Toolkit
Comment 2•16 years ago
|
||
no further informations after support intervention, nor enough steps to reproduce, this looks like incomplete.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•