Ubuntu
network-manager package

indicator-network show wifi disabled on a bootstrap install or ota update on 31

Bug #1319906 reported by Dave Morley on 2014-05-15

8

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	network-manager (Ubuntu)	Fix Released	Critical	Mathieu Trudel-Lapierre

Bug Description

Indicator network shows wifi disabled on a fresh bootstrapped install or on an ota update.

Enabling the wifi will aloow it to search and connect to a new network.

On reboot wifi is disabled again on manta and flo but not on mako by the look of it.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: network-manager 0.9.8.8-0ubuntu10
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.2-0ubuntu3
Architecture: armhf
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Thu May 15 15:38:10 2014
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
InstallationDate: Installed on 2014-05-15 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140515.1)
IpRoute:
default via 10.86.112.74 dev rmnet_usb0 proto static
10.86.112.0/24 dev rmnet_usb0 proto kernel scope link src 10.86.112.73 metric 13
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
PciNetwork:

SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 2014-05-15T09:58:23
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
/234308403223936/context3 00f83d8b-6636-7d5d-3266-70a1176b7bff gsm 0 never yes yes /org/freedesktop/NetworkManager/Settings/1
/234308403223936/context1 a12a5a56-2d89-315e-38b0-9d3e8d4fe0e5 gsm 1400168303 Thu 15 May 2014 03:38:23 PM UTC yes yes /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
/ril_0 gsm connected /org/freedesktop/NetworkManager/Devices/1
wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.8.8 connected enabled enabled enabled enabled enabled

Tags:

Revision history for this message

Dave Morley (davmor2) wrote on 2014-05-15:

#1

Dependencies.txt Edit (4.4 KiB, text/plain; charset="utf-8")
IpAddr.txt Edit (3.9 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (1.3 KiB, text/plain; charset="utf-8")
NetDevice.dummy0.txt Edit (154 bytes, text/plain; charset="utf-8")
NetDevice.lo.txt Edit (142 bytes, text/plain; charset="utf-8")
NetDevice.p2p0.txt Edit (255 bytes, text/plain; charset="utf-8")
NetDevice.rev_rmnet0.txt Edit (229 bytes, text/plain; charset="utf-8")
NetDevice.rev_rmnet1.txt Edit (229 bytes, text/plain; charset="utf-8")
NetDevice.rev_rmnet2.txt Edit (229 bytes, text/plain; charset="utf-8")
NetDevice.rev_rmnet3.txt Edit (229 bytes, text/plain; charset="utf-8")
NetDevice.rev_rmnet4.txt Edit (229 bytes, text/plain; charset="utf-8")
NetDevice.rev_rmnet5.txt Edit (229 bytes, text/plain; charset="utf-8")
NetDevice.rev_rmnet6.txt Edit (229 bytes, text/plain; charset="utf-8")
NetDevice.rev_rmnet7.txt Edit (229 bytes, text/plain; charset="utf-8")
NetDevice.rev_rmnet8.txt Edit (229 bytes, text/plain; charset="utf-8")
NetDevice.rmnet0.txt Edit (216 bytes, text/plain; charset="utf-8")
NetDevice.rmnet1.txt Edit (216 bytes, text/plain; charset="utf-8")
NetDevice.rmnet2.txt Edit (216 bytes, text/plain; charset="utf-8")
NetDevice.rmnet3.txt Edit (216 bytes, text/plain; charset="utf-8")
NetDevice.rmnet4.txt Edit (216 bytes, text/plain; charset="utf-8")
NetDevice.rmnet5.txt Edit (216 bytes, text/plain; charset="utf-8")
NetDevice.rmnet6.txt Edit (216 bytes, text/plain; charset="utf-8")
NetDevice.rmnet7.txt Edit (217 bytes, text/plain; charset="utf-8")
NetDevice.rmnet_smux0.txt Edit (232 bytes, text/plain; charset="utf-8")
NetDevice.rmnet_usb0.txt Edit (744 bytes, text/plain; charset="utf-8")
NetDevice.rmnet_usb1.txt Edit (742 bytes, text/plain; charset="utf-8")
NetDevice.rmnet_usb2.txt Edit (744 bytes, text/plain; charset="utf-8")
NetDevice.rmnet_usb3.txt Edit (744 bytes, text/plain; charset="utf-8")
NetDevice.sit0.txt Edit (143 bytes, text/plain; charset="utf-8")
NetDevice.wlan0.txt Edit (449 bytes, text/plain; charset="utf-8")
NetworkManager.conf.txt Edit (75 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (128 bytes, text/plain; charset="utf-8")
RfKill.txt Edit (112 bytes, text/plain; charset="utf-8")
SystemImageInfo.txt Edit (222 bytes, text/plain; charset="utf-8")
WifiSyslog.txt Edit (201.4 KiB, text/plain; charset="utf-8")
modified.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf.txt Edit (7.4 KiB, text/plain; charset="utf-8")

Oliver Grawert (ogra) on 2014-05-15

Changed in network-manager (Ubuntu):
importance:	Undecided → Critical
assignee:	nobody → Mathieu Trudel-Lapierre (mathieu-tl)
status:	New → Confirmed

Revision history for this message

Tony Espy (awe) wrote on 2014-05-15:

#2

Just to be clear, we've had discussions about whether or not Wi-Fi should be enabled by default on a bootstrap install.

My opinion on this is that it should *not* be enabled by default as without user intervention, it's not going to automatically connect anyways and thus will just chew up battery. Also, if Wi-Fi is enabled, but not connected to an AP, there's no indication of this on the status bar, so a user will be unaware of this unless they open up the indicator network-menu ( see bug #1287210 ).

That said, if Wi-Fi was enabled and an update caused it to become disabled, that's certainly a bug.

Finally, I realize having Wi-Fi enabled after a device flash is useful for testing. We discussed enhancing 'phablet-network' to have the smarts to be able to enable Wi-Fi when provisioning a device which would solve the testing issue in theory.

Revision history for this message

Dave Morley (davmor2) wrote on 2014-05-15:

#3

Tony
I would leave wifi enabled on device that doesn't have a user setup. As soon as there is a user setup, part of those steps should be to setup a wifi connection and if there is none turn the wifi setting to off. In a similar fashion to wifi detection in desktop ubiquity now just with the added step of turning it off if it is not selected or no wifi ap exist.

That seems more logical to me at any rate.

Revision history for this message

Dave Morley (davmor2) wrote on 2014-05-15:

#4

Image 32 seems to be fine.

Mathieu Trudel-Lapierre (cyphermox) on 2014-05-22

Changed in network-manager (Ubuntu):
status:	Confirmed → Fix Released

Revision history for this message

Tony Espy (awe) wrote on 2014-05-29:

#5

@Dave, re: comment #3, is there a concrete work item for RTM to create an OOB experience that would allow a user to configure and/or disable WiFi on first boot? Has anyone looked at the OOB experience for IOS or Android for comparison?

If we *are* going to provide an OOB experience that handles this, then I'm OK with WiFi being on by default...

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.