touch-packages team mailing list archive

[Tony Espy <1431471@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

NetworkManager incorrectly uses GPRS contexts from any SIM directory
instead of limiting the GPRS contexts used to those the currently active
SIM.

This bug was discovered on krillin while trying to determine whether bug
#1425987 was a duplicate of bug #1418077.

I've attached the NetworkManager log messages extracted from the syslog
contained in the network-test-session tarball attached to bug #1425987.

If you look at the attached netlog, after '/208150102671184/context1' is
disabled, you'll see NM try a 'context3', 'context5', and 'context1'
again. The odd thing is that the related IMSI is not '208150102671184'
it's '208103698221268'. Looking at network-test-session.log ( also
attached ), you'll see that '208150102671184' is the IMSI for ril_0, and
that ril_1 is PIN-locked.

This bug was discovered on krillin running vivid-proposed #122.

The version of NetworkManager on this image is: 0.9.10.0-4ubuntu6

** Affects: network-manager (Ubuntu)
     Importance: High
     Assignee: Mathieu Trudel-Lapierre (mathieu-tl)
         Status: Confirmed

** Changed in: network-manager (Ubuntu)
       Status: New => Confirmed

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu)
     Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

-- 
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/1431471

Title:
  NetworkManager uses ofono GPRS contexts for wrong SIM

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager incorrectly uses GPRS contexts from any SIM directory
  instead of limiting the GPRS contexts used to those the currently
  active SIM.

  This bug was discovered on krillin while trying to determine whether
  bug #1425987 was a duplicate of bug #1418077.

  I've attached the NetworkManager log messages extracted from the
  syslog contained in the network-test-session tarball attached to bug
  #1425987.

  If you look at the attached netlog, after '/208150102671184/context1'
  is disabled, you'll see NM try a 'context3', 'context5', and
  'context1' again. The odd thing is that the related IMSI is not
  '208150102671184' it's '208103698221268'. Looking at network-test-
  session.log ( also attached ), you'll see that '208150102671184' is
  the IMSI for ril_0, and that ril_1 is PIN-locked.

  This bug was discovered on krillin running vivid-proposed #122.

  The version of NetworkManager on this image is: 0.9.10.0-4ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431471/+subscriptions