gnome-shell crashed with SIGSEGV in FT_Load_Glyph()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
no se a que se deba
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-shell 3.10.0.
ProcVersionSign
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 28 11:20:24 2013
DisplayManager: gdm
ExecutablePath: /usr/bin/
ExecutableTimes
GsettingsChanges: b'org.gnome.
InstallationDate: Installed on 2013-05-30 (120 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: /usr/bin/
ProcCwd: /home/ariel
SegvAnalysis:
Segfault happened at: 0x7f1c80462a10: mov %rdx,0x10(%rax)
PC (0x7f1c80462a10) 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: gnome-shell
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
FT_Load_Glyph () from /usr/lib/
SystemImageInfo: Error: [Errno 2] No existe el archivo o el directorio: 'system-image-cli'
Title: gnome-shell crashed with SIGSEGV in FT_Load_Glyph()
UpgradeStatus: Upgraded to saucy on 2013-06-03 (117 days ago)
UserGroups: adm autopilot cdrom dip lpadmin netdev plugdev sambashare sudo vboxusers
gdmSessionLog:
/etc/gdm/Xsession: Beginning session setup...
localuser:ariel being added to access control list
localuser:ariel being added to access control list
Script para cjkv iniciada en run_im.
Script para default iniciada en run_im.
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.