Reporting bugs about Ubuntu

[NoOp]

On 10/01/2009 10:50 AM, Xandros Pilosa wrote:
> NoOp pravi:
> 
> <snip>
> 
>> Oh wait, 438847 is an actual crash of apport... but now that you can't
>> file bugs directly in launchpad anymore (apparently we aren't bright
>> enough), I guess I'll get something to crash & see if apport
>> communicates with launchpad that way so I can file a new bug that way...
>> or not.
> 
> It seems that we still have the option to file a bug directly as 
> directed in [1]:
> 
> <quote>...If for some reason you cannot file a bug through the Apport 
> tool you can file one via Launchpad. When doing so please ensure that 
> you have determined which package it should be filed against. Read 
> 'finding the right package' for guidance or use Launchpad's package 
> search feature. To file a bug against a specific package use a url 
> similar to the following, 
> http://bugs.launchpad.net/ubuntu/+source/PACKAGENAME/+filebug?no-redirect, 
> where PACKAGENAME is the name of the source package about which you want 
> to file the bug....</quote>
> 
> [1] https://help.ubuntu.com/community/ReportingBugs
> 
> Haven't tried it yet, though.
> 
> Regards
> 

https://bugs.launchpad.net/ubuntu/+source/apport/+filebug?no-redirect=
works. However, I have enough issues already without having to bookmark
a link
(http://bugs.launchpad.net/ubuntu/+source/PACKAGENAME/+filebug?no-redirect),
fill in the packagename, and file the bug.

In the past I've always been quite active in filing Unbuntu bugs, see:
<https://bugs.launchpad.net/~glgxg/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=INVALID&field.status%3Alist=WONTFIX&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY>

but adding one more hoop to go through is pretty much testing my
'goodwill' with regards to further bug reporting.