compiz crashed with SIGSEGV in FT_Load_Glyph()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unity (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.
ProcVersionSign
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Mar 30 14:25:12 2014
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2013-07-04 (268 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=de_DE
PATH=(custom, no user)
XDG_RUNTIME_
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f6eb38ce860: mov %rdx,0x10(%rax)
PC (0x7f6eb38ce860) 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/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
FT_Load_Glyph () from /usr/lib/
Title: compiz crashed with SIGSEGV in FT_Load_Glyph()
UpgradeStatus: Upgraded to trusty on 2014-03-29 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
| Niklas Wenzel (nikwen) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
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.