nautilus crashed with SIGSEGV

[Martin Olsson]

Binary package hint: nautilus

crash... stack contains ?? but I suspect after retracing it might become a dupe of Bug #403549 ??

ProblemType: Crash
Architecture: amd64
Date: Sat Jan 30 15:45:01 2010
Disassembly: 0x7f5667bf8def: Cannot access memory at address 0x7f5667bf8def
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.29.2-0ubuntu1
ProcCmdline: nautilus --sm-client-id 1047cea494f387188d126236167244559500000017680029 --sm-client-state-file /home/username/.config/session-state/nautilus-1264805696.desktop
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
SegvAnalysis:
 Segfault happened at: 0x7f5667bf8def: Cannot access memory at address 0x7f5667bf8def
 PC (0x7f5667bf8def) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV
Uname: Linux 2.6.32-12-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Martin Olsson (mnemo)]

apport crash report was there in notification tray pretty much right away when I booted it... I'm using lucid pre-release bits as of 2010-01-30... the crash doesn't happen every boot

[Apport retracing service (apport)]

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.

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