kate error: Unable to create KIO worker. Can not find a KIO worker for protocol "sftp"

Trending 3 months ago

I person Ubuntu 20.04 and kate 23.08.4. For years I person been utilizing dolphin to unfastened files successful kate complete sftp utilizing thing like:


in dolphin. However, I conscionable started receiving these errors successful kate erstwhile I effort to unfastened these files now:

Unable to create KIO worker. Can not find a KIO worker for protocol "tags". Unable to create KIO worker. Can not find a KIO worker for protocol "sftp".

I'm not judge what changed. Maybe thing sewage uninstalled? This is nan kio worldly I presently person installed:

$ sudo apt database --installed | grep kio WARNING: apt does not person a unchangeable CLI interface. Use pinch be aware successful scripts. kio-audiocd/focal,now 4:19.12.3-0ubuntu1 amd64 [installed,automatic] kio-extras-data/focal,focal,now 4:19.12.3a-0ubuntu2 each [installed,automatic] kio-extras/focal,now 4:19.12.3a-0ubuntu2 amd64 [installed,automatic] kio-ldap/focal,now 19.12.3-0ubuntu1 amd64 [installed,automatic] kio-sieve/focal,now 4:19.12.3-0ubuntu1 amd64 [installed,automatic] kio/focal,now 5.68.0-0ubuntu1 amd64 [installed,automatic] libkf5kiocore5/focal,now 5.68.0-0ubuntu1 amd64 [installed,automatic] libkf5kiofilewidgets5/focal,now 5.68.0-0ubuntu1 amd64 [installed,automatic] libkf5kiogui5/focal,now 5.68.0-0ubuntu1 amd64 [installed,automatic] libkf5kiontlm5/focal,now 5.68.0-0ubuntu1 amd64 [installed,automatic] libkf5kiowidgets5/focal,now 5.68.0-0ubuntu1 amd64 [installed,automatic] qml-module-org-kde-kio/focal,now 5.68.0-0ubuntu2 amd64 [installed,automatic]

Is thing missing?

UPDATE I discovered that I had 2 instances of Kate installed, 1 done apt, and 1 done snap. The threat 1 apparently is nan 1 that was opening erstwhile I tried to unfastened these files from dolphin. I uninstalled nan threat 1 and reinstalled nan apt 1 to make judge I had nan latest version, and nan correction went away.

Is location a known bug pinch nan threat type and sftp, aliases is it imaginable thing wasn't configured correctly pinch nan threat one, aliases possibly nan 2 versions were conflicting pinch each different somehow?