On Tue, 27 Sep 2011 12:05:38 +0000 Michael Biebl <bi...@debian.org> wrote:
> On 27.09.2011 02:29, clayton wrote: > > Package: network-manager > > Version: 0.9.0-2 > > Severity: important > > > > On my Debian Testing system, I just did a routine daily upgrade and > > saw a new network-manager come down. Thereafter, I could not > > connect to my WPA wireless access point, even after a reboot. I > > upgraded my wpasupplicant to a newer version available in unstable, > > ie. > > > > Preparing to replace wpasupplicant 0.7.3-3 (using > > ..../wpasupplicant_0.7.3-3.1_i386.deb) ... > > > > and my ability to connect to my access point was immediately > > restored. I believe network-manager needs to require the newer > > version of wpasupplicant. > > The minimum required dependency on wpasupplicant should be > sufficient. I suspect wpasupplicant is a red herring. > > Please downgrade wpasupplicant again, reboot your system, then send > me a debug log following the instructions at [1] . To increase the > verbosity, you can use the --log-level=DEBUG command line parameter. > > [1] http://live.gnome.org/NetworkManager/Debugging Hi Michael, Strangely enough, after downgrading wpasupplicant and rebooting twice, I was unable to reproduce the problem. (Note that I did try a reboot before sending the original bug report.) I have attached the syslog for what I believe to be the moment when I updated shortly after turning on the machine this morning. Note the last two lines when wlan0 because "unavailable" and "inactive". Clayton
syslog
Description: Binary data
