nautilus crashed with SIGSEGV in g_closure_invoke()

[pss]

Binary package hint: nautilus

Description: Ubuntu 9.10
Release: 9.10
nautilus:
  Встановлено: 1:2.28.1-0ubuntu1
  Кандидат: 1:2.28.1-0ubuntu1
  Таблиця версій:
 *** 1:2.28.1-0ubuntu1 0
        500 http://ua.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
Nautilus crashed when try to unmount partition on ext4 fs
An IO "Permission denied" error occured

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Oct 31 14:54:26 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.28.1-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=uk_UA.UTF-8
 PATH=(custom, user)
 LANG=uk_UA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x104b6c3: cmpb $0x0,(%edx)
 PC (0x0104b6c3) ok
 source "$0x0" ok
 destination "(%edx)" (0x08fe5000) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:_gtk_mount_operation_lookup_info (context=0x8c47628,
gtk_mount_operation_show_processes (op=0x8e6fdb8,
?? () from /usr/lib/libgio-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0

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