On Thu, 2007-10-11 at 12:47 -0400, Bill Peck wrote: > Joel Goguen wrote: > > I have a need for it, and I imagine it's a common one. I have a > > wireless network at home, and I put the laptop to sleep and head to my > > university. When I get there, I have to wait sometimes minutes for > > the list to refresh and my campus network to appear so NM can attempt > > to connect to it. Or I can open a terminal and manually restart NM, > > but that's not something a common user should be expected to do IMO. > > When I first get to campus I still see all the networks I can see from > > my house, even though none of them are anywhere near the campus. > > After a few minutes of waiting, during which I'm checking the applet > > list at least once every 30 seconds, the list finally refreshes and NM > > connects to my campus network. This doesn't seem very user-friendly > > to me. > > > > What distro are you using? I put my laptop to sleep between work and > home and it connects to each network right away when it wakes up. > > I've never had a problem, both with Fedora 6 and 7. Ubuntu. This occurred both with Feisty and with the latest Gutsy beta. A few times, daemon.log shows that NM crashed with signal 11 (SIGSEGV, segmentation fault) and then the crash manager tries to say it crashed with signal 5. -- Joel Goguen http://jgoguen.net/ The human mind treats a new idea the way the body treats a strange protein -- it rejects it. -- P. Medawar
Attachment:
signature.asc
Description: This is a digitally signed message part