gnome-about-me crashed with SIGSEGV in pixman_image_composite()

[Alvin Thompson]

Binary package hint: gnome-control-center

tried to invoke System-->Preferences-->About Me

ProblemType: Crash
Architecture: amd64
Date: Fri Sep 25 22:51:47 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-about-me
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha amd64 (20090925)
NonfreeKernelModules: nvidia
Package: gnome-control-center 1:2.28.0-0ubuntu2
ProcCmdline: gnome-about-me
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x7fffa6733f3d: mov %rcx,0x18(%rsp)
 PC (0x7fffa6733f3d) ok
 source "%rcx" ok
 destination "0x18(%rsp)" (0x7fffa46425a8) in non-writable VMA region: 0x7fffa4640000-0x7fffa4646000 r--p /usr/lib/libgnutls.so.26.14.10
SegvReason: writing VMA /usr/lib/libgnutls.so.26.14.10
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/libpixman-1.so.0
 ?? () from /usr/lib/libpixman-1.so.0
 pixman_image_composite ()
 ?? () from /usr/lib/libcairo.so.2
 ?? () from /usr/lib/libcairo.so.2
Title: gnome-about-me crashed with SIGSEGV in pixman_image_composite()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:pixman_composite_rect_general (data=0x7fffa4648660)
pixman_image_composite_rect (
pixman_image_composite (op=<value optimized out>,
_cairo_image_surface_composite_trapezoids (
_cairo_surface_composite_trapezoids (op=17,

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Alvin Thompson (alvint-deactivatedaccount)]

It only crashed that one time...

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.