Lucid: nautilus crashed with SIGSEGV after login

[Anthony Hook]

Binary package hint: nautilus

I did updates on 2/22/10 on Lucid Lynx, and received this notification immediately after logging in.

ProblemType: Crash
Architecture: amd64
Date: Thu Feb 11 12:23:18 2010
Disassembly: 0x7f3b7d0baf85: Cannot access memory at address 0x7f3b7d0baf85
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: nautilus 1:2.29.90-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SegvAnalysis:
 Segfault happened at: 0x7f3b7d0baf85: Cannot access memory at address 0x7f3b7d0baf85
 PC (0x7f3b7d0baf85) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nautilus
Stacktrace:
 #0 0x00007f3b7d0baf85 in ?? ()
 No symbol table info available.
 #1 0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV
Uname: Linux 2.6.32-13-generic x86_64
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vboxusers
XsessionErrors:
 (gnome-settings-daemon:2236): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2236): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2267): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (Do:2274): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.

[Apport retracing service (apport)]

Stacktrace:
 #0 0x00007f3b7d0baf85 in ?? ()
 No symbol table info available.
 #1 0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()

[Pedro Villavicencio (pedro)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Anthony Hook (anthonyhook)]

I have not been able to reproduce this problem with Lucid's Alpha release yet, it may have been a one-time deal.

[Victor Vargas (kamus)]

@Anthony, is this issue still affecting you using latest version of nautilus 2.30.x? Thanks in advance.

[Anthony Hook (anthonyhook)]

@Kamus I am not having this problem since 2.30.x, it hasn't done this yet. Thanks.

[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.