There is no warning message when inserting a forbidden symbol (/) in filename
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GTK+ |
Fix Released
|
Low
|
|||
One Hundred Papercuts |
In Progress
|
Low
|
Timothy Arceri | ||
gtk+2.0 (Ubuntu) |
Triaged
|
Low
|
Ubuntu Desktop Bugs |
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/
-------
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.
description: | updated |
description: | updated |
summary: |
- Incoherent warning message when inserting a forbidden symbol in filename + There is no warning message when inserting a forbidden symbol (/) in + filename |
description: | updated |
Changed in gtk+2.0 (Ubuntu): | |
status: | Incomplete → Triaged |
Changed in gtk: | |
status: | Unknown → New |
Changed in gtk: | |
importance: | Unknown → Low |
Changed in hundredpapercuts: | |
importance: | Undecided → Low |
status: | Confirmed → Triaged |
Changed in hundredpapercuts: | |
assignee: | nobody → Papercuts Ninja (papercuts-ninja) |
milestone: | none → precise-9-miscellaneous |
Changed in gtk: | |
status: | New → Confirmed |
Changed in hundredpapercuts: | |
milestone: | precise-9-miscellaneous → quantal-10-gtk |
Changed in hundredpapercuts: | |
milestone: | quantal-10-gtk → raring-gtk |
Changed in hundredpapercuts: | |
assignee: | Paper Cuts Ninja (papercuts-ninja) → Timothy Arceri (t-fridey) |
Changed in hundredpapercuts: | |
status: | Triaged → In Progress |
Changed in hundredpapercuts: | |
milestone: | raring-gtk → papercuts-s-gtk |
Changed in gtk: | |
status: | Confirmed → Fix Released |
I assume you're describing the behaviour of the Save dialog.
I think this is not a bug: when you type in "foo/bar", it's interpreted as file "bar" in subdirectory "foo". If subdirectory /home/john/ Desktop/ foo (or whatever) doesn't exist, you're informed about it. This is useful when instead of navigating to the folder where you want to save, you just type the path to the desired file.