Ubuntu
network-manager package

Editing /etc/network/interfaces causes Gutsy 7.10 to crash

Bug #192252 reported by Peter Belew
8
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Ubuntu and kernel version information
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"
Linux cupid 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux

I have Gutsy 7.10 installed in a Averatec 3280 laptop, and have been trying to configure /etc/network/interfaces for various locations, so I can select them either manually or by automatic detection of the networks. (I want fixed IP's or dhcp address detection in various locations, specific ESSID's in some locations, special routing in some locations, etc.) This has worked in earlier versions of Ubuntu, on the same computer.

The problem I am having is that when the interfaces file is written, very often the system crashes with I blank screen. I have tried using ifdown plus stopping the network daemon (/etc/init.d/networking stop) in various combinations, but most of the time the system crashes. This happens either when I edit the file with gedit or vi, or when I edit a copy of the file, then copy it to interfaces.

Right now, what I am doing is adding some lines to /etc/init.d/networking to do that copy in the "start)" case. Then if I stop and start networking the new version of the file will get copied; I have to be careful to shut down the interface in use first.

Obviously, this is not normal behavior, and it makes modification of /etc/network/interfaces very difficult.

Currently, I have a user script to select my wired or wireless connections in the stanzas of /etc/network/interfaces, using statements like

  sudo ifup ath0=ath0-home

to select the required stanza.

Revision history for this message
Peter Belew (peterbe) wrote :

I think this may be related to Bug #129183, which I reported earlier - in that case, I was trying to enable a different wireless card on the same laptop, but with the same result - blank screen.

In any event, for this bug, either it doesn't happen or happens less frequently if I shut down the wireless interface (ifdown ath0) before saving a new /etc/network/interfaces file.

The previous bug involved the built-in ra2500 card, this one has been happening while I was trying to use a Netgear WG511T or WG511TNA card (both designations appear on the box!).

Revision history for this message
Peter Belew (peterbe) wrote :

This problem did not occur under Feisty on the same laptop.

Also, it does not occur on my desktop system, running 6.06 LTS (Dapper) on a Dell PowerEdge 400SC, with two Ethernet NICs.

It appears to be new with Gutsy, from my limited testing.

Revision history for this message
Jonathan Carter (jonathan) wrote :

Does this problem persist in Hardy?

Revision history for this message
Peter Belew (peterbe) wrote : Re: [Bug 192252] Re: Editing /etc/network/interfaces causes Gutsy 7.10 to crash

I have no idea. I subsequently installed Debian on that laptop, and
haven't tried Ubuntu on it since (though I have hardy on four desktop
systems, including a Dell PowerEdge 400SC, with no serious problems).

Peter

On Thu, Oct 2, 2008 at 12:29 PM, Jonathan Carter <email address hidden> wrote:
> Does this problem persist in Hardy?
>
> --
> Editing /etc/network/interfaces causes Gutsy 7.10 to crash
> https://bugs.launchpad.net/bugs/192252
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) 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:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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