Feisty: Keyboard and Gnome freezes with Network Manager

I should also mention that I was unable to ctrl-alt-num to any other terminals, or to shut down the computer normally (though the log says it received a shutdown signal)

This happened again today - I'm now running NetworkManager in --no-daemon mode to see if I can catch the crash.

So, the last line from NetworkManager is always:

NetworkManager: <information> wpa_supplicant(8496): WPA: Association event - clear replay counter
NetworkManager: <information> wpa_supplicant(8496): EAPOL: External notification - portEnabled=0
NetworkManager: <information> Activation (eth1) failed.
NetworkManager: <information> Deactivating device eth1.
sendmsg(CTRL_IFACE monitor): No such file or directory
sendmsg(CTRL_IFACE monitor): No such file or directory
sendmsg(CTRL_IFACE monitor): No such file or directory
rmdir[ctrl_interface]: No such file or directory

I'm going to file a new bug under NetworkManager, because I seem to be talking to myself!

I don't seem to be able to file a bug under NetworkManager! Maybe I need to file a bug about that...

Here's another clue:
netstat becomes a zombie proc after NetworkManager loses the AP the first time...

Yup, still a bug... is there an annual "bug day" when somebody looks at these?

Bug still in effect.

I wonder if this bug will disappear magically under Gutsy?

I tried to post a comment a while back but ironically my computer froze while doing so. I have exactly the same problem as you. The easiest way I've found to avoid the problem is to quickly turn off roaming and set network manager to a manual configuration. That often means I have to run dhclient myself every time the connection dies but at least I can keep my system up.

I posted more details here: http://ubuntuforums.org/showthread.php?p=4516727

Rob,

The problem is much improved under Gutsy, though Network Manager still has a
hard time in situations with multiple AP to one network. Like you said, I
just have a manual setting for campus use now. At least it (almost) never
locks up now.

On Fri, Mar 14, 2008 at 9:04 PM, Rob Van Dam <email address hidden> wrote:

> I tried to post a comment a while back but ironically my computer froze
> while doing so. I have exactly the same problem as you. The easiest
> way I've found to avoid the problem is to quickly turn off roaming and
> set network manager to a manual configuration. That often means I have
> to run dhclient myself every time the connection dies but at least I can
> keep my system up.
>
> I posted more details here:
> http://ubuntuforums.org/showthread.php?p=4516727
>
> --
> Feisty: Keyboard and Gnome freezes with Network Manager
> https://bugs.launchpad.net/bugs/138969
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
------------------------------------------------------------------------------
http://severnclaystudio.wordpress.com

i think there has been done a lot of work concerning network-manager. is this still a problem with hardy?

I'm not on campus very often anymore so I can't test this easily now. However, I can say that upgrading to Hardy did NOT eliminate the problem. I cannot however speak for any updates to network-manager since the initial hardy release because I just haven't be in a situation to test it recently.

according to upstream bug this is fixed.