mission-control-5 crashed with SIGSEGV in thread_memory_from_self()

Bug #1227284 reported by ariel sandoval
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)
New
Medium
Unassigned

Bug Description

ayuda por favor

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: telepathy-mission-control-5 1:5.14.1-1ubuntu5
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic x86_64
ApportVersion: 2.12.2-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 18 13:07:40 2013
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationDate: Installed on 2013-05-30 (110 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-3-generic root=UUID=fa0c3a7c-e5f4-47da-b196-99197deaefd1 ro vesafb.invalid=1 drm.debug=0xe nopat plymouth:debug
ProcEnviron:
 SHELL=/bin/false
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=es_CO:es
 LANG=es_CO.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7febd3ac4a57 <g_slice_alloc+167>: mov (%rbx),%rax
 PC (0x7febd3ac4a57) ok
 source "(%rbx)" (0x00010000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slist_prepend () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
SystemImageInfo: Error: [Errno 2] No existe el archivo o el directorio: 'system-image-cli'
Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to saucy on 2013-06-03 (107 days ago)
UserGroups:

Revision history for this message
ariel sandoval (arielsanflo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 thread_memory_from_self () at /build/buildd/glib2.0-2.37.93/./glib/gslice.c:514
 g_slice_alloc (mem_size=16) at /build/buildd/glib2.0-2.37.93/./glib/gslice.c:994
 g_slist_insert_sorted_real (list=0x2104e80, data=0x2104e80, func=0x7fffe3840550, user_data=0x7fffe3840600) at /build/buildd/glib2.0-2.37.93/./glib/gslist.c:924
 ?? ()
 ?? ()

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 telepathy-mission-control-5 (Ubuntu):
importance: Undecided → Medium
summary: - mission-control-5 crashed with SIGSEGV in g_slice_alloc()
+ mission-control-5 crashed with SIGSEGV in thread_memory_from_self()
tags: removed: need-amd64-retrace
information type: Private Security → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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