[Desktop-packages] [Bug 1718737] [NEW] Firefox: all tabs loose page display and internet access but new tabs work normally

2017-09-21 Thread Michael F Winthrop
Public bug reported:

Significant problems with KUBUNTU 16.04.3 WiFi.

I had been an early adopter of KUBUNTU 16.04, before the warnings about
on-line upgrade from KUBUNTU 14.04 came out. To solve those problems, I
re-installed KUBUNTU 16.04.3 from disk over the system partition of my
PC while retaining my user partition, applications, and downloads
partitions (also WIN10) KUBUNTU 16.04 WiFi was bad before and remained
bad after. KUBUNTU 14.04 had some problems, but that eventually was
resolved.

Most recent complaint is Firefox will loose all displayed tabbed web
pages and those web pages cannot be refreshed. Opening a new web tab
works perfectly. Pasting a broken web page URL into a new tab works
perfectly.

For some time I have had WiFi failures on boot.The ifconfig initially
said there was no WiFi device.  IMPORTANT NOTE: Ethernet has always
worked and I have had to string a cat5 cable across my house several
times to get network access for repairs. I installed network-manager (it
was missing ??) and WiFi showed up via ifconfig.

After installing network-manager (again) ifconfig showed WiFi with a new
ID: wlp12s0. Next I manually inserted this new ID into
/etc/network/interfaces because wlan0 is apparently OBE:

#--- wlp12s0  ---wlan--
auto wlp12s0

iface wlp12s0 inet static
  address 192.168.99.12
  netmask 255.255.255.0 
  gateway 192.168.99.1
  wpa-ssid Disco
  wpa-psk pre-shared-key

At this point, WiFi would work about 50% of the time on boot/reboot.
ifconfig always shows it as configured. The network-manager widget only
shows it when it is configured via boot-up. If boot-up fails to
configure WiFi the widget only shows Ethernet. It is displayed in
network-manager but it is not available to connect. Network-manager
showed Ethernet as available to turn OFF. Eventually I tried to put
Ethernet up/down in as an option and eliminated Ethernet always up (this
was explicitly not set to be always up, but that was the case anyhow)
Now Ethernet up/down is always up on boot-up.

BEGIN DIGRESSION
When I looked at the password, I noted that in network-manager there is a 
wallet requirement to access the password (if I chose to use it) so I tried 
that. That accomplished requiring me to unlock the wallet on the occasions when 
WiFi was working. However WiFi did operate more often the before. I made the 
password available without wallet since it did no useful help in this problem. 
This improve operations even more, but not reliably at all times,
END OF DIGRESSION

I next installed WiFiRadar which sometimes would run and other times
would not.(It remains installed but I am not using it now. In
particular, it could not raise WiFi from the dead when it did execute
properly. It did allow me to correct some elements of the WiFi
configuration that network-manager had wrong. It fixed the password
issue.

An odd part of this problem still occurs when WiFi does work (now about
80% of the time): ifupdown enp9s0 is connected as UP when WiFi is also
UP on boot-up. In this situation Ethernet interferes with network access
as if it is a valid connection to the same router as WiFi. When I
disconnect ifupdown enp9s0, it remains available for connect but WiFi no
longer is interfered with by the Ethernet connection that was not there.
When I run ifconfig enp9s0 down, ifconfig no longer shows enp9s0 but the
widget still shows ifupdown enp9s0 available to connect.

The Firefox issue appears to not be related to that application
directly.

I have a broadcom WiFi device in a Dell 1525 Inspiron laptop.

** Affects: gnome-nettool (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Firefox: all tabs loose page display and internet access but new tabs
  work normally

Status in gnome-nettool package in Ubuntu:
  New

Bug description:
  Significant problems with KUBUNTU 16.04.3 WiFi.

  I had been an early adopter of KUBUNTU 16.04, before the warnings
  about on-line upgrade from KUBUNTU 14.04 came out. To solve those
  problems, I re-installed KUBUNTU 16.04.3 from disk over the system
  partition of my PC while retaining my user partition, applications,
  and downloads partitions (also WIN10) KUBUNTU 16.04 WiFi was bad
  before and remained bad after. KUBUNTU 14.04 had some problems, but
  that eventually was resolved.

  Most recent complaint is Firefox will loose all displayed tabbed web
  pages and those web pages cannot be refreshed. Opening a new web tab
  works perfectly. Pasting a broken web page URL into a new tab works
  perfectly.

  For some time I have had WiFi failures on boot.The ifconfig initially
  said there was no WiFi device.  IMPORTANT NOTE: Ethernet has always
  worked and I have had to string a cat5 cable across my house several
  times to get network access for repairs. I installed network-manager
  (it was missing ??) and 

[Desktop-packages] [Bug 1718253] [NEW] dependency mismatch in libzmq3-dev and libzmq5-dev for Xenial

2017-09-19 Thread Michael Schnaitter
Public bug reported:

Trying to install libzmq5-dev instead selects libzmq3-dev. libzmq3-dev
then has an incorrect dependency on libzmq5 instead of libzmq3, the
latter of which is not available in the repos for Xenial.

** Affects: zeromq3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apt libzmq xenial zeromq

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

Title:
  dependency mismatch in libzmq3-dev and libzmq5-dev for Xenial

Status in zeromq3 package in Ubuntu:
  New

Bug description:
  Trying to install libzmq5-dev instead selects libzmq3-dev. libzmq3-dev
  then has an incorrect dependency on libzmq5 instead of libzmq3, the
  latter of which is not available in the repos for Xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1718253/+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 1715582] Re: "Operation not supported by backend" when backing up to smb server

2017-09-18 Thread Michael Terry
Can't reproduce yet...  Still thinking about this one.

** Summary changed:

- deja-dup fails to backup
+ "Operation not supported by backend" when backing up to smb server

** Changed in: deja-dup (Ubuntu)
   Status: Fix Committed => 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/1715582

Title:
  "Operation not supported by backend" when backing up to smb server

Status in deja-dup package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  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/1715582/+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 1715582] Re: deja-dup fails to backup

2017-09-15 Thread Michael Terry
Hrm.  Is it possible to share your /etc/samba/smb.conf?

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

Title:
  deja-dup fails to backup

Status in deja-dup package in Ubuntu:
  Fix Committed

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  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/1715582/+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 1715582] Re: deja-dup fails to backup

2017-09-15 Thread Michael Terry
(On the server of course)

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

Title:
  deja-dup fails to backup

Status in deja-dup package in Ubuntu:
  Fix Committed

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  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/1715582/+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 1717230] Re: InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid://

2017-09-14 Thread Michael Terry
** Also affects: deja-dup (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1490048
   Importance: Unknown
   Status: Unknown

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

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

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

Bug description:
  1. I plug in my external USB HDD.
  2. I enter the LUKS password to unlock it.
  3. The disk is automatically mounted.
  4. Deja-dup shows a popup window with this text: InvalidBackendURL: missing 
// - relative paths not supported for scheme gio+invalid: gio+invalid://

  It might be that I renamed the partions on the disk.
  I'm using Fedora 26 fully up-to-date.

  lsb_release -d
  Description:  Fedora release 26 (Twenty Six)

  dnf list installed | grep deja-dup
  deja-dup.x86_6435.6-1.fc26 
@updates 
  deja-dup-nautilus.x86_64   35.6-1.fc26 
@updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1717230/+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 1717230] Re: InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid://

2017-09-14 Thread Michael Terry
** Changed in: deja-dup
   Status: Fix Committed => Fix Released

** 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/1717230

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

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

Bug description:
  1. I plug in my external USB HDD.
  2. I enter the LUKS password to unlock it.
  3. The disk is automatically mounted.
  4. Deja-dup shows a popup window with this text: InvalidBackendURL: missing 
// - relative paths not supported for scheme gio+invalid: gio+invalid://

  It might be that I renamed the partions on the disk.
  I'm using Fedora 26 fully up-to-date.

  lsb_release -d
  Description:  Fedora release 26 (Twenty Six)

  dnf list installed | grep deja-dup
  deja-dup.x86_6435.6-1.fc26 
@updates 
  deja-dup-nautilus.x86_64   35.6-1.fc26 
@updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1717230/+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 1715582] Re: deja-dup fails to backup

2017-09-12 Thread Michael Terry
Does this work if you open your samba server in Nautilus ("Files")?
Deja-dup just uses the same gvfs operations nautilus does.  If it works
there, it should work in deja-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/1715582

Title:
  deja-dup fails to backup

Status in deja-dup package in Ubuntu:
  Fix Committed

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  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/1715582/+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 1715582] Re: deja-dup fails to backup

2017-09-12 Thread Michael Terry
Thanks for the update, Wolf!

The first error you reported is the real one [1]: "Operation not
supported by backend."  Samba has a history of being a bit flaky over
gvfs.  I'll try to reproduce here and see if I know why this is
happening for ya.

[1] Don't bother running deja-dup with sudo, it's not surprising that it
doesn't work.  Root doesn't have the same access to the user's DBus
session that the user does.  So a lot of stuff (including all gvfs file
operations) fails.

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

Title:
  deja-dup fails to backup

Status in deja-dup package in Ubuntu:
  Fix Committed

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  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/1715582/+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 1716672] Re: Deja-dup can't be unistallled

2017-09-12 Thread Michael Terry
Looks like ubuntu-mate-meta should make deja-dup a Recommends, not a
Depends, so that users can uninstall it.

** Package changed: deja-dup (Ubuntu) => ubuntu-mate-meta (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/1716672

Title:
  Deja-dup can't be unistallled

Status in ubuntu-mate-meta package in Ubuntu:
  New

Bug description:
  I find this utility to be too buggy and its implementation a total
  hazard so I wanted to uninstall it but I have to uninstall the Mate
  desktop

  sudo apt-get purge deja-dup
  [sudo] password for ccheco: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
deja-dup* deja-dup-backend-cloudfiles* deja-dup-backend-gvfs* 
deja-dup-backend-s3* deja-dup-caja* ubuntu-mate-desktop*
  0 upgraded, 0 newly installed, 6 to remove and 22 not upgraded.
  After this operation, 3,148 kB disk space will be freed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Sep 12 09:07:58 2017
  InstallationDate: Installed on 2017-08-11 (31 days ago)
  InstallationMedia: Ubuntu-MATE 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/ubuntu-mate-meta/+bug/1716672/+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 1686066] Re: Rhythmbox no support for iPod nano 7th gen

2017-09-10 Thread Michael Steffens
Fix was released with which version?

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

Title:
  Rhythmbox no support for iPod nano 7th gen

Status in libgpod package in Ubuntu:
  Fix Released

Bug description:
  I also filed a feature request for Rhythmbox, here the link
  https://bugzilla.gnome.org/show_bug.cgi?id=781191#c1

  Ubuntu 16.04 (64Bit)
  It seems that libgpod needs to support the new iPod nano 7th gen first, then 
rhythmbox will support the device. Any chance of that happening?

  :~$ rhythmbox -D ipod
  (12:25:32) [0xe624c0] [rb_ipod_plugin_init] rb-ipod-plugin.c:92: RBIpodPlugin 
initialising

  (rhythmbox:9839): Gtk-WARNING **: Duplicate child name in GtkStack:
  Add to Playlist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgpod/+bug/1686066/+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 1715749] Re: Intermittent black screen on HP EliteBook 840 G1

2017-09-10 Thread Michael von Glasow
Update on behavior: the last few times the internal display went black,
I did not touch the keyboard and mouse at all, and the display came back
after a few seconds. (Tested with the laptop in the port replicator and
an external display connected via the DP port.)

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

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  New

Bug description:
  Occasionally, the internal laptop display goes black for a few
  seconds, then comes back to life. The external display stays on. It
  looks as if power management were kicking in by error but affecting
  only the internal display.

  When I’m working with the external display, I need to move the mouse
  into the area managed by the internal display to wake it up again;
  else it seems to remain black (though I haven’t tested that behavior
  thoroughly).

  Most tests with the external display were made with the port
  replicator and an external display plugged into one of the DP ports
  via a DP–DVI adapter. I cannot tell for sure what the behavior is with
  the external display plugged directly into the laptop.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+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 1715749] [NEW] Intermittent black screen on HP EliteBook 840 G1

2017-09-07 Thread Michael von Glasow
Public bug reported:

Occasionally, the internal laptop display goes black for a few seconds,
then comes back to life. The external display stays on. It looks as if
power management were kicking in by error but affecting only the
internal display.

When I’m working with the external display, I need to move the mouse
into the area managed by the internal display to wake it up again; else
it seems to remain black (though I haven’t tested that behavior
thoroughly).

Most tests with the external display were made with the port replicator
and an external display plugged into one of the DP ports via a DP–DVI
adapter. I cannot tell for sure what the behavior is with the external
display plugged directly into the laptop.

The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
finally moved to the EliteBook 840 G1.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Sep  8 00:53:24 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-12-09 (1002 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  New

Bug description:
  Occasionally, the internal laptop display goes black for a few
  seconds, then comes back to life. The external display stays on. It
  looks as if power management were kicking in by error but affecting
  only the internal display.

  When I’m working with the external display, I need to move the mouse
  into the area managed by the internal display to wake it up again;
  else it seems to remain black (though I haven’t tested that behavior
  thoroughly).

  Most tests with the external display were made with the port
  replicator and an external display plugged into one of the DP ports
  via a DP–DVI adapter. I cannot tell for sure what the behavior is with
  the external display plugged directly into the laptop.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+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 1715582] Re: deja-dup fails to backup

2017-09-07 Thread Michael Terry
OK, I'm not entirely sure why you hit this situation, but I can see in
the code why you might end up with that error.  So I've committed a fix
to avoid ending up there, and added code to print the error to the
console, so next time this happens we can have more of a clue.

https://git.launchpad.net/deja-
dup/commit/?h=36=9954525d56b2b604114cbc7fbf15d99983edfacb

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

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

Title:
  deja-dup fails to backup

Status in deja-dup package in Ubuntu:
  Fix Committed

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  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/1715582/+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 1050509] Re: Duplicity doesn't handle non-utf8 filenames well

2017-09-06 Thread Michael Terry
To be clear, this bug is about filenames that are NOT valid utf8.  Most
user errors in bugs and comments here are about filenames that are utf8
-- but not ascii -- and duplicity having problems with that.  But this
bug is for those filenames that are truly bizarre.

