[Desktop-packages] [Bug 1880830] Re: deja-dup failing with gpg read errors

[Vej]

** Also affects: deja-dup
   Importance: Undecided
   Status: New

** Changed in: deja-dup
   Status: New => Confirmed

** Changed in: deja-dup
   Importance: Undecided => Critical

** Changed in: deja-dup
   Importance: Critical => Medium

** Changed in: deja-dup
   Status: Confirmed => Triaged

-- 
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/1880830

Title:
  deja-dup failing with gpg read errors

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Starting a couple weeks ago, backups have begun failing with the
  following message. Until now, I have had no problems with backups; I
  backup via ssh to a cloud provider. (Until ~6 months ago I was backing
  up via ssh to a machine on my local net.) The scheduled backup asks
  for my ssh key passphrase and backup encryption passphrase as normal,
  but a few minutes later this error is displayed. The mounted ssh
  filesystem is visible in Nautilus and looks normal to me.

  GPGError: GPG Failed, see log below:
  = Begin GnuPG log =
  gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect
  gpg: AES256 encrypted data
  gpg: encrypted with 1 passphrase
  gpg: block_filter 0x562ce7e1c020: read error (size=16008,a->size=16008)
  gpg: block_filter 0x562ce7e1ccc0: read error (size=15992,a->size=15992)
  gpg: WARNING: message was not integrity protected
  gpg: block_filter: pending bytes!
  gpg: block_filter: pending bytes!
  = End GnuPG log =

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: deja-dup 40.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 27 00:27:14 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2016-04-15 (1503 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to eoan on 2020-01-01 (147 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1880830/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1962593] Re: SMB Mount to backup directory prevents mounting parent directory

[Vej]

Hello Dan,

thank you for reporting this bug. I am triaging this as "Medium" for
Ubuntu because it has "a moderate impact on a core application" but
"Low" for Déjà Dup (upstream) as it does not affect any interaction in
the application itself.

Some comments on the proposed solutions:

Déjà Dup is unlikely to implement a new "Share root" because that goes
against the policy of providing a tool for (new) standard users and
keeping the interface as simple as possible.

The second solution is much better in this regard as it hides the
workaround from the user.

Leaving Déjà Dup as "New" for now as I will have to check who does the
mount in the end.

** Changed in: deja-dup
   Importance: Undecided => Low

-- 
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/1962593

Title:
  SMB Mount to backup directory prevents mounting parent directory

Status in Déjà Dup:
  New
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  May also apply to the "duplicity" package and is related to network
  "mount"s:

  To reproduce:
  * Set up a writeable SMB share: smb://1.2.3.4/backup
  * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup
  * Using "deja-dup" -> "Storage location" set:
  Storage location: Network Server
  Network Location: smb://1.2.3.4/backup/UbuntuBackup
  Folder: MyMachineBackup
  * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup")
  * Select "deja-dup" -> "Overview" -> "Back Up Now..."
  * Allow the backup to start, but not finish
  * Go to Nautilus (file browser) -> "+ Other Locations"
    - At the bottom set "Connect to server" to: smb://1.2.3.4/backup

  Result:
  * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the 
"UbuntuBackup" subdir is currently mounted
  * Can happen at semi-random times if the backup is on a schedule
  * This is especially a problem when backing up remotely over a VPN which can 
take a long time
  * Prevents access to all parent folders of the backup folder
  * Nautilus will hang, unable to mount the "backup" parent directory
  * Also a problem if the "smb://1.2.3.4/backup" folder is bookmarked in 
nautilus
  * This problem is persistent throughout backup process and for a period of 
time afterwards until the mount to "UbuntuBackup" times out or the backup 
process exits

  Possible solutions:
  * Add a configuration option to deja-dup/duplicity to specify the "Share 
root" and mount that first before accessing the configured "Network Location"
  * Have deja-dup or duplicity attempt to mount the parent 
directory/directories first by starting at the root of the SMB share and 
walking down the directory tree until a successful mount is made. In the above 
example, start by attempting to mount "smb://1.2.3.4/backup" first and then 
"smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, 
try each one successively)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: deja-dup 40.7-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 08:51:47 2022
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2021-09-13 (168 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1962593/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1962593] Re: SMB Mount to backup directory prevents mounting parent directory

[Vej]

** Changed in: deja-dup (Ubuntu)
   Status: New => Triaged

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1962593

Title:
  SMB Mount to backup directory prevents mounting parent directory

Status in Déjà Dup:
  New
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  May also apply to the "duplicity" package and is related to network
  "mount"s:

  To reproduce:
  * Set up a writeable SMB share: smb://1.2.3.4/backup
  * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup
  * Using "deja-dup" -> "Storage location" set:
  Storage location: Network Server
  Network Location: smb://1.2.3.4/backup/UbuntuBackup
  Folder: MyMachineBackup
  * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup")
  * Select "deja-dup" -> "Overview" -> "Back Up Now..."
  * Allow the backup to start, but not finish
  * Go to Nautilus (file browser) -> "+ Other Locations"
    - At the bottom set "Connect to server" to: smb://1.2.3.4/backup

  Result:
  * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the 
"UbuntuBackup" subdir is currently mounted
  * Can happen at semi-random times if the backup is on a schedule
  * This is especially a problem when backing up remotely over a VPN which can 
take a long time
  * Prevents access to all parent folders of the backup folder
  * Nautilus will hang, unable to mount the "backup" parent directory
  * Also a problem if the "smb://1.2.3.4/backup" folder is bookmarked in 
nautilus
  * This problem is persistent throughout backup process and for a period of 
time afterwards until the mount to "UbuntuBackup" times out or the backup 
process exits

  Possible solutions:
  * Add a configuration option to deja-dup/duplicity to specify the "Share 
root" and mount that first before accessing the configured "Network Location"
  * Have deja-dup or duplicity attempt to mount the parent 
directory/directories first by starting at the root of the SMB share and 
walking down the directory tree until a successful mount is made. In the above 
example, start by attempting to mount "smb://1.2.3.4/backup" first and then 
"smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, 
try each one successively)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: deja-dup 40.7-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 08:51:47 2022
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2021-09-13 (168 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1962593/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1915161] Re: deja dup won't restore a folder where name contains apostrophe and space

[Vej]

