On 2012-03-30 10:44:07 -0700, Russ Allbery wrote: > Vincent Lefevre <vinc...@vinc17.net> writes: > > On 2012-03-29 13:07:56 -0700, Russ Allbery wrote: > > >> Well, it seems like you should file bugs if you can, because a lot of > >> these are not universal problems and therefore probably aren't known > >> issues. > > > I did several months ago: > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637267 > > This is the one that no one else who's using wicd seems to be able to > duplicate. I agree with other people that this is probably something > specific to your hardware.
It could be related to many things (in particular configuration), but the problem is purely software, as seen in the logs. > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638591 > > I don't think your diagnosis of this is correct, in that I don't think > wicd is what's doing this. I was getting things like that with Network > Manager as well, and usually rebooting my wireless router makes this > behavior stop. I always wrote this one off to crappy consumer wireless > routers, which have all sorts of strange failure modes when they're not > rebooted regularly. The router may be a bit bad, but the kernel apparently could handle it, and that's wicd that chose to force the disconnection. So, this is a 100% wicd bug. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120330231642.gv9...@xvii.vinc17.org