Computer name changed

Bug #1268182 reported by Yorkshire Tyke on 2014-01-11
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Déjà Dup
Medium
Unassigned
deja-dup (Ubuntu)
Medium
Unassigned

Bug Description

I am/was using Deja-Dup (version 26.0) on Fedora 19, I modified my router settings to use openDNS instead of my ISP's DNS.
Then the next time I ran Deja-dup I had the message:-

The existing backup is of a computer named
advancedsearch.virginmedia.com, but the current
computer's name is Zotac-Zbox-ID82. If this is
unexpected, you should backup to a different location.

Since I wasn't asked to specify a computer name, and the underlying "duplicity" (version: 0.6.22) would appear to get the machine name from the wrong file, I understand that the computer name is kept in two files (a bad practice in my mind).

So can the interface be changed to show and or allow one to specify what hostname is used?

I reinstalled my machine, and changed my hostname in the way (it could have been a new machine).
I didn't used deja-dup for restoration as I restored some things I don't back up (as multi media easy to find elsewhere, binaries folder).

It feel like deja-dup ask me to send to trash all history or change my hostname to match my previous one?

I let you guess what new/lazy user would do.

Vej (vej) on 2017-03-08
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):
importance: Undecided → Medium
Vej (vej) wrote :

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 the one from socket.gethostname().

The later one is a problem of duplicity and therefore handled in bug #667885 ("
duplicity prefers fully-qualified-domain-name (fqdn) over hostname").

The first problem might be fixable in Déjà Dup. I will examine this further.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers