I think this is a report against Deja Dup - that string is an error
message we give if 'duplicity --version' doesn't actually give us a
parsable version string.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Interesting… that usually means that duplicity crashed on us or had some
other odd error when we asked it for its version.
But when you do it on the terminal, it’s fine…
Are you using the standard Ubuntu distro version of deja Dup (vs flatpak
or snap releases?)
--
You received this bug
https://bugs.kde.org/show_bug.cgi?id=486422
Bug ID: 486422
Summary: Suspend inhibits also end up keeping the display on
Classification: Plasma
Product: Powerdevil
Version: 5.27.80
Platform: Kubuntu
OS: Linux
Hmm, that's odd. That means... maybe there's a problem decrypting some
of your metadata, but you do have an unencrypted version of that
metadata in duplicity cache folders...?
But if you can restore stuff, that likely means you can decrypt the
latest actual data...
If you run "DEJA_DUP_DEBUG=1
Hmm, that's odd. That means... maybe there's a problem decrypting some
of your metadata, but you do have an unencrypted version of that
metadata in duplicity cache folders...?
But if you can restore stuff, that likely means you can decrypt the
latest actual data...
If you run "DEJA_DUP_DEBUG=1
OK that is an interesting data point about the password != NULL
failure... But that error is probably coming from the gvfsd-sftp binary,
not the deja-dup binary.
As another data point, if you use a newer version - like from snap or
flatpak installs, does that change anything? I don't remember
Hmm… that means we aren’t able to store passwords in your desktop
secrets / passwords store. It looks like you’re using gnome, so that’s
very unexpected (there are known issues with KDE).
If you connect to these servers using the basic Files (nautilus) app, do
the passwords get saved?
** Changed
Good news! You can simply drop the Depends entirely for Deja Dup. It used to
used pkexec, but no longer user policykit at all, since version 42.0 I believe.
The packaging suggests (but does not recommend) python3-pydrive. Which
means it isn't installed by default when you install deja-dup. (Which I
believe is done so that python3-pydrive doesn't have to be promoted to
main.)
But the packaging does also set it up so that Deja Dup *should* have
offered
If you install python3-pydrive does that error go away?
--
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/1995073
Title:
Ubuntu 22.10 deja-dup throws exception when login
Status in
** Changed in: deja-dup (Ubuntu)
Status: Incomplete => 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/1980934
Title:
Backup fail with unknown error
Status in
https://gitlab.gnome.org/World/deja-dup/-/blob/main/PACKAGING.md has
some advice for packagers around enabling restic support.
(Though note that it references the new `-Dpackagekit=enabled` flag
which only exists in 44.x. Just ignore that for 43.x. PackageKit is
automatically used as long as it
Hello, sorry this fell off my radar. I'm not sure what to do though,
since there's so little actionable information.
Is it possible to get more of the logs from running "DEJA_DUP_DEBUG=1
deja-dup"? There's nothing in what you posted originally that looks like
an actual error message.
--
You
Those messages from the log look innocent enough to me. So the backups
themselves work correctly, but when we get to the verification step at
the end, you see an unknown error? No further output in that dialog?
The verification step tries to restore a canary file we insert in the
backup, just to
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
** 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/1933717
Title:
Backup messages in wrong language
Status in
** Changed in: deja-dup (Ubuntu)
Status: Confirmed => 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/1933717
Title:
Backup messages in wrong language
To manage notifications
** 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/1778638
Title:
duplicity stuck in splice() call on Bionic
** 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/1778638
Title:
duplicity stuck in splice() call on Bionic
To manage
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355
** Bug watch added: Debian Bug tracker #1011355
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355
** Also affects: deja-dup (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355
Importance: Unknown
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355
** Bug watch added: Debian Bug tracker #1011355
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355
** Also affects: deja-dup (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355
Importance: Unknown
Package: deja-dup
Version: 42.7-1
Severity: important
X-Debbugs-Cc: m...@mterry.name
Dear Maintainer,
I'm the upstream maintainer of Deja Dup. Google will be removing
a particular oauth workflow that Deja Dup uses in September.
This means that any new authentications for users trying to connect
Looks like Debian stable is using 42.7 right now - should I file a bug
on the Debian side to track that too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973816
Title:
Deja Dup's Google support
Hello! I'm the upstream maintainer of Deja Dup. Google will be removing a
particular oauth workflow that Deja Dup uses in September.
This means that any new authentications for users trying to connect Deja Dup to
their Google account will fail after that date (existing users that have
already
Looks like Debian stable is using 42.7 right now - should I file a bug
on the Debian side to track that 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/1973816
Title:
Deja Dup's
OK, I've made a little wiki page about this issue for distro maintainers
(no real new information, but it does have links to patches at the
bottom). The patches should cover all affected versions that Ubuntu
supports (40.7, 42.8, and 42.9).
https://wiki.gnome.org/Apps/DejaDup/GoogleAuthChange2022
OK, I've made a little wiki page about this issue for distro maintainers
(no real new information, but it does have links to patches at the
bottom). The patches should cover all affected versions that Ubuntu
supports (40.7, 42.8, and 42.9).
https://wiki.gnome.org/Apps/DejaDup/GoogleAuthChange2022
Public bug reported:
Hello! I'm the maintainer of Deja Dup. I was recently made aware that
Google is removing an oauth workflow that Deja Dup uses, in September.
Here's their blog post about it:
https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html
Here's the upstream bug
Public bug reported:
Hello! I'm the maintainer of Deja Dup. I was recently made aware that
Google is removing an oauth workflow that Deja Dup uses, in September.
Here's their blog post about it:
https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html
Here's the upstream bug
Deja Dup could maybe be smarter in the specific case of SMB mounts and
only try to mount the root folder...
If you switch your settings from:
Network Location: smb://1.2.3.4/backup/UbuntuBackup
Folder: MyMachineBackup
to:
Network Location: smb://1.2.3.4/backup
Folder:
Deja Dup could maybe be smarter in the specific case of SMB mounts and
only try to mount the root folder...
If you switch your settings from:
Network Location: smb://1.2.3.4/backup/UbuntuBackup
Folder: MyMachineBackup
to:
Network Location: smb://1.2.3.4/backup
Folder:
I think that /tmp filename is a file that duplicity proceeds to throw
away. It copies files there, tries to unpack them, then cleans up after
itself (regardless of success). So that error message would be a lot
more useful if it indicated what the actual source file it had copied
from the storage
I think that /tmp filename is a file that duplicity proceeds to throw
away. It copies files there, tries to unpack them, then cleans up after
itself (regardless of success). So that error message would be a lot
more useful if it indicated what the actual source file it had copied
from the storage
I tested this and it worked!
- Made an initial backup, not saving password.
- Backed up again, changing the password.
With the old version, I got an error at "verify the backup" step. But
the backup files did end up being written with the wrong password.
With the new version, it did not accept
I tested this and it worked!
- Made an initial backup, not saving password.
- Backed up again, changing the password.
With the old version, I got an error at "verify the backup" step. But
the backup files did end up being written with the wrong password.
With the new version, it did not accept
It escaped my attention at the time, but Ubuntu 18.04 released with both
a version of duplicity that shows the new incremental-backups-also-have-
this-issue behavior (see my comment 22) and a release of deja-dup that
wasn't yet fixed to avoid it.
Which means that deja-dup in Ubuntu 18.04 is still
It escaped my attention at the time, but Ubuntu 18.04 released with both
a version of duplicity that shows the new incremental-backups-also-have-
this-issue behavior (see my comment 22) and a release of deja-dup that
wasn't yet fixed to avoid it.
Which means that deja-dup in Ubuntu 18.04 is still
It escaped my attention at the time, but Ubuntu 18.04 released with both
a version of duplicity that shows the new incremental-backups-also-have-
this-issue behavior (see my comment 22) and a release of deja-dup that
wasn't yet fixed to avoid it.
Which means that deja-dup in Ubuntu 18.04 is still
Michael Terry created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/670
Hello! I recently made a new room on the gnome.org matrix home server:
#deja-dup:gnome.org
This is just a tiny dev chat room for the GNOME Circle app Deja Dup.
I wanted to publicly list
*** This bug is a duplicate of bug 1933717 ***
https://bugs.launchpad.net/bugs/1933717
Hello and thank you for the report! Oddly enough, this is an Ubuntu
translation issue, where some German ended up sneaking into the English
translation. It’s fixed for the next release, but I guess they
*** This bug is a duplicate of bug 1933717 ***
https://bugs.launchpad.net/bugs/1933717
Hello and thank you for the report! Oddly enough, this is an Ubuntu
translation issue, where some German ended up sneaking into the English
translation. It’s fixed for the next release, but I guess they
Interesting. Jesse, that might be due to
https://gitlab.com/duplicity/duplicity/-/merge_requests/31 which
rejiggered how `--exclude-if-present` checks files in order to avoid a
fatal error that occurred in some edge cases. That change was released
in 0.8.17.
Maybe we would need a smarter fix to
Interesting. Jesse, that might be due to
https://gitlab.com/duplicity/duplicity/-/merge_requests/31 which
rejiggered how `--exclude-if-present` checks files in order to avoid a
fatal error that occurred in some edge cases. That change was released
in 0.8.17.
Maybe we would need a smarter fix to
This looks to be an Ubuntu translation error. The current package of
language-pack-gnome-en-base has some German phrases in its en_GB
translations for deja-dup!
Looks like they were fixed in May in the Ubuntu translation sources:
This looks to be an Ubuntu translation error. The current package of
language-pack-gnome-en-base has some German phrases in its en_GB
translations for deja-dup!
Looks like they were fixed in May in the Ubuntu translation sources:
This looks like a transient error, some issue with python3 on your
install?
But regardless, more recent releases of Ubuntu have deja-dup depend
directly on duplicity and gvfs-backends
** Project changed: deja-dup => deja-dup (Ubuntu)
** Changed in: deja-dup (Ubuntu)
Status: New => Fix
This looks like a transient error, some issue with python3 on your
install?
But regardless, more recent releases of Ubuntu have deja-dup depend
directly on duplicity and gvfs-backends
** Project changed: deja-dup => deja-dup (Ubuntu)
** Changed in: deja-dup (Ubuntu)
Status: New => Fix
Sorry you were hit by this issue! But good news is that a fix is
available. It was caused by an interaction between Deja Dup and
duplicity when a single quote was followed by a space.
This was fixed upstream in duplicity 0.8.17 (and worked around in deja-
dup 42.5). Both those fixes are in Ubuntu
Sorry you were hit by this issue! But good news is that a fix is
available. It was caused by an interaction between Deja Dup and
duplicity when a single quote was followed by a space.
This was fixed upstream in duplicity 0.8.17 (and worked around in deja-
dup 42.5). Both those fixes are in Ubuntu
** Changed in: deja-dup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915161
Title:
deja dup won't restore a folder where name contains apostrophe and
** 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/1915161
Title:
deja dup won't restore a folder where name contains
Robin, do you mind filing a new bug? Will be easier for me to dig into
what's not working for you, rather than adding on to this 2013 issue.
Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
Robin, do you mind filing a new bug? Will be easier for me to dig into
what's not working for you, rather than adding on to this 2013 issue.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.kde.org/show_bug.cgi?id=430081
Bug ID: 430081
Summary: Preference windows built with libhandy may not render
correctly
Product: Breeze
Version: 5.19.5
Platform: Ubuntu Packages
OS: Linux
I think the English word used is Utilities
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873238
Title:
Deja-dup icon is missing only runs from terminal
To manage notifications about this bug go
I think the English word used is Utilities
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1873238
Title:
Deja-dup icon is missing only runs from terminal
Status in deja-dup package
Oh that’s interesting yes. I’ll have to see how to get the quota info
from gvfs and apply it to our calculations. Thank you for the report!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
Oh that’s interesting yes. I’ll have to see how to get the quota info
from gvfs and apply it to our calculations. Thank you for the report!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906304
(Any one of those should work by itself)
--
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/1905170
Title:
Impossible to create a full backup due to permission error on
Oh and I should have mentioned workarounds:
- give everyone execute permission on the offending folder
- install the snap version of duplicity
- install the snap (or flatpak) version of deja-dup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Oh and I should have mentioned workarounds:
- give everyone execute permission on the offending folder
- install the snap version of duplicity
- install the snap (or flatpak) version of deja-dup
--
You received this bug notification because you are a member of Desktop
Packages, which is
(Any one of those should work by itself)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905170
Title:
Impossible to create a full backup due to permission error on
/home/lost+found folder
To
This is a bug in a possible interaction between Deja Dup >= 42.1 and
Duplicity < 0.8.16.
Which means as of this writing it definitely affects 20.10, and may
affect 21.04 if Duplicity doesn't get bumped before release.
This was fixed in Duplicity by the following patch:
This is a bug in a possible interaction between Deja Dup >= 42.1 and
Duplicity < 0.8.16.
Which means as of this writing it definitely affects 20.10, and may
affect 21.04 if Duplicity doesn't get bumped before release.
This was fixed in Duplicity by the following patch:
Were you using the snap package? There was a bug briefly in duplicity
that would have caused this error, but it is fixed now. Do you still see
this?
I don’t believe the bug was ever present in Ubuntu 20.04 itself.
** Changed in: deja-dup (Ubuntu)
Status: New => Incomplete
--
You
Were you using the snap package? There was a bug briefly in duplicity
that would have caused this error, but it is fixed now. Do you still see
this?
I don’t believe the bug was ever present in Ubuntu 20.04 itself.
** Changed in: deja-dup (Ubuntu)
Status: New => Incomplete
--
You
** 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/1027514
Title:
Restore dialog becomes too huge when restoring too
** 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/1027514
Title:
Restore dialog becomes too huge when restoring too many files
To
** Changed in: deja-dup (Ubuntu)
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/953194
Title:
deja-dup attempts to backup "lost+found"
To manage
** Changed in: deja-dup (Ubuntu)
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/953194
Title:
deja-dup attempts to backup "lost+found"
Latest versions show a notification that will bring the dialog open as
needed. (Or starting the app from the application launcher will also
show it.)
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Latest versions show a notification that will bring the dialog open as
needed. (Or starting the app from the application launcher will also
show it.)
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
That UI has been redesigned and is a lot better now.
** 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/1281675
Title:
That UI has been redesigned and is a lot better now.
** 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/1281675
Title:
The scheduling
Nikita, your issue actually looks a lot like something fixed in duplicity
0.8.16:
https://gitlab.com/duplicity/duplicity/-/commit/f6809e8a4e09b70138a0902434d8c88d3c4c8ccb
Try installing the snap version of deja-dup or duplicity, both of which
have the fix for this.
--
You received this bug
Nikita, your issue actually looks a lot like something fixed in duplicity
0.8.16:
https://gitlab.com/duplicity/duplicity/-/commit/f6809e8a4e09b70138a0902434d8c88d3c4c8ccb
Try installing the snap version of deja-dup or duplicity, both of which
have the fix for this.
--
You received this bug
Yeah an sru should be fine — no dramatic changes in there, but plenty of
nice fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901340
Title:
Backup doesn't automatically start when drive is
Yeah an sru should be fine — no dramatic changes in there, but plenty of
nice fixes.
--
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/1901340
Title:
Backup doesn't automatically start
Ah, OK. Maybe the previous problem with the snap was because the old
session monitor was still active? Odd.
But glad it worked now!
So yeah, looks like the fixes in 42.3 work for your case, and it's
possible the patches around encrypted & removable drives from 42.3 and
42.4 should be backported
Ah, OK. Maybe the previous problem with the snap was because the old
session monitor was still active? Odd.
But glad it worked now!
So yeah, looks like the fixes in 42.3 work for your case, and it's
possible the patches around encrypted & removable drives from 42.3 and
42.4 should be backported
Version 42.3 did fix an error with scheduled backups to encrypted
drives! I suspect that might be what you're hitting? Can you try the
snap and see if that fixes things? Might want to make a manual backup
first just to confirm everything is working.
snap install deja-dup --classic
sudo apt remove
Version 42.3 did fix an error with scheduled backups to encrypted
drives! I suspect that might be what you're hitting? Can you try the
snap and see if that fixes things? Might want to make a manual backup
first just to confirm everything is working.
snap install deja-dup --classic
sudo apt remove
Huh... That first message, I'm not sure I've seen before.
This might be a dup of https://bugs.launchpad.net/duplicity/+bug/1828869
?
You could test that by installing the snap version of duplicity and
uninstalling the distro version:
snap install duplicity --classic
sudo apt remove duplicity
Huh... That first message, I'm not sure I've seen before.
This might be a dup of https://bugs.launchpad.net/duplicity/+bug/1828869
?
You could test that by installing the snap version of duplicity and
uninstalling the distro version:
snap install duplicity --classic
sudo apt remove duplicity
I have some further details about this bug! Not super positive, but
still.
First, I'm going to mark bug #676767 a duplicate of this. That's a
slightly older bug with the same symptom, and a workaround (of deleting
the cache) that doesn't seem to work in all cases. But ultimately, it's
I have some further details about this bug! Not super positive, but
still.
First, I'm going to mark bug #676767 a duplicate of this. That's a
slightly older bug with the same symptom, and a workaround (of deleting
the cache) that doesn't seem to work in all cases. But ultimately, it's
When I use the metric prometheus_sd_discovered_targets it only shows the
targets discovered in the same data center as the prometheus instance.
I have servers/services across multiple datacenters. All of these are shown
when looking at the prometheus/Targets view and the prometheus/Service
Public bug reported:
httplib2 0.16 changed how 308 redirects are handled. This broke some
existing python packages that weren't expecting that change when talking
to Google servers that use 308 redirects. Like PyDrive.
= Reproducing =
Reproducing is a little difficult. I'm not entirely sure
** 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/953194
Title:
deja-dup attempts to backup "lost+found"
Status in
** 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/953194
Title:
deja-dup attempts to backup "lost+found"
To manage notifications
*** This bug is a duplicate of bug 1360734 ***
https://bugs.launchpad.net/bugs/1360734
Hmm, I'm sorry this is happening! I've seen reports of duplicity giving
this error before. I'll mark this bug as a duplicate of one of them.
Practically, until this gets fixed, I'd say try deleting
*** This bug is a duplicate of bug 1360734 ***
https://bugs.launchpad.net/bugs/1360734
Hmm, I'm sorry this is happening! I've seen reports of duplicity giving
this error before. I'll mark this bug as a duplicate of one of them.
Practically, until this gets fixed, I'd say try deleting
Michael Terry created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/415
### Requested details
1. The list name: `deja-dup-list`
2. The rationale on why the mailing list should be archived (i.e project
unmaintained): Migrating to Discourse
3. Whether the list
I think this should be fixed with 42.2, which now looks at /etc/fatal
and mounts the target drive if necessary.
** Changed in: deja-dup
Status: New => Fix Released
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a
I think this should be fixed with 42.2, which now looks at /etc/fatal
and mounts the target drive if necessary.
** Changed in: deja-dup
Status: New => Fix Released
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a
I’m moving all the suggestions for more advanced include/exclude support
to a single ticket on Gitlab
https://gitlab.gnome.org/World/deja-dup/-/issues/112
** Bug watch added: gitlab.gnome.org/World/deja-dup/-/issues #112
https://gitlab.gnome.org/World/deja-dup/-/issues/112
** Changed in:
I’m moving all the suggestions for more advanced include/exclude support
to a single ticket on Gitlab
https://gitlab.gnome.org/World/deja-dup/-/issues/112
** Bug watch added: gitlab.gnome.org/World/deja-dup/-/issues #112
https://gitlab.gnome.org/World/deja-dup/-/issues/112
** Changed in:
** Changed in: deja-dup (Ubuntu)
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/1815056
Title:
deja-dup is asking for the admin password
** Changed in: deja-dup (Ubuntu)
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/1814238
Title:
deja-dup saves passphrase in /tmp
To manage notifications
** Changed in: deja-dup (Ubuntu)
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/1815056
Title:
deja-dup is asking for the admin password
To manage
1 - 100 of 14175 matches
Mail list logo