That said, the fix for both is similar.  Ever since adding gettext
support, we've used utility functions in util.py to convert between byte
and unicode strings.  Those functions pass the 'replace' option to
decode/encode while they're at it, which gracefully handles non-utf8
characters.  As we fix normal utf8 conversion errors, by using those
utility functions we also make the non-utf8 cases better.

So where are we today?  We've fixed a bunch of UnicodeDecodeErrors
throughout duplicity [1].  I don't think we've fixed 100% of them, but I
do think we've hit the majority of the use cases by now.

This generic bug might not be super useful anymore.  It might be better
to close this?  And keep using separate bugs for each specific instance
of a decode error.

[1]
https://bugs.launchpad.net/duplicity/+bugs?field.searchtext=ordinal+not+in+range=-status=Search%3Alist=NEW%3Alist=CONFIRMED%3Alist=TRIAGED%3Alist=INPROGRESS%3Alist=FIXCOMMITTED%3Alist=FIXRELEASED%3Alist=INCOMPLETE_WITH_RESPONSE%3Alist=INCOMPLETE_WITHOUT_RESPONSE

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

Title:
  Duplicity doesn't handle non-utf8 filenames well

Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  This is a break-out bug from bug 989496.

  If the user is using a filename encoding that is non-utf8, duplicity
  doesn't have special support for that.  It mixes use of filenames for
  both printing/logging and for opening.  All print/log uses should use
  a utf8 version of the filename.  All actual file operations should use
  the native encoding.

  This will likely involve a new field like pretty_name or something on
  ROPath.

  I suspect the number of users with non-utf8 systems is low.  So I'm
  setting as low priority.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1050509/+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 1276327] Re: deja-dup/duplicity fails gpg encrypted backup in trusty

2017-09-06 Thread Michael Terry
** Also affects: duplicity
   Importance: Undecided
   Status: New

** Changed in: duplicity
   Status: New => Fix Released

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

Title:
  deja-dup/duplicity fails gpg encrypted backup in trusty

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released

Bug description:
  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1489, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1483, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1332, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1414, in do_backup
  globals.gpg_profile.passphrase = get_passphrase(1, action)
File "/usr/bin/duplicity", line 168, in get_passphrase
  pass1 = getpass.getpass(_("GnuPG passphrase:")+" ")
File "/usr/lib/python2.7/getpass.py", line 83, in unix_getpass
  passwd = fallback_getpass(prompt, stream)
File "/usr/lib/python2.7/getpass.py", line 118, in fallback_getpass
  return _raw_input(prompt, stream)
File "/usr/lib/python2.7/getpass.py", line 128, in _raw_input
  prompt = str(prompt)
  UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 
10: ordinal not in range(128)

  1) lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  2) apt-cache policy duplicity
  duplicity:
Installed: 0.6.23-0ubuntu1
Candidate: 0.6.23-0ubuntu1
Version table:
   *** 0.6.23-0ubuntu1 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3) I expected the scheduled backups to succeed as the used to do in the past.
  4) The backup aborts with the error message listed above

  Additonally deja-dup-preferences vanished from System Preferences, but
  that should perhaps be logged as a different bug.

  Downgrading deja-dup/duplicity to the saucy versions restores
  functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1276327/+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

2017-09-06 Thread Michael Terry
The workaround landed in artful. I'm keeping a look out for any reports
of this bug still happening there.

-- 
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 1683145] Re: Mouse pointer speed setting has no effect

2017-09-03 Thread Michael MacEachern
This is affecting me even on Kubuntu 17.04, on a fresh install.

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

Title:
  Mouse pointer speed setting has no effect

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  In Setting, Mouse & Touchpad, changing the Mouse pointer speed has no effect 
after upgrading from 16.10 to 17.04.
  Same with Touchpad pointer speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr 16 16:21:26 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-06-21 (664 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1683145/+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 1641423] Re: Backup fails with message: 'Failed to execute child process "duplicity" (No such file or directory)' or 'No module named gi.repository': missing deja-dup-backend-g

2017-08-31 Thread Michael Terry
Yeah this was improved in 17.10. This bug still affects 17.04.

As a workaround, run apt install deja-dup-backend-gvfs and this should
be fixed for ya.

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

Title:
  Backup fails with message: 'Failed to execute child process
  "duplicity" (No such file or directory)' or 'No module named
  gi.repository': missing deja-dup-backend-gvfs, duplicity, and/or
  python-gi packages

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

Bug description:
  Ubantu 16.04

  Cant find out version of backup but it was loaded with distro 16.04
  and all software is up to date so it should be latest

  I dont know how to get the information
   in 3 & 4

  from the error maessage:
  Failed to execute child process "duplicity" (No such file or directory)
  It looks like a required file is missing

  I tried removing backup and reinstalling but it still fails with the
  same error

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1641423/+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

2017-08-26 Thread Michael Terry
Sigh, I've never been able to reproduce this.  Despite several people
saying it's connected to Chrome Remote Desktop, we also have several
reports of it happening without that involved.

I'm currently testing a workaround (committed to trunk) that sets a
memory limit on the monitor process, as a quick and dirty hack to
alleviate the effects of this bug.  If anyone wants to test on their
machine, you can edit /etc/xdg/autostart/deja-dup-monitor.desktop to
change its Exec line to:

Exec=bash -c "ulimit -v 100; 
/usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor"
X-GNOME-AutoRestart=true

(change the x86_64-linux-gnu part as needed)

I'd welcome reports of success or failure with this.

-- 
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 1302416] Re: deja-dup monitor was taking 6GB of memory

2017-08-26 Thread Michael Terry
** Also affects: deja-dup
   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/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 908791] Re: Backing up to ftp or sftp, creates "sftp:" or "ftp:" folder in Deja-Dup launch place

2017-08-26 Thread Michael Terry
Ah... running as root.  Yeah, most of deja-dup won't work when running
as root.

Perhaps we should error out in that case...

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

Title:
  Backing up to ftp or sftp, creates "sftp:" or "ftp:" folder in Deja-
  Dup launch place

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

Bug description:
  1. I'm using up to date ArchLinux, x86_64.
  2.  20.2-2
  3. org.gnome.DejaDup backend 'file'
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD', '/home/ernestas/dw', 
'/home/ernestas/Muzika', '/home/ernestas/books']
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup last-backup '2011-12-26T15:08:43.807421Z'
  org.gnome.DejaDup last-restore ''
  org.gnome.DejaDup last-run '2011-12-26T15:08:43.807421Z'
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup periodic-period 7
  org.gnome.DejaDup prompt-check ''
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup welcomed true
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File path 
'ftp://ernes...@home.versme.net:21/home/ernestas/backup/'
  org.gnome.DejaDup.File relpath @ay []
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.Rackspace container 'pluto'
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'pluto'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.U1 folder '/deja-dup/pluto'

  **

  Let's say I launch Deja-Dup in home directory /home/ernestas. Then it creates 
/home/ernestas/sftp:/ or /home/ernestas/ftp:/ directories at which it places 
backups.
  What dependencies is Deja-Dup missing and why isn't it displaying any errors 
about that?

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/908791/+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 1711953] Re: deja-dup-monitor crashed with signal 5 in g_settings_get_value()

2017-08-24 Thread Michael Terry
*** This bug is a duplicate of bug 1712757 ***
https://bugs.launchpad.net/bugs/1712757

** This bug has been marked a duplicate of bug 1712757
   
/usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor:5:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_value:g_settings_get_boolean:deja_dup_migrate_settings

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

Title:
  deja-dup-monitor crashed with signal 5 in g_settings_get_value()

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  This error was reported soon after start-up, when executing the
  command apt-get upgrade.  The system version is

  "Linux richard-desktop 4.11.0-13-generic #19-Ubuntu SMP Thu Aug 3
  15:14:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  The error occurred on date "Sun 20 Aug 21:30:32 BST 2017"

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.4-0ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Aug 20 21:18:29 2017
  ExecutablePath: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-03-30 (143 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor
  Signal: 5
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   deja_dup_migrate_settings () from 
/usr/lib/x86_64-linux-gnu/deja-dup/libdeja.so
  Title: deja-dup-monitor crashed with signal 5 in g_settings_get_value()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1711953/+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 1712757] Re: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor:5:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_value:g_settings_get_boolean:deja_dup_m

2017-08-24 Thread Michael Terry
So my best guess... is that deja-dup-monitor is being run (it starts
120s after login) while an upgrade is happening, before the gschemas are
re-compiled but after the binaries are installed.

That seems like a small window...  But certainly possible.  I imagine it
won't happen during a release upgrade, thankfully.

I'm not sure whether this is worth trying to work around?

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

** Changed in: deja-dup (Ubuntu)
   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/1712757

Title:
  /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-
  
monitor:5:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_value:g_settings_get_boolean:deja_dup_migrate_settings

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
deja-dup.  This problem was most recently seen with package version 
35.5-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/5709e9321dbca261fbe04fa7c3be988a53d3f4da 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1712757/+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 1712714] Re: deja-dup autopkgtest failure with meson 0.42

2017-08-24 Thread Michael Terry
** Changed in: deja-dup (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  deja-dup autopkgtest failure with meson 0.42

Status in deja-dup package in Ubuntu:
  New

Bug description:
  deja-dup's autopkgtest now fails with meson 0.42.

  
  autopkgtest [01:28:42]: test check: ---]
  checkFAIL stderr: Warning: This executable is deprecated. Use 
"meson test" instead.autopkgtest [01:28:46]: test check:  - - - - - - - - - - 
results - - - - - - - - - -
  

  http://autopkgtest.ubuntu.com/packages/d/deja-dup/artful/armhf

  Basically change "mesontest" to "meson test" in debian/tests/check

  I'm setting the importance to High because this autopkgtest regression
  prevents other packages from migrating to artful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1712714/+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 1368640] Re: When backup system, need to click cancel button twice to close Encryption Password Needed page.

2017-08-22 Thread Michael Terry
** 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/1368640

Title:
  When backup system, need to click cancel button twice to close
  Encryption Password Needed page.

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

Bug description:
  When backup system, need to click cancel button twice to close
  Encryption Password Needed page. You must backuped your system with
  encryption before.

  Steps:
  1. Enter into System settings-->Backup,
  2. Click back up now, backup the system with encryption
  3. Click the back up now button again,
  4. Click cancel button in Encryption Password Needed page
  -->Failed. Need to click cancel button twice to close Encryption Password 
Needed page.

  Configuration:
  PC: Dell Vostro
  OS: Ubuntu kylin 14.10 daily 0912

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1368640/+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 1623835] Re: Scrolled Windows in backup/restore progress are too small to read

2017-08-22 Thread Michael Terry
** Changed in: deja-dup (Ubuntu)
   Status: In Progress => Fix Released

** No longer affects: deja-dup (Ubuntu Yakkety)

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

Title:
  Scrolled Windows in backup/restore progress are too small to read

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

Bug description:
  [Impact]

* Expanding the scrolled windows for backup or restore progress in
  deja-dup are just one line high, making them unreadable.

  [ Test Case ]

* Install Ubuntu 16.10 final or 17.04 daily.
* Open deja-dup and configure a backup location.
* Start a backup and the Details during a running backup, you'll see the 
scrolled window is just one line high.

  After installing the patched daja-dup package following the same steps
  will result in the backup/restore progress scrolled windows defaulting
  to several lines of readable output.

  [ Regression Potential ]

* None.

  [ Other Info ]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: deja-dup 34.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 15 09:21:28 2016
  InstallationDate: Installed on 2016-07-25 (51 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to yakkety on 2016-09-06 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1623835/+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 1266025] Re: backup folder in ~/.cache/deja-dup/tmp does not exist

2017-08-22 Thread Michael Terry
*** This bug is a duplicate of bug 1318833 ***
https://bugs.launchpad.net/bugs/1318833

** This bug has been marked a duplicate of bug 1318833
   "No such file or directory" during backup

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

Title:
  backup folder in ~/.cache/deja-dup/tmp does not exist

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Déjà-dup backups fail with an error message "The backup folder
  »/home/username/.cache/deja-dup/tmp/duplicity-il-Au69-tempdir/mktemp-
  51Sz0x-3« does not exist.". This folder does indeed not exist. When
  clicking the close button, deja-dup aborted.

  For weeks not a single deja-dup backup completed successfully due to
  various reported bugs. When I attempt to restore files, I see that
  files have been backuped, but I cannot be sure whether the files are
  complete. This makes the backups absolutely useless because I have no
  guarantee that I can restore all the files.

  I would strongly recommend to review _all_ error messages that deja-
  dup might produce and allow users to continue an interrupted backup
  process when the issue has been resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1266025/+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 1397118] Re: Deja Dup finishes with mysterious message

2017-08-22 Thread Michael Terry
*** This bug is a duplicate of bug 1570204 ***
https://bugs.launchpad.net/bugs/1570204

** 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/1397118

Title:
  Deja Dup finishes with mysterious message

Status in deja-dup package in Ubuntu:
  New

Bug description:
  After an automated backup I'm left with this message:

Backup Finished

Could not back up the following files. Please make sure you are able
  to open them.

/home//.cache/dconf
/home//.gvfs

  The beginning of the message implies that the backup job finished but
  the text after that leaves uncertainty. It's not clear if I am
  supposed to follow up with an action.

  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 27 20:55:56 2014
  InstallationDate: Installed on 2014-09-13 (74 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140308)
  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/1397118/+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

2017-08-22 Thread Michael Terry
** Also affects: deja-dup
   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/1570204

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

Status in Déjà Dup:
  New
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 1368640] Re: When backup system, need to click cancel button twice to close Encryption Password Needed page.

2017-08-22 Thread Michael Terry
Thanks for the bug!  This should be fixed in master now.

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

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

Title:
  When backup system, need to click cancel button twice to close
  Encryption Password Needed page.

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

Bug description:
  When backup system, need to click cancel button twice to close
  Encryption Password Needed page. You must backuped your system with
  encryption before.

  Steps:
  1. Enter into System settings-->Backup,
  2. Click back up now, backup the system with encryption
  3. Click the back up now button again,
  4. Click cancel button in Encryption Password Needed page
  -->Failed. Need to click cancel button twice to close Encryption Password 
Needed page.

  Configuration:
  PC: Dell Vostro
  OS: Ubuntu kylin 14.10 daily 0912

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1368640/+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 1019293] Re: "gpg: can't handle text lines longer than 19995 characters" error when backing up

