nautilus crashed with SIGSEGV

[Yannick Pflanzer]

I used Firefox and suddenly Nautilus crashed. I do not know the exact cause.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-16.24-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Fri Sep 28 19:23:58 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'1095x739+65+24'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1afb841923: mov 0x30(%rbx),%rdi
 PC (0x7f1afb841923) ok
 source "0x30(%rbx)" (0x00006780) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 (firefox:2655): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed
 (firefox:2655): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed
 (gnome-settings-daemon:2087): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.34.0/./gobject/gsignal.c:3397: signal name `got_published_files' is invalid for instance `0x7f5390001600'

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