Searched for app-cdr/brasero or brasero does not return all bug relating to brasero failed to return this bug: https://bugs.gentoo.org/show_bug.cgi?id=397469 Reproducible: Always Steps to Reproduce: goto https://bugs.gentoo.org/buglist.cgi?quicksearch=app-cdr%2Fbrasero or https://bugs.gentoo.org/buglist.cgi?quicksearch=brasero search results not returned Actual Results: 398475 nor Normal Linu gnome@gentoo.org UNCO --- app-cdr/brasero-3.2.0-r1: buffer overflow while burning audiocd 397419 nor Normal Linu gnome@gentoo.org CONF --- brasero 3.2.0 refuses to burn dual layer DVD+R discs using libburn backend Expected Results: bug 397469
The search includes only open bugs by default. 397469 is RESOLVED and thus not in the result set for your query. https://bugs.gentoo.org/page.cgi?id=quicksearch.html explains the syntax of the quicksearch, and how to use ALL to search for closed bugs as well.
Fair enough but what is your main search for? Me just coming on to the site for a first time to report a bug (in a very long time) Thought I had checked to see if I has been doing anything silly. (Which I was a bit and could have fixed it finding the original bug) Though I had checked for a duplicate bug and therefore follow procedure. (I do now understand that on here the search is different here: https://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%20Linux&format=guided however it not clear) I personally won't be making the same mistake again but how many duplicate bugs are down to this? (Just a question for discussion I don't know the right answer) (In reply to comment #1) > The search includes only open bugs by default. 397469 is RESOLVED and thus not > in the result set for your query. > > https://bugs.gentoo.org/page.cgi?id=quicksearch.html explains the syntax of the > quicksearch, and how to use ALL to search for closed bugs as well.
(In reply to comment #2) > Fair enough but what is your main search for? > Without using any of the advanced query syntax mentioned in the guide, for quickly finding *open* bugs (i.e. ones that are most likely to affect you right now) matching your query string.
