Bug 340510 - Konversation Handbook in Help menu gives only error message
Summary: Konversation Handbook in Help menu gives only error message
Status: RESOLVED FIXED
Alias: None
Product: konversation
Classification: Applications
Component: documentation (show other bugs)
Version: frameworks
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-30 22:08 UTC by Valorie Zimmerman
Modified: 2016-01-15 23:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Valorie Zimmerman 2014-10-30 22:08:43 UTC 
In testing bug #340508 I discovered that the Konversation Handbook is no longer found. Error message: Could not launch the KDE Help Center: Could not find service 'khelpcenter'.

This probably confirms the bug.

Reproducible: Always

Steps to Reproduce:
1. Click Help
2. Select Konversation Handbook
3. Error message


Expected Results:  
I expected to find the Handbook. I know one exists, as I was using it before upgrading.

Using Kubuntu 14.10 with Plasma 5
Comment 1 Burkhard Lück 2014-10-31 11:18:53 UTC 
Confirmed using Kubuntu 14.10 with Plasma 5 in a VM

But I get this error with any application trying to launch the documentation via Help button.
khelpcenter help:konversation in konsole works

In my separate kf5 user environment I can launch any documentation via Help button in kf5 or kde4 apps
Comment 2 Burkhard Lück 2014-11-02 22:00:24 UTC 
Should be fixed with https://git.reviewboard.kde.org/r/119589/
Comment 3 Burkhard Lück 2014-11-14 14:49:55 UTC 
Updated the VM with Kubuntu 14.10 to 5.1.1 and still get the error message: Could not launch the KDE Help Center: Could not find service 'khelpcenter' for any kde4 app when I try to open the handbook via application help button

@ Valorie:
Bug assignee Konversation Developers  is obviously wrong here
Comment 4 Valorie Zimmerman 2016-01-15 23:43:51 UTC 
I notice that I never closed this bug, although it is fixed.

Thanks!