failure modifying /etc/hosts on NM profile change

Bug #196000 reported by Thelema
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Low
Unassigned

Bug Description

(Submitted this bug to NetworkManager bug tracker, and they say it's an Ubuntu program that touches /etc/hosts)

Using Ubuntu 7.10 amd64

When using NM to change from one profile to another, after a few changes, first
Mozilla stops being able to resolve hostnames (even though the network works
and I can resolve hostnames from the command line) and then my session dies.
The intervening issues don't have to do with NM, so I'll report them to the
glibc people (it turns out that having a line in /etc/hosts that's >3,000
characters causes important things to segfault), but I blame NM for causing
that 3000+ character line in my /etc/hosts file. If you really need it, I can
push NM to breaking things again (this has happened twice when messing with
profiles), so I can post the broken hosts file. I attach my fixed hosts file,
with [[*]] indicating where the previous word was repeated ~350 times and
followed by ~700 empty lines:

127.0.0.1 localhost
127.0.1.1 thelema-laptop

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

72.151.208.234 philwall [[*]]
192.168.0.2 sampo

Thanks for looking into this.

Revision history for this message
Joseph Piché (josephpiche) wrote :

Thank you for reporting this bug. Can you please post the exact steps taken to reproduce this bug, then also post the resulting /etc/hosts file.

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Joseph Piché (josephpiche) wrote :

Also, if you could please add /var/log/syslog to this report after you post the steps to reproduce the bug. For more information please see https:/wiki.ubuntu.com/DebuggingNetworkManager.

Thanks.

Revision history for this message
Basilio Kublik (sourcercito) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks again!

Changed in network-manager:
importance: Undecided → Low
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.