nautilus crashed with SIGSEGV in g_main_context_dispatch() after copying a file

[Aram Loosman]

Version info:
Ubuntu: 12.04
Nautilus: 1:3.3.90-0ubuntu4

I tried to copy a file from an usb pen to my personal folder (not encrypted).
After reopening nautilus i saw, that the file indeed was correctly copied, so the crash happened after copying.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.90-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CheckboxSubmission: 5189ea5bbf94b744fc317499337f6af4
CheckboxSystem: b1865df84255b8716d3bcc269ff410d1
Date: Mon Mar 5 08:53:53 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: org.gnome.nautilus.window-state geometry '819x250+65+24'
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=de_CH:de
 PATH=(custom, no user)
 LANG=de_CH.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f13197a03bf: mov %eax,0x8(%rbx)
 PC (0x7f13197a03bf) ok
 source "%eax" ok
 destination "0x8(%rbx)" (0x7f1200000008) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #944624, 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.