modem-manager crashed with SIGSEGV in g_slice_alloc() - REGRESSION: No internet access via mobile broadband
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ModemManager |
Fix Committed
|
Undecided
|
Unassigned | ||
modemmanager (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
network-manager (Ubuntu) |
Invalid
|
Critical
|
Unassigned |
Bug Description
Happened again, after some attempts to connect via mobile broadband.
With 12.10 access via mobile broadband works with this machine.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: modemmanager 0.6.0.0.
Uname: Linux 3.9.0-030900rc5
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Wed Apr 3 18:37:32 2013
ExecutablePath: /usr/sbin/
InstallationDate: Installed on 2013-03-28 (5 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
MarkForUpload: True
ProcCmdline: /usr/sbin/
ProcEnviron:
PATH=(custom, no user)
TERM=linux
SegvAnalysis:
Segfault happened at: 0x7f7286b66f7f <g_slice_
PC (0x7f7286b66f7f) 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_
g_slice_alloc0 () from /lib/x86_
g_type_
?? () from /usr/lib/
g_object_newv () from /usr/lib/
Title: modem-manager crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
---
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
DistroRelease: Ubuntu 13.04
InstallationDate: Installed on 2013-03-28 (12 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
MarkForUpload: True
Package: network-manager
PackageArchitec
ProcVersionSign
Tags: raring
Uname: Linux 3.8.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
Changed in modemmanager (Ubuntu): | |
status: | Confirmed → Incomplete |
tags: | added: patch |
Changed in modemmanager: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in network-manager (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in modemmanager: | |
importance: | Medium → Undecided |
status: | New → Fix Committed |
There isn't enough information here to debug it yet. What were you doing when it crashed? Plugging in a new modem?
Could you try to reproduce the crash and provide debugging logs for ModemManager, as outlined in http:// wiki.ubuntu. com/DebuggingNe tworkManager ?
Thanks!