The flatpak and snap releases of Deja Dup now include this duplicity
fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268182
Title:
Computer name changed
To manage notifications about this bug g
To Vej's points:
> Fix the problem, that accepting the changed hostname is not persistent
It *should* already be persistent. In the sense that each time duplicity
backs up, it writes the current hostname to the manifest and checks
against that going forward.
I think it just looks like it's not p
Adding to my last reply:
Re-connect internet and backup continues normally without issue.
Literally, I do no name change but it complains about one. Something is
really messed up here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just had this happen with internet disconnected. I did no name change of
my own.
Reproduce:
Run backups normal with internet.
Keep router connected but pull internet.
Have Deja Dup run backups.
2nd day Deja Dup complains stupidly about a name change.
For whatever reason, the name Duja Dup use
I'm having a similar problem and unable to find a solution so far. I'm
running an Ubuntu 18.04 derivative - Peppermint 10 Respin. I damaged my
partition and had to install the system again and was able to restore
many of my settings and all my files. The problem is that when I
installed the syst
This bug report (and its duplicate) deal with two problems (in my
opinion):
- Fix the problem, that accepting the changed hostname is not persistent
(i.e. that the dialog is showed more than once).
- Find a solution for the problem, that the hostname from
socket.getfqdn() does not always match th
** Also affects: deja-dup (Ubuntu)
Importance: Undecided
Status: New
** Changed in: deja-dup
Status: New => Confirmed
** Changed in: deja-dup (Ubuntu)
Status: New => Confirmed
** Changed in: deja-dup
Importance: Undecided => Medium
** Changed in: deja-dup (Ubuntu)