** Description changed: Output from requested commands: [danne@danne-fnuttbook] ~/Downloads> nmcli con status - NAME UUID DEVICES DEFAULT VPN - Auto wiberg.nu 00d990e8-dac8-4e7d-b74a-aae85dfea53a wlan0 yes no + NAME UUID DEVICES DEFAULT VPN + Auto wiberg.nu 00d990e8-dac8-4e7d-b74a-aae85dfea53a wlan0 yes no [danne@danne-fnuttbook] ~/Downloads> nmcli dev list GENERAL.DEVICE: wlan0 GENERAL.TYPE: 802-11-wireless GENERAL.DRIVER: brcmsmac GENERAL.HWADDR: 48:5D:60:D1:94:CA GENERAL.STATE: connected CAPABILITIES.CARRIER-DETECT: no CAPABILITIES.SPEED: 72 Mb/s WIFI-PROPERTIES.WEP: yes WIFI-PROPERTIES.WPA: yes WIFI-PROPERTIES.WPA2: yes WIFI-PROPERTIES.TKIP: yes WIFI-PROPERTIES.CCMP: yes AP1.SSID: 'TN_private_A394FY' AP1.BSSID: 90:84:0D:F0:1D:81 AP1.MODE: Infrastructure AP1.FREQ: 2442 MHz AP1.RATE: 54 MB/s AP1.SIGNAL: 32 AP1.SECURITY: WPA AP1.ACTIVE: no AP2.SSID: 'TROSKVERK12' AP2.BSSID: 00:14:6C:78:8E:32 AP2.MODE: Infrastructure AP2.FREQ: 2462 MHz AP2.RATE: 54 MB/s AP2.SIGNAL: 35 AP2.SECURITY: WEP AP2.ACTIVE: no AP3.SSID: 'mickeHemma' AP3.BSSID: 00:1F:33:42:91:FB AP3.MODE: Infrastructure AP3.FREQ: 2417 MHz AP3.RATE: 54 MB/s AP3.SIGNAL: 45 AP3.SECURITY: WPA WPA2 AP3.ACTIVE: no AP4.SSID: 'wiberg.nu' AP4.BSSID: 68:EF:BD:FC:D3:21 AP4.MODE: Infrastructure AP4.FREQ: 2447 MHz AP4.RATE: 54 MB/s AP4.SIGNAL: 85 AP4.SECURITY: WPA2 AP4.ACTIVE: yes IP4-SETTINGS.ADDRESS: 192.168.242.23 IP4-SETTINGS.PREFIX: 24 (255.255.255.0) IP4-SETTINGS.GATEWAY: 192.168.242.1 IP4-DNS1.DNS: 192.168.243.12 IP4-DNS2.DNS: 8.8.8.8 GENERAL.DEVICE: eth0 GENERAL.TYPE: 802-3-ethernet GENERAL.DRIVER: atl1c GENERAL.HWADDR: BC:AE:C5:A4:59:09 GENERAL.STATE: unavailable CAPABILITIES.CARRIER-DETECT: yes CAPABILITIES.SPEED: unknown WIRED-PROPERTIES.CARRIER: off - ProblemType: Bug - DistroRelease: Ubuntu 11.10 + ProblemType: BugDistroRelease: Ubuntu 11.10 Package: checkbox 0.12.8 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 CheckboxSubmission: 996d1de4f6d61b166432b4fc30b66f28 CheckboxSystem: 9c26adf6eed2f681ba41f94dd24c07e4 - Date: Tue Oct 18 23:24:44 2011 - InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) - SourcePackage: checkbox + Date: Tue Oct 18 23:24:44 2011InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)SourcePackage: checkbox UpgradeStatus: No upgrade log present (probably fresh install) + + [Impact] + Under certain cases (such as the reported one, where a VPN and the wireless connection had the same name) the connect_wireless script can become confused and attempt to bring up the non-wireless connection. This obviously makes the wireless tests fail even though the wireless connection may be working fine. Wireless is considered important for portable systems, so this will also wrongly and negatively affect the Ubuntu Friendly ratings of systems. + + [Development fix] + Checkbox revision 1113 fixes this by including the connection types when calling "nm con list" and then grepping to select only the ones with type "wireless". + + [Stable fix] + This is fixed in http://bazaar.launchpad.net/~checkbox-dev/checkbox/trunk/revision/1113. Also, the linked branch (https://code.launchpad.net/~roadmr/ubuntu/oneiric/checkbox/0.12.9) contains this and other fixes and merges cleanly against Ubuntu checkbox 0.12.8. + + [Test case] + - Configure a wireless and wired connections so that the name as returned in "nmcli -t -f NAME,TYPE con list" is the same for both. + - Ensure that the system is connected through wireless and the wired connection is not active (disconnect the cable). + - run /usr/share/checkbox/connect_wireless + + Expected result: + - All connections are brought down, and the wireless connection is re-brought up. End result: only wireless is connected. + + Actual result: + - All connections are brought down, and nothing is brought back up (though an attempt will be made to wrongly activate the ethernet connection). + + [Regression potential] + An attempt to bring up an ethernet connection would fail anyway, so even if we find no wireless connections when we previously found at least one (potentially not wireless) connection (which would result in a failed test either way) this doesn't regress from a previous, known-good behavior. + + About the only possible regression case is if the output of nmcli con + list ever returns wireless connections with a type other than + "wireless", as they will then not be picked up by the grep section of + the script, where previously they were picked up.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/877752 Title: connect_wireless can unintentionally choose a non-wireless connection to connect to To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox/+bug/877752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
