mission-control-5 crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-mission-control-5 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: telepathy-
Occurred while typing a message
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: telepathy-
ProcVersionSign
Uname: Linux 2.6.32-24-generic x86_64
NonfreeKernelMo
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 20 18:30:01 2010
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANG=en_AU.UTF-8
SegvAnalysis:
Segfault happened at: 0x431ee6: mov (%rdi),%ebx
PC (0x00431ee6) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%ebx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-
StacktraceTop:
?? ()
?? ()
g_closure_invoke ()
?? () from /usr/lib/
g_signal_
Title: mission-control-5 crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
visibility: | private → public |
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #638671, 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.