modem-manager crashed with SIGSEGV in custom_init_response()

Bug #1153190 reported by Mattia Rizzolo
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
modemmanager (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I just log in in my account and I got this error.
The last thig I do is to clear all user hide directory to restor to "factory settings".

Probably it is a duplicate of the bug 811612.

The only modem was connected when the error occurred was a nokia 5230.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: modemmanager 0.6.0.0.really-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-10.19-generic 3.8.2
Uname: Linux 3.8.0-10-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Mon Mar 4 14:27:39 2013
ExecutablePath: /usr/sbin/modem-manager
MarkForUpload: True
ProcCmdline: /usr/sbin/modem-manager
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
SegvAnalysis:
 Segfault happened at: 0x1de7700: add %al,(%rax)
 PC (0x01de7700) in non-executable VMA region: 0x01d9f000-0x01e17000 rw-p [heap]
 source "%al" ok
 destination "(%rax)" (0x01de46d0) ok
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 mm_serial_port_close ()
 ?? ()
Title: modem-manager crashed with SIGSEGV in mm_serial_port_close()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Mattia Rizzolo (mapreri) wrote :
Mattia Rizzolo (mapreri)
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 custom_init_response (port=port@entry=0x1dd9000, response=response@entry=0x1db5b20, error=error@entry=0x1ddaf30, user_data=user_data@entry=0x1de92f0) at mm-plugin-base.c:981
 handle_response (port=<optimized out>, response=0x1dd0300, error=0x1ddaf30, callback=0x433840 <custom_init_response>, callback_data=0x1de92f0) at mm-at-serial-port.c:134
 mm_serial_port_close (self=0x1dd9000) at mm-serial-port.c:970
 supports_task_dispose (object=0x1de92f0) at mm-plugin-base.c:401

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in modemmanager (Ubuntu):
importance: Undecided → Medium
summary: - modem-manager crashed with SIGSEGV in mm_serial_port_close()
+ modem-manager crashed with SIGSEGV in custom_init_response()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in modemmanager (Ubuntu):
status: New → Confirmed
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.