Hi Mathieu, This doesn't quite match the behavior I've seen. Observable behavior is this:
When I first log in after a reboot, I see the nm applet and the little pulsing volcano lines, then it connects to my ap, does its dhcp and gives me the correct ip address. I can access my network just fine. Then after a while, the applet simply disappears and there's no other indication of a problem, except that ifconfig will show that the ip address has reverted to the 10. address. Now the thing is that this "applet disappearing act" can happen at different times. Sometimes the applet (and proper ip address) can stay up for hours after first login after reboot. Other times, it goes away almost immediately. In all cases though I do see the notification popup that it's connected to the proper ssid. Just sometimes the applet crashes immediately and sometimes it stays up for minutes or hours. I haven't correlated the applet crash to any specific system or network activity. Usually the machine is just sitting there idle when the applet crashes. Note that once the applet has crashed, nothing short of a reboot will revive the wireless connection. I am in the classic (no effects) gnome session because unity and compiz have had some severe problems lately. I see some updates to compiz have landed, so I'll plug in a wired ethernet (which *always* works, even when the applet has crashed), do an update, reboot and see what that side looks like. I'm of course happy to help debug or investigate in any way that's helpful. Feel free to ping me on irc again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/710711 Title: NetworkManager crashed with SIGABRT in raise() -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