2017-08-22 Thread Michael Terry
** Summary changed:

- deja-jup gets into ask password loop when backing up some data
+ "gpg: can't handle text lines longer than 19995 characters" error when 
backing up

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

Title:
  "gpg: can't handle text lines longer than 19995 characters" error when
  backing up

Status in deja-dup package in Ubuntu:
  New

Bug description:
  When I run deja-dup, and it encounters some data* it asks for the
  password to be reentered, and when you do that, it tries again, and
  gets in the same loop, over and over until you cancel. Nothing ends up
  being backed up.

  * e.g. my gpg public keyring, but when I exclude .gnupg, it has what
  may be the same problem on something else too, so I think that's
  coincidence.

  The last part of the log is at the bottom of this, and I'll attach the
  final 1000 lines. I don't think this is a duplicate of bug #883742, as
  the source of the error is quite different.

  DUPLICITY: DEBUG 1
  DUPLICITY: . Selecting /home/robin/.gnupg/gpg.conf

  DUPLICITY: DEBUG 1
  DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'gpg.conf') and None

  DUPLICITY: DEBUG 1
  DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'gpg.conf') 
/home/robin/.gnupg/gpg.conf reg) and None

  DUPLICITY: INFO 4 'home/robin/.gnupg/gpg.conf'
  DUPLICITY: . A home/robin/.gnupg/gpg.conf

  DUPLICITY: DEBUG 1
  DUPLICITY: . Selecting /home/robin/.gnupg/gpg.conf~

  DUPLICITY: DEBUG 1
  DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'gpg.conf~') and None

  DUPLICITY: DEBUG 1
  DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'gpg.conf~') 
/home/robin/.gnupg/gpg.conf~ reg) and None

  DUPLICITY: INFO 4 'home/robin/.gnupg/gpg.conf~'
  DUPLICITY: . A home/robin/.gnupg/gpg.conf~

  DUPLICITY: DEBUG 1
  DUPLICITY: . Selecting /home/robin/.gnupg/pubring.gpg

  DUPLICITY: DEBUG 1
  DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'pubring.gpg') and None

  DUPLICITY: DEBUG 1
  DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'pubring.gpg') 
/home/robin/.gnupg/pubring.gpg reg) and None

  DUPLICITY: INFO 4 'home/robin/.gnupg/pubring.gpg'
  DUPLICITY: . A home/robin/.gnupg/pubring.gpg

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-_XHa0A-tempdir/mkstemp-DS0LuL-1

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-_XHa0A-tempdir/mktemp-w2gx_c-2

  DUPLICITY: INFO 1
  DUPLICITY: . GPG error detail: Traceback (most recent call last):
  DUPLICITY: .   File "/usr/bin/duplicity", line 1403, in 
  DUPLICITY: . with_tempdir(main)
  DUPLICITY: .   File "/usr/bin/duplicity", line 1396, in with_tempdir
  DUPLICITY: . fn()
  DUPLICITY: .   File "/usr/bin/duplicity", line 1366, in main
  DUPLICITY: . full_backup(col_stats)
  DUPLICITY: .   File "/usr/bin/duplicity", line 500, in full_backup
  DUPLICITY: . globals.backend)
  DUPLICITY: .   File "/usr/bin/duplicity", line 378, in write_multivol
  DUPLICITY: . globals.gpg_profile, globals.volsize)
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 
332, in GPGWriteFile
  DUPLICITY: . file.close()
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 
221, in close
  DUPLICITY: . self.gpg_failed()
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 
206, in gpg_failed
  DUPLICITY: . raise GPGError, msg
  DUPLICITY: . GPGError: GPG Failed, see log below:
  DUPLICITY: . = Begin GnuPG log =
  DUPLICITY: . gpg: can't handle text lines longer than 19995 characters
  DUPLICITY: . = End GnuPG log =
  DUPLICITY: . 
  DUPLICITY: . 

  DUPLICITY: ERROR 31 GPGError
  DUPLICITY: . GPGError: GPG Failed, see log below:
  DUPLICITY: . = Begin GnuPG log =
  DUPLICITY: . gpg: can't handle text lines longer than 19995 characters
  DUPLICITY: . = End GnuPG log =
  DUPLICITY: .

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Fri Jun 29 14:04:01 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to precise on 2012-05-08 (52 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1019293/+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 1270592] Re: backup restore test not working

2017-08-22 Thread Michael Terry
*** This bug is a duplicate of bug 918489 ***
https://bugs.launchpad.net/bugs/918489

After some testing, I think I know what could cause this (now very old)
bug. There was a bug in deja-dup/duplicity that allowed for an
accidental change in password when making the occasional full backup
checkpoint (bug 918489, fixed in deja-dup 34.3).

Here's how this would be reproduced, using deja-dup <= 34.2:
- Create a new backup with password 'a'
- Keep backing up until deja-dup decides to make a new backup. Then either have 
a different password saved in gnome-keyring or enter a different password when 
it prompts. Say, 'b'
- Now you have two backup chains with different passwords, but deja-dup will 
keep adding new backups.
- Until either your cache gets blown away or deja-dup decides to do its 
every-two-months backup-validation check. (Or heaven forbid, your hard drive 
gets blown away and you need to restore.)
- When either happens, duplicity will try to download the encrypted manifest 
files for all the backups and deja-dup will prompt you for the decryption 
password.
- If you enter 'a', it will choke on your second backup and show the password 
prompt again. If you enter 'b' it will choke on the first. Thus you get eternal 
backup prompts.

The only way to recover is to blow away older backups (or the whole
thing) and start over. If you were trying to restore, your files can be
manually recovered using duplicity though.

Anyway. That's my research into what this bug was likely about. I'll
mark it as a dup of bug 918489 (which has been fixed for a while).

** This bug has been marked a duplicate of bug 918489
   duplicity allows bad passphrase on full backup if archive cache exists

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

Title:
  backup restore test not working

Status in deja-dup package in Ubuntu:
  New

Bug description:
  I'm on 13.10 with an encrypted drive - every now and then, the backup
  program supplies apop-up asking to test the restore function (see
  http://imagizer.imageshack.us/v2/800x600q90/843/ot9x.png for an image
  of the pop-up)...

  It never seems to be successful - I have entered the excryption
  password that I use to access the drive and it never seems happy - can
  anyone tell me what's wrong?

  Thanks,
  Tom

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1270592/+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 1219187] Re: deja-dup cannot decrypt my backup any more, GPG reports "bad session key"

2017-08-22 Thread Michael Terry
*** This bug is a duplicate of bug 918489 ***
https://bugs.launchpad.net/bugs/918489

After some testing, I think I know what could cause this (now very old)
bug.  There was a bug in deja-dup/duplicity that allowed for an
accidental change in password when making the occasional full backup
checkpoint (bug 918489, fixed in deja-dup 34.3).

Here's how this would be reproduced, using deja-dup <= 34.2:
- Create a new backup with password 'a'
- Keep backing up until deja-dup decides to make a new backup.  Then either 
have a different password saved in gnome-keyring or enter a different password 
when it prompts.  Say, 'b'
- Now you have two backup chains with different passwords, but deja-dup will 
keep adding new backups.
- Until either your cache gets blown away or deja-dup decides to do its 
every-two-months backup-validation check.  (Or heaven forbid, your hard drive 
gets blown away and you need to restore.)
- When either happens, duplicity will try to download the encrypted manifest 
files for all the backups and deja-dup will prompt you for the decryption 
password.
- If you enter 'a', it will choke on your second backup and show the password 
prompt again.  If you enter 'b' it will choke on the first.  Thus you get 
eternal backup prompts.

The only way to recover is to blow away older backups (or the whole
thing) and start over.  If you were trying to restore, your files can be
manually recovered using duplicity though.

Anyway.  That's my research into what this bug was likely about.  I'll
mark it as a dup of bug 918489.

** This bug has been marked a duplicate of bug 918489
   duplicity allows bad passphrase on full backup if archive cache exists

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

Title:
  deja-dup cannot decrypt my backup any more, GPG reports "bad session
  key"

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Deja-dup cannot decrypt my backup any more. This seems to be a
  duplicate of https://bugzilla.novell.com/show_bug.cgi?id=821767.

  This is the error message:
  Import of duplicity.backends.sshbackend Failed: No module named paramiko
  Synchronizing remote metadata to local cache...
  GnuPG passphrase: 
  Copying duplicity-full-signatures.20130828T120049Z.sigtar.gpg to local cache.
  GPGError: GPG Failed, see log below:
  = Begin GnuPG log =
  gpg: CAST5 encrypted data
  gpg: encrypted with 1 passphrase
  gpg: decryption failed: Bad session key
  = End GnuPG log =

  I am *sure* my password is correct. And I have also verified the keyboard 
mapping did not change. I also unset GPG_AGENT_INFO and killed gpg-agent (just 
in case).
  So what can this be? Is it in fact an incorrect password or has something 
else gone bad?

  GPG 1.4.11, duplicity 0.6.18, deja-dup 22.0

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17
  Uname: Linux 3.5.0-39-generic i686
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: i386
  Date: Sat Aug 31 10:35:35 2013
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130214)
  MarkForUpload: True
  ProcEnviron:
   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/ubuntu/+source/deja-dup/+bug/1219187/+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 1577109] Re: deja-dup does not complain if SMB target is not available

2017-08-21 Thread Michael Terry
We should already be notifying the user in this case. Something like
"Scheduled backup delayed. Backup will begin when the network is
connected."

Sounds like that didn't work in this case.

The desktop environment was Unity I'm guessing?

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

Title:
  deja-dup does not complain if SMB target is not available

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Half a year ago I upgraded our NAS with a different server and
  subsequently changed all our Linux desktops to back up to the new
  destination. Except one which I forgot. Since deja-dup never
  complained on this machine, the respective user also didn't complain
  and simply assumed everything was OK. So we lost half a year of backup
  security; luckily, the machine did not die.

  Deja-dup should show an error message if the SMB target is not
  available at backup time - it did not do this here, it just failed
  silently. This is OK if one backup fails because the network is out,
  but if multiple backups (or a repeated attempt) fail it should
  definitely complain.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-58.64~14.04.1-generic 3.19.8-ckt16
  Uname: Linux 3.19.0-58-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May  1 09:50:19 2016
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   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/ubuntu/+source/deja-dup/+bug/1577109/+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 1450429] Re: Backups configuration duplicated folders

2017-08-21 Thread Michael Terry
Can someone affected please provide the following? Thank you!

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

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

Title:
  Backups configuration duplicated folders

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04
  unity-control-center 15.04.0+15.04.20150410-0ubuntu1

  Just a small UI bug.
  I'm using the Backups UI from Settings/System to backup files to a network 
share.
  I've removed the ~/Downloads folder from the 'Folders to ignore' section.
  When I open the Backups UI now for the first time, the folders in 'Folders to 
save' and 'Folders to ignore' are correct.
  But when I go back to All Settings and then open Backups again, each folder 
in these sections will be shown twice.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 13:03:05 2015
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-02-11 (77 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to vivid on 2015-04-30 (0 days ago)
  usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1450429/+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 1599662] Re: Backups Folders to ignore list shows duplicates

2017-08-21 Thread Michael Terry
*** This bug is a duplicate of bug 1450429 ***
https://bugs.launchpad.net/bugs/1450429

** This bug has been marked a duplicate of bug 1450429
   Backups configuration duplicated folders

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

Title:
  Backups Folders to ignore list shows duplicates

Status in deja-dup package in Ubuntu:
  New

Bug description:
  The System Settings -> Backups -> Folders to ignore list sometimes
  shows duplicate entries. Sometimes it shows the list as it should.
  Navigating from the Folders to ignore list back to All Settings, and
  then back to Backups,Folders to ignore produces inconsistent results.

  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:26:49 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/deja-dup/+bug/1599662/+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 1368640] Re: When backup system, need to click cancel button twice to close Encryption Password Needed page.

2017-08-21 Thread Michael Terry
** Also affects: deja-dup
   Importance: Undecided
   Status: New

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

** 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/1368640

Title:
  When backup system, need to click cancel button twice to close
  Encryption Password Needed page.

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

Bug description:
  When backup system, need to click cancel button twice to close
  Encryption Password Needed page. You must backuped your system with
  encryption before.

  Steps:
  1. Enter into System settings-->Backup,
  2. Click back up now, backup the system with encryption
  3. Click the back up now button again,
  4. Click cancel button in Encryption Password Needed page
  -->Failed. Need to click cancel button twice to close Encryption Password 
Needed page.

  Configuration:
  PC: Dell Vostro
  OS: Ubuntu kylin 14.10 daily 0912

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1368640/+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 908791] Re: Backing up to ftp or sftp, creates "sftp:" or "ftp:" folder in Deja-Dup launch place

2017-08-21 Thread Michael Terry
I believe this is fixed in artful. I think the problem was gvfs-backends
not being installed, so glib thought an sftp URI was just a relative
path. But we install gvfs-backends for you if it is missing now.

** 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/908791

Title:
  Backing up to ftp or sftp, creates "sftp:" or "ftp:" folder in Deja-
  Dup launch place

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

Bug description:
  1. I'm using up to date ArchLinux, x86_64.
  2.  20.2-2
  3. org.gnome.DejaDup backend 'file'
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD', '/home/ernestas/dw', 
'/home/ernestas/Muzika', '/home/ernestas/books']
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup last-backup '2011-12-26T15:08:43.807421Z'
  org.gnome.DejaDup last-restore ''
  org.gnome.DejaDup last-run '2011-12-26T15:08:43.807421Z'
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup periodic-period 7
  org.gnome.DejaDup prompt-check ''
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup welcomed true
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File path 
'ftp://ernes...@home.versme.net:21/home/ernestas/backup/'
  org.gnome.DejaDup.File relpath @ay []
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.Rackspace container 'pluto'
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'pluto'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.U1 folder '/deja-dup/pluto'

  **

  Let's say I launch Deja-Dup in home directory /home/ernestas. Then it creates 
/home/ernestas/sftp:/ or /home/ernestas/ftp:/ directories at which it places 
backups.
  What dependencies is Deja-Dup missing and why isn't it displaying any errors 
about that?

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/908791/+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 1437514] Re: Feature Request Déjà Dup Exit Prompt

2017-08-21 Thread Michael Terry
Yes, deja-dup resumes where it left off after it is interrupted. This is
why we don't warn when closing or inhibit logging out etc.

