InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid://

[Ads20000]

Workaround: Delete your backup and make a new one

---

Same problem as https://bugs.launchpad.net/deja-dup/+bug/1717230 but opening a new bug because as far as I know that's standard practice when a bug is apparently not fixed by a previous fix? If that's not correct, then instead the status of the bug needs to be changed back to Confirmed from Fix Released.

I ran into this bug by plugging in my external drive (with a backup on it) and trying to (update my) back up to it.

The bug is potentially a regression in 36.2-0ubuntu1 (since the bug was apparently fixed in 36.1-0ubuntu1).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: deja-dup 36.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 26 02:39:52 2017
InstallationDate: Installed on 2017-08-03 (114 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to artful on 2017-10-21 (35 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Claud S (claud)]

Got the same error but in my case the backup had already been running for a while when suddenly a window was shown:
Backup Failed
InvalidBackendURL: missing // - relative paths not supported for scheme invalid: invalid://

uname: 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

packages:
deja-dup/artful,now 36.2-0ubuntu1 amd64 [installed]
deja-dup-caja/artful,artful 0.0.4-0ubuntu2 all
duplicity/artful,now 0.7.12-1ubuntu1 amd64 [installed]

[Vej (vej)]

This should be "fixed again" in 37.1-0ubuntu1, see bug #1715582.

Setting this as a duplicate.

Best

Vej

[Ads20000 (ads20000)]

I still have this problem in Ubuntu 18.04 (with the backup I made on 17.10 (if I recall correctly)).

[Ads20000 (ads20000)]

Removing the bug this was marked a dupe of ( bug 1715582 ) because I still have this issue on 18.04 (albeit without the 'gio+' prefixes in the title.

[Vej (vej)]

Hello Ads2000.

The "fix" for the previous duplicate was telling the users to include a share, if I got this right. So could you please ensure, that your server address is something like smb://gnome.org/deja-dup instead of just smb://gnome.org/?

Thanks

[Ads20000 (ads20000)]

In which case the fix is not relevant for this bug, since I was backing up to a USB stick, not a server?
I can't reproduce this bug now because I did a new full backup to workaround the problem, but it seems other people are affected in any case, so perhaps someone affected could provide more details about this bug if I can't.