Description of problem: When a domain user (domain joined with realmd, standard config) tries to use deja-dup, the backup fails completely. How reproducible: All the time Steps to Reproduce: 1. Join a domain 2. Login with a user domain 3. set-up a backup with duplicity Actual results: says something about being unable to restore the metadata Expected results: Should back up your files Additional info: The problem is that by default, realmd creates a /home/<domain>/<user> home directory. /home/<domain> is owned by root:root and has only rwx-x-x rights and deja-dup is silly enough to unnecessarily want to read this diectory to make the diff instead of reading the *real* user's home directory which is fully readable and accessible: DUPLICITY: DEBUG 1 DUPLICITY: . Comparing () and () DUPLICITY: DEBUG 1 DUPLICITY: . Selecting /home DUPLICITY: DEBUG 1 DUPLICITY: . Comparing ('home',) and ('home',) DUPLICITY: WARNING 10 '/home/<domain>' DUPLICITY: . Error accessing possibly locked file /home/<domain> DUPLICITY: WARNING 10 '/home/lost+found' DUPLICITY: . Error accessing possibly locked file /home/lost+found DUPLICITY: WARNING 10 '/lost+found' DUPLICITY: . Error accessing possibly locked file /lost+found DUPLICITY: WARNING 10 '/root' DUPLICITY: . Error accessing possibly locked file /root giving read access on /home/<domain> to everyone fixes the problem.
Try http://koji.fedoraproject.org/koji/taskinfo?taskID=6728739 If you are using Fedora 20, https://admin.fedoraproject.org/updates/deja-dup-30.0-1.fc20
Will test shortly. Thank you. François.
Note: yum --enablerepo=updates-testing install duplicity The latest version is required for testing this deja-dup
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.