Comment 23 for bug 291760

OK - I've got some good news and some bad news. The good new is that I
created a usb key of Jaunty alpha 4 to test, and as far as I could tell,
the problem did not occur. My wireless connection did drop out
periodically, but that actually *did* seem like a driver issue (when it
died, it went completely out, and it was intermittent. You could set
your watch by the problem I'm having in intrepid.)
The bad news is that, in the interest of science, I installed the latest
jaunty packages of network-manager, network-manager-gnome,
wpasupplicant, and a handful of other packages I needed to satisfy
dependencies on my intrepid setup. Unfortunately, the problem seems to
still occur. I even did remove --purge on the old packages before
installing the new ones.
In other news, I check my friend's setup, and she has the same problem,
but she is using the broadcom wl driver (i'm using intel iwl3945), and
her setup was a fresh intrepid install from 2 months ago.

So, this is really confusing - the fact that I'm running most of the
jaunty software makes it seem like a driver issue, but the problem
occurs across drivers. Could it be a bug further down in the kernel
wireless stack? Any other ideas on how to debug this?

Here's the list of packages I updated:
libgnome-keyring0_2.25.90-0ubuntu1_i386.deb
libnss3-1d_3.12.2~rc1-0ubuntu2_i386.deb
network-manager-gnome_0.7-0ubuntu1_i386.deb
libnm-util1_0.7-0ubuntu1_i386.deb
libxcb-render-util0_0.2.1+git1-1_i386.deb wpasupplicant_0.6.6-2_i386.deb
libnspr4-0d_4.7.3-0ubuntu2_i386.deb
network-manager_0.7-0ubuntu1_i386.deb