desktop-packages team mailing list archive

[launchpadmember <43379@xxxxxxxxxxxxxxxxxx>]

I can also confirm that this bug still seems to be present in v11.04
Natty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/43379

Title:
  nm-applet vanished, disappears from tray

Status in NetworkManager:
  Invalid
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “network-manager-applet” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Arch Linux:
  New

Bug description:
  Evaluation:
  There are two known reasons why nm-applet can disappear from system tray:
   1. network-manager-applet crashes by itself
   2. network-manager becomes unavailable (aka it crashes).

  Please don't post additional information and logs to this bug if you
  experience any of the two cases above ... and file a *new* bug against
  the  packages.

  So when nm-applet has disappeared, check whether
   1. ps -eaf | grep nm-applet
   2. ps -eaf | grep NetworkManager | grep -v NetworkManagerDispatcher

  yield any results. If nm-applet isn't running, file a bug against network-manager-applet package; in case NetworkManager isn't running, please file a bug against network-manager and attach your daemon.log/syslog.
  We (the bug triagers) will then try to find the appropriate duplicate and ask for more info if needed.

  
  ----------- Original Summary

  Binary package hint: network-manager-gnome

  The Actors:
    Fire  -- the stalwart DHCP server running Debian Stable (Sarge)
    Dib   -- the noble laptop and DHCP client, possessing a heart of gold
    and an instance of nm-applet.  Dib runs the latest Dapper (May 5th
    2006) running nm-applet version 0.6.2-0ubuntu5.
    Christian -- the mad scientist

  The Scene:
    A dark and stormy night.  
    Fire has already given Dib a dynamic IP addressed based on his wifi
    MAC address.
    Christian wants to make Dib's IP static when Dib is connected via wifi.

  What Happened:
    Christian, sitting at his laptop, Dib, starts to edit the Fire's
    DHCPd configuration remotely via SSH.  He sets Dib's wifi MAC
    address to return the same IP as the wired MAC does.

    Christian restarts the DHCP server. The next time Dib asks the DHCP
    server what it's IP address is, it will change from .189 to .16

    A few minutes later, Dib sends the DHCP request.  All the SSH
    connections freeze (as expected) and the nm-applet shows its
    reconnecting to the network.  As nm-applet gets to the end of its
    reconnect cycle, when it should have shown the wifi bars again, it
    vanishes.

    Christian confirms that nm-applet is still running.  Christian tries
    to restart nm-applet, but to no avail... Christian checks the
    network, it is correctly configured, but nm-applet has lost its
    mind.

    A complete reboot is required to make nm-applet work again.

  What was Expected:
    It should have "Just Worked". 

  Conclusion:
    nm-applet or network-manager didn't deal very well with the same
    network connection handing out a new IP address, even though this is
    acceptable DHCP behavior.

    Also, Christian gets into strange moods at time and submits bug
    reports with a bizarre sense of humor.  But at least the reports are
    proof-read.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/43379/+subscriptions