[gutsy] networkmanager crashes when trying to access a wpa-enterprise or open network

Bug #145134 reported by SeG
2
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: network-manager

I toyed around a little and found out that when the networks signal quality is too poor like 30 or so the networkmanager does not only not connect to this network it crashes. The only thing the user sees is that the nm-aplet is missing all of a sudden and you have no chance to access a network any more.

I hade to restart the NetworkManagerDispatcher and the NetworkManager to get it going again.

this is what dmesg gave me:
[11474.322290] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command.
[11477.562885] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command.
[ 4318.635427] ADDRCONF(NETDEV_UP): eth1: link is not ready
[11542.542283] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[11553.595261] eth1: no IPv6 routers present

By the way I am using a freshly installed feisty which I upgraded to gutsy and the rt kernel

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

What is the 'rt' kernel? Can you please attach your /var/log/syslog as well?

Changed in network-manager:
status: New → Incomplete
Revision history for this message
SeG (razahel) wrote :

With rt I meant the realtime kernel for gutsy.
I excerpted the part from my syslog and attached it. I have noticed that the NetworkManager also crashes after several hours of connection to my WPA Enterprise network.

Revision history for this message
SeG (razahel) wrote :

Here is also the new syslog which recorded when NetworkManager crashed after a while running

Revision history for this message
SeG (razahel) wrote :

Ohh I nearly forgot to mention,but if I want to change the network I am connected to the NetworkManager takes a long time to react, if it reacts at all.

Revision history for this message
SeG (razahel) wrote :

does sombody still care about this because it is still not fixed?

Revision history for this message
SeG (razahel) wrote :

I did some testing now the Networkmanager does not crash anymore, but it still hangs and the nm-applet takes a long time to update its changes.

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

please test the package mentioned in https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/145683/comments/15

does it fix your experience as well?

Changed in network-manager:
importance: Undecided → Medium
Revision history for this message
SeG (razahel) wrote :

nice!

with the 3 files from your repo the networkmanager shows quicker when you want to switch networks.
The only thing is I right now cannot switch from WPA network to WPA-enterprise (802.1X) I attached the syslog

Revision history for this message
SeG (razahel) wrote :

I now use only die network-manager dep from alexanders repo link and the updated packages in the standard repo and everything right now seems to work fine!

As of now everything works well enough! :)

Revision history for this message
SeG (razahel) wrote :

Hmm ok the problem now is, when the connection to network has a poor quality my X freezes.

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
do you still experience this issue with the current version of the application?, could you please try to reproduce this using the live environment of the Desktop CD of the development release - Hardy Heron.

Thanks in advance

Changed in network-manager:
assignee: nobody → sourcercito
Revision history for this message
Brett Howard (brett-livecomputers) wrote :

How does your X freeze? Is it actually X that freezes or is it gnome and the gnome-panel? I think this sounds quite similar to my experience that I have under bug 211471.

https://bugs.launchpad.net/bugs/211471

Revision history for this message
Brett Howard (brett-livecomputers) wrote :

I should add that I'm using hardy and an ipw2200

Revision history for this message
Brett Howard (brett-livecomputers) wrote :

I believe it may not be network-manager that is crashing but nm-applet. I find that I'm actually connected to the network but gnome seems to be out to lunch. I find that the new map built into the time applet seems to send gnome equally out to lunch when it hangs up.

Changed in network-manager:
assignee: sourcercito → nobody
Revision history for this message
Alexander Sack (asac) wrote :

NM 0.7 has better support and most likely doesnt crash here anymore. if you still see it, please reopen.

Changed in network-manager:
status: Incomplete → Invalid
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.