nautilus crashed with SIGSEGV

Bug #818587 reported by simon
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

ocurred when trying to erease some files of the trash; they were ereased and nautilus didn't close
.......................................................
ocurrió cuando intentaba borrar unos archivos de la papelera; fueron eliminados y nautilus NO se cerro.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
Architecture: amd64
Date: Sat Jul 30 12:26:48 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: nautilus /media/VOLUMEN\ NUE
ProcEnviron:
 LANGUAGE=es_VE:en
 PATH=(custom, no user)
 LANG=es_VE.utf8
 LC_MESSAGES=es_VE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f0b0372317a: movlpd (%rsi),%xmm2
 PC (0x7f0b0372317a) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm2" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-07-30 (0 days ago)
UserGroups:

Revision history for this message
simon (sianhulo) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #805968, 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.

visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.