** Also affects: deja-dup (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: deja-dup (Ubuntu Groovy)
   Status: New => Triaged

** Changed in: deja-dup (Ubuntu Groovy)
   Importance: Undecided => Medium

** Also affects: duplicity (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: duplicity (Ubuntu)
   Status: New => Fix Released

** Changed in: duplicity (Ubuntu Groovy)
   Status: New => Triaged

** Changed in: duplicity (Ubuntu Groovy)
   Importance: Undecided => Medium

-- 
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/1915161

Title:
  deja dup won't restore a folder where name contains apostrophe and
  space

Status in deja-dup package in Ubuntu:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released
Status in deja-dup source package in Groovy:
  Triaged
Status in duplicity source package in Groovy:
  Triaged

Bug description:
  I have a folder entitled Mothers' Union. I use Deja-Dup to backup it
  up (along with many other folders) on Ubuntu 20.10. When I open Deja-
  Dup and click on the restore option and pick a back-up date it shows
  all the folders in the backup except this one (Mothers' Union). If I
  remove the apostrophe from the folder name it backs it up fine and can
  be restored. Other folders where the apostrophe is in the name but not
  followed by a space (e.g. John's Documents) also backup and restore
  correctly. Not sure if this is a bug but it's unfortunate that with
  this combination of an apostrophe and a space in the name I can't
  restore the folder.

  1. Ubuntu 20.10
  2. deja-dup 42.2-1ubuntu1
  3. I expected to be able to restore the folder with the apostrophe and space 
in the name (Mothers' Union)
  4. The folder is not available in any of the restore points.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1915161/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1881926] Re: deja-dup fails with root account

[Vej]

** Changed in: duplicity (Ubuntu Focal)
   Status: New => Triaged

** Changed in: duplicity (Ubuntu Focal)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1881926

Title:
  deja-dup fails with root account

Status in Duplicity:
  Invalid
Status in duplicity package in Ubuntu:
  Fix Committed
Status in duplicity source package in Focal:
  Triaged

Bug description:
  I am running deja-dup in Ubuntu 20.04 (Focal Fossa), which has
  duplicity/focal,now 0.8.11.1612-1 and deja-dup/focal,now
  40.6-1ubuntu2.

  When I run deja-dup as myself, it runs fine, but when I launch it with
  sudo, it fails:

  Traceback (innermost last):
File "/usr/bin/duplicity", line 106, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 92, in with_tempdir
  fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in 
main
  action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, 
in ProcessCommandLine
  globals.backend = backend.get_backend(args[0])
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in 
get_backend
  obj = get_backend_object(url_string)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in 
get_backend_object
  return factory(pu)
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", 
line 82, in __init__
  ensure_dbus()
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", 
line 37, in ensure_dbus
  output = p.communicate()[0].decode("utf8", errors="replace")
   AttributeError: 'str' object has no attribute 'decode'

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1881926/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1881926] Re: deja-dup fails with root account

[Vej]

** Also affects: duplicity (Ubuntu Focal)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1881926

Title:
  deja-dup fails with root account

Status in Duplicity:
  Invalid
Status in duplicity package in Ubuntu:
  Fix Committed
Status in duplicity source package in Focal:
  Triaged

Bug description:
  I am running deja-dup in Ubuntu 20.04 (Focal Fossa), which has
  duplicity/focal,now 0.8.11.1612-1 and deja-dup/focal,now
  40.6-1ubuntu2.

  When I run deja-dup as myself, it runs fine, but when I launch it with
  sudo, it fails:

  Traceback (innermost last):
File "/usr/bin/duplicity", line 106, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 92, in with_tempdir
  fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in 
main
  action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, 
in ProcessCommandLine
  globals.backend = backend.get_backend(args[0])
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in 
get_backend
  obj = get_backend_object(url_string)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in 
get_backend_object
  return factory(pu)
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", 
line 82, in __init__
  ensure_dbus()
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", 
line 37, in ensure_dbus
  output = p.communicate()[0].decode("utf8", errors="replace")
   AttributeError: 'str' object has no attribute 'decode'

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1881926/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1873238] Re: Deja-dup icon is missing only runs from terminal

[Vej]

Hello Keith,

Déjà Dup has been moved to a "submenu" called helper programs or the
like (I only have a translated version available so I am not sure about
the exact name here). Try searching for "Backup" that should bring the
icon up.

Please tell us if this fixes the issue or not.

** Changed in: deja-dup (Ubuntu)
   Status: New => Incomplete

-- 
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/1873238

Title:
  Deja-dup icon is missing only runs from terminal

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  This is occuring just on Ubuntu 20.04 Beta for me.

  The Deja-Dup icon has gone missing from the application's menu.
  Searching for it does not yield any results via the gnome shell
  search.

  It will run if I open a terminal and type "deja-dup"

  While running from the terminal instead of the description in the top
  bar/panel being the expected "Backups" the description now reads
  "Org.gnome.DejaDup"

  All other functionality seems to work as normal when run from
  terminal.

  I have tried uninstalling and reinstalling via synaptic and the Ubuntu
  Software but the issue is persisting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: deja-dup 40.6-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 10:59:36 2020
  InstallationDate: Installed on 2019-10-20 (178 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to focal on 2020-04-06 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1873238/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1868705] Re: Update deja-dup to 40.6

[Vej]

** Also affects: deja-dup (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: deja-dup (Ubuntu Focal)
   Status: New => Triaged

** Changed in: deja-dup (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: deja-dup (Ubuntu Focal)
   Importance: Medium => High

-- 
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/1868705

Title:
  Update deja-dup to 40.6

Status in deja-dup package in Ubuntu:
  Triaged
Status in deja-dup source package in Focal:
  Triaged
Status in deja-dup package in Debian:
  Unknown

Bug description:
  Please update deja-dup to 40.6. It is a bug-fix release.

  https://gitlab.gnome.org/World/deja-dup/-/blob/master/NEWS.md

  40.6
  Fixes a bug that prevented backing up to Google Drive accounts with unlimited 
quotas
  Updated translations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1868705/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847706] Re: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3

[Vej]

Hello everyone.

The Dependencies.txt states duplicity 0.8.04-2ubuntu1 which does indeed
seem to be python3. So confirming on grounds of technical information
given by the original reporter.

** Changed in: deja-dup
   Status: New => Triaged

** Changed in: deja-dup (Ubuntu)
   Status: New => Triaged

** Changed in: deja-dup
   Importance: Undecided => Critical

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => High

** Also affects: deja-dup (Ubuntu Eoan)
   Importance: High
   Status: Triaged

** Changed in: deja-dup (Ubuntu Eoan)
Milestone: None => eoan-updates

** Tags added: regression-proposed

-- 
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/1847706

Title:
  Deja Dup still tells python-gi (python 2) is required while duplicity
  is now python3

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged
Status in deja-dup source package in Eoan:
  Triaged

Bug description:
  Please see the screenshot attached. When running a backup operation
  against a remote server with SSH, Deja Dup stops by saying "python-gi"
  package is required.

  However, duplicity is updated with Python3 now, so it doesn't make
  sense to install Python 2 based package. The prerequisite check needs
  to be updated probably with python3-gi instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: deja-dup 40.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 12:34:15 2019
  InstallationDate: Installed on 2019-08-28 (43 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1847706/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1079555] Re: File restore is completely abandoned due to a single invalid backup file

[Vej]

** Changed in: deja-dup (Ubuntu)
   Status: New => Triaged

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Wishlist

** Summary changed:

- File restore is completely abandoned due to a single invalid backup file
+ Have an option to continue with only partly restore in case of error.

-- 
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/1079555

Title:
  Have an option to continue with only partly restore in case of error.

Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  While restoring files from a backup, Deja Dup failed with a hash
  mismatch for one of the (many) difftar.gz files. It showed an error
  message, and when I closed that error message Deja Dup exited. As a
  result, Deja Dup abandoned the entire operation, leaving only the
  files that had been restored by this point. The application provided
  no means for solving the problem. A screenshot of the error message is
  attached.

  At a bare minimum, the error message should try to communicate which
  files it can't restore as a result of the error. Telling me which
  difftar.gz file is corrupted is as good as giving me a core dump at
  this point. In my case, I _did_ get back all the files I wanted, but
  only by painstakingly restoring individual subdirectories and keeping
  a careful list of which files triggered which errors.

  Deja Dup should offer to continue, skipping whatever it needs to skip.
  Additionally, it would be nice if the application provided some means
  for working around the issue (for example, looking for earlier
  versions of the lost files), but that's probably for another bug
  report.

  "Close" should be labelled "Abort" to communicate the fact that it
  will drop everything and probably not do what you want to have happen
  if you were interested in restoring files from a backup.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1079555/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 994215] Re: deja-dup doesn't support correctly symbolic links in paths

[Vej]

Closing this to be very outdated, without getting any confirmation in
around 7 years. If you find this in an recent version of Déjà Dup.
Please file a new bug stating that Version.

Thanks

** Changed in: deja-dup (Ubuntu)
   Status: New => Won't Fix

-- 
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/994215

Title:
  deja-dup doesn't support correctly symbolic links in paths

Status in deja-dup package in Ubuntu:
  Won't Fix

Bug description:
  When restoring files from backups, files are not found if the path
  includes symbolic links :

  example :  ( relative to user's home )

  Images is a link to Donnees/Images

  Images/ is included in backup : 
  restoration of Images/aaa.jpg will fail. ( file not found)

  Donnees/Images is included in backup :
  restoration of Donnees/Images/aaa.jpg works

  Unfortunately, in this case right-mouse menu option "restore" is not proposed 
when browsing Images/, but is ok when browsing Donnees/Images/
   
  I guess that absolute paths are saved in backups, instead of relative ones. 
So the shell option has to be aware of absolute path and give it to the backend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/994215/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1734499] Re: InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid://

[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

-- 
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:
  Confirmed

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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1778638] Re: duplicity stuck in splice() call on Bionic

[Vej]

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => High

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Triaged

-- 
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/1778638

Title:
  duplicity stuck in splice() call on Bionic

Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  I am using Duplicity through Deja-Dup through its deja-dup-monitor
  process. After update to Bionic, it has basically stopped doing
  backups. Version is duplicity 0.7.17+bzr1357, Python version is
  2.7.15rc1, Xubuntu Bionic.

  It seems to be stuck in pipes related call. When I try to strace the
  process I get this:

  strace: Process 28490 attached
  splice(9, [359], 16, NULL, 1048576, SPLICE_F_MORE

  From handle 9 to 16. The handle 9 is a file on my CIFS mount to where
  I do backups. If I go to the directory and do ls it works fine:

  duplicity 28490 USER9r  REG   0,52  359
  67128742 /var/backups/USER/backup.HOST/duplicity-
  inc.20180611T014226Z.to.20180612T014125Z.manifest.gpg

  Handle 16 is a pipe:

  duplicity 28490 USER   16w FIFO   0,12  0t0
  1415081 pipe

  Its other end is handle 13, I think:

  duplicity 28490 USER   13r FIFO   0,12  0t0
  1415081 pipe

  But I do not see anyone reading from it. That sounds like the issue.

  It seems to be stuck in GIO file handling code:

  (gdb) bt
  #0  0x7f0e78588dda in splice (fd_in=9, off_in=0x7ffe5e958388, fd_out=16, 
off_out=0x0, len=1048576, flags=4) at ../sysdeps/unix/sysv/linux/splice.c:26
  #1  0x7f0e6ee2672e in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #2  0x7f0e6ee2d827 in g_file_copy () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #3  0x7f0e76ccfdae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #4  0x7f0e76ccf71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #5  0x7f0e6fb8ecfa in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #6  0x7f0e6fb908e8 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #7  0x7f0e6fb84c39 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #8  0x5560917a1f60 in PyEval_EvalFrameEx ()

  I have already tried to restart it and it got stuck like this again
  the next backup cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1778638/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 918489] Re: duplicity allows a new, different passphrase if an archive cache exists

[Vej]

** Changed in: duplicity
   Status: New => Confirmed

** Changed in: duplicity (Ubuntu)
   Importance: Undecided => High

** Changed in: duplicity (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/918489

Title:
  duplicity allows a new, different passphrase if an archive cache
  exists

Status in Déjà Dup:
  Fix Released
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Fix Released
Status in duplicity package in Ubuntu:
  Triaged
Status in deja-dup source package in Trusty:
  Fix Released
Status in duplicity source package in Trusty:
  Confirmed
Status in deja-dup source package in Xenial:
  Fix Released
Status in duplicity source package in Xenial:
  Confirmed
Status in deja-dup source package in Yakkety:
  Fix Released
Status in duplicity source package in Yakkety:
  Confirmed

Bug description:
  when doing a backup for the first time, dejadup verifies your
  passphrase by having you enter it twice.

  on future incremental backups it doesn't need to do this because
  entering the wrong password will result in the backup failing.

  with the periodic 'full' backups that happen from time to time,
  however, any password will be accepted.

  this can lead to a situation where you accidentally type the wrong
  password once and are left in a situation where you don't know what
  you typed and have no way to get your files (or do another incremental
  backup on top of it).

  i think this is what happened to me recently.

  clearly, the fix is to explicitly verify the passphrase is correct
  when doing a new full backup.  this may be a duplicity bug.

  === Ubuntu deja-dup SRU information ===

  [impact]
  Users may unwittingly re-set their backup password and not be able to restore 
their data.

  [test case]
  - $ deja-dup-preferences # set up a dummy backup
  - $ deja-dup --backup # complete first encrypted full backup
  - $ rename 's/\.2016/\.2000/' /path/to/test/backup/*
  - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/*
  - $ deja-dup --backup # second backup, enter the wrong password
  - $ deja-dup --restore # try to restore with original password

  [regression potential]
  Should be limited?  The fix is to delete the duplicity cache files, which 
ought to be safe to delete.

  It's possible if a full backup is being resumed, we might delete the
  current progress.  That is a better bug to have than this bug, though.
  A more complicated patch would need to be investigated to prevent
  that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/918489/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1776030] Re: Backup fails with "an unknown error"

[Vej]

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => High

-- 
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/1776030

Title:
  Backup fails with "an unknown error"

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Trying to a backup to a network drive.  Yesterday Backup decided to do
  the preiodic full backup.  But it fails, and I get the following error
  information with the "unknown error" message:

  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1522, in do_backup
  check_last_manifest(col_stats)  # not needed for full backup
File "/usr/bin/duplicity", line 1227, in check_last_manifest
  last_backup_set.check_manifests()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 201, 
in check_manifests
  remote_manifest = self.get_remote_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 242, 
in get_remote_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 188, in 
from_string
  vi = VolumeInfo().from_string(match.group(1))
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 388, in 
from_string
  raise VolumeInfoError("Start or end index not set")
   VolumeInfoError: Start or end index not set



  lsb_release -rd >
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  apt-cache policy deja-dup >
  deja-dup:
Installed: 37.1-2fakesync1
Candidate: 37.1-2fakesync1
Version table:
   *** 37.1-2fakesync1 500
  500 http://la-mirrors.evowise.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-2fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  9 21:14:08 2018
  InstallationDate: Installed on 2016-02-26 (834 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (37 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1776030/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1778638] Re: duplicity stuck in splice() call on Bionic

[Vej]

** Changed in: duplicity
   Status: New => Confirmed

-- 
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/1778638

Title:
  duplicity stuck in splice() call on Bionic

Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  I am using Duplicity through Deja-Dup through its deja-dup-monitor
  process. After update to Bionic, it has basically stopped doing
  backups. Version is duplicity 0.7.17+bzr1357, Python version is
  2.7.15rc1, Xubuntu Bionic.

  It seems to be stuck in pipes related call. When I try to strace the
  process I get this:

  strace: Process 28490 attached
  splice(9, [359], 16, NULL, 1048576, SPLICE_F_MORE

  From handle 9 to 16. The handle 9 is a file on my CIFS mount to where
  I do backups. If I go to the directory and do ls it works fine:

  duplicity 28490 USER9r  REG   0,52  359
  67128742 /var/backups/USER/backup.HOST/duplicity-
  inc.20180611T014226Z.to.20180612T014125Z.manifest.gpg

  Handle 16 is a pipe:

  duplicity 28490 USER   16w FIFO   0,12  0t0
  1415081 pipe

  Its other end is handle 13, I think:

  duplicity 28490 USER   13r FIFO   0,12  0t0
  1415081 pipe

  But I do not see anyone reading from it. That sounds like the issue.

  It seems to be stuck in GIO file handling code:

  (gdb) bt
  #0  0x7f0e78588dda in splice (fd_in=9, off_in=0x7ffe5e958388, fd_out=16, 
off_out=0x0, len=1048576, flags=4) at ../sysdeps/unix/sysv/linux/splice.c:26
  #1  0x7f0e6ee2672e in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #2  0x7f0e6ee2d827 in g_file_copy () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #3  0x7f0e76ccfdae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #4  0x7f0e76ccf71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #5  0x7f0e6fb8ecfa in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #6  0x7f0e6fb908e8 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #7  0x7f0e6fb84c39 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #8  0x5560917a1f60 in PyEval_EvalFrameEx ()

  I have already tried to restart it and it got stuck like this again
  the next backup cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1778638/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1814238] Re: deja-dup saves passphrase in /tmp

[Vej]

** Changed in: deja-dup (Ubuntu)
   Status: New => Triaged

-- 
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/1814238

Title:
  deja-dup saves passphrase in /tmp

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  I have unchecked the "save passphrase" option in deja-dup, but still I
  have found the file /tmp/deja-dup-HXGLWZ that contains my passphrase
  in the clear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-2fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  1 10:59:06 2019
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1814238/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1744584] Re: Exclude Snap .cache from Dejadup backups

[Vej]

This has been released upstream with version 38.0

** Changed in: deja-dup
   Status: Fix Committed => Fix Released

-- 
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/1744584

Title:
  Exclude Snap .cache from Dejadup backups

Status in Déjà Dup:
  Fix Released
Status in Snappy:
  New
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  The official Backup solution offered by Ubuntu does not support
  advanced whitelisting/blacklisting of directories. With the
  introduction of snaps, the cache of the snap apps is stored in ~/snaps
  /APP-NAME/VERSION/.cache. Unfortunately this means that Deja dup can't
  be configured to exclude these directories from backups.

  Since 2009, there have been several requests from the community to add
  support of advanced include/exclude support in Dejadup but there is no
  progress. Do you have any plans to provide minimum support for
  excluding specific snap folders such as .cache?

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1744584/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1747646] Re: Authentication error with google drive [$10]

[Vej]

** Changed in: deja-dup
   Status: New => Triaged

** Changed in: deja-dup
   Importance: Undecided => High

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Medium

** Tags added: bionic

** Changed in: deja-dup (Ubuntu)
Milestone: None => bionic-updates

** Summary changed:

- Authentication error with google drive [$10]
+ Authentication error with google drive

-- 
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/1747646

Title:
  Authentication error with google drive

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  Hi,

  I'm having an issue using deja-dup to back up my laptop to my google
  drive.

  When backing only a small folder (eg: ~/Documents) every thing works fine.
  However when trying to backup my whole home folder (/home/myusername) I get 
an "Invalid credentials" error after 5-10 min.

  The back up seems to start normally and my destination folder starts
  filling with "duplicity-full...difftar.gz" files, but eventually I get
  the Invalid Credentials error.

  
  lsb_release -d
  Fedora release 27 (Twenty Seven)

  rpm -q deja-dup duplicity
  deja-dup-37.1-1.fc27.x86_64
  duplicity-0.7.16-1.fc27.x86_64

  deja-dup.log attached.
  I cannot attach deja-dup.gsettings since i can only join 1 file. Will send if 
needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1747646/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1254291] Re: Cant re-add rubbish bin to exclusions after removing

[Vej]

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Low

-- 
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/1254291

Title:
  Cant re-add rubbish bin to exclusions after removing

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  open deja-dup for the first time.
  Navigate to folders and highlight "Rubbish bin" 
  Realise you made a mistake and want to re-add the Rubbish Bin to the list of 
exclusions.
  Press the "+" icon then get lost in nautilus, unable to find "Rubbish bin".

  I would expect it to be possible to re-add the rubbish bin to
  exclusions.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: deja-dup 27.3.1-0ubuntu1
  Uname: Linux 3.12.0-031200-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sat Nov 23 15:51:19 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-06-29 (511 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to saucy on 2013-07-12 (133 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1254291/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1761216] Re: Backup fails if backup destination is not mounted

[Vej]

Hello everyone.

This is related to bug #804170 but goes even further. instead of
preventing to run backups only if the "hard-to-detect sometimes-
directories" are available it requests to make them available.

This would be a new feature.

** Also affects: deja-dup
   Importance: Undecided
   Status: New

** Changed in: deja-dup
   Status: New => Confirmed

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: deja-dup
   Importance: Undecided => Wishlist

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: deja-dup
   Status: Confirmed => Triaged

** Tags added: needs-design

-- 
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/1761216

Title:
  Backup fails if backup destination is not mounted

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  I have set my backup destination to a separate drive in the machine,
  but not at the default location.

  When the backup runs, it fails stating permission denied, as the
  destination drive is not mounted.

  When I enter the proper destination in the backup at the "storage
  location", the drive then mounts and is present on the desktop. Then
  the backup will run successfully.

  I then "unmount" the drive using the menu on the drive icon, and the
  mounted drive disappears from the desktop. I don't need a bunch of
  drives listed or shown on my desktop, as it detracts from the beauty
  of the screen.

  If I mount the drive before running the backup, it will succeed.

  My point with this is that I am not going to mount the drive every
  time I run backup, and when mounted, I don't need it listed or shown
  on my desktop.

  In unity, the drives appeared in the launcher or dock, and there was
  an option to "remove from launcher", which still left the drive
  mounted, but off the desktop and launcher. This was a nice way to fix
  this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1761216/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1769891] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: ordinal not in range(128)

[Vej]

*** This bug is a duplicate of bug 1736164 ***
https://bugs.launchpad.net/bugs/1736164

Hello everyone.

I marked this bug as a duplicate, because the stacktrace is so close to
the one of bug #1736164. Please feed additional informations not
included in bug #1736164 to the comments of that bug.

Thanks

Vej

** This bug has been marked a duplicate of bug 1736164
   deja-dup/duplicity backup fails with UnicodeDecodeError

-- 
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/1769891

Title:
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
  37: ordinal not in range(128)

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Hello

  duplicity crash after backup because there is a python error

  Step to reproduce.

  1. Active developper option in software center
  2. install the backup python pyckage
  3. Lanch a backup with duplicity command

  Result :

  
   Type of backup set:Time:   Number of volumes:
  Full Tue Feb 20 22:00:34 2018  2284
   Incremental Thu Feb 22 03:26:48 2018 1
   Incremental Fri Feb 23 23:23:09 201842
   Incremental Wed Apr  4 15:54:05 2018   151
   Incremental Thu Apr  5 04:27:55 2018 1
   Incremental Sat Apr 14 21:51:41 2018 1
  -
  Also found 0 backup sets not part of any chain,
  and 1 incomplete backup set.
  These may be deleted by running duplicity with the "cleanup" command.
  Registering (mktemp) temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Deleting /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Forgetting temporary file /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Processing remote manifest 
duplicity-inc.20180405T022755Z.to.20180414T195141Z.manifest (154)
  Found manifest volume 1
  Found 1 volumes in manifest
  Registering (mktemp) temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 556, in 
get
  "from backend") % util.ufn(local_path.name))
   BackendException: File /tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not 
found locally after get from backend

  Attempt 1 failed. BackendException: File 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not found locally after get from 
backend
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 552, in 
get
  self.backend._get(remote_filename, local_path)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", 
line 151, in _get
  self.__copy_file(source_file, target_file)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", 
line 124, in __copy_file
  None, self.__copy_progress, None)
   Error: g-io-error-quark: Error opening file 
“/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3”: No such file or directory 
(1)

  Releasing lockfile 
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
  Removing still remembered temporary file 
/tmp/duplicity-hFkoYG-tempdir/mkstemp-useaK1-1
  Removing still remembered temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
  Cleanup of temporary directory /tmp/duplicity-hFkoYG-tempdir failed - this is 
probably a bug.
  Releasing lockfile 
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 658, in incremental_backup
  sig_chain.get_fileobjs())
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 539, 
in get_fileobjs
  return [filename_to_fileobj(f) for f in self.get_filenames(time)]
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 676, in 
get_fileobj_read
  self.get(filename, tdp)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 392, in 
inner_retry
  util.uexc(e)), code=code, extra=e

[Desktop-packages] [Bug 1736164] Re: deja-dup/duplicity backup fails with UnicodeDecodeError

[Vej]

Hello James,

thanks for comment #14, which indicates a problem with the unicode
handling of the original error message.

I recommend to everyone attempting to fix this to look at the solution
from bug #1377873 and investigate if this patch had been removed or
somehow deactivated.

** Changed in: deja-dup (Ubuntu)
   Status: New => Triaged

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => High

** Tags added: bionic

-- 
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/1736164

Title:
  deja-dup/duplicity backup fails with UnicodeDecodeError

Status in Déjà Dup:
  Triaged
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Triaged
Status in deja-dup package in Fedora:
  In Progress

Bug description:
  See: https://bugzilla.redhat.com/show_bug.cgi?id=1470873

  
  Description of problem:
  With the update from Fedora 25 to Fedora 26 Workstation, backups with 
deja-dup/duplicity are failing

  
  Version-Release number of selected component (if applicable):
  duplicity 0.7.13.1
  deja-dup 34.3

  How reproducible:
  Always (scheduled and manually started backup)

  
  Steps to Reproduce:
  1. Wait for the scheduled backup to start or start it via the "Backup now" 
button
  2. Some or a large number of files might get backed up, then the backup stops 
with "Failed with an unknown error"
  3.

  Actual results:
  Backup fails

  Expected results:
  Backup completes as it always did

  
  Additional info:
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1540, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1534, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1385, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1516, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 453, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 452, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 341, in put
  backend.put(tdp, dest_filename)
File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 376, 
in inner_retry
  % exception_traceback())
File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 51, in 
exception_traceback
  return uexc(msg)
File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 79, in 
uexc
  e = unicode(e).encode('utf-8')
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 746: 
ordinal not in range(128)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1736164/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1767148] Re: Exclusion list treats home directory differently

[Vej]

*** This bug is a duplicate of bug 1570204 ***
https://bugs.launchpad.net/bugs/1570204

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #1570204, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1570204
   Deja-dup tries to save directories that sould be ignored

-- 
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/1767148

Title:
  Exclusion list treats home directory differently

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Adding to Folders to ignore, you can navigate to /home/greg/.gvfs in
  the GUI, but it gets stored as ~/.gvfs in the exclusion list.

  When the backup runs, it gives the "Backup Finished" but Could not
  back up the following files.  Please make sure you are able to open
  them.

  /home/greg/.gvfs
  /home/greg/.gvfs
  /home/greg/.gvfs

  The same diretory is listed 3 times n the warning message.

  As a workaround, I want to add the fully qualified pathname to the
  exclusion file to see if that fixes it, but basically I just want to
  properly ingore the folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 36.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 26 09:02:36 2018
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1767148/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1755023] Re: Restore ignores what I type into the folder box

[Vej]

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1755023

Title:
  Restore ignores what I type into the folder box

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  I have my computer using Deja Dup to backup everything to a particular
  folder on a secondary drive. When I try to use Deja Dup to restore a
  backup from a different folder on that drive, it does not scan that
  folder.

  1. Open Deja Dup and click the Restore... button.
  2. In the Restore From Where? window, the Backup location is set to my 
external hard drive, and the Folder field is set to my current backup folder. 
From here, I try paths "a" and "b" below:
  3a. Change the text in the Folder field to be the name of the folder 
containing my previous computer's backup, and click Forward.
  4a. I am presented with a list of backups from my current backup folder, not 
from the other folder I tried to select.
  3b. Change the Backup location field to Local Folder, and now click the 
Choose Folder... button that has appeared next to the Folder field.
  4b. Browse to the mount point of my secondary drive, and select the backup 
folder that was used for my previous computer. Click OK, and then Forward.
  5b. I am presented with the message "Restore Failed" "No backups to restore"

  I'm on Ubuntu 17.10 with deja-dup 36.3-0ubuntu0.1 and duplicity
  0.7.12-1ubuntu1

  I have attached deja-dup.gsettings to this bug report. I will add debug 
outputs in comments below.
  In those logs, it should be noted that my secondary drive is named "Octonary" 
and is mounted at "/media/paul/Octonary". My current backup folder is 
"/media/paul/Octonary/Ubuntu Backup 3", and the backup folder of my previous 
computer is "/media/paul/Octonary/Ubuntu Backup 2".

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1755023/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1755023] Re: Restore ignores what I type into the folder box

[Vej]

** Also affects: deja-dup (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1755023

Title:
  Restore ignores what I type into the folder box

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  I have my computer using Deja Dup to backup everything to a particular
  folder on a secondary drive. When I try to use Deja Dup to restore a
  backup from a different folder on that drive, it does not scan that
  folder.

  1. Open Deja Dup and click the Restore... button.
  2. In the Restore From Where? window, the Backup location is set to my 
external hard drive, and the Folder field is set to my current backup folder. 
From here, I try paths "a" and "b" below:
  3a. Change the text in the Folder field to be the name of the folder 
containing my previous computer's backup, and click Forward.
  4a. I am presented with a list of backups from my current backup folder, not 
from the other folder I tried to select.
  3b. Change the Backup location field to Local Folder, and now click the 
Choose Folder... button that has appeared next to the Folder field.
  4b. Browse to the mount point of my secondary drive, and select the backup 
folder that was used for my previous computer. Click OK, and then Forward.
  5b. I am presented with the message "Restore Failed" "No backups to restore"

  I'm on Ubuntu 17.10 with deja-dup 36.3-0ubuntu0.1 and duplicity
  0.7.12-1ubuntu1

  I have attached deja-dup.gsettings to this bug report. I will add debug 
outputs in comments below.
  In those logs, it should be noted that my secondary drive is named "Octonary" 
and is mounted at "/media/paul/Octonary". My current backup folder is 
"/media/paul/Octonary/Ubuntu Backup 3", and the backup folder of my previous 
computer is "/media/paul/Octonary/Ubuntu Backup 2".

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1755023/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1763488] Re: restore only does not use information from "folder" text field

[Vej]

*** This bug is a duplicate of bug 1755023 ***
https://bugs.launchpad.net/bugs/1755023

Hello Dark Dragon,

thank for taking the time to report this bug.

Because your problem had been reported in bug #1755023, I am marking
this as a duplicate and Ubuntu as affected in bug #1755023.

If you want to give further informations or discuss about this problem
use bug bug #1755023 please.

Best Regards

Vej

** Also affects: deja-dup
   Importance: Undecided
   Status: New

** This bug has been marked a duplicate of bug 1755023
   Restore ignores what I type into the folder box

-- 
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/1763488

Title:
  restore only does not use information from "folder" text field

Status in Déjà Dup:
  New
Status in deja-dup package in Ubuntu:
  New

Bug description:
  I want to restore files from a server backup. I do not want to create
  a backup.

  So I click in the "Overview" tab the "Restore" button and then select
  my Nextcloud server and enter something in the "Folder" field. This
  does not work

  When I enter the information in "Storage location" and then start the
  restore, it works. When I click again on "Restore" and change the
  information in the "Folder" field, it still uses the old folder (the
  one in "Storage location").

  So my conclusion is that the "Folder" field in the "Restore" dialog is
  just ignored and the information from "Storage location" is used
  instead.

  Can someone confirm?

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1763488/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

[Vej]

Resetting to Triaged, because the duplicates bug #1756817 and bug
#1756776 show the same characteristics as described in comment #50.

** Changed in: deja-dup (Ubuntu Bionic)
   Status: Fix Released => Triaged

-- 
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/1751460

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacage::::operator()

Status in Déjà Dup:
  New
Status in WebKit:
  Fix Released
Status in deja-dup package in Ubuntu:
  Triaged
Status in webkit2gtk package in Ubuntu:
  Invalid
Status in deja-dup source package in Xenial:
  Triaged
Status in deja-dup source package in Artful:
  Triaged
Status in deja-dup source package in Bionic:
  Triaged

Bug description:
  Impact
  --
  webkit2gtk 2.20 adds a new security feature called the Gigacage that uses an 
extremely large virtual memory address space (much larger than available 
physical memory).

  Deja Dup's monitor background service had "ulimit -v 100" (that's
  1 GB) set as a workaround for a memory leak issue that the developer
  was unable to reproduce.

  After upgrading to the new webkit2gtk version, Deja Dup's monitor
  service will crash because of that virtual memory limit.

  Test Case
  -
  Install the deja-dup update.
  Install the webkit2gtk update from a PPA (not prepared yet).
  Log out. Log in.
  After a few minutes, check /var/crash/ for any Deja Dup crash reports.

  Regression Potential
  
  This could reintroduce the memory leak bug, but otherwise this is a minimal 
fix. Even if that happens, it's better than the service refusing to run.

  Other Info
  --
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1c3dda588:movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1751460/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

[Vej]

Hello!

I noticed that the recent duplicate bug #1760233 does use deja-dup
37.1-2fakesync1, although this bug had been marked as fixed for this
package.

Should we reset this to "Triaged"?

-- 
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/1751460

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacage::::operator()

Status in Déjà Dup:
  New
Status in WebKit:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Invalid
Status in deja-dup source package in Xenial:
  Triaged
Status in deja-dup source package in Artful:
  Triaged
Status in deja-dup source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  webkit2gtk 2.20 adds a new security feature called the Gigacage that uses an 
extremely large virtual memory address space (much larger than available 
physical memory).

  Deja Dup's monitor background service had "ulimit -v 100" (that's
  1 GB) set as a workaround for a memory leak issue that the developer
  was unable to reproduce.

  After upgrading to the new webkit2gtk version, Deja Dup's monitor
  service will crash because of that virtual memory limit.

  Test Case
  -
  Install the deja-dup update.
  Install the webkit2gtk update from a PPA (not prepared yet).
  Log out. Log in.
  After a few minutes, check /var/crash/ for any Deja Dup crash reports.

  Regression Potential
  
  This could reintroduce the memory leak bug, but otherwise this is a minimal 
fix. Even if that happens, it's better than the service refusing to run.

  Other Info
  --
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1c3dda588:movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1751460/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1651396] Re: Allow people to exclude corrupted incremental backup from chain

[Vej]

Hello.

I included this in the bugs description to make it something specific to
work on.

Please note that this is somehow similar to bug #826712, which asks for
an automatic restore option for corrupted manifests.

Best Regards

Vej

** Summary changed:

- Backup fails every time after one incremental file is possibly corrupted
+ Allow people to exclude corrupted incremental backup from chain

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Wishlist

** Description changed:

  The backup location is on a NAS mounted with NFS. I get this message
  every time I try to make a new backup:
  
  Backup Failed
  
  Invalid data - SHA1 hash mismatch for file:
-  duplicity-inc.20161219T001458Z.to.20161220T001456Z.vol1.difftar.gpg
-  Calculated hash: 3dde403f81e36268ce9b7f53478d9dd8301a439c
-  Manifest hash: b46782fb799c7c5a543ac88d9bfb7cc1df25d38c
+  duplicity-inc.20161219T001458Z.to.20161220T001456Z.vol1.difftar.gpg
+  Calculated hash: 3dde403f81e36268ce9b7f53478d9dd8301a439c
+  Manifest hash: b46782fb799c7c5a543ac88d9bfb7cc1df25d38c
  
- 
- Can someone recommend a better backup software for personal use?
+ People have to use "a workaround" which isn't explained anywhere in the
+ documentation if a backup gets corrupted. It isn't even obvious from the
+ error message that an earlier backup got corrupted.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 20 12:36:15 2016
  InstallationDate: Installed on 2014-05-16 (949 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to xenial on 2016-08-02 (139 days ago)

** Also affects: deja-dup
   Importance: Undecided
   Status: New

** Changed in: deja-dup
   Status: New => Triaged

** Changed in: deja-dup
   Importance: Undecided => Wishlist

-- 
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/1651396

Title:
  Allow people to exclude corrupted incremental backup from chain

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  The backup location is on a NAS mounted with NFS. I get this message
  every time I try to make a new backup:

  Backup Failed

  Invalid data - SHA1 hash mismatch for file:
   duplicity-inc.20161219T001458Z.to.20161220T001456Z.vol1.difftar.gpg
   Calculated hash: 3dde403f81e36268ce9b7f53478d9dd8301a439c
   Manifest hash: b46782fb799c7c5a543ac88d9bfb7cc1df25d38c

  People have to use "a workaround" which isn't explained anywhere in
  the documentation if a backup gets corrupted. It isn't even obvious
  from the error message that an earlier backup got corrupted.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 20 12:36:15 2016
  InstallationDate: Installed on 2014-05-16 (949 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to xenial on 2016-08-02 (139 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1651396/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1651396] Re: Backup fails every time after one incremental file is possibly corrupted

[Vej]

Hello!

There is obviously nothing we can do about packages which got corrupted
on the backup media or during transfers.

So what exactly is this bugreport asking for?

Best Regards

Vej

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Incomplete

-- 
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/1651396

Title:
  Backup fails every time after one incremental file is possibly
  corrupted

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  The backup location is on a NAS mounted with NFS. I get this message
  every time I try to make a new backup:

  Backup Failed

  Invalid data - SHA1 hash mismatch for file:
   duplicity-inc.20161219T001458Z.to.20161220T001456Z.vol1.difftar.gpg
   Calculated hash: 3dde403f81e36268ce9b7f53478d9dd8301a439c
   Manifest hash: b46782fb799c7c5a543ac88d9bfb7cc1df25d38c


  Can someone recommend a better backup software for personal use?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 20 12:36:15 2016
  InstallationDate: Installed on 2014-05-16 (949 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to xenial on 2016-08-02 (139 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1651396/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1756068] Re: .

[Vej]

** Changed in: deja-dup (Ubuntu)
   Status: New => Invalid

-- 
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/1756068

Title:
  .

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1756068/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

[Vej]

You fixed by removing a fix without taking measurements to prevent the problem 
the fix was for?
Are you going to handle that as well or are we just going to see the OOM bugs 
again?

If you are handling this in another bug: Please link it here.

Thanks

Vej

-- 
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/1751460

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacage::<lambda()>::operator()

Status in Déjà Dup:
  New
Status in WebKit:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Triaged
Status in deja-dup source package in Xenial:
  Triaged
Status in webkit2gtk source package in Xenial:
  Confirmed
Status in deja-dup source package in Artful:
  Triaged
Status in webkit2gtk source package in Artful:
  Confirmed
Status in deja-dup source package in Bionic:
  Fix Released
Status in webkit2gtk source package in Bionic:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1c3dda588:movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess<bmalloc::PerHeapKind >::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1751460/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

[Vej]

@Marcin For a workaround you can try mounting with --bind instead of
symlinking.

If you do, please let us now if this worked for you.

Best

Vej

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1217959

Title:
  'metadata' file not found when creating backup ("Could not restore
  ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

Status in Déjà Dup:
  Confirmed
Status in duplicity package in Ubuntu:
  Incomplete

Bug description:
  Linux release: Ubuntu 13.04 64bit
  Kernel: 3.8.0-29-generic
  Python: 2.7.4
  Deja Dup: 26.0
  Duplicity: 0.6.21

  Hi. I've tried to do my monthly or so backup recently, but Deja Dup
  crashed after trying to backup a very large file (VM disk with Windows
  7, 50GB or so). I tried to do another one, this time excluding all my
  large VM's. However, now when trying to do a backup I'm getting the
  following error a few seconds after inputting my encryption password:

  Could not restore ‘/home/tom/.cache/deja-dup/metadata’: File not found
  in backup

  I've tried reinstalling both deja-dup and duplicity, purging
  duplicity, deleting deja-dup and duplicity from /home/tom/.cache,
  deleting the backup files on the external drive, deleting it's config
  as described here http://askubuntu.com/questions/53980/how-to-delete-
  all-the-settings-for-deja-dup. I know (well, I have some evidence
  supporting this) that the drive itself isn't faulty as I managed to
  backup my old laptop to the drive using duplicity and it worked fine
  (Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs
  momentarily.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1217959/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1740238] Re: 'operation already pending' error when drive gets available, manual start required

[Vej]

I currently see the same on one PC. I will retest this whenever I found
the time to upgrade the computer to 17.10 or 18.04.

Distribution: Ubuntu 16.04.3 LTS
deja-dup: 34.2-0ubuntu1.1 
duplicity: 0.7.06-2ubuntu2


** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1740238

Title:
  'operation already pending' error when drive gets available, manual
  start required

Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  I have scheduled daily backups for a laptop to be kept forever on a
  drive that is often disconnected from the laptop. I connect it when I
  can; when I connect it, it gives a 'Backups failed' error stating that
  an operation is already pending. I must then open Backups from the
  launcher for this pending backup to begin. Please fix these two bugs
  (or single bug causing two problems?) so that the backup starts
  without telling me an operation (presumably the backup that starts) is
  already pending, and without me having to open Backups for it to
  start.

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 27 17:51:10 2017
  InstallationDate: Installed on 2017-11-20 (36 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1740238/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1212570] Re: If network location unavailable, allow "retry"

[Vej]

** Changed in: deja-dup
   Status: New => Triaged

** Changed in: deja-dup
   Importance: Undecided => Wishlist

** Changed in: deja-dup (Ubuntu)
   Status: New => Triaged

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Wishlist

-- 
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/1212570

Title:
  If network location unavailable, allow "retry"

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  It'd be nice if there was a "retry" button if the network resource is
  not available.

  Current workflow: 
   - deja-dup pops up, tries to backup, NAS turned off, deja-dup complains
   - hit OK button
   - turn on NAS, wait
   - find deja-dup in the system settings
   - start backup

  This could be simplified to:
   - deja-dup pops up, tries to backup, NAS turned off, deja-dup complains
   - turn on NAS, wait
   - hit retry

  Happens to me every week. :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1212570/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1302416] Re: deja-dup monitor was taking 6GB of memory

[Vej]

The fix, which landed in artful, causes a regression. See bug #1727653.

-- 
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/1302416

Title:
  deja-dup monitor was taking 6GB of memory

Status in Déjà Dup:
  New
Status in deja-dup package in Ubuntu:
  Confirmed
Status in deja-dup package in Debian:
  New

Bug description:
  Booted fresh, computer started to be slow and after a while i realized
  deja-dup monitor was taking 6GB of memory. Haven't tried rebooted
  again. Will do so in a moment.

  Sorry can't provide more info :/

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 09:40:07 2014
  InstallationDate: Installed on 2011-11-21 (864 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=ca_ES
   TERM=xterm
   PATH=(custom, no user)
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to trusty on 2012-02-27 (766 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1302416/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727653] Re: error: can't start new thread

[Vej]

This seems to be a regression introduced by a fix for bug #1302416.

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Critical

** Tags added: regression-release

-- 
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/1727653

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Triaged
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1371613] Re: Backup result message nonsense when some folders failed AND a verification test was done

[Vej]

** Tags added: artful

-- 
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/1371613

Title:
  Backup result message nonsense when some folders failed AND a
  verification test was done

Status in deja-dup package in Ubuntu:
  New

Bug description:
  There are two bugs here; I'm describing the second, layered on the
  first:

  The first is that even though I have explicitly listed ~/.cache in the
  folders to ignore, I get a complaint that it failed to back up
  something in .cache.

  the second bug is that when it does a password/restore verification
  test (which it does every two months), I end up with a completion
  message that makes no sense: it tells me that the test succeeded, but
  then lists a couple of files, suggesting maybe that they were the only
  ones which were backed up? Or the only ones for which the restore test
  was successful?

  See attached graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 19 09:45:48 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-21 (29 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1371613/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1745874] Re: Contradictory and unclear completion report: "Not all files could be backed up" "Your files were successfully backed up"

[Vej]

*** This bug is a duplicate of bug 1371613 ***
https://bugs.launchpad.net/bugs/1371613

Hello!

You already filed a bug about this. So I am marking this as a duplicate.

** This bug has been marked a duplicate of bug 1371613
   Backup result message nonsense when some folders failed AND a verification 
test was done

-- 
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/1745874

Title:
  Contradictory and unclear completion report: "Not all files could be
  backed up" "Your files were successfully backed up"

Status in deja-dup package in Ubuntu:
  New

Bug description:
  When Deja Dup finished, it sent a message to my OS saying that the
  backup was finished but that not all files could be backed up.  I
  clicked on the message to get more information, and it simply
  disappeared.

  I found the dialog window from deja dup and it says:

  Backup Finished

  Your files were successfully backed up and tested.

  With no more comment, it then listed two files (full paths).
  Presumably these are files that were not backed up, yet the window
  says nothing about that.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 36.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 28 09:13:52 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (71 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1745874/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1732530] Re: Dejadup is not working b/c duplicity is not installed

[Vej]

This change was made to remove Python 2 from the Ubuntu-ISO. There
should be a button asking you about installation on first use.

** Changed in: deja-dup (Ubuntu)
   Status: New => Won't Fix

-- 
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/1732530

Title:
  Dejadup is not working b/c duplicity is not installed

Status in ubuntu-mate:
  Invalid
Status in deja-dup package in Ubuntu:
  Won't Fix
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntukylin-meta package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 17.10

  Dejadup is not working b/c duplicity is not installed. After a manual
  install, Deja-Dup works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1732530/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1740238] Re: 'operation already pending' error when drive gets available, manual start required

[Vej]

** Summary changed:

- Backups gives 'operation already pending' error when I connect the drive, and 
I must open Backups to start this pending operation after closing the error 
message.
+ 'operation already pending' error when drive gets available, manual start 
required

-- 
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/1740238

Title:
  'operation already pending' error when drive gets available, manual
  start required

Status in deja-dup package in Ubuntu:
  New

Bug description:
  I have scheduled daily backups for a laptop to be kept forever on a
  drive that is often disconnected from the laptop. I connect it when I
  can; when I connect it, it gives a 'Backups failed' error stating that
  an operation is already pending. I must then open Backups from the
  launcher for this pending backup to begin. Please fix these two bugs
  (or single bug causing two problems?) so that the backup starts
  without telling me an operation (presumably the backup that starts) is
  already pending, and without me having to open Backups for it to
  start.

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 27 17:51:10 2017
  InstallationDate: Installed on 2017-11-20 (36 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1740238/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1744584] Re: Exclude Snap .cache from Dejadup backups

[Vej]

** Changed in: deja-dup
   Status: New => Triaged

** Changed in: deja-dup
   Importance: Undecided => Wishlist

** Also affects: deja-dup (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: deja-dup (Ubuntu)
   Status: New => Triaged

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Wishlist

-- 
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/1744584

Title:
  Exclude Snap .cache from Dejadup backups

Status in Déjà Dup:
  Triaged
Status in Snappy:
  New
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  The official Backup solution offered by Ubuntu does not support
  advanced whitelisting/blacklisting of directories. With the
  introduction of snaps, the cache of the snap apps is stored in ~/snaps
  /APP-NAME/VERSION/.cache. Unfortunately this means that Deja dup can't
  be configured to exclude these directories from backups.

  Since 2009, there have been several requests from the community to add
  support of advanced include/exclude support in Dejadup but there is no
  progress. Do you have any plans to provide minimum support for
  excluding specific snap folders such as .cache?

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1744584/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1090541] Re: Problems uploading to ftp server

[Vej]

Closing as outdated for the upstream package of Ubuntu.

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1090541

Title:
  Problems uploading to ftp server

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Invalid
Status in deja-dup package in Ubuntu:
  Invalid
Status in Arch Linux:
  New

Bug description:
  Description:  Ubuntu 12.10
  deja-dup  24.0-0ubuntu1
  duplicity 0.6.19-0ubuntu2

  
  Im uploading my backups to a ftp server (Dlink DNS-323) and since Ubuntu 
12.10 the backup hangs at uploading and nothing happens. According to the 
logfile of the ftp the last duplicity-inc..to..vol.difftar.gz hasnt been 
uploaded 
  the last duplicity-inc..to..vol.difftar.gz can be found on the ftp server but 
with size 0
  it looks like it only uploads 3-4 duplicity-inc..to..vol.difftar.gz before it 
hangs.  

  1st debug run
  DUPLICITY: INFO 2 4929484316
  DUPLICITY: . Processed volume 14

  DUPLICITY: DEBUG 1
  DUPLICITY: . Registering (mktemp) temporary file 
/tmp/duplicity-xodUb_-tempdir/mktemp-xsAFTU-11

  DUPLICITY: INFO 11
  DUPLICITY: . AsyncScheduler: running task synchronously (asynchronicity 
disabled)

  DUPLICITY: INFO 1
  DUPLICITY: . Writing 
ftp://backup@192.168.0.199/HP-Mini-Marijo/duplicity-inc.20121210T045327Z.to.20121214T191855Z.vol15.difftar.gz

  2nd debug run (previus session terminated with resume later)
  DUPLICITY: INFO 2 5135117373
  DUPLICITY: . Processed volume 18

  DUPLICITY: DEBUG 1
  DUPLICITY: . Registering (mktemp) temporary file 
/tmp/duplicity-RK7THk-tempdir/mktemp-zO9Z_p-6

  DUPLICITY: INFO 11
  DUPLICITY: . AsyncScheduler: running task synchronously (asynchronicity 
disabled)

  DUPLICITY: INFO 1
  DUPLICITY: . Writing 
ftp://backup@192.168.0.199/HP-Mini-Marijo/duplicity-inc.20121210T045327Z.to.20121214T191855Z.vol19.difftar.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1090541/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 985512] Re: support system backups (set up a backup run by root)

[Vej]

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Wishlist

-- 
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/985512

Title:
  support system backups (set up a backup run by root)

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  
  It would be great if you could "fix Deja Dup to ask for permission to read 
things it can't." (From answer to question #67726).

  
  Also from that thread: 
  ---
  This is what I'm using now:

  sudo duplicity / scp://username@host/backupdirectory/duplicity/
  --asynchronous-upload --exclude /tmp --exclude /proc --exclude /media
  --exclude /mnt --exclude /cdrom --exclude /sys --gpg-options
  ='--compress-algo=bzip2 --bzip2-compress-level=9' -v5

  I can *almost* do this via [deja-dup], but when I run it as root it I don't 
have access to the typical Nautilus style "Connect to Server" options. It seams 
there isn't a way to specify an scp destination. Then there's also the 
scheduling issue mentioned above.
  ---

  Deja-dup might not have to run as root just to go through the GUI to
  configure the system backup (profile). It might be enough to be able
  to trigger backups from the command line as root (su, sudo), or by
  dropping a script into /etc/cron.daily.

  OTOH with backintime you run it as root to create the config files for
  root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/985512/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1734499] Re: InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid://

[Vej]

*** This bug is a duplicate of bug 1715582 ***
https://bugs.launchpad.net/bugs/1715582

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

Setting this as a duplicate.

Best

Vej

** This bug has been marked a duplicate of bug 1715582
   "Operation not supported by backend" when backing up to smb server

-- 
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:
  Confirmed

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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

[Vej]

Hello Jared.

Thanks for letting us know about this.

Can you please add the file /tmp/deja-dup.log after running the line
below and replicating the problem ? This is an old bug so a new log
might be helpful for us to figure out what went wrong here:

DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-
dup.log

Best Regards

Vej

** Changed in: duplicity (Ubuntu)
   Status: Expired => Incomplete

** Changed in: deja-dup
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1217959

Title:
  'metadata' file not found when creating backup ("Could not restore
  ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

Status in Déjà Dup:
  Incomplete
Status in duplicity package in Ubuntu:
  Incomplete

Bug description:
  Linux release: Ubuntu 13.04 64bit
  Kernel: 3.8.0-29-generic
  Python: 2.7.4
  Deja Dup: 26.0
  Duplicity: 0.6.21

  Hi. I've tried to do my monthly or so backup recently, but Deja Dup
  crashed after trying to backup a very large file (VM disk with Windows
  7, 50GB or so). I tried to do another one, this time excluding all my
  large VM's. However, now when trying to do a backup I'm getting the
  following error a few seconds after inputting my encryption password:

  Could not restore ‘/home/tom/.cache/deja-dup/metadata’: File not found
  in backup

  I've tried reinstalling both deja-dup and duplicity, purging
  duplicity, deleting deja-dup and duplicity from /home/tom/.cache,
  deleting the backup files on the external drive, deleting it's config
  as described here http://askubuntu.com/questions/53980/how-to-delete-
  all-the-settings-for-deja-dup. I know (well, I have some evidence
  supporting this) that the drive itself isn't faulty as I managed to
  backup my old laptop to the drive using duplicity and it worked fine
  (Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs
  momentarily.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1217959/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1743013] Re: deja-dup fails when launched automatically

[Vej]

Hello Wolf,

thanks for taking the time to improve Déjà Dup and Duplicity.

To mark another package as affected by a bug you should simply use the
link "Also affects project" on the original bug. Opening a bug to get
someone else to do this is not the preferred way here.

This is not a valid bug and will therefore be marked as invalid.

Best

Vej

** Changed in: deja-dup (Ubuntu)
   Status: New => Invalid

-- 
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/1743013

Title:
  deja-dup fails when launched automatically

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  In #1727653 an error was reported that stated that backup using
  duplicity failed.

  However, the error only manifests in duplicity but is triggered by the
  calling Deja-Dup.

  Launching Deja-Dup automatically will ALWAYS lead to the error.

  Launching Deja-Dup from the console/bash will NEVER lead to the error.

  Any attempts to set number of open file limits do not remedy the
  issue.

  Please refer to #1727653 and associated errors as all analysis have
  gone into duplicity so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 36.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 12 18:55:12 2018
  InstallationDate: Installed on 2017-10-20 (84 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1743013/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 498933] Re: Crash when restoring data KeyError

[Vej]

Setting back to confirmed because Kenneths question from comment #36 is
implicitly answered in comment #38.

** Changed in: duplicity
   Status: Expired => Confirmed

-- 
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/498933

Title:
  Crash when restoring data KeyError

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: deja-dup

  1) Ubuntu 9.10
  2) Deja Dup 10.2-0ubuntu1.1
  3) I expected my backup to be restored
  4) Deja Dup crashed instead.

  I just tried to restore the backup I made, and it crashes repeatedly
  when trying to restore.

  I have it setup to backup my home directory, and tried restoring to
  both the original location as well as a completely different folder.
  Both lead to the same error message.

  
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 825, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 818, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 775, in main
  restore(col_stats)
File "/usr/bin/duplicity", line 436, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 521, in 
Write_ROPaths
  ITR(ropath.index, ropath)
File "/usr/lib/python2.6/dist-packages/duplicity/lazy.py", line 336, in 
__call__
  last_branch.fast_process, args)
File "/usr/lib/python2.6/dist-packages/duplicity/robust.py", line 38, in 
check_common_error
  return function(*args)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 574, in 
fast_process
  ropath.copy(self.base_path.new_index(index))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 412, in copy
  other.writefileobj(self.open("rb"))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 574, in 
writefileobj
  buf = fin.read(_copy_blocksize)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 199, in 
read
  if not self.addtobuffer():
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 224, in 
addtobuffer
  self.tarinfo_list[0] = self.tar_iter.next()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 331, in 
next
  self.set_tarfile()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 320, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 472, in get_fileobj_iter
  backup_set.volume_name_dict[vol_num],
  KeyError: 15

  ProblemType: Bug
  Architecture: i386
  Date: Sun Dec 20 19:59:06 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/deja-dup
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: deja-dup 10.2-0ubuntu1.1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: deja-dup
  Uname: Linux 2.6.31-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/498933/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1729695] Re: ASCII decode error, but not due to filenames in backup target

[Vej]

Hello!

This looks exactly like a very old bug, that should be fixed for a
while. So I am wondering if this is  the old problem, which sometimes
stays if people continue to use their old backups while upgrading to
newer versions. So I have to ask a few questions:

When did you first configured Déjà Dup?
 Is this an old backup, which you kept, while upgrading (!) to newer versions 
of Ubuntu?
 When did you installed a fresh Ubuntu on that pc for the last time?

Please set the state back to new after answering!

Best regards

Vej

** Changed in: deja-dup (Ubuntu)
   Status: New => Incomplete

-- 
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/1729695

Title:
  ASCII decode error, but not due to filenames in backup target

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 17.10, I have deja-dup 36.2-0ubuntu1 installed. When I run
  "DEJA_DUP_DEBUG=1 deja-dup", it starts a backup as soon as it opens,
  as expected. But the backup fails. I get the following at the end of
  the output. I tried uninstalling Dropbox and deleting its .dropbox-
  dist directory, and then deja-dup crashed when trying to back up a
  completely different file (but the same byte in the same position). So
  I don't think this is due to any of the filenames I have in my backup
  target. I also tried a few commands to find non-ASCII filenames, with
  no luck. I'm not sure what else I can do to troubleshoot.

  
  DUPLICITY: INFO 4 
'home/paul/.dropbox-dist/dropbox-lnx.x86_64-38.4.27/PyQt5.QtGui.so'
  DUPLICITY: . A 
home/paul/.dropbox-dist/dropbox-lnx.x86_64-38.4.27/PyQt5.QtGui.so

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/home/paul/.cache/deja-dup/1499b6292f58faddd30853ffbbfefcf6/duplicity-S72EWc-tempdir/mktemp-hYd54u-1

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/home/paul/.cache/deja-dup/1499b6292f58faddd30853ffbbfefcf6/duplicity-VyBN42-tempdir/mktemp-BO1DKJ-1

  DUPLICITY: INFO 11
  DUPLICITY: . AsyncScheduler: running task synchronously (asynchronicity 
disabled)

  DUPLICITY: INFO 1
  DUPLICITY: . Writing duplicity-full.20171102T205615Z.vol1.difftar.gz

  DUPLICITY: DEBUG 1
  DUPLICITY: . Releasing lockfile 
/home/paul/.cache/deja-dup/1499b6292f58faddd30853ffbbfefcf6/lockfile.lock

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-c9BMvB-tempdir/mktemp-RtijDc-270

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-c9BMvB-tempdir/mkstemp-3cxG5G-1

  DUPLICITY: ERROR 30 UnicodeDecodeError
  DUPLICITY: . Traceback (most recent call last):
  DUPLICITY: .   File "/usr/bin/duplicity", line 1546, in 
  DUPLICITY: . with_tempdir(main)
  DUPLICITY: .   File "/usr/bin/duplicity", line 1540, in with_tempdir
  DUPLICITY: . fn()
  DUPLICITY: .   File "/usr/bin/duplicity", line 1391, in main
  DUPLICITY: . do_backup(action)
  DUPLICITY: .   File "/usr/bin/duplicity", line 1510, in do_backup
  DUPLICITY: . full_backup(col_stats)
  DUPLICITY: .   File "/usr/bin/duplicity", line 575, in full_backup
  DUPLICITY: . globals.backend)
  DUPLICITY: .   File "/usr/bin/duplicity", line 456, in write_multivol
  DUPLICITY: . (tdp, dest_filename, vol_num)))
  DUPLICITY: .   File 
"/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 146, in 
schedule_task
  DUPLICITY: . return self.__run_synchronously(fn, params)
  DUPLICITY: .   File 
"/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 172, in 
__run_synchronously
  DUPLICITY: . ret = fn(*params)
  DUPLICITY: .   File "/usr/bin/duplicity", line 455, in 
  DUPLICITY: . vol_num: put(tdp, dest_filename, vol_num),
  DUPLICITY: .   File "/usr/bin/duplicity", line 344, in put
  DUPLICITY: . backend.put(tdp, dest_filename)
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", 
line 376, in inner_retry
  DUPLICITY: . % exception_traceback())
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/util.py", 
line 52, in exception_traceback
  DUPLICITY: . return uexc(msg)
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/util.py", 
line 80, in uexc
  DUPLICITY: . e = unicode(e).encode('utf-8')
  DUPLICITY: . UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in 
position 736: ordinal not in range(128)
  DUPLICITY: .

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:G

[Desktop-packages] [Bug 1725432] Re: Restore failed due to missing source option

[Vej]

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => High

-- 
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/1725432

Title:
  Restore failed due to missing source option

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Committed

Bug description:
  [ Impact ]

  Users can't restore a backup on a fresh install from the deja-dup UI.

  [ Test Case ]

  Open "Backups" (or run 'deja-dup') and click the "Restore..." button.

  You should see a dropdown with options for a location, but instead
  with this bug, you see an empty dialog.

  [ Regression Potential ]

  Pretty small.  The proposed patch just moves some widget
  initialization earlier.

  [ Original Bug Description ]

  Installed a new Ubuntu 17.10, created my user and tried to restore the 
backups from the server.
  Pressed Overview, Restore and get an empty dialog. From screen shots I found 
I assume there should be some drop downs or buttons etc. but my dialog is empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1725432/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1093611] Re: After the last update, the scheduling of déjà-dup is not working anymore

[Vej]

Closing as none of the mentioned releases is currently supported. Please
open a new bug if you see this using a more recent version of Ubuntu.
Thanks!

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1093611

Title:
  After the last update, the scheduling of déjà-dup is not working
  anymore

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Recently there was an update of the deja-dup package, and since then, I have 
found that the scheduling is not working anymore.
  I mean that I have turned on "Automatic Backup", and set a backup every day. 
This has always worked, since the installation of Ubuntu 12.04 last April, but 
now no more. In the settings window is displayed that the next backup is for 
today, but the backup never happens. Tomorrow it will be the same thing, and so 
on. 
  To backup my data I have to start the process manually through the settings 
window with the button "Run backup now" (or whatever it is in English).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
  Uname: Linux 3.2.0-35-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17
  Architecture: amd64
  Date: Tue Dec 25 10:55:27 2012
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=it_CH:it
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_CH.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1093611/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1370363] Re: deja-dup fails reporting "Permission denied" if Gnome Keyring is not available

[Vej]

** Summary changed:

- deja-dup fails reporting "Permission denied", no error logs anywhere
+ deja-dup fails reporting "Permission denied" if Gnome Keyring is not available

** Summary changed:

- deja-dup fails reporting "Permission denied" if Gnome Keyring is not available
+ deja-dup fails to backup using SFTP/SSH if Gnome Keyring is not available

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => High

** Also affects: deja-dup
   Importance: Undecided
   Status: New

** Changed in: deja-dup
   Importance: Undecided => High

** Changed in: deja-dup
   Status: New => Confirmed

-- 
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/1370363

Title:
  deja-dup fails to backup using SFTP/SSH if Gnome Keyring is not
  available

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  I have had a working deja-dup setup under Ubuntu 12.04LTS. I upgraded
  to Ubuntu 14.04LTS. Now deja-dup no-longer works, the window states
  "Permission denied" (the German translation), also if I run
  "DEJA_DUP_DEBUG=1 deja-dup --backup" there is no output at all. (I am
  currently trying running it from a KDE desktop.)

  I can still successfully run "duplicity collection-status" + the URL I
  find in org.gnome.deja-dup's file backend configuration and get a
  reasonable output, so it does not appear to be an ssh-related issue.

  I moved .cache/deja-dup out of the way, for no improvement.

  How do we go about debugging this?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Sep 17 08:51:40 2014
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to trusty on 2014-08-29 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1370363/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 953194] Re: deja-dup attempts to backup "lost+found"

[Vej]

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Low

** Also affects: deja-dup
   Importance: Undecided
   Status: New

** Changed in: deja-dup
   Importance: Undecided => Medium

** Changed in: deja-dup
   Status: New => Confirmed

-- 
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/953194

Title:
  deja-dup attempts to backup "lost+found"

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Deja-Dup attempts to backup  */lost+found when it is present in one of
  the backup directories even if it is included in the exclusion list.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 21.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Mon Mar 12 11:02:45 2012
  EcryptfsInUse: Yes
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to precise on 2012-01-09 (63 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/953194/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 306982] Re: Expose better UI for file-based restore

[Vej]

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Wishlist

-- 
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/306982

Title:
  Expose better UI for file-based restore

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  It would be nice if the user can say "I only want to restore these
  files/folders".

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/306982/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 847399] Re: No relevant progress info while doing the actual backup in Dejadup

[Vej]

** Changed in: deja-dup
   Importance: Undecided => Wishlist

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Wishlist

-- 
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/847399

Title:
  No relevant progress info while doing the actual backup in Dejadup

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  When doing the actual backup, the progress bar is moving from 0 to
  100% without any intermediate steps. What also good be usefull: an
  indication what het upload speed is, and in conjunction with the file
  size, a calculated ETA.

  To have some user feedback, is especially important when backing up to
  cloudbased targets like SSH or U1, because they are limited by a
  relatively small upload bandwidth. As for now, the upload seems
  broken, because a user cannot see any progress, only when it's ready.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/847399/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1570204] Re: Deja-dup tries to save directories that sould be ignored

[Vej]

** Changed in: deja-dup
   Importance: Undecided => Medium

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1570204

Title:
  Deja-dup tries to save directories that sould be ignored

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  After running deja-dup, I get the following information:

  Could not back up the following files. Please make sure you are able to open 
them.
  /home/wiktor./cache/dconf
  /home/wiktor/.dbus
  /home/wiktor/.gvfs

  All of the above directories are added to "Folders to ignore" list.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 14 08:39:24 2016
  InstallationDate: Installed on 2016-04-11 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1570204/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 792763] Re: SMB Error: "Backup Failed. Success"

