metacity crashed with SIGSEGV in pango_ot_info_get()

[Albatro74]

Binary package hint: metacity

The error message showed up although I didn't notice a strange behavior. Might be that something on the background failed.

ProblemType: Crash
Architecture: amd64
Date: Tue Oct 13 10:56:31 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/metacity
Package: metacity 1:2.28.0-0ubuntu1
ProcCmdline: metacity
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SegvAnalysis:
 Segfault happened at: 0x7fe609750687: movb $0x0,0x6(%rax)
 PC (0x7fe609750687) ok
 source "$0x0" ok
 destination "0x6(%rax)" (0x7fe6020e0d9a) in non-writable VMA region: 0x7fe6020df000-0x7fe602129000 r--p /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-Bold.ttf
SegvReason: writing VMA /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-Bold.ttf
Signal: 11
SourcePackage: metacity
StacktraceTop:
 ?? () from /usr/lib/libpangoft2-1.0.so.0
 ?? () from /usr/lib/libpangoft2-1.0.so.0
 ?? () from /usr/lib/libpangoft2-1.0.so.0
 ?? () from /usr/lib/libpangoft2-1.0.so.0
 pango_ot_info_get ()
Title: metacity crashed with SIGSEGV in pango_ot_info_get()
Uname: Linux 2.6.31-13-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:GSUBGPOS::sanitize (this=<value optimized out>,
GSUB::sanitize (this=0x213db60, context=0x0)
_hb_ot_layout_init (face=0x213da70)
hb_face_create_for_data (
pango_ot_info_get (face=0x2154020)

[Pedro Villavicencio (pedro)]

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=598611

[Pedro Villavicencio (pedro)]

do you have any specific steps on how to reproduce the issue? Thanks.

[Albatro74 (paolo-bacchetta)]

No unfortunately I cannot reproduce anything related to that. I'm sorry.
I'll keep in touch in case the error shows up again. In any case I
didn't notice the problem anymore since I updated the distro...

On Mon, 2009-10-26 at 18:25 +0000, Pedro Villavicencio wrote:
> do you have any specific steps on how to reproduce the issue? Thanks.
>