Nautilus crashes when attempting to open /usr/bin
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: nautilus
Whenever I attempt to open /usr/bin, Nautilus crashes (undetected by Apport). So far I have been unable to reproduce this behavior when opening any other folders (even if they contain a lot of files like /usr/bin), but attempting to open /usr/bin crashes Nautilus every time.
I have attached a backtrace of the crash. If I need to add debug symbols and re-run it, let me know.
I attempted to get a valgrind report, but the valgrind process ends after Nautilus is launched. If there is a way to attach the pid like with gdb, then I can provide a valgrind report as well.
This is with Lucid, fully up-to-date.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.30.0-0ubuntu4
ProcVersionSign
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Tue Apr 27 00:26:52 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: nautilus
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.
If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.
If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/ apport/ apport- qt --crash- file=/var/ crash/_ my_crash_ report. crash in a terminal - where _my_crash_ report. crash is the crash you would like to report.
I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.