Wrong WWAN value in saved-states if ofono 'Online' toggle fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
urfkill (Ubuntu) |
Fix Released
|
Critical
|
Tony Espy | ||
urfkill (Ubuntu RTM) |
Fix Released
|
Critical
|
Tony Espy |
Bug Description
Sometimes the WWAN value in /var/lib/
Start with flight mode=0. soft=false in all sections in saved-states.
/usr/share/
# restart to write values in saved-state
restart urfkill
/usr/share/
# restart to write values in saved-state
restart urfkill
The modem is not onlined. soft=true for WWAN in saved-states, whilst the remaining sections have the right value:
# cat /var/lib/
[WLAN]
soft=false
[BLUETOOTH]
soft=false
[UWB]
soft=false
[WIMAX]
soft=false
[WWAN]
soft=true
[GPS]
soft=false
[FM]
soft=false
[NFC]
soft=false
[ALL]
soft=false
This bug is triggered by a failure of an ofono SetProperty 'Online' failure. In this case, the MTK modem was involved.
syslog attached. urfkilld executed with -d in upstart script.
Workaround:
It should be possible to restore WWAN state by either:
- deleting the saved-states file and rebooting
OR
- stop urfkill
- edit the file and change the [WWAN] soft=true to soft=false
- start urfkill
summary: |
- Wrong WWAN value in saved-states + Wrong WWAN value in saved-states if ofono 'Online' toggle fails |
description: | updated |
Changed in urfkill (Ubuntu): | |
status: | Triaged → Fix Committed |
description: | updated |
tags: | added: lt-category-visible lt-prio-low |
Changed in urfkill (Ubuntu): | |
assignee: | Mathieu Trudel-Lapierre (mathieu-tl) → Tony Espy (awe) |
status: | Triaged → In Progress |
Changed in urfkill (Ubuntu): | |
importance: | High → Critical |
tags: | added: rtm14 |
Changed in urfkill (Ubuntu): | |
milestone: | none → later |
milestone: | later → none |
tags: | added: touch-2014-09-18 |
Changed in urfkill (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in urfkill (Ubuntu RTM): | |
status: | New → Fix Committed |
importance: | Undecided → Critical |
Changed in urfkill (Ubuntu RTM): | |
assignee: | nobody → Tony Espy (awe) |
Changed in urfkill (Ubuntu): | |
status: | Fix Committed → Fix Released |
An interesting line in syslog is:
URfkill[3014]: <warning> Could not set Online property in oFono: Timeout was reached
In the case of MTK modem, onlining the modem after powering it on takes ~8 seconds, so probable the timeout has to be increased (maybe to ~20 seconds to be on the safe side).
However, even if there is a timeout the values written in the file should reflect what the user wanted, as the only way get back to normal state is to use /usr/share/ urfkill/ scripts/ block to activate the modem.