Version: 0.9.5 (using KDE 4.0.0) Installed from: MS Windows Binaries OS: MS Windows Dolphin's path handling appears to be buggy. If you enter "x:", where "x" is a valid driveletter, it fails to open it, even though "/x:" and "x:\" do work, and even though these are changed by Dolphin to "x:". When navigating to subfolders of drives, Dolphin shows "/" in the path instead of "\" even though it's running on Windows. When I enter "\x:\" it changes it to "%5Cx:%5c" and I get an assertion failure: Assertion failed! Program: C:\Program Files\KDE\bin\dolphin.exe File: D:\kde-mingw\tmp\kdelibs-3.97.20...\kstand...irs.cpp Line: 688 Expression: prefix.at(prefix.length() - 1) == '/' || prefix.at(prefix.length() - 1) == '\\' For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts (Press Retry to debug the application - JIT must be enabled) [Note: I had to type this in from a screenshot, so it may not be character-perfectly quoted.]
In Dolphin 1.0.99 on KDE 4.00.80 I have similar experience. I don't get the assertion failure and crash (maybe it's only in DEBUG builds). When I enter E: Dolphin changes it to file://e and displays a warning "Could not start process Unable to create io-slave: klauncher said: Unknown protocol 'smb'."
still present in the last kde 4.0.73
> If you enter "x:", where "x" is a valid driveletter, it fails to open it, This is true for Dolphin. Konqueror loads "x:" correctly though. I get the same thing here as S Page has commented. > When I enter "\x:\" it changes it to "%5Cx:%5c" and I get an assertion failure: Doesn't happen here on konqueror or dolphin. It changes to "x:" instead. My experience is the same as S Page on KDE 4.0.73 here.
So I'm confirming the X: on dolphin bug. The rest of it doesn't seem to happen anymore. X: tells you Unknown Protocol: 'smb'. X:\ turns in to X: and displays correctly.
CC'ing the KDE on Windows team to this bug report.
Confirmed in Kde for Windows 4.1.1
Fixed the X: - bug in r872668, not backported to 4.1 yet \X:\ is already converted to X: The only thing left is the wrong displaying of the path, but that's only a displaying error.