Rebooting after disabling wifi leaves wifi in wrong state (enabled but doesn't show networks)

Bug #1362133 reported by Brendan Donegan on 2014-08-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-network (Ubuntu)
High
Brendan Donegan
urfkill (Ubuntu)
Critical
Unassigned

Bug Description

Steps to reproduce:

1.) Open the network indicator
2.) Toggle the Wi-Fi switch to 'Off'
3.) Reboot the device
4.) Open the network indicator

Expected result:

Wi-Fi is either disabled and shows no networks, or is enabled and shows networks

Actual result:

Wi-Fi is enabled and shows no networks. Toggling it on and off returns it to normal.

Thomas Strehl (strehl-t) on 2014-09-04
Changed in indicator-network (Ubuntu):
assignee: nobody → Jussi Pakkanen (jpakkane)
tags: added: touch-2014-09-25
Changed in indicator-network (Ubuntu):
importance: Undecided → Critical
importance: Critical → High
Jussi Pakkanen (jpakkane) wrote :

The output of nmcli is this:

nmcli d
DEVICE TYPE STATE
/ril_1 gsm disconnected
/ril_0 gsm disconnected
wlan0 802-11-wireless unavailable

The top bar icon shows that wifi is off but indicator-network shows it to be on.

Jussi Pakkanen (jpakkane) wrote :

More output:

dbus-send --dest=com.canonical.indicator.network --print-reply /com/canonical/indicator/network org.gtk.Actions.Describe string:wifi.enable
method return sender=:1.40 -> dest=:1.83 reply_serial=2
   struct {
      boolean true
      signature ""
      array [
         variant boolean true
      ]
   }

dbus-send --system --print-reply --dest=org.freedesktop.URfkill /org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get string:org.freedesktop.URfkill.Killswitch string:state
method return sender=:1.44 -> dest=:1.192 reply_serial=2
   variant int32 0

system-image-cli -i
current build number: 32
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2014-09-12 07:15:07
version version: 32
version ubuntu: 20140912
version device: 20140908-d8c11f3
version custom: 1410480110

Jussi Pakkanen (jpakkane) wrote :
Antti Kaijanmäki (kaijanmaki) wrote :

Jussi was testing n krillin, which has a known issue with wifi rfkill. so jussis report is unrelated to this one.

Brendan, next time you see this happen please provide the following info from the device shell as phablet user:

$ nmcli d
$ $ dbus-send --dest=com.canonical.indicator.network --print-reply /com/canonical/indicator/network org.gtk.Actions.Describe string:wifi.enable
$ dbus-send --system --print-reply --dest=org.freedesktop.URfkill /org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get string:org.freedesktop.URfkill.Killswitch string:state

Changed in indicator-network (Ubuntu):
status: New → Incomplete
assignee: Jussi Pakkanen (jpakkane) → Brendan Donegan (brendan-donegan)
Antti Kaijanmäki (kaijanmaki) wrote :

And I will emphasize: next time you see this happening on _mako_

Jussi Pakkanen (jpakkane) wrote :

On Mako the command outputs are exactly the same.

Antti Kaijanmäki (kaijanmaki) wrote :

OK, so we have the saved-states being wrong after boot again.

Changed in indicator-network (Ubuntu):
status: Incomplete → Confirmed
status: Confirmed → Invalid
Changed in urfkill (Ubuntu):
status: New → Confirmed
importance: Undecided → Critical
Tony Espy (awe) wrote :

Note, I marked this a duplicate of bug #1321627 as we have a rather large pending landing for urfkill which has re-written much of the code that deals with enabling/disabling individual killswitches in addition to FlightMode.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers