turn off wifi, reboot, wwan modem stays off too

[Alexander Sack]

on latest devel, if i turn off wifi and rebooting, you will see that wwan modem doesn't come up either. If i enable wifi, wwan comes up and if i turn it off it stays up. rebooting again makes wwan to not come up.

ogra said on IRC it might be an indicator issue. Feel free to move bug to proper project as needed. Ping me on IRC if you have questions (bugmail is buggy on my side).

Here my saved-states:

cat /var/lib/urfkill/saved-states
[ALL]
soft=false

[WLAN]
soft=true

[BLUETOOTH]
soft=false

[UWB]
soft=false

[WIMAX]
soft=false

[WWAN]
soft=false

[GPS]
soft=false

[FM]
soft=false

[NFC]
soft=false

[Alexander Sack (asac)]

See comment in other bug about WLAN/WWAN different treatment (https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1321627/comments/13)

but for this bug i sense this might be relevant:

14:32 < asac> i see in arbitrator that we use the WLAN setting as our general state?
14:32 < asac> if (type == RFKILL_TYPE_ALL)
14:32 < asac> type = RFKILL_TYPE_WLAN;
14:32 < asac> guess thats cause of my bug?
14:33 < asac> e.g. if you ask for state of all, you return the state of WLAN? so if i turn off wlan it tells whoever is asking that efverything is off?

[Mathieu Trudel-Lapierre (cyphermox)]

That part is irrelevant. It's just a way to make the RFKILL_TYPE_ALL return something useful, but that's not what is being looked for for flight mode, or for WWAN. Both of those have their own values. (not to say that we can't improve on this though)

Before we look into what might be broken here in urfkill, let's make sure the indicator is doing the right thing.

[Tony Espy (awe)]

@asac

How are you rebooting the device, via shell command?

I flashed/wiped image #u85 and then tried to reproduce via the following steps:

1. Verify the WiFi is enabled, then disable via the network menu
2. Run 'adb shell reboot'

Repeat.

I ran ~10 cycles and never saw the problem you've described. Can you include the image # you're using, and maybe syslog as well?

[Tony Espy (awe)]

@asac

Sorry, I missed the fact that you'd already attached your syslog. That said, I'm going to file a new bug against urfkill as it's logging is minimal to say the least. In fact I see only four log messages from urfkill in your entire syslog:

Jun 13 13:57:19 ubuntu-phablet URfkill[905]: Starting urfkilld version 0.6.0
Jun 13 13:57:26 ubuntu-phablet NetworkManager[1699]: <info> urfkill appeared on the bus

[Tony Espy (awe)]

Correction, that should've read only two messages ( ie. two "Starting urfkilld...." ) are currently logged.

[Tony Espy (awe)]

OK, so I was wrong about the verbosity of urfkill, it turns out that it does in fact log FlightMode operations and individual device blocking.

After reviewing the syslog, it appears to match the saved_states you posted in the description in that WLAN is shown as blocked, but WWAN is never shown as blocked.

So, if you can reproduce this again, if you could update your "steps to reproduce" and provide output from 'list-modems', that would be super helpful!

[Launchpad Janitor (janitor)]

[Expired for indicator-network (Ubuntu) because there has been no activity for 60 days.]