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

Bug #987310 reported by typo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)
New
Undecided
Unassigned

Bug Description

I started my computer and opened the webbrowser and then I regonized, that telepathy-mission-control-5 crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-mission-control-5 1:5.12.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Mon Apr 23 15:55:52 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=15f81d13-b83c-4192-aa7d-865c6e24cc0e ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f551aacd04c <free+60>: mov (%rax),%rdi
 PC (0x7f551aacd04c) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 free () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_hash_table_remove_all () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: mission-control-5 crashed with SIGSEGV in free()
UpgradeStatus: Upgraded to precise on 2012-04-17 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
typo (gnomeuser8) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #979827, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
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.