I can perform that workaround, too, but the real culprit is gvfs and it
really should be fixed.
On Sat, Jun 2, 2018 at 3:15 AM, Oscar Carlberg <email address hidden>
wrote:
> I have the exact same problem. A workaround I use for now is to mount
> the NFS share in fstab and point deja-dup to the local mount, not ideal
> though.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1773717
>
> Title:
> Deja Dup will not allow nfs backup
>
> Status in Déjà Dup:
> New
>
> Bug description:
> This works as expected on my Arch Linux machine. Does not work on
> either machine running Ubuntu 18.04
>
> From the command line when I run duplicity, I ge tthis
>
> $ duplicity .bashrc nfs://192.168.2.198/mnt/first_NAS/Backups/Kris
> UnsupportedBackendScheme: scheme not supported in url: nfs://
> 192.168.2.198/mnt/first_NAS/Backups/Kris
>
> I do not know if this is the correct syntax or not form teh cli, but I
> thouught I'd try to see if there is any info which may help with
> diagnosis.
>
> I want to use nfs as my repository. I can mount it, so it exists. I
> can have a non elevated user (does not have sudo capability) on the
> Arch machine also use an nfs directory on the server as his backup
> location.
>
> It apears that there is a package which is not installed or some
> package is not yet configured. I am not aware of anything I did on the
> Arch machine to cause this to work.
>
> $ lsb_release -d
> Description: Ubuntu 18.04 LTS
>
> $ dpkg-query -W deja-dup duplicity
> deja-dup 37.1-2fakesync1
> duplicity 0.7.17-0ubuntu1
>
>
> $ cat /tmp/deja-dup.gsettings
> org.gnome.DejaDup last-restore ''
> org.gnome.DejaDup periodic true
> org.gnome.DejaDup periodic-period 7
> org.gnome.DejaDup full-backup-period 90
> org.gnome.DejaDup backend 'remote'
> org.gnome.DejaDup last-run ''
> org.gnome.DejaDup nag-check ''
> org.gnome.DejaDup prompt-check '2018-05-15T00:41:10.878761Z'
> org.gnome.DejaDup root-prompt true
> org.gnome.DejaDup include-list ['/home/kmgrider/Documents',
> '/home/kmgrider/Downloads', '/home/kmgrider/eagle',
> '/home/kmgrider/Pictures', '/home/kmgrider/Videos']
> org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
> org.gnome.DejaDup last-backup ''
> org.gnome.DejaDup allow-metered false
> org.gnome.DejaDup delete-after 0
> org.gnome.DejaDup.Rackspace username ''
> org.gnome.DejaDup.Rackspace container 'X550VX'
> org.gnome.DejaDup.S3 id ''
> org.gnome.DejaDup.S3 bucket ''
> org.gnome.DejaDup.S3 folder 'X550VX'
> org.gnome.DejaDup.OpenStack authurl ''
> org.gnome.DejaDup.OpenStack tenant ''
> org.gnome.DejaDup.OpenStack username ''
> org.gnome.DejaDup.OpenStack container 'X550VX'
> org.gnome.DejaDup.GCS id ''
> org.gnome.DejaDup.GCS bucket ''
> org.gnome.DejaDup.GCS folder 'X550VX'
> org.gnome.DejaDup.Local folder 'X550VX'
> org.gnome.DejaDup.Remote uri 'nfs://192.168.2.198/mnt/first_NAS/Backup'
> org.gnome.DejaDup.Remote folder 'Kris'
> org.gnome.DejaDup.Drive uuid ''
> org.gnome.DejaDup.Drive icon ''
> org.gnome.DejaDup.Drive folder '$HOSTNAME'
> org.gnome.DejaDup.Drive name ''
> org.gnome.DejaDup.GOA id ''
> org.gnome.DejaDup.GOA folder 'X550VX'
> org.gnome.DejaDup.GOA type 'google'
> org.gnome.DejaDup.File short-name ''
> org.gnome.DejaDup.File type 'normal'
> org.gnome.DejaDup.File migrated true
> org.gnome.DejaDup.File name ''
> org.gnome.DejaDup.File path ''
> org.gnome.DejaDup.File uuid ''
> org.gnome.DejaDup.File icon ''
> org.gnome.DejaDup.File relpath @ay []
>
> $ cat /tmp/deja-dup.log
> $ DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log
>
> ** (org.gnome.DejaDup:13905): WARNING **: 20:16:27.467:
> BackendRemote.vala:86: The specified location is not supported
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/deja-dup/+bug/1773717/+subscriptions
>
I can perform that workaround, too, but the real culprit is gvfs and it
really should be fixed.
On Sat, Jun 2, 2018 at 3:15 AM, Oscar Carlberg <email address hidden>
wrote:
> I have the exact same problem. A workaround I use for now is to mount /bugs.launchpad .net/bugs/ 1773717 168.2.198/ mnt/first_ NAS/Backups/ Kris endScheme: scheme not supported in url: nfs:// 2.198/mnt/ first_NAS/ Backups/ Kris dup.gsettings 15T00:41: 10.878761Z' kmgrider/ Documents' , kmgrider/ Downloads' , '/home/ kmgrider/ eagle', kmgrider/ Pictures' , '/home/ kmgrider/ Videos' ] DejaDup. Rackspace username '' DejaDup. Rackspace container 'X550VX' DejaDup. S3 id '' DejaDup. S3 bucket '' DejaDup. S3 folder 'X550VX' DejaDup. OpenStack authurl '' DejaDup. OpenStack tenant '' DejaDup. OpenStack username '' DejaDup. OpenStack container 'X550VX' DejaDup. GCS id '' DejaDup. GCS bucket '' DejaDup. GCS folder 'X550VX' DejaDup. Local folder 'X550VX' DejaDup. Remote uri 'nfs:// 192.168. 2.198/mnt/ first_NAS/ Backup' DejaDup. Remote folder 'Kris' DejaDup. Drive uuid '' DejaDup. Drive icon '' DejaDup. Drive folder '$HOSTNAME' DejaDup. Drive name '' DejaDup. GOA id '' DejaDup. GOA folder 'X550VX' DejaDup. GOA type 'google' DejaDup. File short-name '' DejaDup. File type 'normal' DejaDup. File migrated true DejaDup. File name '' DejaDup. File path '' DejaDup. File uuid '' DejaDup. File icon '' DejaDup. File relpath @ay [] DejaDup: 13905): WARNING **: 20:16:27.467: vala:86: The specified location is not supported /bugs.launchpad .net/deja- dup/+bug/ 1773717/ +subscriptions
> the NFS share in fstab and point deja-dup to the local mount, not ideal
> though.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Deja Dup will not allow nfs backup
>
> Status in Déjà Dup:
> New
>
> Bug description:
> This works as expected on my Arch Linux machine. Does not work on
> either machine running Ubuntu 18.04
>
> From the command line when I run duplicity, I ge tthis
>
> $ duplicity .bashrc nfs://192.
> UnsupportedBack
> 192.168.
>
> I do not know if this is the correct syntax or not form teh cli, but I
> thouught I'd try to see if there is any info which may help with
> diagnosis.
>
> I want to use nfs as my repository. I can mount it, so it exists. I
> can have a non elevated user (does not have sudo capability) on the
> Arch machine also use an nfs directory on the server as his backup
> location.
>
> It apears that there is a package which is not installed or some
> package is not yet configured. I am not aware of anything I did on the
> Arch machine to cause this to work.
>
> $ lsb_release -d
> Description: Ubuntu 18.04 LTS
>
> $ dpkg-query -W deja-dup duplicity
> deja-dup 37.1-2fakesync1
> duplicity 0.7.17-0ubuntu1
>
>
> $ cat /tmp/deja-
> org.gnome.DejaDup last-restore ''
> org.gnome.DejaDup periodic true
> org.gnome.DejaDup periodic-period 7
> org.gnome.DejaDup full-backup-period 90
> org.gnome.DejaDup backend 'remote'
> org.gnome.DejaDup last-run ''
> org.gnome.DejaDup nag-check ''
> org.gnome.DejaDup prompt-check '2018-05-
> org.gnome.DejaDup root-prompt true
> org.gnome.DejaDup include-list ['/home/
> '/home/
> '/home/
> org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
> org.gnome.DejaDup last-backup ''
> org.gnome.DejaDup allow-metered false
> org.gnome.DejaDup delete-after 0
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
> org.gnome.
>
> $ cat /tmp/deja-dup.log
> $ DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log
>
> ** (org.gnome.
> BackendRemote.
>
> To manage notifications about this bug go to:
> https:/
>