[Vej]

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Incomplete

-- 
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/792763

Title:
  SMB Error: "Backup Failed. Success"

Status in Déjà Dup:
  Incomplete
Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  I just made today some changes to which directories should be backed up. Deja 
Dup seemed to be accepting the changes and started the back up. The process 
failed with a weird notification window which I don't know what to make of. 
Title says "Backup failed" and then it says "Success" in the window itself. See 
attached screenshot. Kinda funny, don't you think?! :-)
  I don't know where I can find log files to see if there is any extra 
information that can be usefull

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/792763/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1720337] Re: deja-dup repeatedly asks for password in KDE

[Vej]

Hello Victor,

thanks for your bug report.

Can you please provide us with the file /tmp/deja-dup.gsettings after running 
the following line (you may want to scrub the file of any incriminating file 
names or details):
gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings

I want to verify that this is not a problem in your configuration of
Déjà Dup.

Thanking you in anticipation

Vej


** Changed in: deja-dup (Ubuntu)
   Status: New => Incomplete

-- 
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/1720337

Title:
  deja-dup repeatedly asks for password in KDE

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  I have kubuntu 16.04 LTS as a clean install in my laptop.

  When deja-dup is set to backup automatically and to encrypt files,
  every time it starts to backup, it asks for the encryption password.
  This happens to me only in KDE, as before I had installed ubuntu MATE
  and deja-dup didn't ask for the password more than once, the first
  time it runs the backup, as normal.

  In kubuntu, once I put the encryption password as deja-dup always asks
  for, the backup runs OK.

  I have searched in Google for similar problems, like in:
  https://bbs.archlinux.org/viewtopic.php?id=123644 and I found that
  kubuntu does not install gnome-keyring when deja-dup is installed.

  As deja-dup is developed for GNOME desktop environment it seems that
  it needs this package for functioning properly (for saving the
  passwords).

  Once I installed gnome-keyring and its dependencies as requested by
  the package manager (I like to use Synaptic even in Kubuntu), the
  problem has gone and deja-dup backups just nicely now. Not more asking
  for password every time.

  So, summarizing:

  1) What I expect to happen: that deja-dup doesn't ask for the backup
  password every time that it runs a backup in kubuntu.

  2) What it happens instead: deja-dup asks for it every time because it
  needs, also in kubuntu, the package gnome-keyring installed along with
  its dependencies.

  3) Hence, I request that kubuntu installs automatically gnome-keyring
  when deja-dup is marked to be installed or it won't work properly, as
  quoted.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1.1
  Uname: Linux 4.13.4-041304-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Sep 29 12:01:56 2017
  InstallationDate: Installed on 2017-07-30 (60 days ago)
  InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1720337/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1570204] Re: Deja-dup tries to save directories that sould be ignored

