nautilus crashed with SIGSEGV in malloc()

[Philip Peitsch]

Binary package hint: nautilus

Happened just after login

ProblemType: Crash
Architecture: amd64
CheckboxSubmission: caa155f54c0f4362405eca2142b98252
CheckboxSystem: 9038dc5b445882e24b06ebe5cf05c9fc
CrashCounter: 1
Date: Sat Sep 12 11:49:17 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.27.92-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
SegvAnalysis:
 Segfault happened at: 0x7fa25de3ce60: mov 0x8(%r12),%r15
 PC (0x7fa25de3ce60) ok
 source "0x8(%r12)" (0x7fa25ff86ac0) in non-readable VMA region: 0x7fa25fd9c000-0x7fa25ff9c000 ---p /usr/lib/libcairo.so.2.10800.8
 destination "%r15" ok
SegvReason: reading VMA /usr/lib/libcairo.so.2.10800.8
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 malloc () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 iconv_open () from /lib/libc.so.6
Title: nautilus crashed with SIGSEGV in malloc()
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users

[Apport retracing service (apport)]

StacktraceTop:malloc_consolidate (av=0x7fa25e131e40) at malloc.c:5089
_int_malloc (av=0x7fa25e131e40, bytes=977)
*__GI___libc_malloc (bytes=32640) at malloc.c:3638
__gconv_open (toset=<value optimized out>,
iconv_open (tocode=<value optimized out>,

[Pedro Villavicencio (pedro)]

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.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.