Posts

Showing posts with the label Deja Dup

Deja Dup: "Restore Single File" fails with "cannot create directory" error message

While using Deja Dup to do a "Restore Single File" operation from within Nautilus into /etc/cups/ppd, which is owned by root, I encountered an error.  Deja Dup finds the file and tries to do the restore operation, but fails due to "cannot create directory" error. Deja Dup needs to create a temporary directory into which the restored file is temporarily placed. If Deja Dup doesn't have write permission in this directory the restore operation will therefore fail with the "cannot create directory" message. I probably could have run Deja Dup as root but maybe that's not such a good idea for one thing, and also I would have had to reenter the info regarding the access key etc. This info is already in Deja Dup if it runs in normal user mode. There also doesn't seem to be a way when running in this mode to have Deja Dup place the restored file in some other directory  (/tmp/ or /home/me/tmp) other than the canonical one (i.e. the original locati...

Deja Dup thinks current computer name is bar but it should be foo

Fedora 17 x86_64 - running the "Backup" utility aka Deja Dup. Set it up previously and ran at least one backup. Now a regularly scheduled backup starts and get an error message along the lines of "Computer Name Changed" "The existing backup is of a computer named foo but the current computer's name is bar. If this is unexpected you should backup to a different location". In my case the actual (incorrect) name of the "current computer" was something like 12-34-56-78.tvc-ip.com which made absolutely no sense at all.  (I made up the numbers which represent an ip address but the tvc-ip.com is what it really said). So what gives? "Backup" is really "Deja-Dup". "Deja-Dup is really a GUI front end for "Duplicity". "Duplicity" is apparently written in Python. When Python decides to figure out the current computer's name, it calls                           socket.getfqdn() So I ...