Bug 164711 - Many help archives are missing. Seems like khelpcenter hasn't been fully installed
Summary: Many help archives are missing. Seems like khelpcenter hasn't been fully inst...
Status: RESOLVED WORKSFORME
Alias: None
Product: khelpcenter
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Documentation Editorial Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-23 01:09 UTC by Mavi Ruiz
Modified: 2016-03-12 22:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mavi Ruiz 2008-06-23 01:09:35 UTC
Version:           3.5.9 (using 3.5.9, compiled sources)
Compiler:          Target: i586-manbo-linux-gnu
OS:                Linux (i686) release 2.6.24.4-desktop586-3mnb

When I look in the index for some help, or in the search box, for example, when I looking for help with digikam, in the text box it apears: Doesn't exist documentation for /digikam/index.html.And the same for the rest of apps.
Comment 1 Burkhard Lück 2008-07-24 16:25:30 UTC
digikam is not in the kde 3.5.9 main modules, but in extragear/graphics.
Did you really compile digikam from sources?
I suppose you installed digikam from your distro, but not the digikam doc packages (e.g. in ubuntu digikam-doc).
This should apply to the other apps, whre you miss the documentation, as distros often split applications and documentations into different packages.
Comment 2 Greg Letiecq 2008-12-13 16:00:19 UTC
This also is the case with KDE 4.1.  Digikam fires an error that it can't open Help Center, and it also doesn't recognize there's a browser installed.  Other issues prevent being able to provide more specific details.
Comment 3 Burkhard Lück 2011-07-20 16:36:56 UTC
Checked again in Kubuntu 10.10 with
$ digikam --version
Qt: 4.7.0
KDE Development Platform: 4.6.2 (4.6.2)
digiKam: 1.8.0

Handbook is properly opened.
Comment 4 Luigi Toscano 2016-03-12 22:19:38 UTC
Closing as per comment #3, it looks like a temporary/compilation/deployment problem.