mission-control-5 crashed with SIGSEGV in __libc_start_main()
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-
ProcVersionSign
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/
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=
ProcEnviron:
XDG_RUNTIME_
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-
StacktraceTop:
?? ()
?? ()
__libc_start_main (main=0x40e2a0, argc=1, ubp_av=
?? ()
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
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.