network-manager crash on boot on krillin/devel-proposed
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | network-manager (Ubuntu) |
Critical
|
Tony Espy | ||
Bug Description
current build number: 198
device name: krillin
channel: ubuntu-
network-manager:
Installed: 1.0.4-0ubuntu3
network-manager crashes and keeps re-spawning, making the device unusable.
Related branches
CVE References
| Jean-Baptiste Lallement (jibel) wrote : | #1 |
| John McAleely (john.mcaleely) wrote : | #2 |
| Changed in network-manager (Ubuntu): | |
| assignee: | nobody → Tony Espy (awe) |
| status: | New → Confirmed |
| importance: | Undecided → High |
| Francis Ginther (fginther) wrote : | #3 |
This is currently blocking all boottesting for package promotion into wily. For reference, see the packages marked with "Boottest result: Regression" in http://
| Changed in network-manager (Ubuntu): | |
| importance: | High → Critical |
| Tony Espy (awe) wrote : | #4 |
Confirmed on krillin ( devel-proposed #206 ). The .crash file wasn't very useful, but I should be able to diagnose fairly quick.
| Tony Espy (awe) wrote : | #5 |
Here's the backtrace:
#0 0x000aa24c in platform_link_added (self=self@
ignore = 0
factory = <optimized out>
device = <optimized out>
error = 0x0
__func__ = "platform_
#1 0x000ac02a in platform_
links_array = 0x2089420
links = <optimized out>
i = 3
#2 nm_manager_start (self=self@
priv = <optimized out>
__func__ = "nm_manager_start"
#3 0x0003c662 in main (argc=1, argv=0xbef66e14) at main.c:500
net_enabled = <optimized out>
| Tony Espy (awe) wrote : | #6 |
The code in question is this:
/* Try registered device factories */
factory = nm_device_
if (factory) {
gboolean ignore = FALSE;
device = nm_device_
if (!device) {
if (!ignore) {
}
return;
}
}
The crash is happening when error->message is accessed in the call to nm_log_warn.
| Changed in network-manager (Ubuntu): | |
| status: | Confirmed → Won't Fix |
| status: | Won't Fix → In Progress |
| Tony Espy (awe) wrote : | #7 |
No crash on mako ( devel-proposed #313 ).
Pretty sure this is being caused by a device factory failure when trying to create a NMDevice instance for 'ccmni0', which is modem device, managed by rild.
| Tony Espy (awe) wrote : | #8 |
NM 0.9.10.0 included an "?" ( if ) check in the log statement that's crashing. Apparently this got lost in the merge. Patch on the way...
| Tony Espy (awe) wrote : | #9 |
Also, testing on krillin ( devel-proposed #225 ) is super painful. Unity seems to slow to crawl while painting the Welcome screen. It take several minutes for the phone to become usable... and spends much of the time prior to this basically frozen on the lock screen.
| Tony Espy (awe) wrote : | #10 |
Fix should land in 1.0.4-0ubuntu4, which is currently in the unapproved queue. Hopefully should land soon.
| Changed in network-manager (Ubuntu): | |
| status: | In Progress → Fix Committed |
| Launchpad Janitor (janitor) wrote : | #11 |
This bug was fixed in the package network-manager - 1.0.4-0ubuntu4
---------------
network-manager (1.0.4-0ubuntu4) wily; urgency=medium
[ Mathieu Trudel-Lapierre ]
* d/p/0001-
Pre-initialize reason for ofono state changes to NULL; this avoids getting
to nm_device_set_state with an invalid reason string. (LP: #1499906)
* d/p/0001-
cleanup ip_string_
version, and start setting NM_MODEM_IP4_METHOD to _STATIC so IP, prefix,
gateway and DNS get properly applied on an oFono modem as it comes up.
* debian/
* debian/
libnm-glib as this would cause type duplication and crashes. (LP: #1499904)
* debian/
crash by dereferencing a NULL pointer if a device can't get created by its
NMDeviceFac
failures; but no need to make all of NM sad. (LP: #1496434)
[ Tony Espy ]
* d/p/0002-
Fix duplicate 'LastSeen' PropertiesChanged signals being generated
after every scan. The 'Last-Seen' property is now only updated when
a scan finishes, and schedule_
new_bss_cb or updated_bss_cb. (LP: #1480877)
* d/p/add_
* d/p/add_
* d/p/CVE-
in ofono settings plugin.
-- Mathieu Trudel-Lapierre <email address hidden> Sat, 26 Sep 2015 00:02:02 -0400
| Changed in network-manager (Ubuntu): | |
| status: | Fix Committed → Fix Released |


@awe, it seems I lack assign-fu. can you take a look at this, but not ahead of the ota-7 wifi related bugs?