GNOME Bugzilla – Bug 142204
Close when standing in empty dir
Last modified: 2005-01-27 23:21:04 UTC
Description of Problem: The Nautilus window will crash if you're standing in a dir that is removed and nautilus tries to refresh it. Steps to reproduce the FIRST variant of the problem: 1. Enter a dir in either spatial or browser view using Nautilus. 2. Remove/Delete/ELIMINATE the dir you're standing in, either by terminal or by an other window. Steps to reproduce the SECOND variant of the problem: 1. Enter a dir in browser view using Nautilus. 2. Right click on the dir in the tree view and choose to move it to the paperbasket (why isn't there an eliminate option?). 3. In the main window, you'll be moved with the dir to the trash. 4. Empty the trash. Actual Results: Instance one: Nautilus window will close with an error message. Instance two: Nautilus window will close with an error message, after having moved you to the trash bin. Expected Results: Instance one: Moved the user one step up in the file hierachy. Instance two: Not being moved with the dir to the trash bin, and not being crashed when emptying it while you're standing in the dir. How often does this happen? Every time. Additional Information: Not that I can think of... just wonder why Nautilus always resizes it's browser window, I want it the size I defined it last time!
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused the crash. Please see http://bugzilla.gnome.org/getting-traces.cgi for more information about getting a useful stack trace.
Problem number one does not seem to exist anymore (Nautilus 2.6.3). Problem number two is still a problem. Nautilus was compiled with --fomit-frame-pointer so I'll need to recompile it to get a good trace. Should I recompile anything else for the stack trace to be correct, or is nautilus all?
recompiling nautilus, gnome-vfs, and eel using CFLAGS="-g -O2" will probably be sufficient for an acceptable stack trace.
do you still get this bug ?
This is still a bug. Clarification: Nautilus does NOT CRASH. Nautilus BROWSER/SPATIAL window CLOSE. It is possible to reproduce this bug in similar ways. The one printed below is simply one that is certain. Same method applies to both, but I will be overly descriptive and rewrite for both: Spatial window close on removal of dir: Open up a terminal and in your home dir you run `mkdir testDir`. Start Nautilus in browser mode, E.G. open ANOTHER terminal and run `nautilus --browser`, and access $HOME/testDir. Press alt+tab to switch to terminal used to create directory. There you will run `rmdir testDir`. Nautilus browser window will disappear. You can use the same method with the spatial method, thereby closing the spatial window CURRENTLY IN THAT DIR. Other windows will remain unaffected. Expected action: Move user to directory up the directory tree, till existant directory found. If it in that process reaches a directory that it is not allowed to read it should, IMHO, transfer the user to his or her home dir. I am working on a stack trace, but since it doesn't crash, I question its use. However, I'm just a hobby programmer. I may have a look at the source too if time is on my side.
s/and rewrite for both/, though am lazy - will rewrite more clearly and definitely/ s/Spatial window close on removal of dir/Nautilus browser window close on removal of dir/ Sorry. Basically same thing for browser and spatial window anyway, as written in above comment.
right, that's a duplicate of #111223
*** This bug has been marked as a duplicate of 111223 ***