The requested page was not found in the document /usr/share/gnome/help/gnome-doc-make/C/gnome-doc-make.xml.

Thanks for the report Duncan.

I don't have an entry in the search results called 'GNOME Documentation Build Utilities'. Do you have gnome-doc-tools installed?

Sorry, I give up. Something is seriously wrong with links in yelp and/or ubuntu-docs. Launchpad is full of them and I just can't be bothered trying to find them. Someone somewhere needs to implement a systemic way of checking for broken links.

I don't have that search result either, even though the document you mention is installed. Do you use beagle by any chance? I wonder if this is something going wrong with the beagle search backend for yelp.

Moving to the yelp source package for now. Please do report any broken links that you find.

Hi Matthew, Phil: No I don't have beagle installed on this system, I thought tracker was the same... oh well.

By searching for 'workspace switcher' I can give you the direct link: file:///usr/share/gnome/help/gnome-doc-make/C/gnome-doc-make.xml#migrating and yes, <section id="migrating"> exists. I can also confirm that the XML opens in firefox.

The link which is contained in my search for 'Workspaces' is file:///usr/share/gnome/help/gnome-doc-make/C/gnome-doc-make.xml#gospanel-3 and in the XML there is no section called "gospanel-3".

So does this bug need to be broken down into several?
* this is a bug in the way that the Yelp 2.19.90 error dialog displays the failed path... it was not showing me the full path, including the section, which failed.
* this is also a bug about a hard-coded path which is wrong (gnome-doc-make.xml#gospanel-3 section doesn't exist)
* this is also a bug about strange differences in search results between systems (without beagle)

do you still get the issue using hardy?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

That specific link works in Hardy - if you can find it.