Version: (using KDE KDE 3.5.6) Installed from: Mandriva RPMs OS: Linux In the KDE Help Center on the "Search Options" tab I click Build Search Index, I selected "Application Manuals" and then I clicked Build Index, It said Index Creation finished but then I clicked Details and the following text appeared: INDEXDIR: /home/jacob/.kde/share/apps/khelpcenter/index/ FINDCMD: find /usr/share/doc/HTML/en/ -name index.docbook Creating index for 'kde_application_manuals' htdig failed So the index creation actually failed.
Created attachment 26302 [details] kcrash file Here's a crash file generated from this bug.
Created attachment 26924 [details] crash file
I have experienced the same issue many times in the past, and am experiencing it right now on a fresh OS install. Everything is exactly as related by Jacob. I get the same message whether I am trying to index the Unix manual pages or a particular program. I am using Mandriva 2007.0 Spring Free. I am surprised this has not yet been fixed. It makes it impossible to use any documentation that was installed initially with the distro. Is there a patch for it or something? Thanks.
SVN commit 1024989 by dfaure: Show "htdig not found" when htdig is, well, not found. Much better than launching the index creation and then it appears to have worked except for a small "htdig failed" line in the huge detailed output... BUG: 146010 M +5 -1 kcmhelpcenter.cpp M +12 -12 searchengine.cpp M +15 -5 searchhandler.cpp M +5 -4 searchhandler.h M +1 -0 searchhandlers/docbook.desktop.cmake M +1 -0 searchhandlers/htdig.desktop.cmake WebSVN link: http://websvn.kde.org/?view=rev&revision=1024989
(In reply to comment #4) > SVN commit 1024989 by dfaure: > > Show "htdig not found" when htdig is, well, not found. Much better than > launching the index creation and then > it appears to have worked except for a small "htdig failed" line in the huge > detailed output... > BUG: 146010 This purpose is better served by saying #!/usr/bin/perl -w in the first line of /usr/lib64/kde4/libexec/khc_docbookdig.pl. Since that is also the recommended invocation string, I would reopen the bug if I knew how to do it.