ctrl-A delete on contents of directory; nautilus immediately crashed. Not replicated.

Bug #478541 reported by Chris Thornett
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nautilus

Used Archive Manager to extract some files from ISO into a folder; tried to access those files from a WINE application (Diablo II); exited the game; selected all files in folder; hit the delete key; all nautilus windows disappeared and nautilus crash report appeared
Later checked and the files had been successfully deleted.
ubuntu 9.10, only one user, nautilus 1:2.28.1-0ubuntu1

ProblemType: Crash
Architecture: i386
Date: Sun Nov 8 15:18:03 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.28.1-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x811ac21 <nautilus_file_peek_display_name+17>: mov 0xc(%eax),%edx
 PC (0x0811ac21) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 nautilus_file_peek_display_name (file=0x0) at nautilus-file.c:3700
 nautilus_file_get_display_name (file=0x0)
 selection_changed_callback (window=0x8e0b018,
 IA__g_cclosure_marshal_VOID__VOID (closure=0x8e7e7f8,
 IA__g_closure_invoke (closure=0x8e7e7f8, return_value=0x0,
Title: nautilus crashed with SIGSEGV in nautilus_file_peek_display_name()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse-access sambashare

Revision history for this message
Chris Thornett (chris-thornett) 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 #477546, 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-i386-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.