Bug 2135134 - "Folder is empty" when trying to restore
Summary: "Folder is empty" when trying to restore
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: duplicity
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-16 15:53 UTC by iolo
Modified: 2022-11-21 15:37 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-11-21 15:37:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description iolo 2022-10-16 15:53:26 UTC
Description of problem:
In F36 I made a backup with Deja Dup and made sure it completed. Then I shutdown the PC, installed the F37 beta, and tried to restore files from that same backup I made earlier. However, all I see in Deja Dup is "Folder is Empty". Deja Dup does seem to see the backups in some sense, because it show me the date in the lower-right corner. Even if I try to select an earlier backup, it still only says "Folder is Empty".

Version-Release number of selected component (if applicable):
43.4-2.fc37

How reproducible:
Always

Steps to Reproduce:
1. Make a backup with Deja-Dup in Fedora 36
2. Install Fedora 37 beta
3. Try to restore the earlier backup

Actual results:
Deja Dup shows "Folder is empty".

Expected results:
Deja Dup lists files and folders available for restoration.

Additional info:

Comment 1 Gwyn Ciesla 2022-10-17 15:52:39 UTC
What version of duplicity do you have? Also, does a new backup to a different location work?

Comment 2 iolo 2022-10-18 23:08:34 UTC
The duplicity package is version 1.0.0-1.fc37. Creating a new backup to a different location does work. I also tested going back to F36 and trying the restore there. It works fine with duplicity package version 0.8.23-1.fc36, even from this location where I'm getting "Folder is empty" in F37.

I thought to test if I can reproduce this when the backups are not protected by a password. I could not. So this problem only happens when the backup is password-protected. In addition, it looks like a password-protected backup works fine if I make it in F37 to begin with, but not if I make one in F36.

Comment 3 Gwyn Ciesla 2022-10-19 20:08:48 UTC
I think this is fixed in 1.0.1.

https://duplicity.gitlab.io/stable/CHANGELOG.html

I'll get that out ASAP.

Comment 4 Fedora Update System 2022-10-19 20:35:18 UTC
FEDORA-2022-279b4ac7ff has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-279b4ac7ff

Comment 5 Fedora Update System 2022-10-21 14:41:02 UTC
FEDORA-2022-279b4ac7ff has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-279b4ac7ff`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-279b4ac7ff

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 iolo 2022-10-21 16:27:21 UTC
I installed the update, DNF reports duplicity version as 1.0.1-1.fc37 but I'm still seeing this problem even after a reboot and a dconf reset.

Comment 7 Gwyn Ciesla 2022-10-21 16:52:48 UTC
Odd, thank  you. I've removed this bug from the update so it stays open.

Comment 8 iolo 2022-11-19 16:44:42 UTC
After installing the proper release of Fedora 37 on two machines, I was able to restore encrypted backups made with Fedora 36 just fine. In other words, whatever was causing this issue seems to be gone now.

Comment 9 Gwyn Ciesla 2022-11-21 15:37:51 UTC
Excellent!


Note You need to log in before you can comment on or make changes to this bug.