gtk-window-decorator crashed with SIGSEGV in gwd_get_decor_frame()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
gtk-window-
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-gnome 1:0.9.4git20110
ProcVersionSign
Uname: Linux 2.6.38-7-generic i686
NonfreeKernelMo
.proc.driver.
.proc.driver.
.proc.driver.
NVRM version: NVIDIA UNIX x86 Kernel Module 270.30 Fri Feb 25 14:34:41 PST 2011
GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-6ubuntu4)
Architecture: i386
CompizPlugins: [core,bailer,
CompositorRunning: compiz
Date: Wed Mar 23 14:45:25 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus: nvidia-current, 270.30, 2.6.38-7-generic, i686: installed
ExecutablePath: /usr/bin/
GraphicsCard: nVidia Corporation NV43 [GeForce 6600 GT] [10de:0140] (rev a2) (prog-if 00 [VGA controller])
JockeyStatus: xorg:nvidia_current - Драйвер ускоренной графики NVIDIA (Проприетарные, Активирован, Используется)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=
LANG=ru_RU.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
Renderer: Unknown
Signal: 11
SourcePackage: compiz
StacktraceTop:
gwd_get_
?? ()
?? () from /usr/lib/
gtk_menu_popup () from /usr/lib/
action_menu_map ()
Title: gtk-window-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare
dmi.bios.date: 11/07/2007
dmi.bios.vendor: Intel Corp.
dmi.bios.version: TS94610J.
dmi.board.
dmi.board.name: D946GZIS
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD66165-302
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCor
version.compiz: compiz 1:0.9.4git20110
version.libdrm2: libdrm2 2.4.23-1ubuntu5
version.
version.
version.
version.
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 #740767, 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.