I guess I'll close this. I don't think it's needed.

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

** Changed in: deja-dup
   Status: Triaged => 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/1437514

Title:
  Feature Request Déjà Dup Exit Prompt

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

Bug description:
  I have raged at this and this is probably a simple request, but when
  accidentally exiting said backup program after it was running for TWO
  HOURS, I wish it had prompted me so I could deny. Please add this
  feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1437514/+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 1662824] Re: remove deja-dup from ubuntu default install

2017-08-21 Thread Michael Terry
Hello! I'm the upstream author of deja-dup. I understand your
frustration, but I think deja-dup does more good than harm.

I'm going to close this bug, because this isn't the best venue for such
a discussion. If you are serious about advocating for deja-dup to be
removed, try your case at ubuntu-desk...@lists.ubuntu.com.

** 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/1662824

Title:
  remove deja-dup from ubuntu default install

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  deja-dup currently has many open bugs, comes pre-installed missing
  many components/dependencies and is generally slow and unreliable.

  Not having a backup solution by default would be more desirable than
  this package.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: deja-dup 34.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb  8 10:16:15 2017
  InstallationDate: Installed on 2017-02-07 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.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/1662824/+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 1348193] Re: Duplicity fails during backup in with_tempdir()

2017-08-21 Thread Michael Terry
*** This bug is a duplicate of bug 1318833 ***
https://bugs.launchpad.net/bugs/1318833

** This bug has been marked a duplicate of bug 1318833
   "No such file or directory" during backup

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

Title:
  Duplicity fails during backup in with_tempdir()

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

Bug description:
  Description:  Ubuntu Utopic Unicorn (development branch)
  Release:  14.10

  duplicity:
    Installed: 0.6.23-1ubuntu5
    Candidate: 0.6.23-1ubuntu5
    Version table:
   *** 0.6.23-1ubuntu5 0
  500 http://au.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

  During a full system backup, using the deja-dup, the process gets about 
half-way through and then stops with the following error:
  Backup Failed
  Failed with an unknown error.

  Traceback (most recent call last):
    File "/usr/bin/duplicity", line 1494, in 
  with_tempdir(main)
    File "/usr/bin/duplicity", line 1488, in with_tempdir
  fn()
    File "/usr/bin/duplicity", line 1337, in main
  do_backup(action)
    File "/usr/bin/duplicity", line 1458, in do_backup
  full_backup(col_stats)
    File "/usr/bin/duplicity", line 542, in full_backup
  globals.backend)
    File "/usr/bin/duplicity", line 403, in write_multivol
  globals.gpg_profile, globals.volsize)
    File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 324, in 
GPGWriteFile
  file = GPGFile(True, path.Path(filename), profile)
    File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 105, in 
__init__
  self.logger_fp = tempfile.TemporaryFile( dir=tempdir.default().dir() )
    File "/usr/lib/python2.7/tempfile.py", line 497, in TemporaryFile
  (fd, name) = _mkstemp_inner(dir, prefix, suffix, flags)
    File "/usr/lib/python2.7/tempfile.py", line 239, in _mkstemp_inner
  fd = _os.open(file, flags, 0600)
  OSError: [Errno 2] No such file or directory: 
'/tmp/duplicity-DEgmK7-tempdir/tmplcuF1s'

  The referred to directory does not exist, however, the following one does 
exist:
  /tmp/duplicity-l4bYos-tempdir/

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1348193/+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 1267590] Re: Automatic Backup after fresh install of trusty fails: no such file or directory

2017-08-21 Thread Michael Terry
*** This bug is a duplicate of bug 1318833 ***
https://bugs.launchpad.net/bugs/1318833

** This bug has been marked a duplicate of bug 1318833
   "No such file or directory" during backup

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

Title:
  Automatic Backup after fresh install of trusty fails: no such file or
  directory

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  While testing da daily snapshot to verfy a different issue I
  configured deja-dup to add the typical load to my system.

  I configured an SSH upload.

  deja-dup failed with:
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1473, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1466, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1436, in main
  full_backup(col_stats)
File "/usr/bin/duplicity", line 541, in full_backup
  globals.backend)
File "/usr/bin/duplicity", line 402, in write_multivol
  globals.gpg_profile, globals.volsize)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 324, in 
GPGWriteFile
  file = GPGFile(True, path.Path(filename), profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 105, in 
__init__
  self.logger_fp = tempfile.TemporaryFile( dir=tempdir.default().dir() )
File "/usr/lib/python2.7/tempfile.py", line 493, in TemporaryFile
  (fd, name) = _mkstemp_inner(dir, prefix, suffix, flags)
File "/usr/lib/python2.7/tempfile.py", line 239, in _mkstemp_inner
  fd = _os.open(file, flags, 0600)
  OSError: [Errno 2] No such file or directory: 
'/tmp/duplicity-dH5tyj-tempdir/tmpTVOITr'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 29.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
  Uname: Linux 3.13.0-1-generic x86_64
  ApportVersion: 2.12.7-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan  9 21:36:37 2014
  InstallationDate: Installed on 2014-01-09 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140109)
  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/1267590/+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 1318833] Re: "No such file or directory" during backup

2017-08-21 Thread Michael Terry
** Summary changed:

- duplicity backup fails in 14.04
+ "No such file or directory" during backup

** Also affects: duplicity
   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/1318833

Title:
  "No such file or directory" during backup

Status in Duplicity:
  New
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  I have an automatic backup system setup running through a script in anacron. 
After upgrading to 14.04 duplicity fails with the following error (when run 
from termina)
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1494, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1488, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1337, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1458, in do_backup
  full_backup(col_stats)
File "/usr/bin/duplicity", line 542, in full_backup
  globals.backend)
File "/usr/bin/duplicity", line 403, in write_multivol
  globals.gpg_profile, globals.volsize)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 327, in 
GPGWriteFile
  bytes_to_go = data_size - get_current_size()
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 320, in 
get_current_size
  return os.stat(filename).st_size
  OSError: [Errno 2] No such file or directory: 
'/tmp/duplicity-Hy90rz-tempdir/mktemp-SB_XJ9-2'

  I am running 14.04 fully updated and 
  duplicity:
Installed: 0.6.23-1ubuntu4
Candidate: 0.6.23-1ubuntu4
Version table:
   *** 0.6.23-1ubuntu4 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Any help?

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1318833/+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 1453114] Re: Backup stops in the middle with a python traceback

2017-08-21 Thread Michael Terry
*** This bug is a duplicate of bug 1318833 ***
https://bugs.launchpad.net/bugs/1318833

** This bug has been marked a duplicate of bug 1318833
   "No such file or directory" during backup

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

Title:
  Backup stops in the middle with a python traceback

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Backup Failed:
  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1494, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1488, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1337, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1458, in do_backup
  full_backup(col_stats)
File "/usr/bin/duplicity", line 542, in full_backup
  globals.backend)
File "/usr/bin/duplicity", line 403, in write_multivol
  globals.gpg_profile, globals.volsize)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 327, in 
GPGWriteFile
  bytes_to_go = data_size - get_current_size()
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 320, in 
get_current_size
  return os.stat(filename).st_size
  OSError: [Errno 2] No such file or directory: 
'/tmp/duplicity-x6bEln-tempdir/mktemp-3XerZ6-13'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  Date: Fri May  8 14:52:01 2015
  InstallationDate: Installed on 2014-11-05 (184 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/1453114/+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 1638510] Re: deja-dup asks to install software not from a trusted source

2017-08-21 Thread Michael Terry
It is expected that deja-dup would ask to install duplicity. Duplicity
is not preinstalled, to avoid having python2 on disk. The fact that the
packagekit dialog warns about untrusted sources makes me think you have
PPAs installed and packagekit should display that in a kinder way (as
that fedora bug suggests).

I don't think there's anything deja-dup can do here. I'll reassign to
packagekit.

** Package changed: deja-dup (Ubuntu) => packagekit (Ubuntu)

** Summary changed:

- deja-dup asks to install software not from a trusted source
+ "install software not from a trusted source" dialog could be more user 
friendly

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

Title:
  "install software not from a trusted source" dialog could be more user
  friendly

Status in packagekit package in Ubuntu:
  Confirmed

Bug description:
  deja-dup opens a dialog "The software is not from a trusted source. Do
  not install this package unless you are sure it is safe to do so"

  But I'm obviously not sure it is safe to do so!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: deja-dup 34.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov  2 09:51:06 2016
  InstallationDate: Installed on 2016-10-31 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.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/packagekit/+bug/1638510/+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 1315671] Re: Deja-dup crashes unable to restore "~/.cache/deja-dup/metadata"

2017-08-21 Thread Michael Terry
*** This bug is a duplicate of bug 1217959 ***
https://bugs.launchpad.net/bugs/1217959

Marked as dup, if this is wrong, please reopen

** This bug has been marked a duplicate of bug 1217959
   'metadata' file not found when creating backup ("Could not restore 
‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

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

Title:
  Deja-dup crashes unable to restore "~/.cache/deja-dup/metadata"

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  I received an update of dublicity yesterday and tried to do a backup
  with deja-dup which, unfortunately, is not able to finish because of
  the following error (translated from spanish):

  Can not restore '~/ .cache / deja-dup / metadata ': File not found in
  the security copy.

  I did a complete new backup without any residue on my external backup
  hard drive.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat May  3 15:11:59 2014
  InstallationDate: Installed on 2014-03-04 (60 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  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/1315671/+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"

2017-08-21 Thread Michael Terry
Reopening. I can easily believe we don't handle a symlinked cache file
well.

** Changed in: deja-dup
   Status: Expired => 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/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:
  New
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 1002198] Re: deja_dup_config_location_add_volume_full: assertion `uuid != NULL' failed

2017-08-21 Thread Michael Terry
*** This bug is a duplicate of bug 985512 ***
https://bugs.launchpad.net/bugs/985512

** This bug has been marked a duplicate of bug 985512
   support system backups (set up a backup run by root)

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

Title:
  deja_dup_config_location_add_volume_full: assertion `uuid != NULL'
  failed

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  sudo su root
  root@ubuntu-jml58z:/home/jml58z# gksu deja-dup-preferences

  ** (deja-dup-preferences:25388): CRITICAL **:
  deja_dup_config_location_add_volume_full: assertion `uuid != NULL'
  failed

  ** (deja-dup-preferences:25388): CRITICAL **:
  deja_dup_config_location_add_volume_full: assertion `uuid != NULL'
  failed

  I receive this error from a fresh install of deja-dup  in Ubuntu
  precise... 12.04

  I want to run deja-dup as root because otherwise there is no way to back up  
cetain files like /etc/sudoers an many others that have  permisions like
  -r--r- 1 root root 

  
  Thanks for any help or advice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1002198/+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)

2017-08-21 Thread Michael Terry
** 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/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 1089799] Re: Backup (Deja-Dup) tries to backup without internet connection

2017-08-21 Thread Michael Terry
This should work these days. If you still experience the isssue, please
reopen.

** Changed in: deja-dup (Ubuntu)
   Status: New => 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/1089799

Title:
  Backup (Deja-Dup) tries to backup without internet connection

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  I'm using an SSH backend to store some backups to a local server.

  When resuming the PC in the morning, deja-dup starts to backup without
  waiting for the internet connection to be up and running. As a
  consequence the "underly process terminates" or something like that.

  Since I cannot change the time of the daily backup (which I would
  prefer to be after a day's work and not before anyway) there is no way
  to work around this problem. Currently I have to start the backup
  manually which obsoletes the main purpose of an automated daily
  backup.

  Please either allow me to set the time of the backup or make the tool
  check whether the eth is ready before running the backup.

  Im running Ubuntu 12.10
  deja-dup is version 24.0-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1089799/+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 1593600] Re: No restore option after fresh install

2017-08-21 Thread Michael Terry
Installing needed packages on the fly is better these days in artful.
Thanks for the report!

** Changed in: deja-dup (Ubuntu)
   Status: New => 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/1593600

Title:
  No restore option after fresh install

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  I had Ubuntu 15.04 and decided to make a fresh install of 16.04
  instead of a double upgrade. I backed up my data (System
  Settings/Backup) on a usb drive and installed.

  After that, I tried to restore my data, but there was no "Restore..."
  option available. I then ran "deja-dup --restore" from the command
  line. It said that there is no duplicity process running, or something
  along these lines. I'm sorry, that I didn't make screenshots.

  I installed duplicity (sudo apt install duplicity) and tried again.
  This time it gave me "BackendException: Could not initialize backend:
  No module named gi.repository". I found this question
  https://answers.launchpad.net/deja-dup/+question/276745 and installed
  python-gi. After that I was able to restore my files.

  I think these packages should be installed by default.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 17 10:01:10 2016
  InstallationDate: Installed on 2016-06-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/1593600/+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 1304072] Re: deja-dup crashed with SIGSEGV in g_hash_table_lookup_node()

2017-08-21 Thread Michael Terry
Do you still experience this? I'm trying to clean up bugs and this is a
bit old with no other reports.

** Information type changed from Private to Public

** 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/1304072

Title:
  deja-dup crashed with SIGSEGV in g_hash_table_lookup_node()

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  Backup runs for a few minutes then crashes with this message.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 23:09:16 2014
  ExecutablePath: /usr/bin/deja-dup
  ProcCmdline: deja-dup --backup
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_quark_from_string () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_thaw_notify () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: deja-dup crashed with SIGSEGV in g_hash_table_lookup()
  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/ubuntu/+source/deja-dup/+bug/1304072/+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 1711953] Re: deja-dup-monitor crashed with signal 5 in g_settings_get_value()

2017-08-21 Thread Michael Terry
Is this reproducible for anyone?

** 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/1711953

Title:
  deja-dup-monitor crashed with signal 5 in g_settings_get_value()

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  This error was reported soon after start-up, when executing the
  command apt-get upgrade.  The system version is

  "Linux richard-desktop 4.11.0-13-generic #19-Ubuntu SMP Thu Aug 3
  15:14:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  The error occurred on date "Sun 20 Aug 21:30:32 BST 2017"

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.4-0ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Aug 20 21:18:29 2017
  ExecutablePath: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-03-30 (143 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor
  Signal: 5
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   deja_dup_migrate_settings () from 
/usr/lib/x86_64-linux-gnu/deja-dup/libdeja.so
  Title: deja-dup-monitor crashed with signal 5 in g_settings_get_value()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1711953/+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 1102676] Re: nautilus crashed with SIGSEGV in _int_malloc()

