Bug 182648 - "open file" dialog does not open files with colon in file name
Summary: "open file" dialog does not open files with colon in file name
Status: RESOLVED DUPLICATE of bug 174864
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-01 01:46 UTC by lciani
Modified: 2009-05-03 03:29 UTC (History)
4 users (show)

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 lciani 2009-02-01 01:46:54 UTC
Version:           4.2.0-7.fc10 (using KDE 4.2.0)
OS:                Linux
Installed from:    Fedora RPMs

In KWrite opening a file with a colon in file name - such as
"filename: text.txt" - fails with 2 messages. Firt error window pops up saying: "URL cannot be listed filename: text.txt". Then, after clicking on OK, a second error window pops up saying "The file given could not be read; check whether it exists or is readable for the current user."

Opening a file named "filename: videofile.avi" with Dragon Player, the second error window says "The file filename:%20videofile.avi/ could not be found"

Opening a file named "filename: text.txt" with Konqueror gives 2 error windows, just like in the case of Dragon Player.

Kate gives 2 error windows. The first one is the same as all previous examples, the second error window says: "Could not start process Unable to create io-slave: klauncher said: unknown protocol «filename».."
Comment 1 lciani 2009-02-01 01:57:20 UTC
Kwrite, Kate, Konqueror and Dragon Player all open the file with a colon in its file name correctly if the applications are launched from within a Konsole window.
Comment 2 Dario Andres 2009-05-03 01:29:55 UTC
Are you entering "filename: foobar.txt" in the File Dialog "Name:" field ? (I wonder why do you use the "filename:" part...) It will try to interpret the "filename:" part as kind of protocol (which in fact it doesn't exist). Just removing "filename:" should do the trick
Or are you trying to open a file which is named indeed "filename: foobar.txt" ?
Thanks
Comment 3 Michael Pyne 2009-05-03 03:29:57 UTC

*** This bug has been marked as a duplicate of bug 174864 ***