Bug#650856: Crash on restore GUI startup

2012-04-10 Thread Laurent Bigonville
Package: deja-dup Followup-For: Bug #650856 Hi, Is this bug relevant? I've quickly tried here with 20.2-2 and it's not crashing. Could someone confirms this? Cheers Laurent Bigonville -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'),

Bug#650856: Crash on restore GUI startup

2012-04-10 Thread Henry-Nicolas Tourneur
Package: deja-dup Followup-For: Bug #650856 I did just check on a Wheezy installation and it's not crashing. I assume the best would be to have Pietro Battiston to test this again with an up to date system. Regards, -- System Information: Debian Release: wheezy/sid APT prefers testing APT

Bug#650856: Crash on restore GUI startup

2012-04-10 Thread Kees de Jong
Package: deja-dup Followup-For: Bug #650856 I can confirm this too, it doesn't crash. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8,

Bug#650856: Crash on restore GUI startup

2011-12-08 Thread Jose Carlos Garcia Sogo
On Sun, Dec 4, 2011 at 1:06 AM, Pietro Battiston m...@pietrobattiston.it wrote: Package: deja-dup Version: 20.2-1 Severity: grave Deja-dup just crashes when started with the --restore argument. Backup instead works fine. At the end of this email is the output when ran in gdb, including a

Bug#650856: Crash on restore GUI startup

2011-12-08 Thread Pietro Battiston
Il giorno gio, 08/12/2011 alle 12.43 +0100, Jose Carlos Garcia Sogo ha scritto: On Sun, Dec 4, 2011 at 1:06 AM, Pietro Battiston m...@pietrobattiston.it wrote: [...] At the end of this email is the output when ran in gdb, including a backtrace. Could you install deja-dup-dbg package

Bug#650856: Crash on restore GUI startup

2011-12-03 Thread Pietro Battiston
Package: deja-dup Version: 20.2-1 Severity: grave Deja-dup just crashes when started with the --restore argument. Backup instead works fine. At the end of this email is the output when ran in gdb, including a backtrace. As far as I can tell, that could also just be a bug in libgtk... I don't