network manager crashes when /etc/network/interfaces is touched [race]

Bug #141106 reported by laksdjfaasdf
8
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Gutsy alpha + current updates:

Description:

When clicking on "Manual configuration..." in network-manager applet, the nm-applet icon sometimes disappears from panel. That means there is no way to go back to automatic network configuration with network-manager.

But even if icon of manual network config tool appears in panel, there is no graphical way to get back the automatic network configuration with nm-applet.

Expected behavior:

After clicking manual configuration, there should appear the manual network config applet icon with an option to switch back to network-manager with one click.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in network-manager.

Revision history for this message
Alexander Sack (asac) wrote :

so what is the problem here? Does the nm-applet completely disappear? If that happens is the NetworkManager process still running? Maybe it crashed?

Changed in network-manager:
status: New → Incomplete
Alexander Sack (asac)
Changed in network-manager:
status: Incomplete → Confirmed
Alexander Sack (asac)
Changed in network-manager:
importance: Undecided → High
status: Confirmed → Fix Committed
Revision history for this message
laksdjfaasdf (laksdjfaasdf) wrote :

Ok, seems you could reproduce the problem. I insert the steps nevertheless:

Steps to reproduce:

I have Network-manager running with icon in panel. I get an IP address through DHCP from a router.

1. Click on Network-Manager applet
2. Choose "Manual Configuration"
3. Click on properties of your wired connection
4. Disable "Enable roaming mode"
5. Choose > Configuration > Static IP address
6. Choose some static address, subnet mask and gateway and click OK
7. Next click on tabs "General", "DNS", "Hosts" in Network settings dialog

Results:

- nm-applet DISAPPEARS from panel but it's still in memory:

1003 13785 0.1 0.9 55216 14672 ? S 11:26 0:00 nm-applet --sm-disable

- It seems that manual network changes are not accepted and IP address stays the same.

Expected behavior:

nm-applet should stay in panel so that there is the possibility to change back to roaming mode.

Revision history for this message
Alexander Sack (asac) wrote :

network-manager (0.6.5-0ubuntu13) gutsy; urgency=low

  * debian/patches/20_do_not_take_over_dhcpv4iface_when_v6_is_configured.patch:
    fix race/null-deref crash that happens if /e/n/i is not completely flushed out
    by editor/network-admin (LP: #141106).
  * debian/patches/41v_lp141233-fix-supplicant-cleanup-crashes.patch: Add patch
    for LP: #141233 - fix crash by not sending ctrl commands to supplicant if no ctrl
    socket is open.
  * debian/patches/series: add new patch to quilt series
  * debian/patches/41t_nm_device_wireless_index_ctrl_sockets_by_run_count.patch:
    use two distinct variables to track and check connect attempt count to
    supplicant and global supplicant socket. Fix bug that prevented network
    manager from attempting to connect to supplicant ctrl for cases where
    global control already took a long time to succeed. (LP: #141233).
  * debian/patches/41t_nm_device_wireless_index_ctrl_sockets_by_run_count.patch:
    close global ctrl socket connection when nm_utils_supplicant_request_with_check
    failed.
  * debian/patches/41u_custom_timeout_for_some_wpa_ctrl_operations.patch: update patch
    because of overlapping change with 41t_* patch.

 -- Alexander Sack <email address hidden> Fri, 21 Sep 2007 11:26:01 +0200

Changed in network-manager:
status: Fix Committed → Fix Released
Revision history for this message
oliver (oliver-schinagl) wrote :

So ... how do you re-enable automatic configuration?

I have the same issue (albeit not dissapearing icon).

I had to temporarly assign a fixed address to my NIC, so i disabled roaming mode (thats the checkbox above the selector to choose DHCP/Static/Zeroconf right? got a dutch version here atm :) ) and I could use my manual config. Then I 'fixed' my problem with my router, wanted to use dhcp/automatic again, but can't get either to work. Choosing dhcp without roaming uses the wireless interface (yep the checkbox to use/enable wired is then checked) and if I use roaming, the checkbox gets a dot in it (opposed to a checkmark) but doesn't get used. My wireless is prefered and the wired option isn't available from NM. I do however get a popup saying 'reconfiguring network'.

So ... how do I re-enable automatic configuration? Any file that can be deleted to reset it?

Revision history for this message
A. Villaveces (avillavecesn) wrote :

Hi,

same issue here, but the icon is not disappearing. It only loses all the ability to see the wireless networks and *only* gives the option of manual configuration. (If I click on "manual configuration" I am led to the old network manager - it works, but too many roundabouts.

How do I re-enable automatic configuration? Any file that can be deleted to reset it?

Thank you!

Revision history for this message
Matt Wilkie (maphew) wrote :

I have the same problem as Oliver and A.Villaveces, I used manual configuration while troubleshooting a network problem and now I'm stuck in manual mode and can't see the list of available wireless networks, even after re-enabling roaming mode. How do we get automatic mode turned back on?

Revision history for this message
Matt Wilkie (maphew) wrote :

ok, I have automatic wireless back. Following a comment on Linux.com[1], I changed both the wired and wireless networks to roaming mode and then rebooted. Voila! I can now see all the wireless networks in my vicinity. Before rebooting I tried simply logging off and back on again but that didn't change anything. I suspect that rebooting was the key, that I didn't need to change the wired network to roaming also, but I'm not about to test it now as I don't want to break it again.

[1] "The missing step" by Anonymous
http://www.linux.com/?module=comments&func=display&cid=1163952

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.