compiz crashed with SIGSEGV in FT_Load_Glyph()

Bug #1301903 reported by Rachel Greenham on 2014-04-03
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
Undecided
Unassigned

Bug Description

I'd opened the dash, and type 't', then I aimed for 'w' (looking for unity tweak tool) but i think i missed and hit some nearby key, because I was at a funny angle to the keyboard.

Everything froze up. Then I think some watchdog cut in and recovered the session and launched this bug.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140402-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 3 13:02:43 2014
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2014-03-08 (25 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f5ecc17793c: testb $0x1,(%rax)
 PC (0x7f5ecc17793c) ok
 source "$0x1" ok
 destination "(%rax)" (0x00000000) 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: Upgraded to trusty on 2014-03-10 (23 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers