gnome-shell crashed with SIGSEGV in FT_Load_Glyph() error occurs touch aplications icon under activities
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
error occurs when touch aplications button under activities. This is gnome installed on kubuntu 14.10 beta 2
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gnome-shell 3.12.2-1ubuntu6
ProcVersionSign
Uname: Linux 3.16.0-21-generic x86_64
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri Oct 10 01:19:50 2014
DisplayManager: lightdm
ExecutablePath: /usr/bin/
GsettingsChanges: b'org.gnome.
InstallationDate: Installed on 2014-10-04 (6 days ago)
InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f0099e1a6dc: mov %rbx,0x18(%rax)
PC (0x7f0099e1a6dc) ok
source "%rbx" ok
destination "0x18(%rax)" (0x00000018) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
FT_Load_Glyph () from /usr/lib/
Title: gnome-shell crashed with SIGSEGV in FT_Load_Glyph()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo
| sleek (sillypeople139) 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 #1208379, 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.