Bug 155058 - Nautilus unselects file when trying to rename
Nautilus unselects file when trying to rename
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: nautilus (Show other bugs)
3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Alexander Larsson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-15 17:19 EDT by stephen
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: Gnome 2.10
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-10-30 10:01:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description stephen 2005-04-15 17:19:41 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

Description of problem:
I right click on a file in nautilus, select rename, nautilus file name editting mode then accepts the name without me having time to change the file name.

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

How reproducible:
Didn't try

Steps to Reproduce:
1.  Right click on file
2.  Select Rename
3.  
  

Actual Results:  Can't edit the name

Expected Results:  Should be able to move mouse into text, select and insertion point and edit name.

Additional info:

I used to think it only happened in list view but happens in icon view from time to time
Comment 1 Roland Knöpfli 2005-04-18 08:12:44 EDT
same problem here using nautilus-2.10.0

does only appear in list view mode. when i change to icon view i can rename the
file without any problems.
Comment 2 stephen 2005-10-29 22:15:15 EDT
I have no long seen this problem with 2.10 or 2.12.  How about your Roland?
Comment 3 Roland Knöpfli 2005-10-30 04:47:35 EST
same here, stephen. since i'm using fedora core 4 (gnome 2.10.0) instead of
ubuntu 5.04 or fedora core 3 i haven't seen the problem anymore.
i think this bug got fixed and so doesn't exist anymore.

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