Well, good news: I'm pretty sure that it is not n-m that's at fault here. I was using stupid gnome 3 and upon switching to KDE I've found that n-m has no trouble auto-connecting to previously saved connections. Yay.
On Sun, Jan 29, 2012 at 11:55 AM, Garrett McLean <[email protected]> wrote: > Package: network-manager > Version: 0.9.2.0-2 > Followup-For: Bug #645815 > > Just updated to -2 today. When I saw n-m was being updated, I stopped > /etc/init.d/networking, commented out my wlan0 lines in interfaces, > restarted > networking, restarted n-m, configured n-m for my wireless setup (though I > already had a profile in /etc/NetworkManager/system-connections), and > restarted > n-m. It auto-connected! However, when I rebooted, it did not auto-connect. > I > even tried restarting n-m after logging in and still no go. > > Don't know if this helps, but here it is, FWIW. > > Thanks. > > > > -- System Information: > Debian Release: wheezy/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.1.0-1-amd64 (SMP w/8 CPU cores) > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages network-manager depends on: > ii adduser 3.113 > ii dbus 1.4.16-1 > ii isc-dhcp-client 4.1.1-P1-17 > ii libc6 2.13-24 > ii libdbus-1-3 1.4.16-1 > ii libdbus-glib-1-2 0.98-1 > ii libgcrypt11 1.5.0-3 > ii libglib2.0-0 2.30.2-4 > ii libgnutls26 2.12.16-1 > ii libgudev-1.0-0 175-3 > ii libnl-3-200 3.2.3-2 > ii libnl-route-3-200 3.2.3-2 > ii libnm-glib4 0.9.2.0-2 > ii libnm-util2 0.9.2.0-2 > ii libpolkit-gobject-1-0 0.104-1 > ii libuuid1 2.20.1-1.2 > ii lsb-base 3.2-28 > ii udev 175-3 > ii wpasupplicant 0.7.3-6 > > Versions of packages network-manager recommends: > ii crda 1.1.2-1 > ii dnsmasq-base 2.59-4 > ii iptables 1.4.12.2-1 > ii modemmanager 0.5-1 > ii policykit-1 0.104-1 > ii ppp 2.4.5-5 > > Versions of packages network-manager suggests: > pn avahi-autoipd <none> > > -- no debconf information >
