modem-manager crashed with SIGSEGV in dbus_connection_send()

[Phill Whiteside]

Binary package hint: modemmanager

This is the 2nd crash, although not fatal to my system this time - It seems to be caused if the 3G network drops out and the usb internet device then tries to connect via gprs (I think that's 2G - 56K link).

I'm running an update to 9.10 from 9.04 Final release & updated I previously noted it onto the ubuntu dev forum, as all I could get out of my system was a series of screen-shots (13 of them !!). I do still have the screen-shots, if they're of any help to anyone.

Linux piglet 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux

sudo apt-cache policy modem-mananger
W: Unable to locate package modem-mananger

Phill.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Nov 4 16:52:36 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/modem-manager
Package: modemmanager 0.2.git.20091014t233208.16f3e00-0ubuntu1
ProcCmdline: /usr/sbin/modem-manager
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0xaa4aab: mov %esi,(%edx)
 PC (0x00aa4aab) ok
 source "%esi" ok
 destination "(%edx)" (0x00006e6f) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 dbus_connection_send () from /lib/libdbus-1.so.3
Title: modem-manager crashed with SIGSEGV in dbus_connection_send()
Uname: Linux 2.6.31-14-generic i686
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #452427, so 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. Please continue to report any other bugs you may find.