Open Bug 2023118 Opened 2 months ago Updated 2 months ago

Backup is not working for profiles restored twice with same backup.

Categories

(Firefox :: Profile Backup, defect, P3)

Firefox 150
Desktop
Windows
defect

Tracking

()

Tracking Status
firefox150 --- affected

People

(Reporter: mchiorean, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Attached image 2026-03-13_12h10_51.png

Found in

  • version: 150.0a1

Affected versions

  • versions: 150.0a1

Tested platforms

  • Affected platforms: Windows
  • Unaffected platforms: Mac, Ubuntu

Preconditions:
browser.backup.archive.enabled
browser.backup.restore.enabled
browser.backup.archive.overridePlatformCheck
browser.backup.restore.overridePlatformCheck
browser.profiles.enabled

Steps to reproduce

  1. Have a legacy profileA.
  2. Do a restore with a selectable backup B by replacing the existing profile.
  3. After restore go to about:preferences and do another restore with the same backup file B.
  4. After the second restore go to about:preferences and do a backup.

Expected result

  • Backup should be performed without issues.

Actual result

  • The following error message is displayed: ‘Hmm, there was a problem backing up’.

Notes
*We will look for regression.

Summary: Backup is not working for profiles restored twice. → Backup is not working for profiles restored twice with same backup.

hmmm I am unable to reproduce this locally - is there a step there that i might be missing?

I used a legacy backup - restored it in a selectable profile with replace - repeated that replace - and then turned on backup.

Flags: needinfo?(mchiorean)

I put a video link here.

Flags: needinfo?(mchiorean)

Could you try changing the backup location and doing a backup? Does the make it work?

Flags: needinfo?(mchiorean)

Same error if changing the location see video.

Flags: needinfo?(mchiorean)

I am unable to reproduce, but given that this only occurs upon recovering the same backup twice (likely only on the same machine), it's not a very likely scenario. Marking as P3/S3!

Severity: -- → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: