In any case I think it is quite important that the user gets a notice about the files that could not be read and are thus not backed up.
What to do if that case is detected while selecting the include dirs in deja-dup or when duplicity runs as a user?
Offer to ask for root permissions for future runs?
Not sure. What is the problem with GIO under gksu / gksudo?
Executing "su-to-root -X -c deja-dup" correctly uses gksu here, but no ssh etc. is available.
To schedule system backups we would just need to be able to run "deja-dup --now" or the generated duplicity command from /etc/cron.daily/deja-dup.
In any case I think it is quite important that the user gets a notice about the files that could not be read and are thus not backed up.
What to do if that case is detected while selecting the include dirs in deja-dup or when duplicity runs as a user?
Offer to ask for root permissions for future runs?
Not sure. What is the problem with GIO under gksu / gksudo?
Executing "su-to-root -X -c deja-dup" correctly uses gksu here, but no ssh etc. is available.
To schedule system backups we would just need to be able to run "deja-dup --now" or the generated duplicity command from /etc/cron. daily/deja- dup.