Closed Bug 1319594 Opened 9 years ago Closed 2 years ago

Many users report unable to restore bookmarks from backups

Categories

(Toolkit :: Places, defect, P3)

Product:
Toolkit
Component:
Places
Version:
45 Branch
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: FredMcD, Unassigned)

References

Details

(Keywords: dataloss)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 Build ID: 20161031153904 Steps to reproduce: I have seen this problem several times in the support forum. Here is the latest; Bookmarks restore doesn't work/can't bookmark https://support.mozilla.org/en-US/questions/1147808 Actual results: User: Found Restore, can see a list of backup bookmark files with dates and file size, but get message "unable to process backup file."
Has STR: --- → no
Component: Untriaged → Bookmarks & History
It would be interesting to know if those backup report 0 items in the menu, and maybe get some of them, even privately. And also if the current database is sane or corrupt, since maybe the problem is not the backup but the destination... Places Maintenance add-on can tell this. Without one of these broken backups and that indication there's nothing to work on here...
The user is https://support.mozilla.org/en-US/user/cfcf May I suggest you contact him directly?
Another user reports same problem; https://support.mozilla.org/en-US/questions/1149508
Severity: normal → major
Component: Bookmarks & History → Places
Keywords: dataloss
Product: Firefox → Toolkit
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
as a side note, our system tells that the backup was corrupt even when it was able to restore everything but 1 bookmark... We should improve on that error messaging.
I have a question. Why compress the backup file? With the problems it causes, why not just do a straight HTML copy?
how is that related to this bug? the backup is not unreadable due to the compression, it's unreadable because of the backup contents.

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: major → --

Unfortunately there is no specific details for this, so there isn't much we can do about it. If new details are reported we can always open a fresh bug.

We do have other bugs on improving error handling and the details in the error message.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.