← Back to team overview

touch-packages team mailing list archive

[Bug 1435776] Re: NM does not activate ofono Inet contexts w/Username but no Password ( eg. giffgaff )

 

This bug is caused by the fact the NM's ofono plugin checks for the
existence of Username and Password properties in the APN, and if found,
adds them as settings to the NM_SETTING_GSM instance ( which is added to
the associated NM_CONNECTION instance ).

For some reason, the fact that only 'Username' is set doesn't seem to
effect the first connection attempt, but them for some reason, the NM
settings code resets its secrets logic and thinks that a 'Password' is
required the next time a connection attempt occurs.

Rather than debug the settings secrets logic, I opted to remove the code
in the ofono plugin which adds these settings, as in reality, NM does
nothing with them, they're actually used by ofono directly.

Likewise the same code ( in src/settings/plugins/ofono/parser.c ) adds
an APN setting to the NM_SETTING_GSM instance, however it searches for
the APN in the context using the key "Apn", when the key is actually
named "AccessPointName".   So, the code was always adding an
NM_SETTING_GSM_APN with value of "".

I will add a branch to the bug later this afternoon.

In the meanwhile, anyone who'd like to test can use the version (
0.9.10.0-4ubuntu15.1~awe4 ) in the phablet-team's telephony PPA:

https://launchpad.net/~phablet-team/+archive/ubuntu/telephony

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1435776

Title:
  NM does not activate ofono Inet contexts w/Username but no Password (
  eg. giffgaff )

Status in the base for Ubuntu mobile products:
  Confirmed
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Device: Krillin
  Software:  Vivid r157

  NM does not activate a valid ofono context which is present in the
  gprs file (context_1 in this case)

  I was able to activate the context manually using ./activate-context
  /ril_0 1

  You can find syslog, list-modems and list-contexts attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435776/+subscriptions


References