unity-window-decorator crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I tried to close a window and this message popped up.. Not sure of the technical aspects. Did my part to take it to your notice.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-gnome 1:0.9.4-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.38-5-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Thu Mar 3 00:18:15 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_IN:en
PATH=(custom, user)
LANG=en_IN
LC_MESSAGES=
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x415c70: mov 0x310(%rax),%rdi
PC (0x00415c70) ok
source "0x310(%rax)" (0x00000310) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
?? ()
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
Title: unity-window-
UpgradeStatus: Upgraded to natty on 2011-02-24 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #727041, 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.