nm-applet randomly(?) becomes non-responsive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: network-manager
running an up to date Gutsy (as of oct 17,2007)
for a wireless driver, I'm using ndiswrapper and networkmanager 0.6.5
NetworkManager and nm-applet work fine most of the time, but once in a while (about once a day over the last week) nm-applet will do this thing where it becomes totally non-responsive. I only notice it when I'm moving around at work and want to switch access points. The first symptom I usually notice is that the network list fails to update to show networks I know I should be seeing. Even after waiting up to 10 minutes for it to get around to it. Once I've seen that I know I'm in trouble but at that point the applet fails to respond to anything I do. Right clicking and left clicking still show their menus, but the options in them fail to elicit a response. I can disable wireless and wired networks and the checks clear but the icon doesnt go to the alert icon it normally would. I can select a different network but it doesn't even try to update them.
Now, I can sometimes recover from this by killing and restarting the nm-applet and NetworkManager applets, but not always. Sometimes it appears to recover and keeps trying to connect to a known networks, but just keeps asking for the key instead of connecting. Other times, it just acts as non-responsive as it did before.
I can always connect using iwconfig and dhclient when NetworkManager is acting up, which makes me pretty sure thats the problem is isolated to NetworkManager.
I'll have a syslog attachment up shortly.
heres my syslog from today. The time it started failing was around 2 pm. Then theres some stuff later from around 6 that was me trying to start it and get it to connect when I got home from work. The earlier stuff was after a clean boot without suspending, I suspended it on the way home, then tried the later stuff.
I did have one thought though, is it possible for laptop mode to mess with it? I have it enabled and when it stopped working was close to a time i plugged it in after having it unplugged for a while, though it wasn't the first time I unplugged it today.