unity-greeter crashed with SIGSEGV in FT_Set_Transform()

[Till Kamppeter]

Right after login.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-greeter 0.0.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 25 19:34:50 2011
ExecutablePath: /usr/sbin/unity-greeter
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7f0997a38c6f <FT_Set_Transform+15>: movl $0x0,0x38(%rax)
 PC (0x7f0997a38c6f) ok
 source "$0x0" ok
 destination "0x38(%rax)" (0x66fffffe5de9d137) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity-greeter
StacktraceTop:
 FT_Set_Transform () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
 _cairo_ft_unscaled_font_set_scale (unscaled=0x188b800, scale=<optimized out>) at /build/buildd/cairo-1.10.2/src/cairo-ft-font.c:780
 _cairo_ft_font_face_scaled_font_create (abstract_font_face=0x188b910, font_matrix=0x1a53ec8, ctm=0x1a53f50, options=0x7ffffc89bb00, font_out=0x7ffffc89b8c8) at /build/buildd/cairo-1.10.2/src/cairo-ft-font.c:1845
 INT_cairo_scaled_font_create (font_face=0x188b910, font_matrix=<optimized out>, ctm=<optimized out>, options=0x7ffffc89bb00) at /build/buildd/cairo-1.10.2/src/cairo-scaled-font.c:1053
 _cairo_gstate_ensure_scaled_font (gstate=0x1a53e60) at /build/buildd/cairo-1.10.2/src/cairo-gstate.c:1803
Title: unity-greeter crashed with SIGSEGV in FT_Set_Transform()
UpgradeStatus: Upgraded to oneiric on 2009-12-18 (615 days ago)
UserGroups:

[Till Kamppeter (till-kamppeter)]

lightdm does not come up. Switched to gdm via SSHing in from another box. Logged in via GDM, crash message appears right after login.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #833619, 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.