[SOLVED] Slackware-current info:/ protocol cannot be initiated in Konqueror
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Slackware-current info:/ protocol cannot be initiated in Konqueror
Maybe it is not much of importance but I liked ability of Konqueror to display manuals and info pages. Just in address bar input
Code:
# ls
this should show manual for 'ls' (but probably requires MANPATH to be set - by default is unset). I did this
Code:
## coreutils
which should show info pages for 'coreutils'. But instead I got this
Quote:
The requested operation could not be completed
Cannot Initiate the info Protocol
Technical Reason: Unable to Launch Process
Details of the Request:
URL: info:/%20coreutils
Protocol: info
Date and Time: Monday, October 29, 2018 10:17 PM
Additional Information:
Description:
The program on your computer which provides access to the info protocol could not be started. This is usually due to technical reasons.
Possible Causes:
The program which provides compatibility with this protocol may not have been updated with your last update of KDE. This can cause the program to be incompatible with the current version and thus not start.
You may have encountered a bug in the program.
Possible Solutions:
Update your software to the latest version. Your distribution should provide tools to update your software.
Contact your appropriate computer support system, whether the system administrator, or technical support group for further assistance.
it does not have much sense. When I was using KDE (actually 3.5) it was really useful.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.