nautilus crashed with SIGSEGV

[dust]

Binary package hint: nautilus

was trying ftp://ftp.videolan.org/pub/testing/vlc-1.0.0-rc2/

can not unmount

ProblemType: Crash
Architecture: i386
Disassembly: 0xb6392d50:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.26.2-0ubuntu2
ProcCmdline: nautilus --no-desktop /home/hostname
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
Stacktrace: #0 0xb6392d50 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: nautilus crashed with SIGSEGV
Uname: Linux 2.6.28-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

scrollkeeper: installed version None, latest version: 0.3.14-16ubuntu1
libcups2: installed version 1.3.9-17ubuntu3, latest version: 1.3.9-17ubuntu3.1
libxi6: installed version 2:1.2.0-1ubuntu1.1, latest version: 2:1.2.0-1ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[dust (hannes-b)]

can not install scrollkeeper because it would remove rarian-compat, ubuntu-desktop and ubuntustudio-desktop.

suggestions?

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace 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.

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