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

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 g_main_context_dispatch()

Status in modemmanager package in Ubuntu:

Bug description:
  Binary package hint: modemmanager

  trying to conect with my build in gobi modem modemmanager crashes

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: modemmanager 0.4+git.20100809t153145.be28089-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-19.28-generic
  Uname: Linux 2.6.35-19-generic i686
  Architecture: i386
  CrashCounter: 1
  Date: Mon Sep  6 12:49:57 2010
  ExecutablePath: /usr/sbin/modem-manager
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcCmdline: /usr/sbin/modem-manager
   Segfault happened at: 0x8072a13:     mov    0x28(%esi),%ecx
   PC (0x08072a13) ok
   source "0x28(%esi)" (0x00000028) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: modemmanager
   ?? ()
   ?? () from /lib/
   g_main_context_dispatch () from /lib/
   ?? () from /lib/
   g_main_loop_run () from /lib/
  Title: modem-manager crashed with SIGSEGV in g_main_context_dispatch()

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to