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 345150 - Keyboard issues when deleting files
Keyboard issues when deleting files
Status: RESOLVED DUPLICATE of bug 540107
Product: nautilus
Classification: Core
Component: general
2.14.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-06-17 01:08 UTC by Sven Arvidsson
Modified: 2008-10-13 12:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Sven Arvidsson 2006-06-17 01:08:33 UTC
This bug was reported to the Debian BTS.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367610

Package: nautilus
Version: 2.14.1-2
Severity: normal


Hi,

(For this bug report, please read "file" as "file/directory".)

I've discovered that when I'm deleting files I can reach a situation where
I can't easily use the keyboard to select the last file.  It is necessary
to do one of the following:

 - Control-A
 - leave the directory and re-enter it
 - use the mouse

the first one is not obvious (and I'm not sure if novice users would find
it) and the latter two are somewhat annoying.

Normally if no files are hilighted in Nautilus you can hit the "right"
key and the first file will be hilighted.  When a file is deleted then
the next file has a selection box around the name, but it isn't hilighted.
It is necessary to use an arrow key to move the hilight onto another
file.

But, if there are only two files left, and you delete one of them, there
is no other file to move the selection on to and hilight.  So you need
to carry out one of the three actions above.

I'm not sure if there is any clear solution to this...
Comment 1 Nelson Benitez 2008-10-13 12:29:29 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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