Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 118797 - moving a directory causes nautilus to crash
moving a directory causes nautilus to crash
Product: Fedora
Classification: Fedora
Component: nautilus (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Alexander Larsson
Depends On:
  Show dependency treegraph
Reported: 2004-03-20 09:28 EST by Glen
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-03-20 13:31:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Glen 2004-03-20 09:28:21 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)

Description of problem:
If I point nautilus to a particular directory, and then open up a
terminal and move that directory, and then go back to nautilus and hit
the "up" button, then nautilus crashes.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Open up nautilus and go to some directory.
2. Open a terminal and move the same directory.
3. Go back to nautilus and hit the "up" button.

Actual Results:  Nautilus crashes.

Expected Results:  I expected it to not crash.

Additional info:
Comment 1 Bart Martens 2004-03-20 13:31:45 EST

The problem does not occur when moving the directory that nautilus is
pointing to, but when moving the parent directory.

I don't see a crash, but I see nautilus display an error message and
close. The message is "<dir> couldn't be found. Perhaps it has
recently been deleted.".

This also happens on Debian Sarge with nautilus version 2.4.2-2.

This problem is also known upstream. I suggest to follow this bug
upstream, and forget it here.

Note You need to log in before you can comment on or make changes to this bug.