nautilus quits when deleting a folder in the left side treeview
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nautilus |
Fix Released
|
Critical
|
|||
nautilus (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Oneiric |
Fix Released
|
High
|
Unassigned |
Bug Description
Steps to reproduce it:
1- Open a nautilus folder
2- Change the Sidebar view to Tree.
3- Delete a directory on that Tree.
ProblemType: CrashDistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.90-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-10-generic i686
NonfreeKernelMo
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
AssertionMessage: *** glibc detected *** nautilus: free(): invalid pointer: 0x08aa2290 ***
CrashCounter: 1
Date: Fri Sep 9 09:34:45 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcCmdline: nautilus
ProcEnviron:
LANGUAGE=en_ZA:en
PATH=(custom, no User Name)
LANG=en_ZA.UTF-8
SHELL=/bin/bash
Signal: 6SourcePackage: nautilus
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/i386-
abort () from /lib/i386-
?? () from /lib/i386-
?? () from /lib/i386-
Title: nautilus assert failure: *** glibc detected *** nautilus: free(): invalid pointer: 0x08aa2290 ***
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Changed in nautilus: | |
importance: | Unknown → Critical |
status: | Unknown → New |
Changed in nautilus: | |
status: | New → Fix Released |
tags: |
added: verification-done removed: verification-needed |
Changed in nautilus (Ubuntu Oneiric): | |
status: | Fix Committed → Fix Released |
Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace. wiki.ubuntu. com/DebuggingPr ogramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
Please try to obtain a backtrace manually following the instructions at http://