gtk-window-decorator crashed with SIGSEGV in max_window_name_width()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
quitting stellarium is the trigger of window-decorator chrash i guess
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-gnome 1:0.9.7.
ProcVersionSign
Uname: Linux 3.2.0-19-
.tmp.unity.
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CompizPlugins: [core,composite
CompositorRunning: compiz
CrashCounter: 1
Date: Tue Mar 20 15:00:27 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/
GraphicsCard:
Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:215a]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120315)
MachineType: LENOVO 4384AW2
ProcCmdline: gtk-window-
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x80602a6 <max_window_
PC (0x080602a6) ok
source "0x204(%eax)" (0x00000204) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
max_window_
update_
?? ()
g_cclosure_
?? () from /usr/lib/
Title: gtk-window-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 11/28/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6MET88WW (1.48 )
dmi.board.name: 4384AW2
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 4384AW2
dmi.product.
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.7.
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
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 #948580, 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.