I think the issue is the the nm_system_apply_ip4_config () method always
returns TRUE, ignoring any errors from nm_system_device_set_ip4_route
(), which returns NULL to signify an error adding a route.
I've added a preliminary fix for this, by adding logic to check for NULL
and immediately return
** Branch linked: lp:~awe/network-manager/lp1435328
--
You received this bug notification because you are a member of Ubuntu
Phonedations bugs, which is subscribed to ofono in Ubuntu.
https://bugs.launchpad.net/bugs/1435328
Title:
Leaving Wifi does not connect to mobile carrier data (GSM)
Sta
Here's the latest update on what we know about this bug.
First, we have working fix for ofono's behavior when a
DATA_CALL_LIST_CHANGED message is received with an empty call list, and
the context stays active but becomes stale/non-working. This should
land in a silo by early tomorrow.
Second, Al
** Tags added: bq hotfix
--
You received this bug notification because you are a member of Ubuntu
Phonedations bugs, which is subscribed to ofono in Ubuntu.
https://bugs.launchpad.net/bugs/1435328
Title:
Leaving Wifi does not connect to mobile carrier data (GSM)
Status in the base for Ubuntu
** Also affects: ofono (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ofono (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: ofono (Ubuntu)
Status: New => In Progress
** Changed in: ofono (Ubuntu RTM)
Status: New => In Progress
** Chan
Turns out pending version of NM was used for the vivid testing mentioned
in comments #26 and #27.
--
You received this bug notification because you are a member of Ubuntu
Phonedations bugs, which is subscribed to ofono in Ubuntu.
https://bugs.launchpad.net/bugs/1435328
Title:
Leaving Wifi does
So in theory, NM should react to the context 'Settings' property
changing to empty, and tear down the connection.
For vivid testing, it's important however that the most recent version
of NM which fixes the NM 5m reconnect bug #1418077 is used. This
version is currently in the following silo:
ht
This bug was fixed in the package ofono -
1.12.bzr6892+15.04.20150407-0ubuntu1
---
ofono (1.12.bzr6892+15.04.20150407-0ubuntu1) vivid; urgency=medium
[ Alfonso Sanchez-Beato ]
* ubuntu-apndb.c, src/common.c, test-common.c: provision IA APNs
LTE modems may require a new IA APN
This bug was fixed in the package ofono -
1.12.bzr6892+15.04.20150407-0ubuntu1
---
ofono (1.12.bzr6892+15.04.20150407-0ubuntu1) vivid; urgency=medium
[ Alfonso Sanchez-Beato ]
* ubuntu-apndb.c, src/common.c, test-common.c: provision IA APNs
LTE modems may require a new IA APN
This bug was fixed in the package ofono -
1.12.bzr6892+15.04.20150407-0ubuntu1
---
ofono (1.12.bzr6892+15.04.20150407-0ubuntu1) vivid; urgency=medium
[ Alfonso Sanchez-Beato ]
* ubuntu-apndb.c, src/common.c, test-common.c: provision IA APNs
LTE modems may require a new IA APN
Some more traces when reproducing the bug:
/system/bin/logcat -v threadtime -b main -b radio
...
04-14 09:31:21.057 1844 1861 D use-Rlog/RLOG-AT: +CGEV: NW DEACT "IP",
"100.125.255.239", 1
...
04-14 09:31:21.058 1844 1861 D use-Rlog/RLOG-RIL: configureNetworkInterface:
Down E
04-14 09:31:21
@Tony, great catch! I have tested your changes and reproduced the bug.
Now list-contexts does not show any active context when ccmni0 is down.
However, NM is not able to recover from this situation. It tries to add
routes before we get the UNSOL_DATA_CALL_LIST_CHANGED event in ofono.
After that it
12 matches
Mail list logo