2017-08-21 Thread Michael Terry
Does anyone still experience this? I'm trying to clean up bugs and this
is quite old with no other reports.

** Information type changed from Private to Public

** 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/1102676

Title:
  nautilus crashed with SIGSEGV in _int_malloc()

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  Auto report 13.04

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: deja-dup 25.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  Date: Sun Jan 20 14:27:13 2013
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2011-03-05 (688 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  ProcCmdline: nautilus
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6cc3c75c96 <_int_malloc+102>:  mov
0x10(%r14),%r8
   PC (0x7f6cc3c75c96) ok
   source "0x10(%r14)" (0x0011) not located in a known VMA region (needed 
readable region)!
   destination "%r8" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f6cc3fb1740 , bytes=bytes@entry=31) 
at malloc.c:3352
   __GI___libc_malloc (bytes=31) at malloc.c:2858
   g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to raring on 2013-01-20 (1 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1102676/+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 1301609] Re: deja-dup crashed with SIGSEGV in __GI___pthread_mutex_lock()

2017-08-21 Thread Michael Terry
Does you still experience this? I'm trying to clean up bugs and this is
a bit old with no other reports.

** Information type changed from Private to Public

** 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/1301609

Title:
  deja-dup crashed with SIGSEGV in __GI___pthread_mutex_lock()

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  Deja-dup has been causing me a lot of problems over the last few days
  - many instant reboots - no errors, no messages in syslog.  This error
  came about after this evening's set of updates - so a step in the
  right direction.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
  Uname: Linux 3.13.0-21-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  2 22:03:29 2014
  ExecutablePath: /usr/bin/deja-dup
  ProcCmdline: deja-dup --backup --auto
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ffec725a414 <__GI___pthread_mutex_lock+4>:  mov
0x10(%rdi),%esi
   PC (0x7ffec725a414) ok
   source "0x10(%rdi)" (0xff60462fff5e443d) not located in a known VMA region 
(needed readable region)!
   destination "%esi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   __GI___pthread_mutex_lock (mutex=0x12a8560) at 
../nptl/pthread_mutex_lock.c:66
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_signal_handlers_destroy () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: deja-dup crashed with SIGSEGV in __GI___pthread_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1301609/+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 988370] Re: deja-dup-monitor crashed with signal 7 in g_settings_schema_source_lookup()

2017-08-21 Thread Michael Terry
Does anyone still experience this? I'm trying to clean up bugs and this
is quite old. It looks like a potential dconf issue anyway.

** Information type changed from Private to Public

** 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/988370

Title:
  deja-dup-monitor crashed with signal 7 in
  g_settings_schema_source_lookup()

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  Again, no idea how this happened -- left computer on overnight,
  unlocked today and crash dialog. No symptom, apparently.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu1
  Architecture: amd64
  Date: Wed Apr 25 12:06:02 2012
  ExecutablePath: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
  ProcCmdline: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF8
   SHELL=/bin/bash
  Signal: 7
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_schema_source_lookup () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: deja-dup-monitor crashed with signal 7 in 
g_settings_schema_source_lookup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: admin cdrom dialout floppy fuse libvirtd lp lpadmin plugdev video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/988370/+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 1576394] Re: deja-dup package dependencies in 16.04

2017-08-21 Thread Michael Terry
*** This bug is a duplicate of bug 1641423 ***
https://bugs.launchpad.net/bugs/1641423

** This bug has been marked a duplicate of bug 1641423
   Backup fails with message: 'Failed to execute child process "duplicity" (No 
such file or directory)' or 'No module named gi.repository': missing 
deja-dup-backend-gvfs, duplicity, and/or python-gi packages

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

Title:
  deja-dup package dependencies in 16.04

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  After a fresh install of Ubuntu 16.04 amd64 desktop, deja-dup did not
  work with some existing backup settings.

  I discovered duplicity was not installed... After manually installing
  "duplicity", deja-dup still did not work (reporting error
  "BackendException") and I discovered I needed to manually install
  "python-gi" as well. Once these were installed, deja-dup began to work
  as expected.

  Listing the dependencies of deja-dup (34.2-0ubuntu1) in Ubuntu 16.04
  gives the following:

  $ apt-cache depends deja-dup
  deja-dup
    Depends: libatk1.0-0
    Depends: libc6
    Depends: libdbusmenu-glib4
    Depends: libgdk-pixbuf2.0-0
    Depends: libglib2.0-0
    Depends: libgtk-3-0
    Depends: libnautilus-extension1a
    Depends: libnotify4
    Depends: libpackagekit-glib2-16
    Depends: libpango-1.0-0
    Depends: libpeas-1.0-0
    Depends: libsecret-1-0
    Depends: libunity-control-center1
    Depends: libunity9
   |Depends: dconf-gsettings-backend
    Depends: 
  dconf-gsettings-backend
    Depends: adwaita-icon-theme
    Recommends: policykit-1
  policykit-1:i386
    Suggests: deja-dup-backend-cloudfiles
    Suggests: deja-dup-backend-gvfs
    Suggests: deja-dup-backend-s3
    Suggests: duplicity

  As one of the popular backends to deja-dup, it might be helpful to
  classify duplicity not as "suggests" but a "depends" package (even
  though its nice to see other backends are also supported).

  In addition, the deja-dup package should include the "python-gi"
  package as a "depends" as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1576394/+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 981944] Re: deja-dup crashed with SIGABRT in raise() after upgrade to precise

2017-08-21 Thread Michael Terry
*** This bug is a duplicate of bug 936721 ***
https://bugs.launchpad.net/bugs/936721

** This bug is no longer a duplicate of private bug 982477
** This bug has been marked a duplicate of bug 936721
   deja-dup crashed with SIGABRT in __assert_fail_base()

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

Title:
  deja-dup crashed with SIGABRT in raise() after upgrade to precise

Status in deja-dup package in Ubuntu:
  New

Bug description:
  I was using deja-dup (it seems) for backup on my netbook.  On upgrade
  to precise, it started crashing as I logged into my session.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic i686
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: i386
  Date: Sat Apr 14 15:13:43 2012
  ExecutablePath: /usr/bin/deja-dup
  InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release 
Candidate i386 (20091020.2)
  ProcCmdline: deja-dup --prompt
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: deja-dup
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   __assert_fail () from /lib/i386-linux-gnu/libc.so.6
   _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6
  Title: deja-dup crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2012-04-14 (0 days ago)
  UserGroups: adm admin audio cdrom dialout fax fuse lpadmin plugdev sambashare 
tape video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/981944/+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 936721] Re: deja-dup crashed with SIGABRT in __assert_fail_base()

2017-08-21 Thread Michael Terry
Does anyone still experience this? I'm trying to clean up bugs and this
is quite old. It looks like a potential gtk issue anyway.

** 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/936721

Title:
  deja-dup crashed with SIGABRT in __assert_fail_base()

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  No

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 21.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic i686
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  Date: Mon Feb 20 08:27:53 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/deja-dup
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  ProcCmdline: deja-dup --prompt
  Signal: 6
  SourcePackage: deja-dup
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   __assert_fail () from /lib/i386-linux-gnu/libc.so.6
   _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6
  Title: deja-dup crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2012-02-17 (2 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/936721/+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 1016012] Re: Backup (Déjà Dup) needs to run with root permissions in Precise

2017-08-21 Thread Michael Terry
*** This bug is a duplicate of bug 985512 ***
https://bugs.launchpad.net/bugs/985512

** This bug has been marked a duplicate of bug 985512
   support system backups (set up a backup run by root)

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

Title:
  Backup (Déjà Dup) needs to run with root permissions in Precise

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Backup with Déjà Dup fails on numerous files due to r/w permissions
  for root only (600). It appears that starting with Precise (12.04)
  many systm files have changed permissions from earlier releases.
  Backup is no longer effective unless run with root permissions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1016012/+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 1264619] Re: When deja-dup backends for 's3', 'ubuntuone' and 'cloudfiles' are removed they should not appear in possible storage locations

2017-08-21 Thread Michael Terry
This situation is better in artful now.  If a backend is missing
packages it needs, it will prompt to install them.  And we no longer use
the meta packages that caused the confusion here.

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

** Changed in: ubuntu-gnome
   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/1264619

Title:
  When deja-dup backends for 's3', 'ubuntuone' and 'cloudfiles' are
  removed they should not appear in possible storage locations

Status in Ubuntu GNOME:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  When deja-dup backends for 's3', 'ubuntuone' and 'cloudfiles' are
  removed they should not appear in possible storage locations.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 29.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 28 03:23:12 2013
  InstallationDate: Installed on 2013-12-28 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20131227)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1264619/+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 1093095] Re: Restore failure from 32bit Ubuntu 12.10 to 64 bit Ubuntu 12.10

2017-08-21 Thread Michael Terry
*** This bug is a duplicate of bug 1252484 ***
https://bugs.launchpad.net/bugs/1252484

** This bug has been marked a duplicate of bug 1293822
   Duplicity crashes with libsyncError: libsync error 103 while in path cycle

** This bug is no longer a duplicate of bug 1293822
   Duplicity crashes with libsyncError: libsync error 103 while in path cycle
** This bug has been marked a duplicate of bug 1252484
   Possible data loss when restarting in the middle of a deleted file

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

Title:
  Restore failure from 32bit Ubuntu 12.10 to 64 bit Ubuntu 12.10

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Hi all, new to this so your help is greatly appreciated.

  1.
  OS: Ubuntu 12.10 (64 bit)

  2.
  Duplicity Version: duplicity 0.6.19-0ubuntu2
  Deja-dup Version: 24.0-0ubuntu1
  Python Version: python 2.7.3-0ubuntu7

  3.
  org.gnome.DejaDup backend 'file'
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
  org.gnome.DejaDup full-backup-period 90
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup last-backup ''
  org.gnome.DejaDup last-restore ''
  org.gnome.DejaDup last-run ''
  org.gnome.DejaDup nag-check ''
  org.gnome.DejaDup periodic false
  org.gnome.DejaDup periodic-period 7
  org.gnome.DejaDup prompt-check '2012-12-22T08:03:36.152875Z'
  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 '500 GB Hard Disk: My Book'
  org.gnome.DejaDup.File path ''
  org.gnome.DejaDup.File relpath b'Backup'
  org.gnome.DejaDup.File short-name 'My Book'
  org.gnome.DejaDup.File type 'volume'
  org.gnome.DejaDup.File uuid '5939-9A9F'
  org.gnome.DejaDup.Rackspace container 'JetJ001U'
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'JetJ001U'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.U1 folder '/deja-dup/JetJ001U'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1093095/+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 1595952] Re: Launches on the wrong configuration tab

2017-08-21 Thread Michael Terry
** Changed in: deja-dup (Ubuntu)
   Status: Triaged => 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/1595952

Title:
  Launches on the wrong configuration tab

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

Bug description:
  On Fedora 24, using deja-dup-34.2-2, duplicity-0.7.07.1-1.

  From Fedora BZ https://bugzilla.redhat.com/show_bug.cgi?id=1327719:

  ---
  When I launch deja-dup from the gnome-shell search it comes up showing 
"Storage location" and "Folder" but the tab list on the left is set to 
"Overview"

  "Overview" should be showing "Last backup" and "Back Up Now..."

  If I click on another left-side tab and back to Overview the display is 
correct.
  ---

  I see this as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1595952/+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 971665] Re: Full system backup hangs at 100% and makes the whole system very unresponsive - BackendException: Got status code 400

2017-08-21 Thread Michael Terry
I'm going to close out this bug.

Some of the mentioned issues have other bugs (deja-dup-monitor taking
resources is bug 1302416).  And the main report of a backup error of
"Got status code 400" is for the U1 backend, which is defunct now that
U1 shut down.

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

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

** Changed in: duplicity (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/971665

Title:
  Full system backup hangs at 100% and makes the whole system very
  unresponsive - BackendException: Got status code 400

Status in Duplicity:
  Invalid
Status in deja-dup package in Ubuntu:
  Invalid
Status in duplicity package in Ubuntu:
  Invalid

Bug description:
  I haven't been able to make full system backups since upgrading to
  Precise. The incremental backups have worked but but the full backups
  hang at 100% and makes the whole system very unresponsive. Even moving
  the mouse doesn't move the pointer on the screen. The only way to
  continue is to wait for ages, the pointer move very little and finally
  the system becomes responsive for a while before it hangs again. Then
  I could wait again or just use REISUB to reboot.

  I first thought that Deja-dup would be uploading a very big file to U1
  service but the last file in the upload file list is about 400kb in
  size so it isn't an upload issue. I have configured Deja-dup to backup
  my home folder to U1 weekly with at least 2 months for storing old
  backups. My U1 storage is currently at 85%.

  Traceback (from deja-dup_full2.log):
  DUPLICITY: WARNING 1
  DUPLICITY: . Attempt 1 failed: BackendException: Got status code 400

  DUPLICITY: DEBUG 1
  DUPLICITY: . Backtrace of previous error: Traceback (innermost last):
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", 
line 311, in iterate
  DUPLICITY: . return fn(*args, **kwargs)
  DUPLICITY: .   File 
"/usr/lib/python2.7/dist-packages/duplicity/backends/u1backend.py", line 188, 
in put
  DUPLICITY: . self.handle_error(raise_errors, 'put', answer, 
source_path.name, remote_full)
  DUPLICITY: .   File 
"/usr/lib/python2.7/dist-packages/duplicity/backends/u1backend.py", line 154, 
in handle_error
  DUPLICITY: . raise BackendException(msg)
  DUPLICITY: .  BackendException: Got status code 400

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic i686
  ApportVersion: 2.0-0ubuntu2
  Architecture: i386
  Date: Mon Apr  2 16:31:44 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 
(20091028.4)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to precise on 2012-03-02 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/971665/+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 875676] Re: Backing up fails with 'IOError CRC check failed'.

2017-08-21 Thread Michael Terry
** Package changed: deja-dup (Ubuntu) => duplicity (Ubuntu)

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

Title:
  Backing up fails with 'IOError CRC check failed'.

