By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 1968

Summary:	[Help Handbooks] Remove Screen Savers from help handbook table of contents
Product:	TDE	Reporter:	Darrell <darrella>
Component:	tdebase	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugwatch, darrella, kb9vqf, michele.calgaro
Priority:	P5
Version:	R14.0.0 [Trinity]
Hardware:	Other
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Bug Depends on:
Bug Blocks:	2014

Description Darrell 2014-02-26 16:53:34 CST

For as long as I can remember in KDE3 the Screen Savers category has always been an empty category in the help handbook table of contents. This remains true in Trinity as well KDE4.

I have tried many kinds of trickery to prevent Screen Savers from appearing in the table of contents, all to no avail.

I do not know the mechanism through which the handbook navigator pulls this directory into the table of contents. I suspect everything is parsed that is in the /opt/trinity/share/applnk directory. Adding *.directory or *.desktop files and editing tde-system-screensavers.directory did not fix the problem.

Comment 1 Michele Calgaro 2014-03-07 02:56:32 CST

Darrell, which screen saver entry are you referring to exactly?
I have an entry under the "Control Center Modules" category, and if I click it points to a page with information in it.
Perhaps I am looking at the wrong entry?

Comment 2 Darrell 2014-03-07 15:23:03 CST

* Open the help handbook.
* Open Application Manuals.
* Open System.
* The Screen Savers category is empty and always has been. Still that way in KDE4 too.

Comment 3 Michele Calgaro 2014-03-08 00:39:08 CST

Thanks

Comment 4 Timothy Pearson 2014-09-24 23:16:30 CDT

Looks like the service group parsing code was to blame for this cosmetic issue.

Fixed in GIT hash 485ab96.

Thanks for reporting!

Comment 5 Darrell 2014-09-30 15:14:06 CDT

>Fixed in GIT hash 485ab96.
Looks good here. Thanks.