Search for document returns an Unknown error: 'URI xref:search=' could not be parsed

Bug #726439 reported by Jean-Baptiste Lallement on 2011-02-28
This bug affects 15 people
Affects Status Importance Assigned to Milestone
yelp (Ubuntu)

Bug Description

Binary package hint: yelp

1. Launch Yelp
2. Select the menu 'Go / All Documents"
2. Enter some text (e.g nautilus) in the address bar
3. Hit Enter

The following error is displayed:
Unknown Error
The URI ‘xref:search=nautilus’ could not be parsed.

Expected Results:
List of documents matching the search list is returned

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: yelp 2.91.90-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
Date: Mon Feb 28 11:01:37 2011
EcryptfsInUse: Yes
 PATH=(custom, user)
SourcePackage: yelp

Jean-Baptiste Lallement (jibel) wrote :
Dylan McCall (dylanmccall) wrote :

This also makes it impossible to access man or info pages through the GUI; I have to open Yelp from the command line with the path as an argument.

I am experiencing what I believe to be this bug on two Natty systems with yelp 3.0.0-0ubuntu2 (one amd64, one i386), but a bit differently than described in this bug report. Searching in yelp works generally, and I cannot produce the problem just by following the steps in the description. However, if I first do Go > All Documents, and then attempt to run my search (by typing it into the address bar and pressing enter), the search fails with "Unknown Error" "The URI ‘xref:search=nautilus’ could not be parsed. If I click the back button to return to the default page ("Ubuntu Desktop Guide"), I can again successfully search (though it doesn't search all documents, of course). On both machines, I am running yelp without arguments. The amd64 system is Lubuntu (set up by installing a command-line only system with the Alternate CD and then installing the package lubuntu-desktop on it), and the i386 system is Ubuntu running Unity.

@Dylan McCall
Are you able to reproduce this by following the steps in Jean-Baptiste Lallement's description precisely, or do you also have to do Go > All Documents (as you would likely do before attempting to search for a manpage) before attempting to search, in order to get the URI could not be parsed error message?

Mannex (russ-mannex) wrote :

This bug also affects me. Here is my system information:

Running Ubuntu 11.04.
uname -m = i686
yelp version 3.0.0-0ubuntu2

Additionally, it seems I only get this bug after selecting All Documents from the Go menu.

Jean-Baptiste Lallement (jibel) wrote :

I'm marking to triage/medium due to the latest comments.

description: updated
description: updated
Changed in yelp (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Jeremy Bicha (jbicha) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug has been reported to the developers of the software. You can track it and make comments at:

Changed in yelp:
importance: Unknown → Medium
status: Unknown → New
tags: added: testcase
Changed in yelp:
status: New → Confirmed
NoOp (glgxg) wrote :

And still broken in 2014:
$ apt-cache policy yelp
  Installed: 3.10.2-0ubuntu1
  Candidate: 3.10.2-0ubuntu1
  Version table:
 *** 3.10.2-0ubuntu1 0
        500 trusty/main amd64 Packages
        100 /var/lib/dpkg/status

Iuri Diniz (iuridiniz) wrote :

still broken in 3.18.1-1ubuntu4 (Ubuntu 16.04.1)

There's a patch in upstream, could it be applied?

Changed in yelp:
status: Confirmed → Expired
Norbert (nrbrtx) wrote :

Ubuntu 16.04 LTS and 18.04 LTS are still affected by this bug.

Changed in yelp (Ubuntu):
status: Triaged → Confirmed
tags: added: bionic cosmic trusty xenial
removed: i386 mago natty running-unity
Norbert (nrbrtx) wrote :
Norbert (nrbrtx) wrote :

Bug confirmed on 18.10, so the patch ( ) from upstream was not applied to the master branch.

Norbert (nrbrtx) on 2018-12-09
tags: added: disco
Norbert (nrbrtx) wrote :

Still exists in 19.04.

Norbert (nrbrtx) on 2019-04-21
tags: added: eoan
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.