files with a '#' in the name are shown as 0 bytes; no preview
Bug #1420519 reported by
Vítor Meneguzzi Groterhorst
This bug affects 9 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Files |
Fix Released
|
High
|
Jeremy Wootten |
Bug Description
If a file has a '#' in its name, Pantheon Files reports it as if it had 0 bytes and shows no preview. That file also can't be opened or renamed from within Pantheon Files, because it says the file doesn't exist.
If the file is created (or renamed) while Pantheon Files is viewing the folder, this does not happen.
How to replicate:
1. Grab a jpg
2. Rename it to #.jpg
3. Close Pantheon Files (this is just needed if you had the file's folder open).
4. Open Pantheon Files (this is just needed if you had the file's folder open).
Related branches
lp:~jeremywootten/pantheon-files/fix-hash-character-in-filename
- Rico Tzschichholz: Approve
-
Diff: 13 lines (+1/-2)1 file modifiedlibcore/gof-directory-async.vala (+1/-2)
Changed in pantheon-files: | |
status: | Confirmed → In Progress |
assignee: | nobody → Jeremy Wootten (jeremywootten) |
milestone: | none → freya-rc1 |
Changed in pantheon-files: | |
status: | In Progress → Fix Committed |
Changed in pantheon-files: | |
milestone: | freya-rc1 → 0.2 |
status: | Fix Committed → Fix Released |
tags: | added: hash name |
To post a comment you must log in.
Similar issue with folders, you can't open a folder that start with # by clicking it (it's like if the parent folder was opening instead), but if you type the path in the location bar you can open it. If you try to rename it, the parent folder is renamed, and the folder with # keeps his name.
And if the folder has a # in the middle, like "t#st", when you open show a message like in the attached image: