Comment 7 for bug 140763

Revision history for this message
Johannes Schmid (jhs.schmid) wrote : Re: NetworkManager is unreliable after resuming from suspend

First, let me be a bit more specific about the "takes ages to connect thing":
In Feisty, nm reconnect that fast that usually after I typed in my password to unlock the screen it had reconnected.
In Gutsy, more than half of the time, the network manager displays a "connected" icon after resume though it is not connected and otherwise it displays a "not connected" icon for ~15 seconds and start to reconnect after that time. Sometimes (read too often) it should crashes and I have to restart nm manually.

After todays update, I had the problem that nm would instantly crash when trying to connect to a wireless with a saved password in keyring manager. Deleting the key and trying some restart eventually solved this but it is really not as nice as it was in feisty.

Please tell me if I can help you with this bug by installing debugging symbols, using gdb, doing other weird things, etc.