SUMMARY It is my understanding that current falkon should support KDE kio. At least it was dealing with the info: protocol (useful to read gnu documentation) nicely until long ago. Currently, on kubuntu cosmic (with the latest KDE from the backports PPA and the latest falkon development snapshot from the dedicated ppa), I am experiencing the following. If I write: `info:sed` on the browser address line, the browser does not recognize the protocol at all and tries to search `info:sed` on the default search engine. If I write `falkon info:sed` on the command line, falkon opens, the kio slave is invoked, but the sed info page is subsequently opened in the default browser that on my system is firefox. Maybe these issues could be related to the fact that falkon complains "Plugin "KDEFrameworksIntegration.so" not found". SOFTWARE/OS VERSIONS Falkon Application version 3.0.99 QtWebEngine version 5.11.1 Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.1
I think that the KDE framework integration plugin is now called FrameworkIntegrationPlugin.so
You need to enable KDE Frameworks Integration plugin in preferences.
- Where is that entry supposed to be? I was expecting to find it in preferences->Extensions, but there is no such entry... - KDE integration used to work and I have not touched any preference. It has stopped working by itself. Only notable change on my side was upgrading from ubuntu bionic (18.04LTS) to cosmic (18.10). Can there be some difference in cosmic requiring some packaging update in falkon?
Furthermore, if KDE integration is OFF, i.e. if falkon is not expected to understand the KIO protocols, I think that it is a bit confusing that `falkon info:sed` ends up opening a (broken - links obviously not working) sed info page in firefox. IMHO the behavior in absence of KDE integration should be consistent with that obtained by putting info:sed in the address bar (either trying to search info:sed through the default search engine or - would be preferrable - an indication that the info: protocol is not supproted in urls).
There were new dependencies for the plugin (KF5::Purpose), so that may be the reason you don't have it. And it's expected to don't understand KIO protocols without this plugin, so it opens unknown URLs externally with xdg-open.