NM doesa handle hostnames more gracefully now. howver, i think in your
case the hostname was updated by something else (e.g. an ifup.d hook or
resolvconf or ppp or dhcp).
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Invalid
--
NetworkManager fouls up /etc/hosts
I messed around with network-admin until the problem stopped happening,
so I took some time today to try and reproduce the problem again. I kept
notes about what I was doing, which I've attached.
The short version is:
- In roaming mode, NetworkManager (well, network-admin, but I suspect they're
You reported this bug a while ago and there hasn't been any activity in
it recently. We were wondering is this still an issue for you? If you
still have this issue please add /var/log/syslog after you reproduced
your bug to this report. For more information please see
** Changed in: network-manager (Ubuntu)
Status: New = Incomplete
--
NetworkManager fouls up /etc/hosts
https://bugs.launchpad.net/bugs/185280
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Open NetworkManager and check what is in the General -- Domain Name
field.
--
NetworkManager fouls up /etc/hosts
https://bugs.launchpad.net/bugs/185280
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
It looks much like this:
Host Settings
Host name: deacon
Domain name: thristian.org
--
NetworkManager fouls up /etc/hosts
https://bugs.launchpad.net/bugs/185280
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
** Changed in: network-manager (Ubuntu)
Sourcepackagename: None = network-manager
--
NetworkManager fouls up /etc/hosts
https://bugs.launchpad.net/bugs/185280
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