[Vej]

** Changed in: deja-dup
   Status: New => Confirmed

-- 
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/1570204

Title:
  Deja-dup tries to save directories that sould be ignored

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  After running deja-dup, I get the following information:

  Could not back up the following files. Please make sure you are able to open 
them.
  /home/wiktor./cache/dconf
  /home/wiktor/.dbus
  /home/wiktor/.gvfs

  All of the above directories are added to "Folders to ignore" list.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 14 08:39:24 2016
  InstallationDate: Installed on 2016-04-11 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1570204/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1351025] Re: "Error setting permissions: Operation not permitted" during backup

[Vej]

** Also affects: deja-dup (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: trusty

-- 
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/1351025

Title:
  "Error setting permissions: Operation not permitted" during backup

Status in Déjà Dup:
  New
Status in deja-dup package in Ubuntu:
  New

Bug description:
  directory selection to backup
  /home
  /etc/tools
  directories to be ignored
  Trash
  ~/Telechargements (using french version) should be something like ~/Downloads 
?

  backup destination set up to local directory /mnt/home-usb-hd/ubuntu_backup : 
this is an external usb hard disk
  /mnt$ ls -l
  total 36
  drwxr-xr-x  2 root root  4096 mai   15 22:27 home-smb-hd
  drwxrwxrwx 23 root root 32768 janv.  1  1970 home-usb-hd

  hard disk is mounted at startup withing /etc/fstab
  # External USB drive
  UUID=18F5-2038/mnt/home-usb-hdvfat
user,auto,fmask=0111,dmask=

  after boot /mnt/home-usb-hd can be browsed, and using a term i'm able to 
create files using command like cat > hello.txt
  /mnt/home-usb-hd/ubuntu_backup also exists 

  schedule : each week
  keep at least 6 months
  --
  $ lsb_release -d
  Description:  Ubuntu 14.04.1 LTS

  $ dpkg-query -W deja-dup duplicity
  deja-dup  30.0-0ubuntu4
  duplicity 0.6.23-1ubuntu4.1

  $  gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings
  ludovic@ludovic-Inspiron-One-2310:~$ cat  gsettings list-recursively 
org.gnome.DejaDup > /tmp/deja-dup.gsettings
  cat: gsettings: Aucun fichier ou dossier de ce type
  cat: list-recursively: Aucun fichier ou dossier de ce type
  cat: org.gnome.DejaDup: Aucun fichier ou dossier de ce type

  oops... something is missing ?
  running DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log
  reproduced bug

  $ ls -l
  total 52
  -rw-rw-r-- 1 ludovic ludovic 0 juil. 31 21:38 deja-dup.gsettings
  -rw-rw-r-- 1 ludovic ludovic 38336 juil. 31 21:48 deja-dup.log
  drwx-- 2 ludovic ludovic  4096 janv.  1  1970 orbit-ludovic
  drwx-- 3 ludovic ludovic  4096 juil. 31 21:39 sni-qt_spotify_6779-BcqifS
  drwx-- 2 ludovic ludovic  4096 juil. 31 19:27 ssh-DTvCOBjq2jSq
  -rw-rw-r-- 1 ludovic ludovic 0 juil. 31 19:27 unity_support_test.0

  /tmp/deja-dup.log will be added to this report

  cd /mnt/home-usb-hd/ubuntu_backup; ls -ltr 
  -rw-rw-rw- 1 root root  42134104 juil. 25 17:43 
duplicity-inc.20140718T210903Z.to.20140725T153906Z.vol17.difftar.gpg
  -rw-rw-rw- 1 root root   9972670 juil. 25 17:43 
duplicity-new-signatures.20140718T210903Z.to.20140725T153906Z.sigtar.gpg
  -rw-rw-rw- 1 root root   990 juil. 25 17:43 
duplicity-inc.20140718T210903Z.to.20140725T153906Z.manifest.gpg
  -rw-rw-rw- 1 root root 2 juil. 31 19:50 test.txt
  -rw-rw-rw- 1 root root  10527973 juil. 31 21:47 
duplicity-inc.20140725T153906Z.to.20140731T194554Z.vol1.difftar.gpg

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1351025/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1674121] Re: "Restore" asks for cryptic authentication to run /bin/sh as superuser

