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

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

Bug Description

Error keeps on popping, all the time.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: telepathy-mission-control-5 1:5.14.1-1ubuntu6
ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
Uname: Linux 3.10.0-5-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Mon Oct 14 06:07:40 2013
ExecutablePath: /usr/lib/telepathy/mission-control-5
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-5-generic root=UUID=d8042cf6-4e66-47d9-828d-56a14e87db80 ro quiet splash vt.handoff=7
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
SegvAnalysis:
 Segfault happened at: 0x410260: mov 0x18(%rdi),%rdi
 PC (0x00410260) ok
 source "0x18(%rdi)" (0x00000018) 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:
 ?? ()
 ?? ()
 __libc_start_main (main=0x40e2a0, argc=1, ubp_av=0x7fff00039088, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff00039078) at libc-start.c:260
 ?? ()
Title: mission-control-5 crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to saucy on 2013-06-12 (123 days ago)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo

Revision history for this message
Piyush Kumar (chirkut-kr) 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 #621048, 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.

information type: 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.