Nothing more
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 23 00:47:09 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'840x550+58+71'"
InstallationDate: Installed on 2013-09-14 (8 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130903)
MarkForUpload: True
ProcCmdline: nautilus /home/username/Documentos/Aficiones/4WD\ Truck/Motor
ProcEnviron:
LD_LIBRARY_PATH=<set>
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=es_ES.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f9950fcedd5: mov 0x10(%rax),%rdi
PC (0x7f9950fcedd5) ok
source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? () from /usr/lib/libgnome-desktop-3.so.7
gnome_desktop_thumbnail_factory_generate_thumbnail () from /usr/lib/libgnome-desktop-3.so.7
?? ()
start_thread (arg=0x7f996b54a700) at pthread_create.c:311
clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Title: nautilus crashed with SIGSEGV in gnome_desktop_thumbnail_factory_generate_thumbnail()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy fuse games lpadmin plugdev sambashare saned scanner src sudo tape tty users video voice
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 #1203349, 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.