1. Open Bookmark Manager. 2. Edit a bookmark with local path - specify another local path. 3. Close Bookmark Manager. 4. Try using the bookmark - you'll see an error message about unsupported protocol. Reason: Bookmark Manager now creates <bookmark ... href="/path/to/file"> instead of <bookmark ... href="file:///path/to/file"> Workaround: specify the location in the form of file:///path/to/file in Bookmark Manager
I'm confirming. Actually with my current KIO version (git) using such bookmark crashes Krusader. But I remember that it was producing mentioned error about unsupported protocol before. I'll check changes in KIO and report the crashing there.
Thanks Martin! Did you have a chance to file a KIO bug? If so, please specify it in the "Depends on" field.
Sorry, I forgot about it. Now I've found the change in KIO which is causing the crash. Q_ASSERT for emptiness of protocol was added and briefly discussed here: https://phabricator.kde.org/D11013 IMO it makes sense that caller with empty protocol (Krusader in this case) is the one that need to be fixed instead informing user of an incorrect URL which regular user is not able to fix anyway. KIO change only made this bug (393320) more important to fix now:).
*** Bug 418349 has been marked as a duplicate of this bug. ***
Moving to KBookmark: I can replicate this behaviour on other applications, like Dolphin or KRDC. Local paths (file:///) can be added, but after editing them the protocol is lost. Also, when editing a location, there is no suggestion for local paths. If this "bug" could not be resolved in KBookMark, a solution would be to validate the path inside the application.
indeed, ideally the file:/// stuff should not disappear!
A note for Krusader developers: If this bug is solved, then the 0f153592 commit (which could be seen in https://commits.kde.org/krusader/0f153592) should be undone in the source code of Krusader (because it was aimed to avoid that Krusader users see the effects of the bug).