compiz crashed with SIGSEGV in CompWindow::id()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
This happens every time I start gitk. It’s 100% reproducible, even under a freshly created account, and makes it completely impossible to run gitk under compiz (the window doesn’t even show up after the crash).
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4git20110
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Mon Apr 4 14:33:55 2011
DistroCodename: natty
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
ProcCmdline: /usr/bin/compiz
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x43bef0 <_ZN10CompWindo
PC (0x0043bef0) ok
source "0x58(%rdi)" (0x00000058) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
CompWindow::id() ()
CompScreen:
PrivateComposi
CompScreen:
PrivateGLScree
Title: compiz crashed with SIGSEGV in CompWindow::id()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
XsessionErrors:
(nautilus:1965): Gtk-WARNING **: Invalid input string
(nautilus:1965): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
(nautilus:1965): GLib-CRITICAL **: g_variant_
version.
version.
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 #747439, 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.