modem-manager crashed with SIGSEGV in g_slice_alloc() - REGRESSION: WWAN/mobile broadband does not work any more in Raring

Bug #1163015 reported by Till Kamppeter
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
modemmanager (Ubuntu)
New
Critical
Unassigned

Bug Description

Crash report appeared after trying to connect to the internet via mobile broadband on my Lenovo Thinkpad Twist. I can access without problems when booting this computer with a Quantal (12.10) live CD. As I tried more than once and got the crash report only one time there can be more things broken than only this crash.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: modemmanager 0.6.0.0.really-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Mon Apr 1 12:00:09 2013
ExecutablePath: /usr/sbin/modem-manager
InstallationDate: Installed on 2013-03-28 (4 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
MarkForUpload: True
ProcCmdline: /usr/sbin/modem-manager
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
SegvAnalysis:
 Segfault happened at: 0x7f1d2e3b4f7f <g_slice_alloc+223>: mov (%rbx),%rax
 PC (0x7f1d2e3b4f7f) ok
 source "(%rbx)" (0x100000001) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 mm_callback_info_new_full ()
 ?? ()
 ?? ()
Title: modem-manager crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.