gtk-window-decorator crashed with SIGSEGV in max_window_name_width()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I dont know what my mom did in computer but when i returned skype was frized and after closing skype getted this error. Most of my errors in Ubuntu happening with skype. I dont use this shit but a lot of people(which age is +30) also using this for community.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-gnome 1:0.9.7.
ProcVersionSign
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelMo
.proc.driver.
.proc.driver.
.tmp.unity.
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,
CompositorRunning: compiz
CrashCounter: 1
Date: Sat Mar 24 22:04:25 2012
DistUpgraded: 2012-03-13 22:12:23,624 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: CLEVO P150HMx
ProcCmdline: /usr/bin/
ProcKernelCmdLine: BOOT_IMAGE=
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: compiz
Title: gtk-window-
UpgradeStatus: Upgraded to precise on 2012-03-13 (11 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XorgConf:
Section "Device"
Identifier "Default Device"
Option "NoLogo" "True"
EndSection
dmi.bios.date: 02/15/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.
dmi.board.name: P150HMx
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: CLEVO
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: P150HMx
dmi.product.
dmi.sys.vendor: CLEVO
version.compiz: compiz 1:0.9.7.
version.ia32-libs: ia32-libs 20090808ubuntu35
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.
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 #953368, 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.