| 2006-06-03 13:44:48 |
Alvin Thompson |
bug |
|
|
added bug |
| 2006-06-03 13:45:29 |
Alvin Thompson |
gnome-network: severity |
Normal |
Major |
|
| 2006-06-03 13:45:29 |
Alvin Thompson |
gnome-network: statusexplanation |
|
|
|
| 2006-07-09 05:19:10 |
Steven Harms |
gnome-network: status |
Unconfirmed |
Confirmed |
|
| 2006-07-09 05:19:10 |
Steven Harms |
gnome-network: statusexplanation |
|
I can confirm this bug, operates as described. |
|
| 2009-03-01 18:45:55 |
Jersey |
description |
Binary package hint: gnome-network
After a fresh install of Dapper, the '/etc/hosts' file looks like this:
127.0.0.1 localhost
127.0.1.1 computername
...
If I rename the computer to 'newname' using 'System-->Administration-->Networking', the file looks like this:
127.0.0.1 localhost newname
127.0.1.1 computername
Obviously, it should be:
127.0.0.1 localhost
127.0.1.1 newname
This causes all sorts of nasty problems.
|
Binary package hint: gnome-network
After a fresh install of Dapper, the '/etc/hosts' file looks like this:
127.0.0.1 localhost
127.0.1.1 computername
...
If I rename the computer to 'newname' using 'System-->Administration-->Networking', the file looks like this:
127.0.0.1 localhost newname
127.0.1.1 computername
Obviously, it should be:
127.0.0.1 localhost
127.0.1.1 newname
This causes all sorts of nasty problems.
In 8.04 Rev.2 There are similar problems, after changing the domain, the entries are not correctly updated in the "hosts" and "hostnames" files. For details see bug 336261
( https://bugs.launchpad.net/bugs/336261 )
I added this here because these two bugs are very similar.
|
|
| 2009-03-01 18:46:28 |
Jersey |
description |
Binary package hint: gnome-network
After a fresh install of Dapper, the '/etc/hosts' file looks like this:
127.0.0.1 localhost
127.0.1.1 computername
...
If I rename the computer to 'newname' using 'System-->Administration-->Networking', the file looks like this:
127.0.0.1 localhost newname
127.0.1.1 computername
Obviously, it should be:
127.0.0.1 localhost
127.0.1.1 newname
This causes all sorts of nasty problems.
In 8.04 Rev.2 There are similar problems, after changing the domain, the entries are not correctly updated in the "hosts" and "hostnames" files. For details see bug 336261
( https://bugs.launchpad.net/bugs/336261 )
I added this here because these two bugs are very similar.
|
Binary package hint: gnome-network
After a fresh install of Dapper, the '/etc/hosts' file looks like this:
127.0.0.1 localhost
127.0.1.1 computername
...
If I rename the computer to 'newname' using 'System-->Administration-->Networking', the file looks like this:
127.0.0.1 localhost newname
127.0.1.1 computername
Obviously, it should be:
127.0.0.1 localhost
127.0.1.1 newname
This causes all sorts of nasty problems.
In 8.04 Rev.2 There are similar problems, after changing the domain, the entries are not correctly updated in the "hosts" and "hostnames" files. For details see bug 336261
I added this here because these two bugs are very similar.
|
|
| 2009-03-01 18:55:21 |
Jersey |
description |
Binary package hint: gnome-network
After a fresh install of Dapper, the '/etc/hosts' file looks like this:
127.0.0.1 localhost
127.0.1.1 computername
...
If I rename the computer to 'newname' using 'System-->Administration-->Networking', the file looks like this:
127.0.0.1 localhost newname
127.0.1.1 computername
Obviously, it should be:
127.0.0.1 localhost
127.0.1.1 newname
This causes all sorts of nasty problems.
In 8.04 Rev.2 There are similar problems, after changing the domain, the entries are not correctly updated in the "hosts" and "hostnames" files. For details see bug 336261
I added this here because these two bugs are very similar.
|
Binary package hint: gnome-network
After a fresh install of Dapper, the '/etc/hosts' file looks like this:
127.0.0.1 localhost
127.0.1.1 computername
...
If I rename the computer to 'newname' using 'System-->Administration-->Networking', the file looks like this:
127.0.0.1 localhost newname
127.0.1.1 computername
Obviously, it should be:
127.0.0.1 localhost
127.0.1.1 newname
This causes all sorts of nasty problems.
Bugs reporting the same or similar : bug 48216 bug 239089 bug 229256 bug 336261
Also 8.04 r2 LTS is affected.
|
|
| 2009-03-01 19:01:24 |
Jersey |
title |
renaming computer does not work properly |
renaming computer does not update hosts, hostnames |
|
| 2009-03-01 19:02:11 |
Jersey |
title |
renaming computer does not update hosts, hostnames |
renaming computer does not update correctly the files: hosts, hostnames |
|
| 2009-03-01 19:33:57 |
Jersey |
description |
Binary package hint: gnome-network
After a fresh install of Dapper, the '/etc/hosts' file looks like this:
127.0.0.1 localhost
127.0.1.1 computername
...
If I rename the computer to 'newname' using 'System-->Administration-->Networking', the file looks like this:
127.0.0.1 localhost newname
127.0.1.1 computername
Obviously, it should be:
127.0.0.1 localhost
127.0.1.1 newname
This causes all sorts of nasty problems.
Bugs reporting the same or similar : bug 48216 bug 239089 bug 229256 bug 336261
Also 8.04 r2 LTS is affected.
|
Also 8.04 r2 LTS is affected.
Binary package hint: gnome-network
After a fresh install of Dapper, the '/etc/hosts' file looks like this:
127.0.0.1 localhost
127.0.1.1 computername
...
If I rename the computer to 'newname' using 'System-->Administration-->Networking', the file looks like this:
127.0.0.1 localhost newname
127.0.1.1 computername
Obviously, it should be:
127.0.0.1 localhost
127.0.1.1 newname
This causes all sorts of nasty problems.
Bugs reporting the same or similar : bug 48216 bug 239089 bug 229256 bug 336261
|
|
| 2009-08-20 13:29:38 |
Milan Bouchet-Valat |
gnome-system-tools (Ubuntu): status |
Confirmed |
Fix Released |
|
