compiz crashed with SIGSEGV in FT_Load_Glyph()

Bug #1287466 reported by JoshuaStrobl on 2014-03-04
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
Undecided
Unassigned

Bug Description

When I hit the super / windows key and started typing "terminal", compiz crashed.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140303-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 4 03:45:13 2014
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2014-03-01 (2 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f7b8723223a: movswl 0x18(%rdx),%r12d
 PC (0x7f7b8723223a) ok
 source "0x18(%rdx)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%r12d" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading 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-04 (0 days ago)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

JoshuaStrobl (joshua.strobl) wrote :
information type: Private → Public
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity (Ubuntu):
status: New → Confirmed

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

tags: removed: need-amd64-retrace
JoshuaStrobl (joshua.strobl) wrote :

Unmarked bug as duplicate as Apport retracing service references a bug that is either private or does not exist. Please have the other bug be marked as public, if it does exist, so individuals like myself can track it's progress.

Christopher Townsend (townsend) wrote :

Ok, made the other bug public, so let's reduplicate this.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers