Ubuntu
unity package

compiz crashed with SIGSEGV in FT_Load_Glyph()

Bug #1286745 reported by AleksK on 2014-03-02

This bug report is a duplicate of: Bug #1199571: Huge multi-threading violations in freetype. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	unity (Ubuntu)	New	Undecided	Unassigned

Bug Description

Crash Compiz when i opened a dash

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140228-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
Uname: Linux 3.13.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Sun Mar 2 13:28:58 2014
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2014-02-27 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224)
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=ru
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=ru_RU.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f3a60d9e7e0: mov %rdx,0x10(%rax)
PC (0x7f3a60d9e7e0) ok
source "%rdx" ok
destination "0x10(%rax)" (0x00000010) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
Title: compiz crashed with SIGSEGV in FT_Load_Glyph()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

AleksK (aleks-kaverin) wrote on 2014-03-02:

Dependencies.txt Edit (30.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-07: This bug is a duplicate

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 #1199571, 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.