Status in Duplicity:
  Confirmed
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  For 4 days déjà dup hasn't been able to perform a backup. It fails
  with the error

  Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (, IOError('CRC check failed 0x8434f7d2L !=
  0x3d503338L',), )

  There is another similar bug #676767 where deleting ~/.cache/deja-dup
  helps. In this case it doesn't.

  I'm quite certain that my backup drive isn't corrupted. (It's a
  raid5.) I'd be happy to provide any additional information needed.

  --

  System information:
  Ubuntu 11.10
  deja-dup 20.0-0ubuntu3
  duplicity 0.6.15-0ubuntu2

  Logs:
  deja-dup.log: http://pastie.org/2705320
  deja-dup.gsettings: http://pastie.org/2705322

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/875676/+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 1462588] Re: Amazon AWS backup fails

2017-08-21 Thread Michael Terry
*** This bug is a duplicate of bug 1423354 ***
https://bugs.launchpad.net/bugs/1423354

** This bug has been marked a duplicate of bug 1423354
   0.7.01 S3 upload completely broken in CentOS - ' assert scheme == 's3', 
AssertionError'

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

Title:
  Amazon AWS backup fails

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1500, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1494, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1327, in main
  action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line 
1047, in ProcessCommandLine
  globals.backend = backend.get_backend(args[0])
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 221, in 
get_backend
  obj = get_backend_object(url_string)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 207, in 
get_backend_object
  return factory(pu)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py", 
line 161, in __init__
  self.resetConnection()
File "/usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py", 
line 183, in resetConnection
  self.conn = get_connection(self.scheme, self.parsed_url, self.storage_uri)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py", 
line 97, in get_connection
  assert scheme == 's3'
  AssertionError

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1462588/+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 1457185] Re: Deja-dup fails backing up

2017-08-21 Thread Michael Terry
*** This bug is a duplicate of bug 875676 ***
https://bugs.launchpad.net/bugs/875676

** This bug has been marked a duplicate of bug 875676
   Backing up fails with 'IOError CRC check failed'.

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

Title:
  Deja-dup fails backing up

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Deja-dup fails with:

  Failed to read /tmp/duplicity-dVcqOt-tempdir/mktemp-DUF_rW-325: (, IOError('CRC check failed 0xd1a0d155 !=
  0x4c0714ccL',), )

  This is an error already reported in 2010 somewhere else.

  tried to mitigate by reinstalling, clearing caches and parameters to
  no avail

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: deja-dup 32.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 20 20:58:37 2015
  InstallationDate: Installed on 2013-05-28 (721 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac 
(20130424)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1457185/+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 1622363] Re: Restore a file doesn't works if the filename include one ' (apostrophe)

2017-08-21 Thread Michael Terry
Seems fixed in artful.

** Changed in: deja-dup (Ubuntu)
   Status: New => 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/1622363

Title:
  Restore a file doesn't works if the filename include one '
  (apostrophe)

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  Trying to restore a specific version of a file, using the context menu (right 
click) in File/Nautilus, I found out that the window of DéjàDup doesn't shows 
up. The problem is that this file has an ' (apostrophe) included in his name. 
Just to try, I have added a second apostrophe to the name, and this time the 
window of DéjàDup it was open as expected.
  I think that there is somewhere a problem of character string, opened and 
closed when a filename includes an apostrophe, that ends up with an error that 
prevents to the DéjàDup window to open up correctly.
  Of course there is no problem at all, when the file names does not include an 
apostrophe.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep 11 19:17:55 2016
  InstallationDate: Installed on 2014-04-23 (871 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1622363/+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 1697155] Re: No progress dialog under Gnome Shell

2017-08-21 Thread Michael Terry
In artful, clicking on the "backup started" notification will bring up
the progress window.

** Changed in: deja-dup (Ubuntu)
   Status: New => 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/1697155

Title:
  No progress dialog under Gnome Shell

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  When connecting the backup drive in Gnome Shell (Ubuntu Gnome), backup
  starts but does not open the progress dialog. It is hard to keep track
  of when the backup process is finished and when it's save to remove
  the drive.

  Workaround: I have to open gnome-system-monitor and look for a process
  "deja-dup" (not to confuse with deja-dup-monitor which remains running
  after completion of the backup).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: deja-dup 34.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jun 10 11:39:49 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-05 (217 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   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/ubuntu/+source/deja-dup/+bug/1697155/+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 1019824] Re: Can't enter WebDAV Storage info

2017-08-21 Thread Michael Terry
This should be fixed these days?

** Changed in: deja-dup (Ubuntu)
   Status: New => 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/1019824

Title:
  Can't enter WebDAV Storage info

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  After running deja-dup-preferences and changing the backup location to
  WebDAV, I can't enter anything into the Server, Port, Folder, or
  Username fields.  Clicking in the text entry boxes shows a cursor, but
  keyboard entry doesn't do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19
  Uname: Linux 3.2.0-26-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  Date: Sun Jul  1 09:32:22 2012
  ExecutablePath: /usr/bin/deja-dup-preferences
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   LANGUAGE=
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to precise on 2012-05-19 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1019824/+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 1191230] Re: Backup doesn't work and an SSL error is displayed

2017-08-21 Thread Michael Terry
This was a bug with the U1 backend, which is no longer supported.
Closing.

** 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/1191230

Title:
  Backup doesn't work and an SSL error is displayed

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  A couple of days agoo I have found that my automatic backup doesn't
  work anymore, and this error is displayed:

  

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1411, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1404, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1386, in main
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 568, in incremental_backup
  sig_chain.get_fileobjs())
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 526, 
in get_fileobjs
  return map(filename_to_fileobj, self.get_filenames(time))
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 550, in 
get_fileobj_read
  self.get(filename, tdp)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 323, in 
iterate
  return fn(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/u1backend.py", 
line 201, in get
  answer = auth.request(remote_full)
File 
"/usr/lib/python2.7/dist-packages/ubuntuone-couch/ubuntuone/couch/auth.py", 
line 152, in request
  url, method=http_method, headers=headers, body=request_body)
File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1444, in 
request
  (response, content) = self._request(conn, authority, uri, request_uri, 
method, body, headers, redirections, cachekey)
File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1196, in 
_request
  (response, content) = self._conn_request(conn, request_uri, method, body, 
headers)
File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1179, in 
_conn_request
  content = response.read()
File "/usr/lib/python2.7/httplib.py", line 548, in read
  s = self._safe_read(self.length)
File "/usr/lib/python2.7/httplib.py", line 647, in _safe_read
  chunk = self.fp.read(min(amt, MAXAMOUNT))
File "/usr/lib/python2.7/socket.py", line 380, in read
  data = self._sock.recv(left)
File "/usr/lib/python2.7/ssl.py", line 241, in recv
  return self.read(buflen)
File "/usr/lib/python2.7/ssl.py", line 160, in read
  return self._sslobj.read(len)
  SSLError: The read operation timed out
  


  As you can see, the last error message line refers to an SSL Error.

  Even the restore operation seems to not work anymore. I have tried to
  restore a file, but the operation never ends. In the Déja-dup window
  the status is always "Preparing...".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
  Uname: Linux 3.2.0-48-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Sat Jun 15 09:23:07 2013
  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/1191230/+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 986898] Re: Icons "Privacy" and "Backup" are swapped in System Settings

2017-08-21 Thread Michael Terry
Backups has been using the safe icon for years at this point.  I'm
closing this for deja-dup.

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => 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/986898

Title:
  Icons "Privacy" and "Backup" are swapped in System Settings

Status in activity-log-manager package in Ubuntu:
  Confirmed
Status in deja-dup package in Ubuntu:
  Won't Fix

Bug description:
  Noticed the icons "Privacy" and "Backup" in System Settings are
  swapped. Dont know if this is really a bug but it makes more sense the
  backup icon being the one with the "back in time clock" and the
  privacy icon being the "safe" icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  Date: Sun Apr 22 16:29:45 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120421)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup22.0-0ubuntu2
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/986898/+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 1201924] Re: deja-dup fails to backup to ubuntu one, with error [Errno 2] No such file or directory

2017-08-21 Thread Michael Terry
U1 is shut down, closing this bug.

** 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/1201924

Title:
  deja-dup fails to backup to ubuntu one, with error [Errno 2] No such
  file or directory

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  I am using Ubuntu 13.04 and deja-dup 26.0 version. I connect to internet 
through my Institute's Authentication Proxy. deja-dup(Backup) fails to backup 
to Ubuntu One after a long time, with this error message,
  "Giving up on request after 5 attempts, last exception [Errno 2] No such file 
or directory".

  Ubuntu One client in my system is able to sync files properly. I
  already installed 'ubuntuone-client-proxy' package.

  Steps to reproduce:
  1. Open deja-dup backup software.
  2. Set it to backup to ubuntuone.
  3. Select Backup Now.

  What is expected?
  It is expected that backup finishes successfully.

  What happens instead?
  It fails after some time with the error mentioned above.

  One more thing is that my Ubuntu One folder has enough space in it. I
  backed up data into other drive and it is not more the 500 MB, and in
  ubuntu one I have more than 4.5 GB free space. So, lack of enough
  space is not the reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1201924/+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 1711953] Re: deja-dup-monitor crashed with signal 5 in g_settings_get_value()

2017-08-21 Thread Michael Terry
This looks like an upgrade issue around the new gsetting key not being
registered in the schema but the new code being run...

I can't reproduce this when running deja-dup-monitor on my system.

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

