gnome-shell crashed with SIGSEGV in Ins_MDRP()

[Bernd Nottelmann]

This happened after I rebooted my machine and logged on.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-shell 3.4.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic i686
ApportVersion: 2.0.1-0ubuntu3
Architecture: i386
Date: Mon Apr 16 18:22:11 2012
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x136a395 <TT_RunIns+10677>: sub 0x4(%ebp),%eax
 PC (0x0136a395) ok
 source "0x4(%ebp)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 TT_RunIns () from /usr/lib/i386-linux-gnu/libfreetype.so.6
 ?? () from /usr/lib/i386-linux-gnu/libfreetype.so.6
 ?? () from /usr/lib/i386-linux-gnu/libfreetype.so.6
 ?? () from /usr/lib/i386-linux-gnu/libfreetype.so.6
 FT_Load_Glyph () from /usr/lib/i386-linux-gnu/libfreetype.so.6
Title: gnome-shell crashed with SIGSEGV in TT_RunIns()
UpgradeStatus: Upgraded to precise on 2012-04-01 (15 days ago)
UserGroups: adm admin lpadmin sambashare

[Apport retracing service (apport)]

StacktraceTop:
 Ins_MDRP (exc=0xaa01878, args=<optimized out>) at /build/buildd/freetype-2.4.8/freetype-2.4.8/src/truetype/ttinterp.c:6133
 TT_RunIns (exc=0xaa01878) at /build/buildd/freetype-2.4.8/freetype-2.4.8/src/truetype/ttinterp.c:8105
 TT_Run_Context (exec=<optimized out>, debug=<optimized out>) at /build/buildd/freetype-2.4.8/freetype-2.4.8/src/truetype/ttinterp.c:751
 TT_Hint_Glyph (loader=0xbfabb2e8, is_composite=0 '\000') at /build/buildd/freetype-2.4.8/freetype-2.4.8/src/truetype/ttgload.c:802
 TT_Process_Simple_Glyph (loader=0xbfabb2e8) at /build/buildd/freetype-2.4.8/freetype-2.4.8/src/truetype/ttgload.c:923

[Launchpad Janitor (janitor)]

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