NetworkManager crashed with SIGSEGV in nm_modem_set_state()

Bug #1420875 reported by Andy Postnikov
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Triaged
High
Unassigned

Bug Description

Errors Bucket for this crash:

https://errors.ubuntu.com/bucket/?id=/usr/sbin/NetworkManager%3A11%3Anm_modem_set_state%3Adisconnect_done%3Acomplete_pending_call_and_unlock%3Adbus_connection_dispatch%3Amessage_queue_dispatch

updated all now after pluggin off usb modem

ProblemType: CrashDistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu6
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
Date: Wed Feb 11 22:13:18 2015
ExecutablePath: /usr/sbin/NetworkManager
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-04-25 (657 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
IpRoute:
 default via 192.168.1.1 dev wlan0 proto static metric 1024
 169.254.0.0/16 dev wlan0 scope link metric 1000
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.31
ProcCmdline: NetworkManager
ProcEnviron:
 LANGUAGE=ru:en_GB:en
 TERM=linux
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f7c88244a76: mov 0x34(%rax),%r13d
 PC (0x7f7c88244a76) ok
 source "0x34(%rax)" (0x00000034) not located in a known VMA region (needed readable region)!
 destination "%r13d" ok
SegvReason: reading NULL VMA
Signal: 11SourcePackage: network-manager
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-wwan.so
 ?? () from /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-wwan.so
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
Title: NetworkManager crashed with SIGSEGV in dbus_connection_dispatch()
UpgradeStatus: Upgraded to vivid on 2014-12-23 (50 days ago)
UserGroups:

nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/2 GREENLAND e332054d-0cd6-4842-b4f9-e732c0b2aad6 /org/freedesktop/NetworkManager/ActiveConnection/0
 eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

Revision history for this message
Andy Postnikov (apostnikov) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 nm_modem_set_state (self=0x116f100, new_state=NM_MODEM_STATE_CONNECTED, reason=0x7f7c8824ae30 "connected") at nm-modem.c:146
 disconnect_done (proxy=0x117d730, call=0x2, user_data=0x7f7c8824ae30) at nm-modem-ofono.c:170
 complete_pending_call_and_unlock (connection=connection@entry=0x1096fa0, pending=0x1171690, message=message@entry=0x118fb20) at ../../dbus/dbus-connection.c:2331
 dbus_connection_dispatch (connection=connection@entry=0x1096fa0) at ../../dbus/dbus-connection.c:4626
 message_queue_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at dbus-gmain.c:90

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in network-manager (Ubuntu):
importance: Undecided → Medium
summary: - NetworkManager crashed with SIGSEGV in dbus_connection_dispatch()
+ NetworkManager crashed with SIGSEGV in nm_modem_set_state()
tags: removed: need-amd64-retrace
description: updated
information type: Private → Public
Changed in network-manager (Ubuntu):
importance: Medium → High
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.