Bug 134946

Summary:	No such file when # in filename
Product:	[Applications] konqueror	Reporter:	Dennis Schridde <heri+kde>
Component:	general	Assignee:	Konqueror Developers <konq-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Dennis Schridde 2006-10-01 14:22:30 UTC

Version:            (using KDE KDE 3.5.4)
Installed from:    Gentoo Packages
Compiler:          gcc (GCC) 4.1.1 (Gentoo 4.1.1-r1) 
OS:                Linux

When I enter a filename in the URL box of Konqueror it get an error message instead of the file. The file exists and is even displayed in the drop down suggestion box.

Beim Laden von file:///home/fuu/.kde/share/apps/konversation/logs/freenode_#warone.log ist folgender Fehler aufgetreten:
Die Datei oder der Ordner /home/fuu/.kde/share/apps/konversation/logs/freenode_ existiert nicht.

English translation:
Error while loading: file:///home/fuu/.kde/share/apps/konversation/logs/freenode_#warzone.log
No such file or directory: /home/fuu/.kde/share/apps/konversation/logs/freenode_

Comment 1 Philip Rodrigues 2006-10-01 14:57:53 UTC

If you just put a path (without file:// at the beginning) it works fine. Clicking on the "browse" button in Location->Open Location dialog just puts a path, so it works fine. Putting the file:// at the beginning signifies that you're giving a URI, so I suppose it should have special characters correctly escaped for a URI.

I think (though I'm not sure), that means this isn't a bug

Comment 2 Dennis Schridde 2006-10-01 15:59:39 UTC

Ok if I write a plain filename it works as expected.
I originally found the problem when I entered:
~/.kde/share/apps/konversation/logs/freenode.net_#kde.log

Konqueror translates this to "http://~/.kde/share/apps/konversation/logs/freenode.net_#kde.log" and reports "unknown host ~".
I then tried to fix this somehow and replaced the "http" with "file", what gave me a "timeout on server ~". So I replaced "~" with my homedir.
Seems like there is some more weirdness going on...
(esp. that http can't find the host, file can, but gets a timeout instead...)

Comment 3 Philip Rodrigues 2007-01-06 19:11:14 UTC

bug 104585 is slightly different, but presumably they have the same cause.

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