Bug 279563

Summary:	[Windows] Using location bar to navigate to a file results in "File Not Found" and a slash (/) appended to end of address
Product:	[Unmaintained] kfile	Reporter:	Andrew <sl...as...h.a.3+kdebugs>
Component:	kurlnavigator	Assignee:	KDE-Windows <kde-windows>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	adaptee, bcooksley, frank78ac, kde-windows, nate, periliocastrol, ps_ml
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Andrew 2011-08-07 02:34:04 UTC

Version:           unspecified (using KDE 4.5.4) 
OS:                MS Windows

When running Dolphin, entering an address with a filename (for example, C:/somefile.txt) will give the error "The file or folder C:/somefile.txt does
not exist".

A slash is appended to the end of the address once the Enter key has been pressed (for example, C:/somefile.txt/)

This behaviour does not occur in Konqueror.

Reproducible: Always

Steps to Reproduce:
On KDE for Windows go into Dolphin and type in an address that points to a file (that does actually exist). Press Enter.

Actual Results:  
An error appears stating "The file or folder C:/somefile.txt does
not exist". A slash is appended to the end of the address.

Expected Results:  
The file should be opened from the location bar.

Comment 1 Jekyll Wu 2012-01-07 05:35:58 UTC

I can reproduce the reported problem using KDE SC 4.7 on Windows XP.

Comment 2 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:18:35 UTC

Resetting assignee to default as per bug #305719

Comment 3 Emilio 2012-11-10 15:36:54 UTC

I can reproduce it with KDE for windows 4.8

Comment 4 Frank Reininghaus 2013-04-30 12:43:22 UTC

Do you see the same behaviour in KDE's file dialog? If yes, it is a kdelibs bug.

Comment 5 Patrick Spendrin 2013-04-30 13:01:27 UTC

Yes, this seems to happen in the native dialogs as well. Do you have an idea where the bug could come from?

Comment 6 Frank Reininghaus 2013-04-30 13:05:28 UTC

Thanks for the quick response. The location bar is provided by the class KUrlNavigator. For the 'editable' mode where you can enter a location using the keyboard, it uses KUrlComboBox. These might be starting points for debugging. I can't help much with debugging because I don't use KDE on Windows.

Comment 7 Patrick Spendrin 2013-04-30 14:48:11 UTC

ok, I just looked into that, and this happens similarly on Linux, except with the following difference: on Linux a default file handler pops up (suse 12.2 here). Dolphin keeps the weird entry in the location bar.
To reproduce:
[- copy a file path into clipboard]
- click into the location bar and enter (=paste) the file path & hit enter.
result:
the location bar stays as '/file/path.ext/' (note the appended slash) and an application is opened to handle the file.
expected result:
the location bar should go back to either the last path (windows explorer default behaviour) or should show the directory the file is in (might actually make more sense).

Comment 8 Frank Reininghaus 2013-05-01 20:00:06 UTC

Right, I can confirm that the slash is appended also in Linux.

(In reply to comment #7)
> expected result:
> the location bar should go back to either the last path (windows explorer
> default behaviour) or should show the directory the file is in (might
> actually make more sense).

I'm not sure if we should do that. There are some situations in which it makes sense to open a file in Dolphin using the location bar. E.g., if you want to view the contents of an archive. In particular, if the archive does not have an archive mime type (like .jar files or office files, which are actually ZIP archives), pasting the file path into the location bar is the only way to view the contents inside Dolphin.

Comment 9 Patrick Spendrin 2013-05-01 20:13:32 UTC

How are those things handled in dolphin? Using the arkkpart as well? Because it should actually be possible to find out if the file is handled (more or less) internally and in case it isn't, use/display a different path.

Comment 10 Nate Graham 2018-06-15 03:29:13 UTC

Is this still relevant or applicable with KDE Frameworks 5.47?

Comment 11 Ben Cooksley 2018-06-15 07:45:04 UTC

Using the current Dolphin from the Binary Factory reveals that Dolphin crashes instead of failing. Judging by the manner in which it crashes, the crash is an infinite recursion.

Comment 12 Nate Graham 2018-06-26 23:09:10 UTC

Thanks Ben. Let's track with with a separate bug, since it seems to be a separate issue.