1

Deja Dup I used today but got this problem -

Backup Finished Could not backup the following files. Please make sure you are able to open them.

/home/anony/.config/enchant
/home/anony/.dbus

Annex

ls -al /home/anony/.config/enchant

total 24
drwx------  2 root  root  4096 Oct 19  2015 .
drwx------ 37 anony anony 4096 Nov 23 09:42 ..
-rw-r--r--  1 root  root     0 Oct 19  2015 en_...dic
-rw-r--r--  1 root  root     0 Oct 19  2015 en_...exc


ls -al /home/anony/.dbus

total 20
drwx------  3 root  root   4096 Oct 19  2015 .
drwx------ 39 anony anony 12288 Nov 30 22:25 ..
drwx------  2 root  root   4096 Oct 19  2015 session-bus
  • 2
    run ls -al /home/..../.config/enchant /home/..../.dbus to see who owns those files – George Udosen Nov 29 '17 at 22:28
  • @George Please see Annex in original post – jam Nov 30 '17 at 22:41
  • @wjandrea Regarding your 2 questions in Answer Section: (1) The only changes were automatic upgrades. (2) I got the ls results by sudo prefix. How useful are these files to include in backup /home/anony/.config/enchant and /home/anony/.dbus - if I restore backup and these files are not there, can I still restore system? – jam Nov 30 '17 at 23:31
  • @jam I think you're missing the point. Those dirs should not be owned by root. That indicates some other issue. Maybe it was as benign as a typo in a chmod command, or maybe it's more systemic. – wjandrea Dec 1 '17 at 3:54
  • But in any case, you don't need to backup ~/.dbus at all, and for ~/.config/enchant, you can just chown it and run the backup again. I'm not sure how important it is -- it seems to be related to the enchant package, which is a spell-checker. – wjandrea Dec 1 '17 at 3:55
2

This isn't a Deja-Dup issue. Those dirs shouldn't be owned by root.

You can run this command to take ownership back:

sudo chown -R $USER:$USER ~/.dbus ~/.config/enchant/

This will fix the immediate issue, but since we don't know the cause, the issue may return. Did you make any changes recently that might have caused this? Where you're able to run ls on the dirs without sudo, that means you're running a root shell. That may be related. Update: OP actually is using sudo.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.