*** This bug is a duplicate of bug 1724638 ***
https://bugs.launchpad.net/bugs/1724638
** Information type changed from Private to Public
** This bug has been marked a duplicate of bug 1724638
deja-dup-monitor crashes with an out-of-memory issue
--
You received this bug notification
So we've started getting some crash reports from deja-dup-monitor
running out of memory in artful. Which is better than this original
bug, but still not ideal. I'd love to root cause this.
I've opened bug 1724638 to keep track of the OOM crashes, keeping this
bug clear from that noise. But if
*** This bug is a duplicate of bug 1724638 ***
https://bugs.launchpad.net/bugs/1724638
** Information type changed from Private to Public
** This bug has been marked a duplicate of bug 1724638
deja-dup-monitor crashes with an out-of-memory issue
--
You received this bug notification
*** This bug is a duplicate of bug 1724638 ***
https://bugs.launchpad.net/bugs/1724638
** Information type changed from Private to Private Security
** Information type changed from Private Security to Public
** This bug has been marked a duplicate of bug 1724638
deja-dup-monitor crashes
The real fix for this bug is to fix original bug 1302416 a better way,
by preventing the memory growth in the first place.
(Maybe we should silence reports of this kind of crash, so users aren't
bugged by it in the meantime?)
** Changed in: deja-dup
Status: New => Confirmed
** Changed
Public bug reported:
In the 36.x series, I added some code that will prevent deja-dup-
monitor's memory usage from growing out of bounds (see original bug
1302416 that I have still been unable to reproduce).
This causes crashes occasionally when the process is prevented from
allocating more
@Reto, can you upload /tmp/deja-dup.gsettings after running the following?
Thanks
gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>From the retraced Stacktrace.txt, it looks like a client dconf thread is
sending a message to the session DBus daemon which ends up trying to use
a bogus GTask structure.
So I'm guessing we are either trashing dconf's memory or this is a
dconf-internal bug? Assigning to dconf to see if this
So I've mentioned I can't reproduce. To be more verbose, when I use
your smb.conf[1] in comment #12 on my up-to-date Ubuntu 16.04 machine, I
can't even navigate to the share in nautilus. I get "Failed to mount
Windows share: Invalid argument" when trying to log into the "nethome"
share on the
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721738
Title:
deja-dup-monitor crashed with SIGSEGV in g_hash_table_lookup_node()
To manage
Does this still affect people? The oldest duplicate is from 2013. The
samba GVFS backend is a moving target, it might have fixed this in the
meantime.
** Changed in: deja-dup
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: deja-dup
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720372
Title:
deja-dup crashed with SIGSEGV in deja_dup_operation_start()
To
That seems fine. (Question: does it work any better if you use relative
path?)
I haven’t been able to reproduce, but I agree there’s a problem. Smb is
the flakiest gvfs backend, it tends to be temperamental.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I assume your testing was on a fresh system, not an upgrade?
We have intentionally hidden several cloud providers by default. See this wiki
page for the explanation and how to unhide them:
https://wiki.gnome.org/Apps/DejaDup/Clouds
But on upgrades, your old settings shouldn’t be affected. If
** Changed in: deja-dup
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720372
Title:
deja-dup crashed with SIGSEGV in deja_dup_operation_start()
To manage
** Information type changed from Private to Public
** Changed in: deja-dup (Ubuntu)
Status: New => Confirmed
** Also affects: deja-dup
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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
(On the server of course)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715582
Title:
deja-dup fails to backup
To manage notifications about this bug go to:
Hrm. Is it possible to share your /etc/samba/smb.conf?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715582
Title:
deja-dup fails to backup
To manage notifications about this bug go to:
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717230
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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.
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276327
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302416
Title:
deja-dup monitor was taking
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
I renamed the help files from deja-dup to org.gnome.DejaDup. So the
deja-dup package is correct and the language packs are simply out of
date.
They should get regenerated in the due course of releasing artful,
right? I've reassigned to the language pack.
** Project changed: deja-dup =>
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
** Also affects: deja-dup
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302416
Title:
deja-dup monitor was taking 6GB of memory
To manage notifications
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908791
Title:
Backing up
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
*** This bug is a duplicate of bug 1712757 ***
https://bugs.launchpad.net/bugs/1712757
** This bug has been marked a duplicate of bug 1712757
** Changed in: deja-dup (Ubuntu)
Assignee: (unassigned) => Michael Terry (mterry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712714
Title:
deja-dup autopkgtest failure with meson 0
** Changed in: deja-dup
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368640
Title:
When backup system, need to click cancel button twice to close
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623835
Title:
Scrolled
*** 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 Ubuntu
Bugs, which is subscribed to
*** 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 Ubuntu
Bugs, which is
** Also affects: deja-dup
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570204
Title:
Deja-dup tries to save directories that sould be ignored
To
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368640
Title:
When backup
*** 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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
*** 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
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
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
*** 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 Ubuntu
Bugs, which is subscribed to
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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:
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
*** 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 Ubuntu
Bugs, which is subscribed to
*** 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 Ubuntu
Bugs, which is subscribed to
*** 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 Ubuntu
Bugs, which is subscribed to
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
*** 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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217959
Title:
*** 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 Ubuntu
Bugs, which is
** Also affects: deja-dup (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985512
Title:
support system backups (set up a backup run by root)
To
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Is this reproducible for anyone?
** Changed in: deja-dup (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711953
Title:
deja-dup-monitor crashed with signal
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
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
*** 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
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 Ubuntu
*** 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
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 Ubuntu
Bugs, which is
*** 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 Ubuntu
Bugs, which is
*** 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
** Changed in: deja-dup (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595952
Title:
Launches on the wrong configuration tab
To manage notifications
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
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:
** Package changed: deja-dup (Ubuntu) => duplicity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications
*** 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
*** 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 Ubuntu
Bugs, which is subscribed
Seems fixed in artful.
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1622363
Title:
Restore a file doesn't works if the filename
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1019824
Title:
Can't enter WebDAV Storage info
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1191230
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201924
Title:
deja-dup fails to backup to ubuntu
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to
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
-
This was filed against deja-dup, not ubuntu. And doesn't have much
information. Is this still happening to you?
** Project changed: deja-dup => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674121
Title:
"Restore" asks for cryptic
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)
** Changed in: deja-dup
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592480
Title:
No Icon in panel when job is running
To manage notifications about
** Changed in: deja-dup
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710491
Title:
When the "Back Up" dialog is resized, the text panel does not
** Changed in: deja-dup
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710309
Title:
Backup does not recognize gpg 2 option and fails
To manage
** Changed in: deja-dup
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674121
Title:
"Restore" asks for cryptic authentication to run /bin/sh as
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710491
Title:
When
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
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
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
** No longer affects: deja-dup
** No longer affects: deja-dup (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710309
Title:
Backup does not recognize gpg 2 option and fails
To manage
** No longer affects: deja-dup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1166019
Title:
duplicity crashed with SIGSEGV in g_file_copy()
To manage notifications about this bug go to:
401 - 500 of 9681 matches
Mail list logo