Search doesn't work?

Asked by Jerzy Jalocha N

At the end of Bug #90271 I added a list of computers related to that problem. This list was compiled from duplicate bugs.

When I search for any of these systems in Launchpad, I get NO results at all.

I'm searching at:

   home > bugs > search

Search strings such as:
 * Averatec 2460
 * SA2053T
 * Freevents x52

Some of these strings appear in the bug's comments, some of them in the original bug report, and some of them even in the bug title.

Am I doing something wrong? Missing a point? Is this a bug?

Revision history for this message
Christian Reis (kiko) said :
#1

On Wed, Jan 23, 2008 at 01:22:37PM -0000, Jerzy Jalocha N wrote:
> Am I doing something wrong? Missing a point? Is this a bug?

Quite possibly more than one bug. Can you help me by giving me evidence
so I can research more? What bugs /should/ those queries have matched?
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125

Revision history for this message
Jerzy Jalocha N (jjalocha) said :
#2

Sure! Here are some examples of pages that (manually) match some search strings:

Averatec 2460
 * Bug #90271
 * Bug #59626
 * Bug #64048
 * Bug #140477

SA2050
 * Bug #90271
 * Bug #140477

SA2053T
 * Bug #90271
 * Bug #156764

Freevents x52
 * Bug #90271
 * Bug #140477

Thanks for your quick reply!

Revision history for this message
Björn Tillenius (bjornt) said :
#3

These bugs aren't found, because the search strings are only present in the bug comments. At the moment only the bug summary and description is searched, due to a bug. You can follow the progress in bug 119780.

Revision history for this message
Jerzy Jalocha N (jjalocha) said :
#4

No, sorry, that is not correct.

As stated in the original question, "Some of these strings appear in the bug's comments, some of them in the original bug report, and some of them even in the bug title". Below, some examples of search strings that appear in the title or in the bug description:

Averatec 2460
 * Bug #59626: "...I have an Averatec 2460..."
 * Bug #64048: LiveCD doesn't boot on Averatec 2460 Intel Core Duo, RTL8139 NIC
 * Bug #64048: "...Edgy won't even boot on my Averatec 2460..."

Freevents x53
 * Bug #87932: Lock up during on Phillips Freevents x53
 * Bug #140477: "...Philips Freevents x53..."

Twinhead Y12H
 * Bug #140477: Kernel hangs/freezes during boot because of module 8139too (affected hardware: philips freevents x52, x53, x55, x56, twinhead y12h)
 * Bug #140477: "...Twinhead Y12H (should be identical to..."

SA2053T
 * Bug #156764: 2.6.22-14-generic kernel distributed with Gutsy does not boot on Everex StepNote SA2053T laptop
 * Bug #156764: "...I have an Everex StepNote SA2053T laptop..."

StepNote
 * Bug #133278: "...Niether Ubunut Fiesty nor Gusty boot the install cd on Everex StepNote SA Series..."
 * Bug #156764: "...I have an Everex StepNote SA2053T laptop..."

Revision history for this message
Stuart Bishop (stub) said :
#5
Revision history for this message
Jerzy Jalocha N (jjalocha) said :
#6

Stuart, thank you very much!
That explains everything. All other examples above are duplicates, too.

It's still a strange behavior that search results of duplicates are not "redirected" to the active bug. Because right now (in default mode), someone searching for his specific problem might not find any entries, and will keep filing duplicate bug reports.

Revision history for this message
Christian Reis (kiko) said :
#7

On Thu, Jan 24, 2008 at 01:09:20PM -0000, Jerzy Jalocha N wrote:
> It's still a strange behavior that search results of duplicates are not
> "redirected" to the active bug. Because right now (in default mode),
> someone searching for his specific problem might not find any entries,
> and will keep filing duplicate bug reports.

That's an interesting point -- that we should include the duplicate's
content when indexing a bug. That's not so easy to do, though, with our
current indexing infrastructure (AFAIK) -- but it's worth filing a bug
if you'd like to do that.

Revision history for this message
Jerzy Jalocha N (jjalocha) said :
#8

I just found that this bug has already been reported on 2006-02-02, and confirmed with medium importance:

Bug #30307: Use terms from duplicate bugs to return originals in searches