← Back to team overview

desktop-packages team mailing list archive

[Bug 393158] Re: There is no warning message when inserting a forbidden symbol (/) in filename

 

** Changed in: hundredpapercuts
     Assignee: (unassigned) => Papercuts Ninja (papercuts-ninja)

** Changed in: hundredpapercuts
    Milestone: None => precise-9-miscellaneous

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/393158

Title:
  There is no warning message when inserting a forbidden symbol (/) in
  filename

Status in GTK+ GUI Toolkit:
  New
Status in One Hundred Paper Cuts:
  Triaged
Status in “gtk+2.0” package in Ubuntu:
  Triaged

Bug description:
  When the user tries to save a file from the "Save" option and Inputs
  labels containing "/" nothing happens, the "Save" dialog remains
  opened and he is not warned with an error message.

  An average user cannot understand this, since the user is not informed
  of what mistake he has done!

  Papercut solution:
   An appropriate dialogue is needed:

  "File names cannot contain "/" "
  "If you intend to save the file in a folder "xx", First Create folder "xx" in the location"

  
  ------------- [Old description] -------------
  When the user types a filename, if he puts a forbidden symbol (like "/" for example) in the name, when clicking on the "Save" button there's a really obscure message coming out: instead of saying "one or more character you have typed are not admitted" , or  "the symbol "/" is not admitted in a file name", it says (approximately, I'm translating from the italian version) "THE FOLDER'S CONTENT CANNOT BE VISUALIZED: error in executing stat of file /home/john/Desktop/xxxxxx : no file or directory".
  --------------------------

  I tried with Openoffice.org, Gedit, Archive manager, Brasero, Sound
  recorder and Gimp, and they all have the same behaviour. The only one
  to give the correct response has been Nautilus which told me that "/"
  is not allowed. I made the tests on a virtual machine running Karmic
  Alpha 2 updated to 07/05/09.

  I think this is very confusing for the newcomer: if it's easily
  fixable, it should be fixed in Karmic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/393158/+subscriptions