Ubuntu
modemmanager package

modem-manager crashed with SIGSEGV in g_match_info_unref()

Bug #1049512 reported by Swen Kühnlein on 2012-09-12

This bug report is a duplicate of: Bug #1015328: modem-manager crashed with SIGSEGV in g_match_info_unref(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	modemmanager (Ubuntu)	New	Undecided	Unassigned

Bug Description

Don't know, when exactly this happened.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: modemmanager 0.6.0.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
Uname: Linux 3.5.0-14-generic i686
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
CrashCounter: 1
Date: Wed Sep 12 00:43:36 2012
ExecutablePath: /usr/sbin/modem-manager
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: /usr/sbin/modem-manager
ProcEnviron:

SegvAnalysis:
Segfault happened at: 0xb76170b1 <g_match_info_unref+33>: lock cmpxchg %edx,(%esi)
PC (0xb76170b1) ok
source "%edx" ok
destination "(%esi)" (0xb76eba94) in non-writable VMA region: 0xb76b9000-0xb7709000 r-xp /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.3312.0
SegvReason: writing VMA /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.3312.0
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
g_match_info_unref () from /lib/i386-linux-gnu/libglib-2.0.so.0
g_match_info_free () from /lib/i386-linux-gnu/libglib-2.0.so.0
mm_gsm_parse_clck_response ()
?? ()
?? ()
Title: modem-manager crashed with SIGSEGV in g_match_info_unref()
UpgradeStatus: Upgraded to quantal on 2012-09-08 (3 days ago)
UserGroups:

Tags:

Revision history for this message

Swen Kühnlein (swen) wrote on 2012-09-12:

Dependencies.txt Edit (2.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-09-12: This bug is a duplicate

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 #1015328, 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.