[Vej]

@Michael Terry: The description of the patch does not seem to have
anything to do with this bug. Is this really fixed for Ubuntu?

-- 
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/1674121

Title:
  "Restore" asks for cryptic authentication to run /bin/sh as superuser

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  I am trying to restore a full backup to an external hard drive.
  After 20 minutes or so, a cryptic gui popup arises which says that "some 
process" wants sudo authentication to run /bin/sh

  It is surely a bug to generate such a vague request for sudo use.

  I note it has been this way since 2013
  (https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1079553 which
  has been unaddressed, so the outcome of denying this request is still
  a great pain), but I am pointing out that this kind of permission
  request is itself a bug, if not a security risk because it teaches
  users to give that kind of permission to an unknown script.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: deja-dup 34.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 19 12:35:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-02-12 (400 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to yakkety on 2017-01-21 (56 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1674121/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1710309] Re: Backup does not recognize gpg 2 option and fails

[Vej]

@Developers: Please note, that the trust-model tofu+pgp is valid for PGP
2. See https://www.gnupg.org/documentation/manuals/gnupg/GPG-
Configuration-Options.html#GPG-Configuration-Options

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1710309

Title:
  Backup does not recognize gpg 2 option and fails

Status in Déjà Dup:
  Triaged
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Triaged
Status in duplicity package in Ubuntu:
  Triaged

Bug description:
  Attempting to create a full backup to a SMB NAS, succeeds if backup is
  set to unencrypted. Fails if password is specified.

  Symptom: deja-dup loops endlessly through "scanning" -> "encryption
  password needed" -> "require password?" and round and round.

  Possibly related to recent gnupg options changes? Creating a GPG key
  pair for enigmail to use was the last major change i made to my set-up
  since the last time these back-ups succeeded. If that's the cause,
  i'll be darned if i can work out what to revert where.

  Release:Ubuntu 16.04.3 LTS
  deja-dup34.2-0ubuntu1.1
  duplicity   0.7.06-2ubuntu2

  Reproduction Steps:

  * Add the line "trust-model tofu+pgp" to the end of your gpg.conf (probably 
~/.gnupg/gpg.conf)
  * Try an encrypted backup of any data to any destination.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1710309/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1710309] Re: Backup does not recognize gpg 2 option and fails

[Vej]

Hello Mats,

thanks for your output.

I was able to reproduce your bug  and will add reproduction steps based
on these lines of your log:

DUPLICITY: . gpg: unknown trust model `tofu+pgp'
DUPLICITY: . gpg: /home/lynx/.gnupg/gpg.conf:89: invalid option

This indicates, that this might be a problem with the backend duplicity,
so I will set this project as affected and forward to both upstreams.

Best

Vej

** Description changed:

  Attempting to create a full backup to a SMB NAS, succeeds if backup is
  set to unencrypted. Fails if password is specified.
  
  Symptom: deja-dup loops endlessly through "scanning" -> "encryption
  password needed" -> "require password?" and round and round.
  
  Possibly related to recent gnupg options changes? Creating a GPG key
  pair for enigmail to use was the last major change i made to my set-up
  since the last time these back-ups succeeded. If that's the cause, i'll
  be darned if i can work out what to revert where.
  
  Release:Ubuntu 16.04.3 LTS
  deja-dup34.2-0ubuntu1.1
  duplicity   0.7.06-2ubuntu2
+ 
+ Reproduction Steps:
+ 
+ * Add the line "trust-model tofu+pgp" to the end of your gpg.conf (probably 
~/.gnupg/gpg.conf)
+ * Try an encrypted backup of any data to any destination.

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Medium

** Also affects: duplicity (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: duplicity (Ubuntu)
   Status: New => Triaged

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: duplicity (Ubuntu)
   Importance: Undecided => Medium

** Also affects: duplicity
   Importance: Undecided
   Status: New

** Also affects: deja-dup
   Importance: Undecided
   Status: New

** Changed in: deja-dup
   Status: New => Triaged

** Changed in: deja-dup
   Importance: Undecided => High

-- 
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/1710309

Title:
  Backup does not recognize gpg 2 option and fails

Status in Déjà Dup:
  Triaged
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Triaged
Status in duplicity package in Ubuntu:
  Triaged

Bug description:
  Attempting to create a full backup to a SMB NAS, succeeds if backup is
  set to unencrypted. Fails if password is specified.

  Symptom: deja-dup loops endlessly through "scanning" -> "encryption
  password needed" -> "require password?" and round and round.

  Possibly related to recent gnupg options changes? Creating a GPG key
  pair for enigmail to use was the last major change i made to my set-up
  since the last time these back-ups succeeded. If that's the cause,
  i'll be darned if i can work out what to revert where.

  Release:Ubuntu 16.04.3 LTS
  deja-dup34.2-0ubuntu1.1
  duplicity   0.7.06-2ubuntu2

  Reproduction Steps:

  * Add the line "trust-model tofu+pgp" to the end of your gpg.conf (probably 
~/.gnupg/gpg.conf)
  * Try an encrypted backup of any data to any destination.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1710309/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1710309] Re: Deja-dup fails to create encrypted backup

[Vej]

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Confirmed

** Summary changed:

- Deja-dup fails to create encrypted backup
+ Backup does not recognize gpg 2 option and fails

** Description changed:

  Attempting to create a full backup to a SMB NAS, succeeds if backup is
  set to unencrypted. Fails if password is specified.
  
  Symptom: deja-dup loops endlessly through "scanning" -> "encryption
  password needed" -> "require password?" and round and round.
  
  Possibly related to recent gnupg options changes? Creating a GPG key
  pair for enigmail to use was the last major change i made to my set-up
  since the last time these back-ups succeeded. If that's the cause, i'll
  be darned if i can work out what to revert where.
+ 
+ Release:Ubuntu 16.04.3 LTS
+ deja-dup34.2-0ubuntu1.1
+ duplicity   0.7.06-2ubuntu2

** Tags added: xenial

-- 
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/1710309

Title:
  Backup does not recognize gpg 2 option and fails

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Attempting to create a full backup to a SMB NAS, succeeds if backup is
  set to unencrypted. Fails if password is specified.

  Symptom: deja-dup loops endlessly through "scanning" -> "encryption
  password needed" -> "require password?" and round and round.

  Possibly related to recent gnupg options changes? Creating a GPG key
  pair for enigmail to use was the last major change i made to my set-up
  since the last time these back-ups succeeded. If that's the cause,
  i'll be darned if i can work out what to revert where.

  Release:Ubuntu 16.04.3 LTS
  deja-dup34.2-0ubuntu1.1
  duplicity   0.7.06-2ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1710309/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1710309] Re: Deja-dup fails to create encrypted backup

[Vej]

Hello Mats,

To figure out what is going on there I would like to ask a few
informations from you:

1. The distribution of Linux you're using:
lsb_release -d

2. The version of deja-dup and duplicity:
(if on Ubuntu or Debian:)
dpkg-query -W deja-dup duplicity

(if on Fedora or other RPM-based systems:)
rpm -q deja-dup duplicity

3. The file /tmp/deja-dup.gsettings after running the following line (you may 
want to scrub the file of any incriminating file names or details):
gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings

4. The file /tmp/deja-dup.log after running the line below and
replicating the problem (you may want to scrub the log of any
incriminating file names or details):

DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-
dup.log

Thanks in advance

Vej

** Changed in: deja-dup (Ubuntu)
   Status: New => Incomplete

-- 
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/1710309

Title:
  Deja-dup fails to create encrypted backup

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  Attempting to create a full backup to a SMB NAS, succeeds if backup is
  set to unencrypted. Fails if password is specified.

  Symptom: deja-dup loops endlessly through "scanning" -> "encryption
  password needed" -> "require password?" and round and round.

  Possibly related to recent gnupg options changes? Creating a GPG key
  pair for enigmail to use was the last major change i made to my set-up
  since the last time these back-ups succeeded. If that's the cause,
  i'll be darned if i can work out what to revert where.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1710309/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1707346] Re: nautilus crashed with SIGSEGV in g_type_check_instance_cast()

[Vej]

** Also affects: deja-dup
   Importance: Undecided
   Status: New

** Changed in: deja-dup
   Status: New => Confirmed

** Changed in: deja-dup
   Importance: Undecided => High

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => High

** Changed in: deja-dup (Ubuntu)
   Importance: High => Critical

** Changed in: deja-dup
   Importance: High => Critical

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1707346

Title:
  nautilus crashed with SIGSEGV in g_type_check_instance_cast()

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Opened a fresh gnome-shell session, and checked for updates via
  synaptic: got the crash at that time. Now nautilus fails to load/open
  (Segmentation fault (core dumped)).

  Note: if deja-dup* packages are downgraded from 35.1 to 34.4, then
  nautilus can be used without warning/error/crash.

  Note2: i've the feeling that nautilus get that issue only with the
  latest deja-dup* 35.1-0ubuntu2 version(but i'm not sure, the previous
  35.1-oubuntu1 had not made nautilus crashing)

  deja-dup (35.1-0ubuntu2) artful; urgency=medium

* debian/tests/control, debian/tests/check:
  - Fix tests; upstream (me) removed the test target we were using

   -- Michael Terry   Fri, 28 Jul 2017 23:15:45 -0400

  ProblemType: Crash-0ubuntu2
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.24.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10
  Uname: Linux 4.11.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jul 29 07:17:08 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f5d3f2f918a :
mov(%rdi),%r9
   PC (0x7f5d3f2f918a) ok
   source "(%rdi)" (0x825cae00) not located in a known VMA region 
(needed readable region)!
   destination "%r9" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libdeja-dup.so
   ?? () from /usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libdeja-dup.so
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1707346/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1700645] Re: Encrypted backup repeatedly asks for password on first use

[Vej]

Hello James,

this should not be triggered by Déjà Dup, but by a combination of a file
/etc/X11/Xsession.d/90gpg-agent together with an entry "use-agent"
inside of ~/.gnupg/gpg.conf.

Can you check, if the file /etc/X11/Xsession.d/90gpg-agent does exist at
your system and if your ~/.gnupg/gpg.conf does include use-agent please?

I will move this bug report over to the Downstream Triagers of the
ubuntu package gnupg-agent, which may ask more questions about this.

** Changed in: deja-dup
   Status: Incomplete => Invalid

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Invalid

** Also affects: gnupg2 (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Encrypted backup repeatedly asks for password on first use
+ gnupg-agent not running when needed by Déjà Dup

** Summary changed:

- gnupg-agent not running when needed by Déjà Dup
+ gpg-agent not running when needed by Déjà Dup

-- 
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/1700645

Title:
  gpg-agent not running when needed by Déjà Dup

Status in Déjà Dup:
  Invalid
Status in deja-dup package in Ubuntu:
  Invalid
Status in gnupg2 package in Ubuntu:
  New

Bug description:
  Some have reported problems before with repeated demands for
  encryption passwords, but mine gives a different error.  I've deleted
  all my previous backups and reinstalled duplicity and deja-dup, but I
  still get the error:

  DUPLICITY: . = Begin GnuPG log =
  DUPLICITY: . gpg: WARNING: "--no-use-agent" is an obsolete option - it has no 
effect
  DUPLICITY: . gpg: invalid size of lockfile 
'/home/username/.gnupg/gnupg_spawn_agent_sentinel.lock'
  DUPLICITY: . gpg: cannot read lockfile
  DUPLICITY: . gpg: can't connect to the agent: Invalid argument
  DUPLICITY: . gpg: problem with the agent: No agent running
  DUPLICITY: . = End GnuPG log =
  DUPLICITY: .
  DUPLICITY: .

  DUPLICITY: ERROR 31 GPGError
  DUPLICITY: . GPGError: GPG Failed, see log below:
  DUPLICITY: . = Begin GnuPG log =
  DUPLICITY: . gpg: WARNING: "--no-use-agent" is an obsolete option - it has no 
effect
  DUPLICITY: . gpg: invalid size of lockfile 
'/home/username/.gnupg/gnupg_spawn_agent_sentinel.lock'
  DUPLICITY: . gpg: cannot read lockfile
  DUPLICITY: . gpg: can't connect to the agent: Invalid argument
  DUPLICITY: . gpg: problem with the agent: No agent running
  DUPLICITY: . = End GnuPG log =
  DUPLICITY: .

  System details:
  Ubuntu 17.04
  deja-dup  34.4-0ubuntu1
  duplicity 0.7.06-2ubuntu3

  Thank you in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1700645/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 847399] Re: No relevant progress info while doing the actual backup in Dejadup

[Vej]

** Changed in: deja-dup
   Status: New => Confirmed

-- 
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/847399

Title:
  No relevant progress info while doing the actual backup in Dejadup

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  When doing the actual backup, the progress bar is moving from 0 to
  100% without any intermediate steps. What also good be usefull: an
  indication what het upload speed is, and in conjunction with the file
  size, a calculated ETA.

  To have some user feedback, is especially important when backing up to
  cloudbased targets like SSH or U1, because they are limited by a
  relatively small upload bandwidth. As for now, the upload seems
  broken, because a user cannot see any progress, only when it's ready.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/847399/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1703797] Re: Deja-dup version info not accessible throug GUI

[Vej]

This is the same with Déjà Dup in Ubuntu and should be trivial to fix,
by adding a small window containing the information and a menu entry as
a submenu of "Help".

** Changed in: deja-dup
   Importance: Undecided => Wishlist

** Changed in: deja-dup
   Status: New => Triaged

** Tags added: needs-design

** Also affects: deja-dup (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: hundredpapercuts
   Importance: Undecided
   Status: New

** Tags added: xenial

** Changed in: deja-dup (Ubuntu)
   Status: New => Triaged

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Wishlist

-- 
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/1703797

Title:
  Deja-dup version info not accessible throug GUI

Status in Déjà Dup:
  Triaged
Status in One Hundred Papercuts:
  New
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  I cannot access the version info of deja-dup (called Backups in
  Fedora) through the GUI. For users not familiar with the command line
  it would be useful if they could learn the deja-dup version through an
  'about' menu entry like most applications have.

  System info:
  Fedora release 26 (Twenty Six)
  deja-dup-34.3-3.fc26.x86_64
  duplicity-0.7.13.1-1.fc26.x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1703797/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1700645] Re: Encrypted backup repeatedly asks for password on first use

[Vej]

** Also affects: deja-dup (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: deja-dup (Ubuntu)
   Status: New => Incomplete

** Tags added: zesty

-- 
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/1700645

Title:
  Encrypted backup repeatedly asks for password on first use

Status in Déjà Dup:
  Incomplete
Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  Some have reported problems before with repeated demands for
  encryption passwords, but mine gives a different error.  I've deleted
  all my previous backups and reinstalled duplicity and deja-dup, but I
  still get the error:

  DUPLICITY: . = Begin GnuPG log =
  DUPLICITY: . gpg: WARNING: "--no-use-agent" is an obsolete option - it has no 
effect
  DUPLICITY: . gpg: invalid size of lockfile 
'/home/username/.gnupg/gnupg_spawn_agent_sentinel.lock'
  DUPLICITY: . gpg: cannot read lockfile
  DUPLICITY: . gpg: can't connect to the agent: Invalid argument
  DUPLICITY: . gpg: problem with the agent: No agent running
  DUPLICITY: . = End GnuPG log =
  DUPLICITY: .
  DUPLICITY: .

  DUPLICITY: ERROR 31 GPGError
  DUPLICITY: . GPGError: GPG Failed, see log below:
  DUPLICITY: . = Begin GnuPG log =
  DUPLICITY: . gpg: WARNING: "--no-use-agent" is an obsolete option - it has no 
effect
  DUPLICITY: . gpg: invalid size of lockfile 
'/home/username/.gnupg/gnupg_spawn_agent_sentinel.lock'
  DUPLICITY: . gpg: cannot read lockfile
  DUPLICITY: . gpg: can't connect to the agent: Invalid argument
  DUPLICITY: . gpg: problem with the agent: No agent running
  DUPLICITY: . = End GnuPG log =
  DUPLICITY: .

  System details:
  Ubuntu 17.04
  deja-dup  34.4-0ubuntu1
  duplicity 0.7.06-2ubuntu3

  Thank you in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1700645/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1048373] Re: No option to remain in one filesystem

[Vej]

** Also affects: deja-dup
   Importance: Undecided
   Status: New

** Changed in: deja-dup
   Status: New => Confirmed

** Changed in: deja-dup
   Importance: Undecided => Medium

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Low

** Tags added: xenial

-- 
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/1048373

Title:
  No option to remain in one filesystem

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  I used "sshfs" to mount a remote filesystem in my home directory and
  it was backed up by Deja-Dup. I should, of course, have added the
  mount-point in my home directory to the exclude list, but I didn't
  realise until the backup had been running for hours and many GB had
  been downloaded on my ADSL connection from the remote SSHFS fileserver
  I was connected to. It would be useful if there was an option for
  Deja_Dup to remain in one filesystem during a backup to avoid this
  type of problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1048373/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

[Vej]

@Dabo Ross: Your problem seems to be different from this one, so a new
bug report is a good idea.

Btw: Please refrain from exaggerating "a symlink set for ~/.cache/deja-
dup gets deleted" to "deletion of symbolic links", because the handling
of ~/.cache/deja-dup is a bit special (unless you see deletion of other
symlinks as well).

Thanks

Vej

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1217959

Title:
  'metadata' file not found when creating backup ("Could not restore
  ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

Status in Déjà Dup:
  Expired
Status in duplicity package in Ubuntu:
  Expired

Bug description:
  Linux release: Ubuntu 13.04 64bit
  Kernel: 3.8.0-29-generic
  Python: 2.7.4
  Deja Dup: 26.0
  Duplicity: 0.6.21

  Hi. I've tried to do my monthly or so backup recently, but Deja Dup
  crashed after trying to backup a very large file (VM disk with Windows
  7, 50GB or so). I tried to do another one, this time excluding all my
  large VM's. However, now when trying to do a backup I'm getting the
  following error a few seconds after inputting my encryption password:

  Could not restore ‘/home/tom/.cache/deja-dup/metadata’: File not found
  in backup

  I've tried reinstalling both deja-dup and duplicity, purging
  duplicity, deleting deja-dup and duplicity from /home/tom/.cache,
  deleting the backup files on the external drive, deleting it's config
  as described here http://askubuntu.com/questions/53980/how-to-delete-
  all-the-settings-for-deja-dup. I know (well, I have some evidence
  supporting this) that the drive itself isn't faulty as I managed to
  backup my old laptop to the drive using duplicity and it worked fine
  (Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs
  momentarily.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1217959/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1668915] Re: Deja-dup 34.3 fails to build with vala 0.35.6

[Vej]

** Changed in: deja-dup
   Status: New => Confirmed

-- 
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/1668915

Title:
  Deja-dup 34.3 fails to build with vala 0.35.6

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup package in openSUSE:
  Confirmed

Bug description:
  Vala 0.35.x (0.36 to be) fails to translate deja-dup:

  [  9%] Generating ConfigBool.c, ConfigChoice.c, ConfigDelete.c, 
ConfigEntry.c, ConfigFolder.c, ConfigLabel.c, ConfigLabelBackupDate.c, 
ConfigLabelDescription.c, ConfigLabelLocation.c, ConfigList.c, 
ConfigLocation.c, ConfigLocationCustom.c, ConfigLocationDAV.c, 
ConfigLocationFile.c, ConfigLocationFTP.c, ConfigLocationGCS.c, 
ConfigLocationGDrive.c, ConfigLocationOpenstack.c, ConfigLocationRackspace.c, 
ConfigLocationS3.c, ConfigLocationSSH.c, ConfigLocationSMB.c, 
ConfigLocationTable.c, ConfigLocationU1.c, ConfigLocationVolume.c, 
ConfigPeriod.c, ConfigRelPath.c, ConfigURLPart.c, ConfigURLPartBool.c, 
ConfigWidget.c, WidgetUtils.c, widgets.vapi, widgets.h, widgets_internal.h
  
/home/abuild/rpmbuild/BUILD/deja-dup-34.3/deja-dup/widgets/ConfigList.vala:336.39-336.42:
 error: Argument 1: Cannot pass value to reference or output parameter
(model as Gtk.ListStore).remove(iter);

  
/home/abuild/rpmbuild/BUILD/deja-dup-34.3/deja-dup/widgets/ConfigLocation.vala:400.18-400.21:
 error: Argument 1: Cannot pass value to reference or output parameter
  store.remove(iter);
   
  
/home/abuild/rpmbuild/BUILD/deja-dup-34.3/deja-dup/widgets/ConfigLocation.vala:405.22-405.29:
 error: Argument 1: Cannot pass value to reference or output parameter
  store.remove(sep_iter);
   

  ** (valac:12386): CRITICAL **: vala_data_type_get_nullable: assertion
  'self != NULL' failed

  (valac:12386): GLib-GObject-WARNING **: invalid cast from
  'ValaNamespace' to 'ValaTypeSymbol'

  (valac:12386): GLib-GObject-WARNING **: invalid cast from
  'ValaNamespace' to 'ValaTypeSymbol'

  (valac:12386): GLib-GObject-WARNING **: invalid cast from
  'ValaNamespace' to 'ValaTypeSymbol'

  (valac:12386): GLib-GObject-WARNING **: invalid cast from 'ValaNamespace' to 
'ValaTypeSymbol'
  Compilation failed: 3 error(s), 0 warning(s)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1668915/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1251628] Re: Warn user if they've manually added remote URLs to includes/excludes

[Vej]

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Low

-- 
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/1251628

Title:
  Warn user if they've manually added remote URLs to includes/excludes

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Error message seems related to: https://bugs.launchpad.net/deja-
  dup/+bug/532197

  3 Days ago, I added a smb volume to the backup the backup went
  fine apparently, today I connected the external hard drive, but it
  failed

  I'll add the DEBUG log and the conf I got from gsettings

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: deja-dup 27.3.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov 15 14:24:28 2013
  InstallationDate: Installed on 2011-10-31 (746 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac 
(20111012)
  MarkForUpload: True
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to saucy on 2013-10-09 (36 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1251628/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1197919] Re: deja-dup password request dialog causes timeout

[Vej]

** Tags added: trusty

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Medium

** Also affects: deja-dup
   Importance: Undecided
   Status: New

** Changed in: deja-dup
   Status: New => Triaged

** Changed in: deja-dup
   Status: Triaged => Won't Fix

** Changed in: deja-dup
   Status: Won't Fix => Confirmed

** Changed in: deja-dup
   Importance: Undecided => High

-- 
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/1197919

Title:
  deja-dup password request dialog causes timeout

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  I have configured deja-dup so that it backups daily to a SMB server
  share. This works fine when I'm at the computer. When I'm not there,
  the deja-dup password prompt for the SMB share pops up. Then, if I
  don't enter the password within a certain time, even with the correct
  password I get a DBus error message and the backup fails.

  deja-dup should prompt for the password and open the connection only
  after having received a password. Or it should automatically retry
  when it gets a timeout error without having to prompt again.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-34.55~precise1-generic 3.5.7.13
  Uname: Linux 3.5.0-34-generic i686
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: i386
  Date: Thu Jul  4 19:34:34 2013
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130214)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1197919/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 974036] Re: Say "No space left on target" while it's in the cache folder that the problem is

[Vej]

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Critical

** Changed in: deja-dup (Ubuntu)
   Importance: Critical => Medium

-- 
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/974036

Title:
  Say "No space left on target" while it's in the cache folder that the
  problem is

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  The problem is that I get the message "No space left on me DD" where "me DD" 
is the name of my backup folder on my NAS.
  There is still 1.9 T free space on that NAS.

  I can see it when running:  gvfs-info -f smb://user@diskstation/backup-profil/
  attributes:
filesystem::size: 2948732551168
filesystem::free: 1929174245376
filesystem::type: cifs
filesystem::readonly: FALSE
gvfs::backend: smb-share

  When I checked the problem was that there was no space left on my home
  folder and after I did a little bit of cleaning it looks like the
  backup process could go on.

  The message here is wrong and there is no easy way to know if we have enough 
space in our /home, /tmp or backup destination.
  Isn't it possible to give some kind of rough estimation to the user.

  Thanks.

  Infos :

  Distribution : Ubuntu 11.10

  Deja-dup & duplicity version :
  deja-dup  20.1-0ubuntu0.2
  duplicity 0.6.15-0ubuntu2

  /tmp/deja-dup.gsettings

  org.gnome.DejaDup backend 'file'
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup exclude-list ['$TRASH', '/home/mike/tralala', 
'/home/mike/tralalala2']
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup last-backup '2012-03-31T19:13:46.682814Z'
  org.gnome.DejaDup last-restore ''
  org.gnome.DejaDup last-run '2012-03-31T19:13:46.682814Z'
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup periodic-period 7
  org.gnome.DejaDup prompt-check '2012-03-17T08:25:18.027345Z'
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup welcomed true
  org.gnome.DejaDup.File icon '. GThemedIcon drive-harddisk-usb drive-harddisk 
drive'
  org.gnome.DejaDup.File name 'Disque dur 1,0 TB: BackUp'
  org.gnome.DejaDup.File path 'smb://user@DiskStation/backup-profil/me%20DD'
  org.gnome.DejaDup.File relpath @ay []
  org.gnome.DejaDup.File short-name 'BackUp'
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File uuid '17AFAA75333D'
  org.gnome.DejaDup.Rackspace container 'me-VGN-FZ31M'
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'me-VGN-FZ31M'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.U1 folder '/deja-dup/me-VGN-FZ31M'

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/974036/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1232873] Re: "could not back up files" dialog never shown; breaks scheduled backups

[Vej]

Hello everyone affected. Is this still related to an option called "--
auto" as described by the original author?

I could not find such an option in a recent version of Déjà Dup.

** Changed in: deja-dup
   Status: Confirmed => Incomplete

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Incomplete

-- 
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/1232873

Title:
  "could not back up files" dialog never shown; breaks scheduled backups

Status in Déjà Dup:
  Incomplete
Status in deja-dup package in Ubuntu:
  Incomplete
Status in deja-dup package in Arch Linux:
  New

Bug description:
  On the conclusion of a backup, if any nonreadable files exist in the
  backup source directories, Deja Dup shows a notification at the bottom
  of my screen telling me that the backup completed but not all files
  were able to be backed up; "see dialog for details". However, this
  dialog never appears. As a result, the "deja-dup --backup --auto"
  process never terminates, as it's waiting for me to close a dialog
  that never appeared in the first place.

  This effectively breaks the automatic, "set-and-forget" backup
  strategy, as deja-dup-monitor will not launch another scheduled backup
  until the deja-dup process exits, which will never happen.

  This only happens when deja-dup is launched with "deja-dup --backup
  --auto"; launching with "deja-dup --backup" (no auto) does show the
  dialog at the end of the process, allowing me to close it and properly
  terminate the backup.

  ~$ lsb_release -d
  Description:  Ubuntu Saucy Salamander (development branch)

  ~$ dpkg-query -W deja-dup duplicity
  deja-dup  27.3.1-0ubuntu1
  duplicity 0.6.21-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1232873/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 989854] Re: Déjà Dup tries to backup during system upgrade

[Vej]

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Medium

-- 
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/989854

Title:
  Déjà Dup tries to backup during system upgrade

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  Déjà Dup tried to backup during system upgrade from Ubuntu 11.10 to
  12.04. Of course it failed because of a broken pipe.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu2
  Uname: Linux 3.0.7-030007-generic i686
  ApportVersion: 2.0.1-0ubuntu6
  Architecture: i386
  Date: Fri Apr 27 17:59:24 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to precise on 2012-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/989854/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 878807] Re: No "Choose Folder..." button when selecting a storage disk

[Vej]

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Wishlist

-- 
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/878807

Title:
  No "Choose Folder..." button when selecting a storage disk

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  When configuring deja-dup through the "Backup" dialog in the settings
  you can select a disk in the "Storage" section. When doing so you only
  get an empty "Folder" input field. This happens for local as well as
  external disks. Not often do you want the backup to be placed directly
  in the root of the disk though.

  It would be more efficient to provide a "Choose Folder..." button,
  just like when selecting the "Local folder" option from the "Backup
  location" dropdown. Only in this case it would use the selected disk
  as a base. This would allow you to quickly choose a subfolder and/or
  create one.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: deja-dup 20.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
  Uname: Linux 3.0.0-12-generic-pae i686
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Thu Oct 20 14:07:12 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/878807/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 957857] Re: No way to change password for a backup set

[Vej]

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Wishlist

-- 
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/957857

Title:
  No way to change password for a backup set

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  In deja-dup-preferences, there is no way to change a password for a
  backup set - without starting the backups again from 0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/957857/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1665402] Re: Own keyboard shortcuts don't work

[Vej]

@Gunnar: You are right. Clicking on "Disabled" opens the window to
record the shortcut.

Nevertheless we have a different behavior between the predefined
shortcuts and the own ones. I consider it unintuitive, that the action
for editing the own shortcuts is used to record predefined shortcuts. A
better UI would keep them the same i.e. to perform no action when
clicking on the name of a predefined shortcut.

** Changed in: unity-control-center (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1665402

Title:
  Own keyboard shortcuts don't work

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I do not know why the own-shortcuts not working. The only what i had
  done in the system is removing the unity-webapps-common and a
  autoremove after that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1665402/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1674121] Re: "Restore" asks for cryptic authentication to run /bin/sh as superuser

[Vej]

@Christopher Thank you for the settings. The option "org.gnome.DejaDup
root-prompt true" might cause this. I do not know (yet) when and why
this is set. This might need to be looked into by an developer. But the
prompt comes from Déjà Dup and should indicate so. I agree.

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => New

** Changed in: deja-dup (Ubuntu)
   Status: New => Triaged

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Medium

** Also affects: deja-dup
   Importance: Undecided
   Status: New

** Changed in: deja-dup
   Status: New => Triaged

** Changed in: deja-dup
   Importance: Undecided => Medium

-- 
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/1674121

Title:
  "Restore" asks for cryptic authentication to run /bin/sh as superuser

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  I am trying to restore a full backup to an external hard drive.
  After 20 minutes or so, a cryptic gui popup arises which says that "some 
process" wants sudo authentication to run /bin/sh

  It is surely a bug to generate such a vague request for sudo use.

  I note it has been this way since 2013
  (https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1079553 which
  has been unaddressed, so the outcome of denying this request is still
  a great pain), but I am pointing out that this kind of permission
  request is itself a bug, if not a security risk because it teaches
  users to give that kind of permission to an unknown script.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: deja-dup 34.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 19 12:35:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-02-12 (400 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to yakkety on 2017-01-21 (56 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1674121/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 947244] Re: deja-dup-monitor does not have branded icon in System Monitor

[Vej]

@Diogo Thanks for letting us know.

-- 
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/947244

Title:
  deja-dup-monitor does not have branded icon in System Monitor

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  deja-dup does not have unique icon in system monitor (as reported in
  LP: #92 which was closed because these should be individual bugs)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/947244/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1675177] Re: Userinterface does not show progress clearly

[Vej]

*** This bug is a duplicate of bug 1623835 ***
https://bugs.launchpad.net/bugs/1623835

Thanks for taking the time to report this bug. The problem is handled in
bug #1623835 and should be fixed upstream.

-- 
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/1675177

Title:
  Userinterface does not show progress clearly

Status in Déjà Dup:
  New
Status in deja-dup package in Ubuntu:
  New

Bug description:
  I get to see only one line in the UI when backing up multiple files. The 
scrollbar does work but the box does not scale with the form.
  See image for clarification (locale is Dutch)

  Description:  Ubuntu 16.10
  deja-dup  34.2-0ubuntu3.1
  duplicity 0.7.06-2ubuntu2

  
  I modified this a little bit, but it should not matter much

  org.gnome.DejaDup last-restore ''
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup full-backup-period 90
  org.gnome.DejaDup backend 'file'
  org.gnome.DejaDup last-run '2017-03-21T01:18:31.743362Z'
  org.gnome.DejaDup nag-check '2017-03-11T06:19:06.743756Z'
  org.gnome.DejaDup prompt-check '2016-06-28T21:39:05.797622Z'
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup include-list ['/home/ivar/Documents']
  org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
  org.gnome.DejaDup last-backup '2017-03-21T01:18:31.743362Z'
  org.gnome.DejaDup periodic-period 1
  org.gnome.DejaDup delete-after 182
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'Home'
  org.gnome.DejaDup.OpenStack authurl ''
  org.gnome.DejaDup.OpenStack tenant ''
  org.gnome.DejaDup.OpenStack username ''
  org.gnome.DejaDup.OpenStack container 'Home'
  org.gnome.DejaDup.GCS id ''
  org.gnome.DejaDup.GCS bucket ''
  org.gnome.DejaDup.GCS folder 'Home'
  org.gnome.DejaDup.GDrive email ''
  org.gnome.DejaDup.GDrive folder '/deja-dup/Home'
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.Rackspace container 'Home'
  org.gnome.DejaDup.File path 'davs://xx.com:443/remote.php/webdav/HomePC'
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.File relpath @ay []
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File type 'normal'


  There seem to be no problems backing up or restoring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1675177/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1675177] Re: Userinterface does not show progress clearly

[Vej]

*** This bug is a duplicate of bug 1623835 ***
https://bugs.launchpad.net/bugs/1623835

** Also affects: deja-dup (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: yakkety

** This bug has been marked a duplicate of bug 1623835
   Scrolled Windows in backup/restore progress are too small to read

-- 
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/1675177

Title:
  Userinterface does not show progress clearly

Status in Déjà Dup:
  New
Status in deja-dup package in Ubuntu:
  New

Bug description:
  I get to see only one line in the UI when backing up multiple files. The 
scrollbar does work but the box does not scale with the form.
  See image for clarification (locale is Dutch)

  Description:  Ubuntu 16.10
  deja-dup  34.2-0ubuntu3.1
  duplicity 0.7.06-2ubuntu2

  
  I modified this a little bit, but it should not matter much

  org.gnome.DejaDup last-restore ''
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup full-backup-period 90
  org.gnome.DejaDup backend 'file'
  org.gnome.DejaDup last-run '2017-03-21T01:18:31.743362Z'
  org.gnome.DejaDup nag-check '2017-03-11T06:19:06.743756Z'
  org.gnome.DejaDup prompt-check '2016-06-28T21:39:05.797622Z'
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup include-list ['/home/ivar/Documents']
  org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
  org.gnome.DejaDup last-backup '2017-03-21T01:18:31.743362Z'
  org.gnome.DejaDup periodic-period 1
  org.gnome.DejaDup delete-after 182
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'Home'
  org.gnome.DejaDup.OpenStack authurl ''
  org.gnome.DejaDup.OpenStack tenant ''
  org.gnome.DejaDup.OpenStack username ''
  org.gnome.DejaDup.OpenStack container 'Home'
  org.gnome.DejaDup.GCS id ''
  org.gnome.DejaDup.GCS bucket ''
  org.gnome.DejaDup.GCS folder 'Home'
  org.gnome.DejaDup.GDrive email ''
  org.gnome.DejaDup.GDrive folder '/deja-dup/Home'
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.Rackspace container 'Home'
  org.gnome.DejaDup.File path 'davs://xx.com:443/remote.php/webdav/HomePC'
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.File relpath @ay []
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File type 'normal'


  There seem to be no problems backing up or restoring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1675177/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1674121] Re: "Restore" asks for cryptic authentication to run /bin/sh as superuser

[Vej]

Hello Christopher!

Could you please provide us with the file /tmp/deja-dup.gsettings after running 
the following line (you may want to scrub the file of any incriminating file 
names or details):
gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings

** Changed in: deja-dup (Ubuntu)
   Status: New => Incomplete

-- 
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/1674121

Title:
  "Restore" asks for cryptic authentication to run /bin/sh as superuser

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  I am trying to restore a full backup to an external hard drive.
  After 20 minutes or so, a cryptic gui popup arises which says that "some 
process" wants sudo authentication to run /bin/sh

  It is surely a bug to generate such a vague request for sudo use.

  I note it has been this way since 2013
  (https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1079553 which
  has been unaddressed, so the outcome of denying this request is still
  a great pain), but I am pointing out that this kind of permission
  request is itself a bug, if not a security risk because it teaches
  users to give that kind of permission to an unknown script.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: deja-dup 34.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 19 12:35:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-02-12 (400 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to yakkety on 2017-01-21 (56 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1674121/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1600783] Re: Not translated string

[Vej]

This might be caused by this code (from ~deja-dup-hackers/deja-dup/34 :
/libdeja/Network.vala lines 40 to 51 in revision 1580):

  public async bool can_reach(string url)
  {
var mon = NetworkMonitor.get_default();
try {
  var socket = NetworkAddress.parse_uri(url, 0);
  return yield mon.can_reach_async(socket);
}
catch (Error e) {
  warning("%s", e.message);
  return false;
}
  }

Please see how the message from GLib.NetworkAddress or GLib.NetworkMonitor is 
passed to the user.
So lets try to find this string in the translation of GLib in vala.

-- 
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/1600783

Title:
  Not translated string

Status in Déjà Dup:
  Confirmed
Status in Ubuntu Translations:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  See
  
https://dl.dropboxusercontent.com/u/26959244/Capture%20du%202016-07-08%2011-59-38.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1600783/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1290852] Re: Deja-dup crashes on Restore on 14.04

[Vej]

This bug is fixed for zesty in duplicity 0.7.06-2ubuntu3.

** Changed in: duplicity (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1290852

Title:
  Deja-dup crashes on Restore on 14.04

Status in deja-dup package in Ubuntu:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released

Bug description:
  Trying to restore my data on my laptop, after my desktop died,
  resulted in error, which I then tried to workaround by adding a try:
  except where the exception was thrown. After that, I got a second
  error on restore.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 29.5-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 11 14:16:38 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-01 (9 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140228)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1290852/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1268182] Re: Computer name changed

[Vej]

This bug report (and its duplicate) deal with two problems (in my
opinion):

- Fix the problem, that accepting the changed hostname is not persistent
(i.e. that the dialog is showed more than once).

- Find a solution for the problem, that the hostname from
socket.getfqdn() does not always match the one from
socket.gethostname().

The later one is a problem of duplicity and therefore handled in bug #667885 ("
duplicity prefers fully-qualified-domain-name (fqdn) over hostname").

The first problem might be fixable in Déjà Dup. I will examine this
further.

-- 
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/1268182

Title:
  Computer name changed

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  I am/was using Deja-Dup (version 26.0)  on Fedora 19, I modified my router 
settings to use openDNS instead of my ISP's DNS. 
  Then the next time I ran Deja-dup I had the message:-

  The existing backup is of a computer named
  advancedsearch.virginmedia.com, but the current
  computer's name is Zotac-Zbox-ID82. If this is
  unexpected, you should backup to a different location.

  Since I wasn't asked to specify a computer name, and the underlying
  "duplicity" (version: 0.6.22) would appear to get the machine name
  from the wrong file, I understand that the computer name is kept in
  two files (a bad practice in my mind).

  So can the interface be changed to show and or allow one to specify
  what hostname is used?

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1268182/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1600299] Re: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted

[Vej]

** Changed in: deja-dup
   Status: Confirmed => Triaged

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: deja-dup
   Importance: Undecided => High

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Medium

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Triaged

-- 
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/1600299

Title:
  Giving up after 5 attempts. Error: g-io-error-quark: The specified
  location is not mounted

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged
Status in deja-dup package in Mandriva:
  New

Bug description:
  I've got my system set up with off-site backup over sftp. This works
  fine but the problem is that while deja-dup is gathering files and
  calculating the backup delta the connection to the server times out.
  This means that it's not available when deja-dup actually tries to
  push files to the server and results in this error message:

  Giving up after 5 attempts. Error: g-io-error-quark: The specified
  location is not mounted (16)

  By sitting in the file manager and jumping between folders the
  connection can be kept alive but that's rather annoying and requires
  my presence. Would really like to see deja-dup actually trying to set
  up the connection again instead.

  
  Using:
  Manjaro 16.06.1
  deja-dup 34.2-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1600299/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 915111] Re: deja-dup Ubuntu One folder is unfortunately named

[Vej]

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: deja-dup (Ubuntu)
 Assignee: MoHcasLu.H (braunsvillevibez) => (unassigned)

-- 
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/915111

Title:
  deja-dup Ubuntu One folder is unfortunately named

Status in Déjà Dup:
  Expired
Status in One Hundred Papercuts:
  Expired
Status in deja-dup package in Ubuntu:
  Won't Fix

Bug description:
  When the user chooses to synchronise their backups on their desktops
  via Ubuntu One, the name of the directory they are given to keep them
  in is not user friendly. While deja-dup is indeed the name of the
  backup application shipped with Ubuntu, no reference is made to this
  anywhere whithin either the software or documentation. I propose that
  this folder be renamed 'Backups', or a variation on a theme.

  I'm not sure if this issue needs to go upstream. Does anyone know if
  it does?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: deja-dup 20.1-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic-pae 3.0.9
  Uname: Linux 3.0.0-14-generic-pae i686
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Thu Jan 12 01:10:35 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/915111/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1315185] Re: pass in trusty, but fails ADT tests in utopic

[Vej]

** Changed in: deja-dup
   Status: Fix Committed => Fix Released

-- 
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/1315185

Title:
  pass in trusty, but fails ADT tests in utopic

Status in Déjà Dup:
  Fix Released
Status in dbus-test-runner package in Ubuntu:
  Invalid
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  I've uploaded a no change rebuild of gvfs, yet it's currently blocked
  on deja-dup and dbus-test-runner ADT tests failing in utopic, yet they
  pass in trusty.

  This should be investigated and if something is wrong, appropriately
  fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1315185/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1657092] Re: deja-dup refers to "Files" instead of "Caja"

[Vej]

This had been released as a part of Déjà Dup 34.4.

** Changed in: deja-dup
   Status: Fix Committed => Fix Released

-- 
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/1657092

Title:
  deja-dup refers to "Files" instead of "Caja"

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Xenial:
  Confirmed
Status in deja-dup source package in Yakkety:
  Confirmed
Status in deja-dup source package in Zesty:
  Fix Released

Bug description:
  The Backups application's Overview screen says "You can restore the
  entire backup with the Restore... button or use Files"

  It should say "or use Caja", since the file manager in Mate has been
  renamed Caja.

  Screenshot attached.

  [Impact]
  * Users of Mate which use Déjà Dup get confused by the wrong terminology 
regarding their file manager.
  * The upstream fix detects Mate desktops using XDG_CURRENT_DESKTOP and fills 
a new variable with "Caja" or "Files". That variable is included in the string 
afterwards.

  [Test Case]
  * Open Déjà Dup inside Ubuntu Mate (launch "deja-dup-preferences" from a 
terminal)
  * Install the necessary software by clicking the "Install..."-button.
  * Create a backup:
  - Choose a location on the "Storage Location" tab (or use the default 
local folder)
  - On the "Overview" tab perform a backup using the button "Backup now"
  * On the "Overview" tab: Look at the description above the restore button.
  * It refers to Files instead of Caja

  [Regression Potential]
  * None that I am aware of. The worst case should be limited to a broken (or 
untranslated) string in Déjà Dup itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1657092/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1329133] Re: Error message about .dbus directory shows up after backup even though the directory is excluded.

[Vej]

*** This bug is a duplicate of bug 1089131 ***
https://bugs.launchpad.net/bugs/1089131

** This bug is no longer a duplicate of bug 1313034
   Deja-dup reports it couldn't backup ~/.cache/dconf and ~/.gvfs even though 
it's not supposed to try to (also, ~/.dbus)
** This bug has been marked a duplicate of bug 1089131
   Stat errors on locked (but excluded) files

-- 
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/1329133

Title:
  Error message about .dbus directory shows up after backup even though
  the directory is excluded.

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Please check the attached screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 12 04:11:35 2014
  InstallationDate: Installed on 2014-05-16 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1329133/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1599657] Re: Backups Folders to ignore are not ignored

[Vej]

*** This bug is a duplicate of bug 1089131 ***
https://bugs.launchpad.net/bugs/1089131

** This bug is no longer a duplicate of bug 1313034
   Deja-dup reports it couldn't backup ~/.cache/dconf and ~/.gvfs even though 
it's not supposed to try to (also, ~/.dbus)
** This bug has been marked a duplicate of bug 1089131
   Stat errors on locked (but excluded) files

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1599657

Title:
  Backups Folders to ignore are not ignored

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  System Settings -> Backups -> Folders to ignore, includes ~/.cache in
  the list. However, after logging into a new Unity session, the backup
  runs automatically and reports that the backup failed because it could
  not read ~/.cache/dconf. The directory is owned by root and not
  readable by the user account. Therefore, it is expected that the
  backup process would not be able to read it.

  ls -al ~/.cache
  drwx--  2 root   root4096 Jul  1 16:25 dconf

  It is also expected that the backup process should not attempt to read
  ~/.cache/dconf since the parent ~/.cache is in the Folder to ignore
  list.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160413-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul  6 18:05:54 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/unity-control-center
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1599657/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1369905] Re: deja-dup ignored-folders are backupped

[Vej]

*** This bug is a duplicate of bug 1089131 ***
https://bugs.launchpad.net/bugs/1089131

** This bug is no longer a duplicate of bug 1313034
   Deja-dup reports it couldn't backup ~/.cache/dconf and ~/.gvfs even though 
it's not supposed to try to (also, ~/.dbus)
** This bug has been marked a duplicate of bug 1089131
   Stat errors on locked (but excluded) files

-- 
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/1369905

Title:
  deja-dup ignored-folders are backupped

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  beowulf:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  beowulf:~$ apt-cache policy deja-dup
  deja-dup:
Installiert:   30.0-0ubuntu4
Installationskandidat: 30.0-0ubuntu4
Versionstabelle:
   *** 30.0-0ubuntu4 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Upon every run of backup, I get the error-message that the file
  "/home/beowulf/.cache/dconf" could not be backuped. So far no problem,
  but In the settings I have set the folder "~/.cache" as part of the
  ignore-list.

  The file should not even be tried to be backuped as the folder is part
  of the ignore list.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 16 09:42:03 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-25 (325 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (146 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1369905/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1118662] Re: Don't warn user that excluded folders couldn't be processed

[Vej]

*** This bug is a duplicate of bug 1089131 ***
https://bugs.launchpad.net/bugs/1089131

** This bug is no longer a duplicate of bug 1313034
   Deja-dup reports it couldn't backup ~/.cache/dconf and ~/.gvfs even though 
it's not supposed to try to (also, ~/.dbus)
** This bug has been marked a duplicate of bug 1089131
   Stat errors on locked (but excluded) files

-- 
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/1118662

Title:
  Don't warn user that excluded folders couldn't be processed

Status in Déjà Dup:
  New
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  From Jason Kennaly (in question https://answers.launchpad.net/deja-
  dup/+question/221322):

  As I indicated in this thread,
  http://ubuntuforums.org/showthread.php?p=12497422=1#post12497422

  I am using this to back up my home directory in Ubuntu 12.10. There is
  a subdirectory called .gnupg. This subdirectory is owned by root. This
  directory is excluded from being backed up.

  Every time Deja Dup runs, I get an error message that this directory
  could not be processed.This is fine, I do not need it backed up, but
  it is frustrating that I get this error message even though this
  directory is excluded from the backup.

  Helpful information:

  ~$ ls -ld .gnupg | grep gnupg
  drwx-- 2 root root 4096 Apr 18  2012 .gnupg
  ~$ deja-dup --version
  deja-dup 24.0
  ~$ duplicity --version
  duplicity 0.6.19

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1118662/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1229490] Re: Deja-dup backup ignores "folders to ignore" setting

[Vej]

*** This bug is a duplicate of bug 1089131 ***
https://bugs.launchpad.net/bugs/1089131

** This bug is no longer a duplicate of bug 1313034
   Deja-dup reports it couldn't backup ~/.cache/dconf and ~/.gvfs even though 
it's not supposed to try to (also, ~/.dbus)
** This bug has been marked a duplicate of bug 1089131
   Stat errors on locked (but excluded) files

-- 
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/1229490

Title:
  Deja-dup backup ignores "folders to ignore" setting

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Every day deja-dup shows a popup message saying it failed to backup 2
  files. The folders containing these files are already in the list of
  folders to ignore, so deja-dup shouldn't even be trying to back them
  up. I'm attaching a screenshot to illustrate.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: deja-dup 26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Tue Sep 24 09:34:32 2013
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2013-08-19 (35 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1229490/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1013207] Re: deja-dup warns about unreadable files that have been configured to be ignored

[Vej]

*** This bug is a duplicate of bug 1089131 ***
https://bugs.launchpad.net/bugs/1089131

** This bug is no longer a duplicate of bug 1313034
   Deja-dup reports it couldn't backup ~/.cache/dconf and ~/.gvfs even though 
it's not supposed to try to (also, ~/.dbus)
** This bug has been marked a duplicate of bug 1089131
   Stat errors on locked (but excluded) files

-- 
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/1013207

Title:
  deja-dup warns about unreadable files that have been configured to be
  ignored

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  I have set up deja-dup (via the Backup system settings module) to
  ignore two folders which are unreadble by me (/opt/lost+found and
  /opt/.Trash-0).  At the end of each weekly back up I get a warning
  specifying that these two directories could not be backed up.  I
  expected deja-dup/duplicity to ignore these folders, but it appears
  duplicity attempted to back them anyway.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  Date: Thu Jun 14 10:37:14 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to precise on 2012-04-30 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1013207/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp