nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

[dino99]

Oneiric i386

How i got that crash:

- opened nautilus to select an app running with wine
- while this app was starting/loading, i've clicked on "x" on top left bar to close nautilus but it dont. So then i wanted to use nautilus menu to close it but it was frozen and the crash happened.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-7.8-generic-pae 3.0.0
Uname: Linux 3.0.0-7-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri Jul 29 11:44:59 2011
ExecutablePath: /usr/bin/nautilus
ProcCmdline: nautilus -n
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80cbcb7: mov 0x60(%edx),%eax
 PC (0x080cbcb7) ok
 source "0x60(%edx)" (0x00000060) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio avahi avahi-autoipd boinc cdrom couchdb crontab daemon debian-tor dialout disk fuse haldaemon klog kmem libuuid lpadmin mail messagebus mlocate mysql mythtv netdev ntp operator plugdev polkituser pulse root sambashare saned shadow ssh ssl-cert sudo syslog tty users utmp video voice www-data
mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2011-07-03T19:42:49

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #807875, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.