To help others who may have this issue, and to help developers debug it, I strongly encourage you to post that your initial results using my suggested fixes made at least *some* progress:
"Ok. That worked, partially. The NetworkManager applet now shows my router and several other networks. However, it doesn't connect. The applet spins for a while and then the laptop hangs. The keyboard is unresponsive. I have to remove the battery in order to reboot. This doesn't happen with a wired connection." At the very least, this gives developers some notion about what is or is not broken: kernel modules, hal, dbus, or NetworkManager. Please rework your comments above and append it to the bug report. Thanks! Brett On 4/9/07, Brett Clippingdale <[EMAIL PROTECTED]> wrote: > Hmm, not good. > > I did a fresh install of Feisty Beta a week ago, and I have to say > I've seen the keyboard lockup recently (perhaps the past few days) > connecting to non-WEP networks. Actually, keyboard/mouse both lock, > even the Gnome system monitor applet meters freeze. > > I've just moved over to Ubuntu from FC6 where I used to see this > often, up until about December. Sounds like a regression in Ubuntu > since Beta, not sure why I don't *seem* to get it using WPA. I don't > recall any recent updates to NetworkManager, perhaps this is a dbus > issue? > > Brett > > > On 4/9/07, Acitta <[EMAIL PROTECTED]> wrote: > > I did all of those things already. to make things easier disabled > > encryption on my linksys router. > > However, there is not much I can do because of this keyboard lockup that > > happens. It seems to be only the keyboard. I can navigate with the mouse > > but am unable to do a shutdown. The keyboard is completely unresponsive. > > This is only happening when NetworkManager is trying to connect to the > > wireless. It doesn't happen with a wired connection. It happens both > > under Gnome and XFCE. This only started this morning, so I wonder if > > something that got upgraded today is causing the problem. > > > > Another thing I don't quite understand: under 6.10, the wireless > > interface was eth1. When I upgraded to Feisty, and first reported this > > bug, the interface was wlan0. Now there is a wifi0 interface created, > > but the system is again connecting to the wireless on eth1. > > > > -- > > Wireless no longer works after upgrade > > https://bugs.launchpad.net/bugs/96532 > > You received this bug notification because you are a direct subscriber > > of the bug. > > > -- Wireless no longer works after upgrade https://bugs.launchpad.net/bugs/96532 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
