Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner.  This release has reached
EOL and the ModemManager code has changed drastically in the newer

** Changed in: modemmanager (Ubuntu)
       Status: Confirmed => Invalid

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.

  modem-manager crashed with SIGSEGV in get_cind_signal_done()

Status in modemmanager package in Ubuntu:

Bug description:
  Lately modem-manager has been crashing (NULL pointer de-reference?).
  So far it has always happened when I am not at the computer.

  This looks similar to bugs #963102 and #915460 but is probably not the
  same (in this case PC is not NULL like in those bugs -- and #963102
  should be fixed on quantal anyway).

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: modemmanager
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Dec  3 06:31:40 2012
  ExecutablePath: /usr/sbin/modem-manager
  ExecutableTimestamp: 1349713961
  InstallationDate: Installed on 2012-11-29 (3 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
  MarkForUpload: True
  ProcCmdline: /usr/sbin/modem-manager
  ProcCwd: /
   PATH=(custom, no user)
   Segfault happened at: 0x42926e:      mov    (%r12),%rdi
   PC (0x0042926e) ok
   source "(%r12)" (0x00000000) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: modemmanager
   ?? ()
   ?? ()
   mm_serial_port_queue_command ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/
  Title: modem-manager crashed with SIGSEGV in mm_serial_port_queue_command()
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to