After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 620001 - Delete button sometimes does not work in Nautilus
Delete button sometimes does not work in Nautilus
Status: RESOLVED DUPLICATE of bug 606619
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.30.x
Other Linux
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-05-29 08:16 UTC by Jochem
Modified: 2010-05-30 17:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jochem 2010-05-29 08:16:22 UTC 
When selecting a few files and then hit Delete on the keyboard to delete these files, they are transported fine to Trash. When I then select a few files again - in the same Nautilus window, not per se in the same folder - and then hit Delete, nothing happens. After reselecting the files and hit Delete again, the files are transported to Trash.

This is always the case and I've made sure that I pressed Delete hard enough. I have no reason to believe the keyboard malfunctions (but unfortunately I haven't been able to test with another one yet).

Extra info:
- Selecting files and then choosing Move to Trash always or moving them to Trash works.
- OS: Ubuntu 10.04 x86_64
- GNOME Nautilus version: 2.30.1
- GNOME version: 2.30.0
Comment 1 Nelson Benitez 2010-05-29 18:06:34 UTC 
I couldn't reproduce this, do you have a reliable way to reproduce this?
Comment 2 Jochem 2010-05-29 20:48:39 UTC 
I'm afraid not. Furthermore, all the settings in Nautilus are standard and there are no extensions installed.
Comment 3 Cosimo Cecchi 2010-05-30 17:50:05 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 606619 ***