Title:
  deja-dup-monitor crashed with signal 5 in g_settings_get_value()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  This error was reported soon after start-up, when executing the
  command apt-get upgrade.  The system version is

  "Linux richard-desktop 4.11.0-13-generic #19-Ubuntu SMP Thu Aug 3
  15:14:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  The error occurred on date "Sun 20 Aug 21:30:32 BST 2017"

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.4-0ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Aug 20 21:18:29 2017
  ExecutablePath: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-03-30 (143 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor
  Signal: 5
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   deja_dup_migrate_settings () from 
/usr/lib/x86_64-linux-gnu/deja-dup/libdeja.so
  Title: deja-dup-monitor crashed with signal 5 in g_settings_get_value()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1711953/+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

2017-08-19 Thread Michael Terry
Yes, Launchpad picked the wrong description.  Here is the one that fixed
it:

deja-dup (35.4-0ubuntu1) artful; urgency=medium

  * New upstream release
- Adds support for GNOME Online Accounts
- Improves dynamic installation support for backend dependencies
- Fixes status icon in non-GNOME desktops (LP: #1592480)
- Improves sudo prompt when restoring outside HOME (LP: #1674121)
- Fixes password prompt loop with a bad gpg config (LP: #1710309)
- Fixes vertical size of backup detail output pane (LP: #1710491)
  * debian/rules:
- Tell deja-dup which packages to install for the various backends
  * debian/control.in:
- Update dependencies
- Drop deja-dup-backend-* meta packages, they are no longer needed
  * debian/patches/install-pygi.patch:
- Drop, no longer needed

 -- Michael Terry <mte...@ubuntu.com>  Thu, 17 Aug 2017 11:10:48 -0400

-- 
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 1133477] Re: [SRU] cut-n-paste move files got stuck forever

2017-08-18 Thread Michael Dooley
Caja bug confirmed Ubuntu MATE 16.04.3 64 bit. After following the test
and fix described in https://ubuntu-mate.community/t/help-test-a
-critical-bug-fix-in-ubuntu-mate-16-04/14624, the issue is resolved.

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

Title:
  [SRU] cut-n-paste move files got stuck forever

Status in caja package in Ubuntu:
  Invalid
Status in gvfs package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Invalid
Status in pcmanfm package in Ubuntu:
  Invalid
Status in caja source package in Xenial:
  Invalid
Status in gvfs source package in Xenial:
  Fix Committed
Status in nautilus source package in Xenial:
  Invalid
Status in pcmanfm source package in Xenial:
  Invalid

Bug description:
  [Impact]
  Without these fixes, copying any more than a few files in several file 
managers including but not limited to Nautilus and Caja either completely 
freezes up the file manager (if this happens with a Cut and Paste, it destroys 
user data by leaving files half moved) or slows it down to a crawl. These bugs 
are not found when using the mv command in the terminal, which will copy the 
files in a couple of seconds at maximum. This is a nightmare for people who 
want to Cut and Paste a lot of files and who need to do it quickly.

  [Test Case]
  Either find some files that you would be OK losing (or have a backup for) or 
create the files yourself. You can run the following command to generate 1024 
empty 1 MB files (do this in an empty directory, where you have at least 1 GB 
of free space), which is a valid way to reproduce this bug:

  i=1 && while [ $i -lt 1025 ]; do dd if=/dev/zero of=$i bs=4k
  iflag=fullblock,count_bytes count=1M; i=$[$i+1]; done

  (Credit to https://stackoverflow.com/a/11779492/4123313 and
  http://tldp.org/LDP/Bash-Beginners-Guide/html/sect_09_02.html - also,
  neither truncate or fallocate are used because the bug cannot be
  reproduced when using those tools, my theory is that with dd it
  actually writes the zeroes, with those tools, they say they wrote the
  zeroes to the filesystems but it seems they actually didn't (something
  along the lines of that), although I could be wrong)

  If you open Nautilus or Caja, and Cut and Paste these 1024 files
  somewhere else, the transfer will slow to a crawl, and in one instance
  where I tried this with 1024 empty 512 MB files, Nautilus actually
  crashed. This is very different to using mv in the terminal before
  doing it in the file manager, which transfers these files flawlessly.

  Once this fix is applied and I recreate these files, the transfer in
  Nautilus and Caja is almost as fast as using mv (I'd say within a
  second), which is what should happen.

  [Breakdown of the patches and the regression potential for each]
  First, I'd like to thank levien for providing the patch links to fix this. 
Without that, it would have been a bit more work to hunt down which patches are 
applicable.

  lp1133477-metadata-use-sequences-instead-of-lists.patch:
  Patch Description: The metabuilder stores files and data in sorted lists. An 
insertion into a sorted list is done in linear time, which highly affects 
efficiency. In order to fix this, use GSequence instead which does insertion 
and deletion in logarithmic time.

  This patch is in here because it helps with a large amount of files.
  Regardless if the files are 1 MB or 10 GB, the sorting of the files to
  be moved/copied is inefficient. This addresses part of the problem by
  making sure large amount of files can be dealt with efficiently. The
  regression potential for this is low, and the only case that I can see
  where a package would regress is a file manager that depends on (not
  100% on this theory but it's a possibility) monitoring the status of
  the list at a given time, and is incompatible with using GSequence. In
  this case, the package would have something peculiar hardcoded, and
  would most likely have an upstream fix that could be backported
  because this fix is in the gvfs release that is already in 17.04 and
  later (so they should have fixed it already). I can't think of a
  package that does this (from what I can tell, it's not sane code if it
  isn't compatible with this change) but if something does regress, it
  should be trivial to fix.

  lp1133477-metadata-use-queues-instead-of-lists.patch:
  Patch Description: Some of the lists used by the metabuilder have items 
appended to them. Appending to a list is done in linear time and this highly 
affects efficiency. In order to fix this, use GQueue which supports appending 
in constant time.

  This patch is extremely similar in function to the last one, but this
  one addresses items appended to a list instead of files and data in
  sorted lists. As such, the regression potential is similar (low)
  because it would involve a package hardcoding some things 

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

2017-08-18 Thread Michael Terry
That behavior hadn't changed: permissions and ownership should be
restored to original values too

-- 
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:
  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 1641423] Re: Backup fails with message: 'Failed to execute child process "duplicity" (No such file or directory)' or 'No module named gi.repository': missing deja-dup-backend-g

2017-08-17 Thread Michael Terry
Support for on-demand installation was recently improved.  If you
trigger a restore or backup before going to the settings Overview page,
we'll prompt to install the packages before you can continue.

** Changed in: deja-dup
   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/1641423

Title:
  Backup fails with message: 'Failed to execute child process
  "duplicity" (No such file or directory)' or 'No module named
  gi.repository': missing deja-dup-backend-gvfs, duplicity, and/or
  python-gi packages

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

Bug description:
  Ubantu 16.04

  Cant find out version of backup but it was loaded with distro 16.04
  and all software is up to date so it should be latest

  I dont know how to get the information
   in 3 & 4

  from the error maessage:
  Failed to execute child process "duplicity" (No such file or directory)
  It looks like a required file is missing

  I tried removing backup and reinstalling but it still fails with the
  same error

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1641423/+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 1592480] Re: No Icon in panel when job is running

2017-08-17 Thread Michael Terry
** 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/1592480

Title:
  No Icon in panel when job is running

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

Bug description:
  Kubuntu 16.04
  deja-dup34.2-0ubuntu1
  duplicity   0.7.06-2ubuntu2

  When Deja Dup is starting the icons in the panel are moved and I can see a 
gap but no deja dup icon.
  To show this icon when the job is running is very helpful. I know that early 
version had this feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1592480/+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

2017-08-17 Thread Michael Terry
** 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/1710309

Title:
  Backup does not recognize gpg 2 option and fails

Status in Déjà Dup:
  Fix Released
Status in deja-dup 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 1674121] Re: "Restore" asks for cryptic authentication to run /bin/sh as superuser

2017-08-17 Thread Michael Terry
** 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/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:
  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 1710491] Re: When the "Back Up" dialog is resized, the text panel does not expand vertically.

2017-08-17 Thread Michael Terry
** 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/1710491

Title:
  When the "Back Up" dialog is resized, the text panel does not expand
  vertically.

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

Bug description:
  When a backup is being run, a details button can be clicked to show
  the list of files being processed. The details appear in a "Back Up"
  dialog. When this dialog is resized, the details text box expands
  horizontally as expected. However, it does not expand vertically.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: deja-dup 34.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug 13 13:09:15 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-08-12 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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/1710491/+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 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

2017-08-16 Thread Michael F Winthrop
I am receiving numerous NM errors on startup, that I captured from
/var/log for one boot on Aug 16 18:10: I ask if the preserved ".files in
the home/user/ directories could be responsible for these errors?

In the captured "fail" list, NM is the main event per this thread 
(nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed)

The problem got more pronounced after:

sudo add-apt-repository ppa:kubuntu-ppa/backports
sudo apt update

This was added after plasma repeatedly dropped the window ornaments.

sudo /var/log# grep fail *log| grep 'Aug 16 18:10'

kern.log:Aug 16 18:10:35 dad314159 kernel: [0.173985] acpi PNP0A03:00: _OSC 
failed (AE_NOT_FOUND); disabling ASPM
kern.log:Aug 16 18:10:35 dad314159 kernel: [4.392621] wl: module 
verification failed: signature and/or required key missing - tainting kernel
kern.log:Aug 16 18:10:36 dad314159 NetworkManager[997]: 
nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
kern.log:Aug 16 18:10:36 dad314159 NetworkManager[997]:   
[1502921436.6054] failed to enumerate oFono devices: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was 
not provided by any .service files
kern.log:Aug 16 18:10:43 dad314159 NetworkManager[997]:   
[1502921443.7380] device (wlp12s0): state change: need-auth -> failed (reason 
'no-secrets') [60 120 7]
kern.log:Aug 16 18:10:43 dad314159 NetworkManager[997]:   
[1502921443.7388] device (wlp12s0): Activation: failed for connection 'Disco'
kern.log:Aug 16 18:10:43 dad314159 NetworkManager[997]:   
[1502921443.7426] device (wlp12s0): state change: failed -> disconnected 
(reason 'none') [120 30 0]
syslog:Aug 16 18:10:35 dad314159 kernel: [0.173985] acpi PNP0A03:00: _OSC 
failed (AE_NOT_FOUND); disabling ASPM
syslog:Aug 16 18:10:35 dad314159 kernel: [4.392621] wl: module verification 
failed: signature and/or required key missing - tainting kernel
syslog:Aug 16 18:10:35 dad314159 avahi-daemon[988]: chroot.c: open() failed: No 
such file or directory
syslog:Aug 16 18:10:35 dad314159 thermald[961]: THD engine start failed
syslog:Aug 16 18:10:36 dad314159 NetworkManager[997]: 
nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
syslog:Aug 16 18:10:36 dad314159 wpa_supplicant[1334]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
syslog:Aug 16 18:10:36 dad314159 NetworkManager[997]:   [1502921436.6054] 
failed to enumerate oFono devices: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was 
not provided by any .service files
syslog:Aug 16 18:10:36 dad314159 systemd[1]: networking.service: Unit entered 
failed state.
syslog:Aug 16 18:10:36 dad314159 systemd[1]: ctdb.service: Unit entered failed 
state.
syslog:Aug 16 18:10:36 dad314159 colord[1188]: (colord:1188): Cd-WARNING **: 
failed to get session [pid 1021]: No such device or address
syslog:Aug 16 18:10:39 dad314159 systemd[1]: sddm.service: Unit entered failed 
state.
syslog:Aug 16 18:10:41 dad314159 colord[1188]: (colord:1188): Cd-WARNING **: 
failed to get session [pid 1494]: No such device or address
syslog:Aug 16 18:10:42 dad314159 systemd[1]: sddm.service: Unit entered failed 
state.
syslog:Aug 16 18:10:43 dad314159 NetworkManager[997]:   [1502921443.7380] 
device (wlp12s0): state change: need-auth -> failed (reason 'no-secrets') [60 
120 7]
syslog:Aug 16 18:10:43 dad314159 NetworkManager[997]:   [1502921443.7388] 
device (wlp12s0): Activation: failed for connection 'Disco'
syslog:Aug 16 18:10:43 dad314159 NetworkManager[997]:   [1502921443.7426] 
device (wlp12s0): state change: failed -> disconnected (reason 'none') [120 30 
0]

I had made the unfortunate "upgrade" from kubuntu 14.04 with kxstudio
and decided to do a clean install to clean up the previous mess, leaving
kxstudio out (because kxstudio is skipping 16.04 in favor of 18.04):

I re-installed kubuntu 16.04,3 from disk downloaded 5 days ago
(1.562.112KB) preserving the /home/dad partition as well as a copy of
the fstab: (shows what was preserved during install on /dev/sd8

 sudo /etc# cat fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sda8 during installation
UUID=27aec088-dbbf-44f9-9c61-ab3c933e054e /   ext3
errors=remount-ro 0   1

# /home was on /dev/sda6 during installation
UUID=cfb5d746-bb65-4061-ba5b-02f60d574c27 /home   ext4defaults  
  0   2

# swap was on /dev/sda5 during installation
UUID=540c3467-7148-463e-858a-cb1435e4503f noneswapsw
  0   0

# mount Windows-Linux Share or /dev/sda3 on /media/sda3  
UUID=62587745587716CF/media/sda3  ntfs  
nls=iso8859-1,rw,umask=000  0  0

# mount usb as execuitable at /media/usb
# /dev/sde1 

[Desktop-packages] [Bug 984899] Re: right-click menu profile preference does not work

2017-08-16 Thread Michael Rowland Hunter
** Summary changed:

- right-click menu profile preference not work
+ right-click menu profile preference does not work

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

Title:
  right-click menu profile preference does not work

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Right click at the terminal area and choose profile -> profile preferences, 
nothing happens. While Edit->profile preferences works properly.
  --- 
  ApportVersion: 2.0.1-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  Package: gnome-terminal 3.4.1.1-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Tags:  precise
  Uname: Linux 3.2.0-23-generic x86_64
  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/ubuntu/+source/gnome-terminal/+bug/984899/+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 1710491] Re: When the "Back Up" dialog is resized, the text panel does not expand vertically.

2017-08-14 Thread Michael Terry
** Also affects: deja-dup
   Importance: Undecided
   Status: New

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

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

Title:
  When the "Back Up" dialog is resized, the text panel does not expand
  vertically.

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

Bug description:
  When a backup is being run, a details button can be clicked to show
  the list of files being processed. The details appear in a "Back Up"
  dialog. When this dialog is resized, the details text box expands
  horizontally as expected. However, it does not expand vertically.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: deja-dup 34.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug 13 13:09:15 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-08-12 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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/1710491/+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

2017-08-14 Thread Michael Terry
OK, fixed in deja-dup.  We now report GPG errors to user unless they
really do look like a bad password error.

https://git.launchpad.net/deja-
dup/commit/?id=e603ce8ac530f764862af082f689d1fa5062be5f

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

** Package changed: duplicity (Ubuntu) => deja-dup (Ubuntu)

-- 
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:
  Fix Committed
Status in deja-dup 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

2017-08-14 Thread Michael Terry
Well the endless loop aspect is probably from how deja dup is driving
duplicity. We treat most fog issues as bad passwords, I believe because
the error messages are a little variable.

So duplicity is likely correctly reporting gpg messages. If it doesn't
catch this case especially, maybe deja dup should try to more narrowly
handle gpg errors and report ones it doesn't recognize to the user.

I'll set task back to deja dup.

** Project changed: duplicity => deja-dup

-- 
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:
  Invalid
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 1592480] Re: No Icon in panel when job is running

2017-08-13 Thread Michael Terry
I've tested in xfce4, and I can see why this bug maybe developed.

We've always set an icon.  But for a while now, we've set the symbolic
version of our icon (a standard icon alternative that is a one-color
outline of an icon, with an adjustable color).  It looks like many
panels don't properly set the symbolic color to use on the icon (i.e.
set a white icon for a dark panel or a dark icon for a white panel).
*Possibly* because they can't and the GtkPlug infrastructure doesn't
give them that option after all.

Anyway.  I've reverted back to the full color icon (which is quite dark,
but not entirely so).  Smart panel implementations can still try and
find the symbolic version themselves and use that in preference if they
like.

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

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

Title:
  No Icon in panel when job is running

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

Bug description:
  Kubuntu 16.04
  deja-dup34.2-0ubuntu1
  duplicity   0.7.06-2ubuntu2

  When Deja Dup is starting the icons in the panel are moved and I can see a 
gap but no deja dup icon.
  To show this icon when the job is running is very helpful. I know that early 
version had this feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1592480/+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

2017-08-12 Thread Michael Terry
** No longer affects: deja-dup

** No longer affects: deja-dup (Ubuntu)

-- 
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 Duplicity:
  New
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/duplicity/+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 1166019] Re: duplicity crashed with SIGSEGV in g_file_copy()

2017-08-12 Thread Michael Terry
** No longer affects: deja-dup

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

Title:
  duplicity crashed with SIGSEGV in g_file_copy()

Status in Duplicity:
  Incomplete
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: duplicity 0.6.21-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sat Apr  6 03:00:37 2013
  ExecutablePath: /usr/bin/duplicity
  InterpreterPath: /usr/bin/python2.7
  MarkForUpload: True
  ProcCmdline: /usr/bin/python /usr/bin/duplicity 
--include=/home/username/.cache/deja-dup/metadata 
--exclude=/home/username/photos --exclude=/home/username/Downloads 
--exclude=/home/username/.local/share/Trash 
--exclude=/home/username/.cache/deja-dup/tmp 
--exclude=/home/username/.xsession-errors --exclude=/home/username/.thumbnails 
--exclude=/home/username/.Private --exclude=/home/username/.gvfs 
--exclude=/home/username/.adobe/Flash_Player/AssetCache 
--exclude=/home/username/.cache/deja-dup --exclude=/home/username/.cache 
--include=/home/username --exclude=/sys --exclude=/run --exclude=/proc 
--exclude=/var/tmp --exclude=/tmp --exclude=** --gio --volsize=25 / 
ftp://anonymous@lacie-2big/Public/backup --no-encryption --verbosity=9 
--gpg-options=--no-use-agent --archive-dir=/home/username/.cache/deja-dup 
--tempdir=/home/username/.cache/deja-dup/tmp --log-fd=21
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f60273fc175 :  mov
(%rax),%eax
   PC (0x7f60273fc175) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: duplicity
  StacktraceTop:
   g_file_copy () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_callable_info_invoke () from /usr/lib/libgirepository-1.0.so.1
   g_function_info_invoke () from /usr/lib/libgirepository-1.0.so.1
  Title: duplicity crashed with SIGSEGV in g_file_copy()
  UpgradeStatus: Upgraded to raring on 2012-10-19 (168 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1166019/+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 1075579] Re: Options during backup aren't completely readable

2017-08-12 Thread Michael Terry
Trunk notifications have been re-jiggered a bit and no longer have
buttons.  So this gets fixed for free I guess.  Thank you for the
report, sorry it languished so long!

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

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

** Changed in: ubuntu-translations
   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/1075579

Title:
  Options during backup aren't completely readable

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

Bug description:
  This is affecting German users of GNOME, using 12.04.1 LTS:

  ~ Organise your Backups with Déjà Dup
  ~ Restart the computer
  ~ Look at the message, in the GNOME notification task bar: You can select 
