Hi, Kenneth! This would almost certainly just be Deja Dup's fault, I
can't imagine duplicity would be an issue here.
@khteh - it should be safe to kill an active duplicity process and
restart your backup, to recover from this happening as a workaround. But
obviously, there's still the bug that it did happen in the first place.
How did you close Deja Dup? Normally, there's the progress dialog with
cancel or resume later buttons, both of which should stop the duplicity
process. If Deja Dup was shut down unexpectedly, I could maybe see this
happening.
** Changed in: deja-dup
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1980908
Title:
duplicity does NOT close properly
Status in Déjà Dup:
Incomplete
Status in Duplicity:
New
Status in duplicity package in Ubuntu:
New
Bug description:
Duplicity process stays running after closing deja-dup backups app
from Ubuntu desktop. Openning up deja-dup again, go to Restore tab,
error message shows "Another duplicity instance is already running
with this archive directory". `ps -ef | grep duplicity` shows the
process still running.
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1980908/+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
