modem-manager crashed with SIGSEGV in internal_queue_command()

[Bartosz Porosinski]

Crashed after invoking command sudo /etc/init.d/network-manager restart
Wireless USB modem was in use

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: modemmanager 0.5.1.96+git201202081807.635fce1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Mon Feb 20 14:51:27 2012
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/sbin/modem-manager
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1)
ProcCmdline: /usr/sbin/modem-manager
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
 ?? ()
 ?? ()
 mm_serial_port_queue_command ()
 ?? ()
 ?? ()
Title: modem-manager crashed with SIGSEGV in mm_serial_port_queue_command()
UpgradeStatus: Upgraded to precise on 2012-02-16 (4 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 internal_queue_command (self=0xb2d130, command=<optimized out>, take_command=1, cached=0, timeout_seconds=3, callback=0, user_data=0x0) at mm-serial-port.c:965
 mm_serial_port_queue_command (self=<optimized out>, command=<optimized out>, take_command=<optimized out>, timeout_seconds=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at mm-serial-port.c:1007
 disable_flash_done (port=0xb2d130, error=<optimized out>, user_data=0xb1acf0) at mm-generic-gsm.c:2072
 handle_response (port=<optimized out>, response=0xb02350, error=0x0, callback=0x423000 <secondary_unsolicited_done>, callback_data=0xb1acf0) at mm-at-serial-port.c:102

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #915460, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad