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

Bug #1154674 reported by Francis Ricardo
220
This bug affects 24 people
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

No

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-9.18-generic 3.8.1
Uname: Linux 3.8.0-9-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Wed Mar 13 12:38:49 2013
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationDate: Installed on 2013-03-13 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130303)
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-9-generic root=UUID=8081a956-8609-46bc-bed6-d6327198bff6 ro quiet splash vt.handoff=7
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f17f3ff5f6f <g_slice_alloc+223>: mov (%rbx),%rax
 PC (0x7f17f3ff5f6f) ok
 source "(%rbx)" (0x00010001) 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
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Francis Ricardo (francys-ricardo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=0x2359690) at /build/buildd/glib2.0-2.35.8/./glib/gslice.c:532
 thread_memory_magazine1_alloc (ix=<optimized out>, tmem=<optimized out>) at /build/buildd/glib2.0-2.35.8/./glib/gslice.c:835
 g_slice_alloc (mem_size=mem_size@entry=16) at /build/buildd/glib2.0-2.35.8/./glib/gslice.c:994
 g_slist_prepend (list=0x0, data=data@entry=0x236e200) at /build/buildd/glib2.0-2.35.8/./glib/gslist.c:267
 g_object_notify_queue_add (nqueue=nqueue@entry=0x2371020, pspec=0x236e200, object=<optimized out>) at /build/buildd/glib2.0-2.35.8/./gobject/gobject.c:307

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 magazine_chain_pop_head()
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 telepathy-mission-control-5 (Ubuntu):
status: New → Confirmed
tags: added: saucy
Logan Rosen (logan)
information type: Private → Public
Revision history for this message
Fabio Duran Verdugo (fabioduran) wrote :

this bug occurrs when No credential found in the keyring.

I add the credential and solution this issue

Revision history for this message
David Girault (dfgweb) wrote :

Hi Fabio,
How do you add credential?
Thanks

tags: added: bugpattern-needed
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.