Ubuntu
modemmanager package

modem-manager crashed with SIGSEGV in g_main_context_dispatch()

Bug #878281 reported by scytlae on 2011-10-19

32

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	modemmanager (Ubuntu)	Expired	Medium	Unassigned

Bug Description

happens when I log in

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: modemmanager 0.5-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Tue Oct 18 18:07:29 2011
ExecutablePath: /usr/sbin/modem-manager
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/sbin/modem-manager
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
Segfault happened at: 0x435d98: mov 0x18(%rax),%rdi
PC (0x00435d98) ok
source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
?? ()
g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
main ()
Title: modem-manager crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to oneiric on 2011-10-12 (7 days ago)
UserGroups:

Tags:

Revision history for this message

scytlae (scytale-gmail) wrote on 2011-10-19:

#1

Dependencies.txt Edit (558 bytes, text/plain; charset="utf-8")
Disassembly.txt Edit (587 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (17.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (746 bytes, text/plain; charset="utf-8")
Registers.txt Edit (711 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (487 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (534 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-10-19:

#2

StacktraceTop:
mm_serial_port_queue_process (data=0x1b41230) at mm-serial-port.c:568
g_main_dispatch (context=0x1b0c970) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:2441
g_main_context_dispatch (context=0x1b0c970) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3011
g_main_context_iterate (context=0x1b0c970, block=<optimized out>, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3089
g_main_loop_run (loop=0x1b10220) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3297

Revision history for this message

Apport retracing service (apport) wrote on 2011-10-19: Stacktrace.txt

#3

Stacktrace.txt Edit (2.9 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2011-10-19: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (2.9 KiB, text/plain)

Changed in modemmanager (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-11-28:

#5

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in modemmanager (Ubuntu):
status:	New → Confirmed

Revision history for this message

Peter Matulis (petermatulis) wrote on 2012-01-17:

#6

This bug was most likely made private due to a stacktrace being included. Yet a public bug was made a duplicate of this private bug, which is a bit of a problem for those following that bug. Does this bug really need to remain private?

Mathieu Trudel-Lapierre (cyphermox) on 2012-01-17

visibility:

private → public

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2012-01-17:

#7

Ideally what we would need would be a debug log from ModemManager trying to establish a connection or trying to probe the ports to see at which point it crashes.

Please follow the steps outlined at http://live.gnome.org/NetworkManager/Debugging under section "Debugging NetworkManager 0.8 and 0.9 3G connections" to attach debugging logs from NetworkManager and ModemManager. Note that this may include sensitive information, so please review the logs first to avoid sending unnecessary private information.

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2012-01-17:

#8

It might be that http://cgit.freedesktop.org/ModemManager/ModemManager/patch/?id=4a0630378a7f68259add9a31a7041d0e073e1ad4 is what we need to fix this under Oneiric (would be fine already in Precise), but the logs will confirm that.

Changed in modemmanager (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-03-18:

#9

[Expired for modemmanager (Ubuntu) because there has been no activity for 60 days.]

Changed in modemmanager (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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