"Forts…", "Spät…" or "Date…". Especially by the last one, there could be 
multiple meanings. A picture of the message is in the attachment.

  The first thing would be that "Fortsetzen" in place of "Fort…" is viewed 
(there is enough place), 
  the second would be that "Später" in place of "Spät…" is viewed (there is 
enough place for one more character),
  the third and last thing would be that someone find an other translation of 
this option. (If the meaning is: Datensicherung abbrechen [cancel Backup], I 
would suppose: Abbrechen [cancel])

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: amd64
  Date: Tue Nov  6 15:51:21 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=de_DE:en
   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/1075579/+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

2017-08-12 Thread Michael Terry
I'm going to close the upstream tasks, as it seems like it was a gvfs
issue in the first place and additionally likely fixed a while back.

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

** Changed in: deja-dup
   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/1090541

Title:
  Problems uploading to ftp server

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Invalid
Status in deja-dup package in Ubuntu:
  Incomplete
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 1710319] [NEW] package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: package evince-common is not ready for configuration cannot configure (current status 'half-in

2017-08-11 Thread Michael Lucas
Public bug reported:

This is in Ubuntu 16.04 LTS on my 64bit Intel Celeron CPU 900 @ 2.2GHz.

Not sure what the deal is actually since the update status shows up to
date.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: evince-common 3.18.2-1ubuntu4.1
ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
Uname: Linux 4.4.0-91-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Aug 11 21:31:05 2017
DpkgHistoryLog:
 Start-Date: 2017-08-11  21:30:43
 Requested-By: lucastoshi (1000)
 Upgrade: update-manager-core:amd64 (1:16.04.7, 1:16.04.8), 
update-manager:amd64 (1:16.04.7, 1:16.04.8), python3-update-manager:amd64 
(1:16.04.7, 1:16.04.8)
DuplicateSignature:
 package:evince-common:3.18.2-1ubuntu4.1
 Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
 Rebuilding /usr/share/applications/bamf-2.index...
 dpkg: error processing package evince-common (--configure):
  package evince-common is not ready for configuration
ErrorMessage: package evince-common is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2016-12-10 (244 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: evince
Title: package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: 
package evince-common is not ready for configuration  cannot configure (current 
status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: evince (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade:
  package evince-common is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in evince package in Ubuntu:
  New

Bug description:
  This is in Ubuntu 16.04 LTS on my 64bit Intel Celeron CPU 900 @
  2.2GHz.

  Not sure what the deal is actually since the update status shows up to
  date.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: evince-common 3.18.2-1ubuntu4.1
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Aug 11 21:31:05 2017
  DpkgHistoryLog:
   Start-Date: 2017-08-11  21:30:43
   Requested-By: lucastoshi (1000)
   Upgrade: update-manager-core:amd64 (1:16.04.7, 1:16.04.8), 
update-manager:amd64 (1:16.04.7, 1:16.04.8), python3-update-manager:amd64 
(1:16.04.7, 1:16.04.8)
  DuplicateSignature:
   package:evince-common:3.18.2-1ubuntu4.1
   Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
   Rebuilding /usr/share/applications/bamf-2.index...
   dpkg: error processing package evince-common (--configure):
package evince-common is not ready for configuration
  ErrorMessage: package evince-common is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-12-10 (244 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: evince
  Title: package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: 
package evince-common is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1710319/+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 1710209] [NEW] package libappstream3 0.9.4-1ubuntu3 [modified: usr/share/doc/libappstream3/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/shar

2017-08-11 Thread Michael Leite
Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libappstream3 0.9.4-1ubuntu3 [modified: 
usr/share/doc/libappstream3/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Fri Aug 11 07:58:41 2017
DpkgHistoryLog:
 Start-Date: 2017-08-11  07:58:37
 Commandline: apt-get -f install
 Requested-By: mike (1000)
 Upgrade: libappstream3:i386 (0.9.4-1ubuntu1, 0.9.4-1ubuntu3)
DpkgTerminalLog:
 Preparing to unpack .../libappstream3_0.9.4-1ubuntu3_i386.deb ...
 Unpacking libappstream3:i386 (0.9.4-1ubuntu3) over (0.9.4-1ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libappstream3_0.9.4-1ubuntu3_i386.deb (--unpack):
  trying to overwrite shared 
'/usr/share/doc/libappstream3/changelog.Debian.gz', which is different from 
other instances of package libappstream3:i386
DuplicateSignature:
 package:libappstream3:0.9.4-1ubuntu3 [modified: 
usr/share/doc/libappstream3/changelog.Debian.gz]
 Unpacking libappstream3:i386 (0.9.4-1ubuntu3) over (0.9.4-1ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libappstream3_0.9.4-1ubuntu3_i386.deb (--unpack):
  trying to overwrite shared 
'/usr/share/doc/libappstream3/changelog.Debian.gz', which is different from 
other instances of package libappstream3:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libappstream3/changelog.Debian.gz', which is different from 
other instances of package libappstream3:i386
InstallationDate: Installed on 2017-02-20 (171 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: appstream
Title: package libappstream3 0.9.4-1ubuntu3 [modified: 
usr/share/doc/libappstream3/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libappstream3/changelog.Debian.gz', 
which is different from other instances of package libappstream3:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: appstream (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict xenial

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

Title:
  package libappstream3 0.9.4-1ubuntu3 [modified:
  usr/share/doc/libappstream3/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libappstream3/changelog.Debian.gz', which is different
  from other instances of package libappstream3:i386

Status in appstream package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libappstream3 0.9.4-1ubuntu3 [modified: 
usr/share/doc/libappstream3/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Aug 11 07:58:41 2017
  DpkgHistoryLog:
   Start-Date: 2017-08-11  07:58:37
   Commandline: apt-get -f install
   Requested-By: mike (1000)
   Upgrade: libappstream3:i386 (0.9.4-1ubuntu1, 0.9.4-1ubuntu3)
  DpkgTerminalLog:
   Preparing to unpack .../libappstream3_0.9.4-1ubuntu3_i386.deb ...
   Unpacking libappstream3:i386 (0.9.4-1ubuntu3) over (0.9.4-1ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libappstream3_0.9.4-1ubuntu3_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libappstream3/changelog.Debian.gz', which is different from 
other instances of package libappstream3:i386
  DuplicateSignature:
   package:libappstream3:0.9.4-1ubuntu3 [modified: 
usr/share/doc/libappstream3/changelog.Debian.gz]
   Unpacking libappstream3:i386 (0.9.4-1ubuntu3) over (0.9.4-1ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libappstream3_0.9.4-1ubuntu3_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libappstream3/changelog.Debian.gz', which is different from 
other instances of package libappstream3:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libappstream3/changelog.Debian.gz', which is different from 
other instances of package libappstream3:i386
  InstallationDate: Installed on 2017-02-20 (171 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: appstream
  Title: package libappstream3 0.9.4-1ubuntu3 [modified: 
usr/share/doc/libappstream3/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libappstream3/changelog.Debian.gz', 
which is different from other instances of package libappstream3:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications 

[Desktop-packages] [Bug 1035517] Re: package nvidia-current 302.17-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-08-10 Thread Michael Pratt
2017 and I am upgrading an old system from 12.04 to 14.04 and this is
STILL a problem

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

Title:
  package nvidia-current 302.17-0ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in nvidia-graphics-drivers package in Ubuntu:
  Expired

Bug description:
  It appeared some python modules were not found --


  Setting up nvidia-current (302.17-0ubuntu2) ...
  update-alternatives: using /usr/lib/nvidia-current/ld.so.conf to provide 
/etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode
  update-alternatives: warning: skip creation of /usr/lib32/libOpenCL.so 
because associated file /usr/lib32/nvidia-current/libOpenCL.so (of link group 
i386-linux-gnu_gl_conf) doesn't exist
  update-alternatives: warning: skip creation of 
/usr/lib32/vdpau/libvdpau_nvidia.so.1 because associated file 
/usr/lib32/nvidia-current/vdpau/libvdpau_nvidia.so.1 (of link group 
i386-linux-gnu_gl_conf) doesn't exist
  update-alternatives: warning: skip creation of /usr/lib32/libvdpau_nvidia.so 
because associated file /usr/lib32/nvidia-current/vdpau/libvdpau_nvidia.so (of 
link group i386-linux-gnu_gl_conf) doesn't exist
  update-alternatives: using /usr/lib/nvidia-current/alt_ld.so.conf to provide 
/etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto 
mode
  update-initramfs: deferring update (trigger activated)
  update-initramfs: Generating /boot/initrd.img-3.2.0-27-generic-pae
  Traceback (most recent call last):
File "/usr/bin/quirks-handler", line 26, in 
  import Quirks.quirkapplier
File "/usr/lib/python2.7/dist-packages/Quirks/quirkapplier.py", line 26, in 

  import XKit.xutils
  ImportError: No module named XKit.xutils
  dpkg: error processing nvidia-current (--configure):
   subprocess installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: nvidia-current 302.17-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21
  Uname: Linux 3.2.0-27-generic-pae i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Aug 10 19:14:42 2012
  DistUpgraded: 2012-08-05 10:01:27,632 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  GraphicsCard:
   NVIDIA Corporation G86 [Quadro NVS 140M] [10de:0429] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo ThinkPad T61 [17aa:20d8]
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MachineType: LENOVO 766303U
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic-pae 
root=UUID=60fb3c3d-57ae-4168-b0fd-b0f9e63ef824 ro quiet splash vt.handoff=7
  SourcePackage: nvidia-graphics-drivers
  Title: package nvidia-current 302.17-0ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to quantal on 2012-08-05 (5 days ago)
  XorgConf:
   Section "Device"
Identifier  "Default Device"
Option  "NoLogo""True"
   EndSection
  dmi.bios.date: 05/11/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC6WW (2.26 )
  dmi.board.name: 766303U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 0372761
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC6WW(2.26):bd05/11/2009:svnLENOVO:pn766303U:pvrThinkPadT61:rvnLENOVO:rn766303U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 766303U
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.7.8-0ubuntu1.2
  version.libdrm2: libdrm2 2.4.37-0ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.12.1.902-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~really6.14.4-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1035517/+subscriptions

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

2017-08-10 Thread Michael Terry
Amr, I don't know about your case specifically, but in Christopher's
case, it was because he was restoring to two different users' home
directories. Basically, anytime you are restoring outside your own home
directory, we go to root. We *could* try to be smarter there, but it
would be a fair amount of effort for (imho) small gain. But you're right
that it would be better if we were that smart.

-- 
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 Committed
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 1709806] [NEW] autopkgtest fails on ppc64el

2017-08-10 Thread Michael Hudson-Doyle
Public bug reported:

Ever since version 2.6.5-2ubuntu1, the autopkgtest for udisks2 has been
very flaky (failing ~80% of the time) on ppc64el:
http://autopkgtest.ubuntu.com/packages/u/udisks2/artful/ppc64el

We attempted to debug a little and managed to reproduce in a VM but we
got confused trying to debug:

[00:09:15]  Summary:
[00:09:17]  - directly calling asubtest fails (call_lock_sync), you 
need to run all Luks tests as they depend on each other
[00:09:18]$ sudo src/tests/integration-test Luks
[00:09:19]There it mostly fails at one of (always a different) 
test
[00:09:21]  - Once the bug was triggered by any of the tests in Luks 
it can be ran into with a subtest alone like
[00:09:23]$ sudo src/tests/integration-test 
Luks.test_ascii_keyfile_newline
[00:09:24]  - at some point after the issue further tests block at 
being unable to remove scsi_debug (needs reboot)
[00:09:26]  - nothing obvious in dmesg, or journal neither on usidk 
nor scsi_debug
[00:09:27]  - I've run a small dbus checker and it lists 
org.freedesktop.UDisks2 still as active
[00:09:28]  With udisk giving neither a crash nor any sort of message 
and the test only reporting a lost connection on the Dbus service I leave it to 
you to continue tmrw
[00:09:31]  mwhudson ^^

** Affects: udisks2 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  autopkgtest fails on ppc64el

Status in udisks2 package in Ubuntu:
  New

Bug description:
  Ever since version 2.6.5-2ubuntu1, the autopkgtest for udisks2 has
  been very flaky (failing ~80% of the time) on ppc64el:
  http://autopkgtest.ubuntu.com/packages/u/udisks2/artful/ppc64el

  We attempted to debug a little and managed to reproduce in a VM but we
  got confused trying to debug:

  [00:09:15]  Summary:
  [00:09:17]  - directly calling asubtest fails (call_lock_sync), you 
need to run all Luks tests as they depend on each other
  [00:09:18]$ sudo src/tests/integration-test Luks
  [00:09:19]There it mostly fails at one of (always a different) 
test
  [00:09:21]  - Once the bug was triggered by any of the tests in 
Luks it can be ran into with a subtest alone like
  [00:09:23]$ sudo src/tests/integration-test 
Luks.test_ascii_keyfile_newline
  [00:09:24]  - at some point after the issue further tests block at 
being unable to remove scsi_debug (needs reboot)
  [00:09:26]  - nothing obvious in dmesg, or journal neither on usidk 
nor scsi_debug
  [00:09:27]  - I've run a small dbus checker and it lists 
org.freedesktop.UDisks2 still as active
  [00:09:28]  With udisk giving neither a crash nor any sort of 
message and the test only reporting a lost connection on the Dbus service I 
leave it to you to continue tmrw
  [00:09:31]  mwhudson ^^

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1709806/+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 1135631] Re: question for autorizattion at restore not recognizable as deja dup

2017-08-09 Thread Michael Terry
*** This bug is a duplicate of bug 1674121 ***
https://bugs.launchpad.net/bugs/1674121

** This bug has been marked a duplicate of bug 1674121
   "Restore" asks for cryptic authentication to run /bin/sh as superuser

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

Title:
  question for autorizattion at restore not recognizable as deja dup

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

Bug description:
  when i restore a file with deja-dup, there is a popup window that asks for 
root privileges to run /bin/sh. There is no recognizable connection to deja-dup 
except for the moment in which this occurs.
  Would it be possible to anounce the source of the question in the "details" 
section or in any other way?

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1135631/+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

2017-08-09 Thread Michael Terry
Code in master should have a less cryptic message.  Now says "Privileges
are required to restore files to system locations"

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

-- 
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 Committed
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


<    5   6   7   8   9   10   11   12   13   14   >