From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830
Description of problem:
Nautilus includes the ability to remove its dialog box asking you if you wish to
move a file to the Trash or delete the file.
The current behavior is as such in Nautilus:
1) If file is located on the same partition as ~/.Trash - move the file to the
~/.Trash and catalog.
2) If file is not located on the same partition as ~/.Trash - delete the file
(asking the user).
Understanding this behavior - if I uncheck "Ask before emptying Trash or
DELETING FILES", I should have the ability to simply click and "Del" to my
heart's content. If so desired, a dialog box could pop up warning the user
_THEN_ that removing this preference could cause a user to inadvertently
permanently delete files.
However, if I go to /tmp on my system (which resides in a different partition),
Nautilus still pops up a dialog box informing me that it is unable to move the
file to the Trash and asks if I wish to permanently delete the file.
This is related to another bug I filed - Bug 78671. "Fixing" bug 78671 is
definitely the preferable option (but would take longer than simply correcting
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open a Nautilus window
2. Go to Edit -> Preferences -> Desktop & Trash
3. Uncheck "Ask before emptying Trash or deleting files"
4. Close configuration window
5. Go to another partition
6. Click on a file to delete and press "Del".
Actual Results: A dialog box pops up (ASKing before deleting a file).
Expected Results: File should be removed. Done and done.
$ rpm -q nautilus
Changing to MoveUpstream keyword instead of GnomeUpstream tracking bug.
sorry about the spam.
I can't reproduce this with 2.8.0. Do you still see this in fc3test3?
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still
running Red Hat Linux, you are strongly advised to upgrade to a
current Fedora Core release or Red Hat Enterprise Linux or comparable.
Some information on which option may be right for you is available at
Red Hat apologizes that these issues have not been resolved yet. We do
want to make sure that no important bugs slip through the cracks.
If this issue is still present in a current Fedora Core release, please
open a new bug with the relevant information.
Closing as CANTFIX.