Bug 144807 - Can not open folders that have a hash (#) in their name
Summary: Can not open folders that have a hash (#) in their name
Status: RESOLVED FIXED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-29 01:27 UTC by skyostil
Modified: 2007-09-24 08:36 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description skyostil 2007-04-29 01:27:59 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    Debian testing/unstable Packages

To reproduce:
1. Create a folder named "foo#bar"
2. Open the containing folder in Dolphin.
3. Click on the newly created folder.
4. Dolphin displays "Custom Path" in the breadcrumb widget and says that the folder ".../foo" does not exist.
Comment 1 Peter Penz 2007-04-30 18:56:16 UTC
Thanks for the report, this bug has been fixed already on the KDE4 version of Dolphin.

Best regards,
Peter
Comment 2 echelon 2007-09-24 00:22:42 UTC
3 cases with '#' in the folder name
..........
1) When I have '#' at the beginning of a folder name I can't access it. Nothing happens when I click on the Icon.

2) When I have the hash as a part of the name, just some where in the name, but not at the beginning, I can access it but the status bar appears yellow with a red circle and a white 'X' in it and the message "The file folder <complete path name> does not exist. No content is visible.
When I use any other application to access the folder I can see and access the content of these folders.

3) When I remove the hash I don't have the problems mentioned above.
Comment 3 Peter Penz 2007-09-24 08:36:17 UTC
I've checked this with the latest SVN build and the points are not reproducible. It's no problem creating #foo or foo#foo within Dolphin and going into those directories. It's also no problem if the directories have been created from outside... Is this bug report for sure for Dolphin 0.9.2 for KDE 4 (no Dolphin version has been specified)?