modem-manager crashed with SIGSEGV in g_udev_marshal_VOID__STRING_OBJECT()

Bug #948929 reported by Keiron Walsh on 2012-03-07
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
modemmanager (Ubuntu)
Undecided
Unassigned

Bug Description

This was an automatic report after a crash

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: modemmanager 0.5.1.96+git201202081807.635fce1-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic i686
ApportVersion: 1.94-0ubuntu2
Architecture: i386
Date: Wed Mar 7 12:31:54 2012
ExecutablePath: /usr/sbin/modem-manager
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: /usr/sbin/modem-manager
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
SegvAnalysis:
 Segfault happened at: 0x3b09e5: cmpb $0x74,(%eax)
 PC (0x003b09e5) ok
 source "$0x74" ok
 destination "(%eax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
 ?? () from /usr/lib/ModemManager/libmm-plugin-simtech.so
 ?? ()
 ?? ()
 ?? ()
 g_udev_marshal_VOID__STRING_OBJECT () from /usr/lib/i386-linux-gnu/libgudev-1.0.so.0
Title: modem-manager crashed with SIGSEGV in g_udev_marshal_VOID__STRING_OBJECT()
UpgradeStatus: Upgraded to precise on 2012-02-14 (21 days ago)
UserGroups:

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #816876, 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.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers