nautilus crashed with SIGSEGV in g_closure_invoke()

[Filiprino]

I opened the properties dialog of an MKV file sitting on my desktop and some seconds after closing that dialog, a crash message showed up with my desktop completely blank, only with the wallpaper, no icons.
The Unity launcher and upper bar is still working perfectly.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: totem 3.4.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
Date: Sat Jan 12 21:33:14 2013
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2010-07-12 (914 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MarkForUpload: True
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f465231c16b: mov (%rcx),%rdi
 PC (0x7f465231c16b) ok
 source "(%rcx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? () from /usr/lib/nautilus/extensions-3.0/libtotem-properties-page.so
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to quantal on 2012-12-26 (17 days ago)
UserGroups: adm admin cdrom debian-tor dialout fuse lpadmin plugdev sambashare wireshark www-data

[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 #1031870, 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.