Public bug reported:
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)
** Affects: deja-dup (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug artful wayland-session
** Description changed:
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)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1734499
Title:
InvalidBackendURL: missing // - relative paths not supported for
scheme gio+invalid: gio+invalid://
Status in deja-dup package in Ubuntu:
New
Bug description:
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1734499/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
