Comment 14 for bug 121228

I also thought originally that this is a network-manager issue, but it's actually gnome-keyring who's at fault here. gnome-keyring and libgnome-keyring0 were recently upgraded in gutsy to 2.19.4.1 from 0.8.1. The latest network-manager from gutsy works great with the old version, but breaks down completely for me with the new one. Even when I applied a workaround mentioned here, wireless connections only lasted a few seconds before breaking up, and network-manager was segfaulting constantly.

So, I went to packages.ubuntu.org, downloaded libgnome-keyring0 and gnome-keyring for feisty, and downgraded them. Everything is back to normal now.

Some of the symptoms of network-manager 0.6.5's differences in communication between keyring 0.8.1 and 2.19.4.1. When I login, I'm normally prompted for my keyring password only. With the latest gutsy version 2.19.4.1, I was instead prompted to "Deny, Allow once, Allow always" for nm-applet. network-manager would then crash. It only "worked" when I had keyring-manager application open at the same time, and even then it would try to connect unsuccessfully for a long time or connect and then crash or disconnect immediately. I'm using WPA2 PSK (AES) with Atheros non-GPL driver (madwifi).