Yes, Quantal doesn't connect and must be manually connected through system settings, even though it remembers the network name, encryption, etc. When it boots up, where it should connect, it says "disconnect" which does show up in the many many messages from network manager on the syslog. Once network manager (or the kernel, I wouldn't know) asks for authenticate it goes right through.
Since Raring is all setup to recognize hidden wireless, the network, and the encryption key it should try that first off. Instead it seems to do a knee jerk disconnect and then never even tries to connect with the information it already has. Where is the spot in the nm script that says go do the connect and authenticate? Why isn't it being issued? Let me go check Precise again. I usually run Raring but do have backup Quantal and Precise partitions. Thanks for looking at this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA Status in “network-manager” package in Ubuntu: Incomplete Bug description: On Acer Aspire 1, Intel Corporation Centrino Wireless-N 1000 [Condor Peak, and on Acer 5253 Broadcom BCM 43225 automatically disconnect from hidden wireless WPA and I have to mouse select the NM applet, choose the only network available, then connect using the already saved encryption key. Ubuntu 12.04.1 and Mint14 connect automatically instead of disconnecting automatically like Raring does. Attached is syslog.1 showing the disconnect, do a gedit and search on disconnect. Manuall connect (to report the bug) then follows. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201211131441.e9e2c56-0ubuntu3 ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0 Uname: Linux 3.7.0-7-generic i686 ApportVersion: 2.7-0ubuntu2 Architecture: i386 Date: Mon Jan 7 14:06:28 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-27 (41 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20121127) IpRoute: default via 192.168.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.5 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1 2544f4e0-61c6-477a-8993-21942972660b 802-3-ethernet 1357585406 Mon 07 Jan 2013 02:03:26 PM EST yes no /org/freedesktop/NetworkManager/Settings/1 LAUREL 0ac07da4-a668-48e4-93fa-5d6db993ad47 802-11-wireless 1357585580 Mon 07 Jan 2013 02:06:20 PM EST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0 connected enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1097002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
