Ubuntu
nautilus package

Rapidly creating/renaming new folders leads to confusing "could not be renamed" message

Bug #663146 reported by Scott Ritchie on 2010-10-19

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Nautilus	Invalid	Undecided	Unassigned
	nautilus (Ubuntu)	Invalid	Low	Unassigned

Bug Description

Binary package hint: nautilus

Right click -> create folder, rename to "a". Then quickly do the same with "b". If you're quick enough (like using hotkeys), you will sometimes encounter an error message:

The item could not be renamed
There is no "untitled folder" in this folder. Perhaps it was just moved or deleted?

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Oct 19 01:16:47 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: nautilus

Tags:

Revision history for this message

Scott Ritchie (scottritchie) wrote on 2010-10-19:

Dependencies.txt Edit (5.1 KiB, text/plain; charset="utf-8")
GConfNonDefault.txt Edit (467 bytes, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (348 bytes, text/plain; charset="utf-8")

Pedro Villavicencio (pedro) on 2010-10-19

Changed in nautilus (Ubuntu):
importance:	Undecided → Low
status:	New → Triaged

Bug Watch Updater (bug-watch-updater) on 2010-10-19

Changed in nautilus:
importance:	Unknown → Medium
status:	Unknown → New

Revision history for this message

dino99 (9d9) wrote on 2013-05-29:

EOL reached on that serie https://wiki.ubuntu.com/Releases

Changed in nautilus (Ubuntu):
status:	Triaged → Invalid
Changed in nautilus:
importance:	Medium → Undecided
status:	New → Invalid

Revision history for this message

Scott Ritchie (scottritchie) wrote on 2013-05-31:

Still live in 13.04, except now it's easier to trigger, because by default when you make a new folder it has the name highlighted for renaming.

The error message is now: There is no "" in this location. Perhaps it was just moved or deleted?

Changed in nautilus (Ubuntu):
status:	Invalid → Confirmed

dino99 (9d9) on 2013-05-31

tags:

added: raring
removed: maverick

Revision history for this message

dino99 (9d9) wrote on 2013-05-31:

Hi Scott,
is that issue seen with raring got with the hardware as the initial report ? That was with gnome2 and raring is gnome3, so the app/libs are so different now.
maybe its an hardware issue (keyboard or else), that should be narrowed down running: sudo fwts for example.

as that report has never catch the devs attention, i doubt it will grab a better one now without giving proof of trouble.

Changed in nautilus (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Scott Ritchie (scottritchie) wrote on 2013-05-31:

It's completely different hardware than my original reporting machine, I suspect that it's reproducable in a lot of cases (just give it a try).

dino99 (9d9) on 2015-07-09

Changed in nautilus (Ubuntu):
status:	Incomplete → Invalid

Revision history for this message

Kevin Markwell (kevinmarkwell) wrote on 2015-07-09:

screenshot of Nautilus showing error message alert box Edit (154.8 KiB, image/jpeg)

Still happens on Ubuntu 15.04 (Vivid Vervet).
Occurs every time when done fairly quickly.
Easiest to cause via [Ctrl][Shift]N test [Return] [Ctrl][Shift]N test2 [Return]
Also occurs in Nemo 4.2.2.
Cannot reproduce in Thunar 1.6.6.
Nautilus screenshot attached.