modem-manager crashed with SIGSEGV in g_main_context_dispatch()

[soundpartner]

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 2.6.35.3
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
ProcEnviron:

SegvAnalysis:
 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
StacktraceTop:
 ?? ()
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_main_loop_run () from /lib/libglib-2.0.so.0
Title: modem-manager crashed with SIGSEGV in g_main_context_dispatch()
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 handle_probe_response (user_data=0x82dc0f8) at mm-plugin-base.c:665
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_main_loop_run () from /lib/libglib-2.0.so.0

[Bryan Quigley (bryanquigley)]

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 versions.