From noreply at ubuntu.com Wed Jun 1 08:09:02 2011 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 01 Jun 2011 08:09:02 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22AlanBell/fullsearchpages=22_by_a?= =?utf-8?q?lanbell?= Message-ID: <20110601080902.30447.57601@ronne.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "AlanBell/fullsearchpages" page has been changed by alanbell: http://wiki-test.ubuntu.com/AlanBell/fullsearchpages?action=diff&rev1=1&rev2=2 This page lists all the pages on the wiki that use the fullsearch term rather than the faster fullsearchcached query. - <> + <> From kate.stewart at canonical.com Wed Jun 1 01:52:08 2011 From: kate.stewart at canonical.com (Kate Stewart) Date: Tue, 31 May 2011 20:52:08 -0500 Subject: Oneiric Alpha 1 images - ready for testing Message-ID: <1306893128.2483.6078.camel@veni> Hi, Initial candidates for Alpha 1 testing are now up on the iso tracker. Please see: http://iso.qa.ubuntu.com/qatracker/ Additional images will be posted there as they emerge. If any serious bugs are spotted, please let us know in #ubuntu-release or #ubuntu-testing on Freenode. Thanks, Kate From noreply at ubuntu.com Thu Jun 2 14:28:23 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 02 Jun 2011 14:28:23 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_brian-murra?= =?utf-8?q?y?= Message-ID: <20110602142823.31899.47631@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=332&rev2=333 ------------------------------------------------------------------------------ ||Thanks for your bug report and for your contribution to Ubuntu. In order to determine if this issue is usplash related, please boot your computer with usplash disabled and then shutdown to see if you can reproduce the issue? To disable usplash for a single boot, follow these steps:<
><
>1. Hold Esc during Grub boot delay to access the boot menu. <
>2. Select your actual Ubuntu boot line and press "e" to edit it. <
>3. Select the "kernel" line and press "e" to edit it. <
>4. At the end of the line, remove "splash" and "quiet" and press "enter". <
>5. Type "b" to boot the custom boot line.|| For Karmic and subsequents releases users : - ||Thanks for your bug report and for your contribution to Ubuntu. In order to determine if this issue is plymouth related, please boot your computer with plymouth disabled and then shutdown to see if you can reproduce the issue? To disable plymouth for a single boot, follow these steps:<
><
>1. Hold Right-Shift during Grub boot delay to access the boot menu. <
>2. Select your actual Ubuntu boot line and press "e" to edit it. <
>3. Select the "linux" line and at the end of the line, remove "splash" and "quiet". <
>5. Type "ctrl + x" to boot the custom boot line.|| + ||Thanks for your bug report and for your contribution to Ubuntu. In order to determine if this issue is plymouth related, please boot your computer with plymouth disabled and then shutdown to see if you can reproduce the issue. To disable plymouth for a single boot, follow these steps:<
><
>1. Hold Right-Shift during Grub boot delay to access the boot menu. <
>2. Select your actual Ubuntu boot line and press "e" to edit it. <
>3. Select the "linux" line and at the end of the line, remove "splash" and "quiet". <
>5. Type "F10" to boot the custom boot line.|| === Debugging Plymouth === - || Thank you for taking the time to report this bug and helping to make Ubuntu better. Please run the command 'apport-collect BUGNUMBER' which will attach necessary information for debugging this as a Plymouth problem. Thanks in advance.|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. Please run the command 'apport-collect BUGNUMBER' which will attach necessary information for debugging this as a plymouth problem. Thanks in advance.|| === Debugging Live CD Installation === From noreply at ubuntu.com Fri Jun 3 17:28:51 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 03 Jun 2011 17:28:51 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_vish?= Message-ID: <20110603172851.31639.65710@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by vish: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=177&rev2=178 The comment on the change is: Cheese apport tags , for more info see its /debian/source_cheese.py ------------------------------------------------------------------------------ || [[https://launchpad.net/ubuntu/+bugs?field.tag=ffox36-hardy|`ffox36-hardy`]] || Regressions on Hardy due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2 || || [[https://launchpad.net/ubuntu/+bugs?field.tag=ffox36-jaunty|`ffox36-jaunty`]] || Regressions on Jaunty due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2 || || [[https://launchpad.net/ubuntu/+bugs?field.tag=ffox36-karmic|`ffox36-karmic`]] || Regressions on Karmic due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2 || + === Cheese Specific === + Tags Apport adds while collecting information for Cheese Webcam Booth. + || '''Tag''' || '''Use case''' || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-error|`gstreamer-error`]] || Bug is related to bad drivers and not Cheese; ''Switch bug to related package(`linux` for missing/bad drivers)''|| + || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-ok|`gstreamer-ok`]] || Video gstreamer input works fine (drivers seem fine), most likely a Cheese bug || == Other specific bug tags == From brian at ubuntu.com Fri Jun 3 19:06:12 2011 From: brian at ubuntu.com (Brian Murray) Date: Fri, 3 Jun 2011 12:06:12 -0700 Subject: [Ubuntu Wiki] Update of "Bugs/Tags" by vish In-Reply-To: <20110603172851.31639.65710@jostaberry.canonical.com> References: <20110603172851.31639.65710@jostaberry.canonical.com> Message-ID: <20110603190612.GZ16423@murraytwins.com> On Fri, Jun 03, 2011 at 05:28:51PM -0000, Ubuntu Wiki wrote: > Dear Wiki user, > > You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. > > The following page has been changed by vish: > http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=177&rev2=178 > > The comment on the change is: > Cheese apport tags , for more info see its /debian/source_cheese.py > > ------------------------------------------------------------------------------ > || [[https://launchpad.net/ubuntu/+bugs?field.tag=ffox36-hardy|`ffox36-hardy`]] || Regressions on Hardy due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2 || > || [[https://launchpad.net/ubuntu/+bugs?field.tag=ffox36-jaunty|`ffox36-jaunty`]] || Regressions on Jaunty due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2 || > || [[https://launchpad.net/ubuntu/+bugs?field.tag=ffox36-karmic|`ffox36-karmic`]] || Regressions on Karmic due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2 || > + === Cheese Specific === > + Tags Apport adds while collecting information for Cheese Webcam Booth. > + || '''Tag''' || '''Use case''' || > + || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-error|`gstreamer-error`]] || Bug is related to bad drivers and not Cheese; ''Switch bug to related package(`linux` for missing/bad drivers)''|| If these are linux bugs wouldn't the better thing be updating the apport package hook for cheese so that the bugs were filed about linux instead? -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From vish at ubuntu.com Sat Jun 4 07:25:07 2011 From: vish at ubuntu.com (Vishnoo) Date: Sat, 04 Jun 2011 12:55:07 +0530 Subject: [Ubuntu Wiki] Update of "Bugs/Tags" by vish In-Reply-To: <20110603190612.GZ16423@murraytwins.com> References: <20110603172851.31639.65710@jostaberry.canonical.com> <20110603190612.GZ16423@murraytwins.com> Message-ID: <1307172307.15991.20.camel@Aspire-5670> On Fri, 2011-06-03 at 12:06 -0700, Brian Murray wrote: > On Fri, Jun 03, 2011 at 05:28:51PM -0000, Ubuntu Wiki wrote: > > Dear Wiki user, > > > > You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. > > > > The following page has been changed by vish: > > http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=177&rev2=178 > > > > The comment on the change is: > > Cheese apport tags , for more info see its /debian/source_cheese.py > > + === Cheese Specific === > > + Tags Apport adds while collecting information for Cheese Webcam Booth. > > + || '''Tag''' || '''Use case''' || > > + || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-error|`gstreamer-error`]] || Bug is related to bad drivers and not Cheese; ''Switch bug to related package(`linux` for missing/bad drivers)''|| > > If these are linux bugs wouldn't the better thing be updating the apport > package hook for cheese so that the bugs were filed about linux instead? > > -- > Brian Murray > Ubuntu Bug Master That was precisely my idea too :-) , but I could not find anyone with time to spare to write a hook which works like that. Mitch did excellent work on the apport hook and said he might look into it again if he had time. (But I havent seen him around for a while.) (A little info about this tagging) Such bugs were a huge problem when I was cleaning up a backlog of unattended Cheese bugs. A lot of the kernel driver bugs were just reported as "Cheese does not detect my webcam" or "Cheese displays image wrong" when gstreamer input would have the same problem. I had to ask reporters to launch the gstreamer stream either via terminal or via the multimedia selector and then triage accordingly. What I do with such bugs is set them to "Incomplete" and ask reporters to apport-collect for the Linux package. Ideally this could be done by apport itself; Once apport detects it is a driver error, collect for linux kernel and file the bug in the kernel. Would be awesome if someone could fix the hook to file the bug in the right place. Any takers? :-) -- Cheers, Vish From brian at ubuntu.com Mon Jun 6 16:13:15 2011 From: brian at ubuntu.com (Brian Murray) Date: Mon, 6 Jun 2011 09:13:15 -0700 Subject: [Ubuntu Wiki] Update of "Bugs/Tags" by vish In-Reply-To: <1307172307.15991.20.camel@Aspire-5670> References: <20110603172851.31639.65710@jostaberry.canonical.com> <20110603190612.GZ16423@murraytwins.com> <1307172307.15991.20.camel@Aspire-5670> Message-ID: <20110606161315.GE16423@murraytwins.com> On Sat, Jun 04, 2011 at 12:55:07PM +0530, Vish wrote: > On Fri, 2011-06-03 at 12:06 -0700, Brian Murray wrote: > > On Fri, Jun 03, 2011 at 05:28:51PM -0000, Ubuntu Wiki wrote: > > > Dear Wiki user, > > > > > > You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. > > > > > > The following page has been changed by vish: > > > http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=177&rev2=178 > > > > > > The comment on the change is: > > > Cheese apport tags , for more info see its /debian/source_cheese.py > > > + === Cheese Specific === > > > + Tags Apport adds while collecting information for Cheese Webcam Booth. > > > + || '''Tag''' || '''Use case''' || > > > + || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-error|`gstreamer-error`]] || Bug is related to bad drivers and not Cheese; ''Switch bug to related package(`linux` for missing/bad drivers)''|| > > > > If these are linux bugs wouldn't the better thing be updating the apport > > package hook for cheese so that the bugs were filed about linux instead? > > > > -- > > Brian Murray > > Ubuntu Bug Master > > That was precisely my idea too :-) , > but I could not find anyone with time to spare to write a hook which > works like that. > Mitch did excellent work on the apport hook and said he might look into > it again if he had time. (But I havent seen him around for a while.) > > (A little info about this tagging) > Such bugs were a huge problem when I was cleaning up a backlog of > unattended Cheese bugs. A lot of the kernel driver bugs were just > reported as "Cheese does not detect my webcam" or "Cheese displays image > wrong" when gstreamer input would have the same problem. > I had to ask reporters to launch the gstreamer stream either via > terminal or via the multimedia selector and then triage accordingly. > > What I do with such bugs is set them to "Incomplete" and ask reporters > to apport-collect for the Linux package. > Ideally this could be done by apport itself; Once apport detects it is a > driver error, collect for linux kernel and file the bug in the kernel. > > Would be awesome if someone could fix the hook to file the bug in the > right place. > Any takers? :-) If you could report a bug about cheese, tag it apport-hook and include information about what gstreamer command to execute to determine if it is a driver issue I will see what I can do. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From brian at ubuntu.com Mon Jun 6 16:40:36 2011 From: brian at ubuntu.com (Brian Murray) Date: Mon, 6 Jun 2011 09:40:36 -0700 Subject: Tagging bugs related to apport package hooks Message-ID: <20110606164036.GH16423@murraytwins.com> I've started tagging bug reports related to modifications or additions of apport package hooks, found in /usr/share/apport/package-hooks/, apport-hook. If you happen to know of bug reports like these I'd appreciate it if you were to also tag them apport-hook. Thanks! -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From micahg at ubuntu.com Mon Jun 6 16:43:49 2011 From: micahg at ubuntu.com (Micah Gersten) Date: Mon, 06 Jun 2011 11:43:49 -0500 Subject: Tagging bugs related to apport package hooks In-Reply-To: <20110606164036.GH16423@murraytwins.com> References: <20110606164036.GH16423@murraytwins.com> Message-ID: <4DED03C5.5070706@ubuntu.com> On 06/06/2011 11:40 AM, Brian Murray wrote: > I've started tagging bug reports related to modifications or additions of > apport package hooks, found in /usr/share/apport/package-hooks/, > apport-hook. If you happen to know of bug reports like these I'd > appreciate it if you were to also tag them apport-hook. > > Thanks! > -- > Brian Murray > Ubuntu Bug Master Should this be an official distro tag? Micah From brian at ubuntu.com Mon Jun 6 16:55:17 2011 From: brian at ubuntu.com (Brian Murray) Date: Mon, 6 Jun 2011 09:55:17 -0700 Subject: Tagging bugs related to apport package hooks In-Reply-To: <4DED03C5.5070706@ubuntu.com> References: <20110606164036.GH16423@murraytwins.com> <4DED03C5.5070706@ubuntu.com> Message-ID: <20110606165517.GI16423@murraytwins.com> On Mon, Jun 06, 2011 at 11:43:49AM -0500, Micah Gersten wrote: > On 06/06/2011 11:40 AM, Brian Murray wrote: > > I've started tagging bug reports related to modifications or additions of > > apport package hooks, found in /usr/share/apport/package-hooks/, > > apport-hook. If you happen to know of bug reports like these I'd > > appreciate it if you were to also tag them apport-hook. > > > > Thanks! > > -- > > Brian Murray > > Ubuntu Bug Master > > Should this be an official distro tag? I think having it be an official distribution tag may lead to lots of bugs being incorrectly tagged, particularly because apport-hook isn't very descriptive and lots of bugs get tagged apport-something. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From micahg at ubuntu.com Mon Jun 6 18:32:16 2011 From: micahg at ubuntu.com (Micah Gersten) Date: Mon, 06 Jun 2011 13:32:16 -0500 Subject: Tagging bugs related to apport package hooks In-Reply-To: <20110606165517.GI16423@murraytwins.com> References: <20110606164036.GH16423@murraytwins.com> <4DED03C5.5070706@ubuntu.com> <20110606165517.GI16423@murraytwins.com> Message-ID: <4DED1D30.5060907@ubuntu.com> On 06/06/2011 11:55 AM, Brian Murray wrote: > On Mon, Jun 06, 2011 at 11:43:49AM -0500, Micah Gersten wrote: >> On 06/06/2011 11:40 AM, Brian Murray wrote: >>> I've started tagging bug reports related to modifications or additions of >>> apport package hooks, found in /usr/share/apport/package-hooks/, >>> apport-hook. If you happen to know of bug reports like these I'd >>> appreciate it if you were to also tag them apport-hook. >>> >>> Thanks! >>> -- >>> Brian Murray >>> Ubuntu Bug Master >> Should this be an official distro tag? > I think having it be an official distribution tag may lead to lots of > bugs being incorrectly tagged, particularly because apport-hook isn't > very descriptive and lots of bugs get tagged apport-something. > > -- > Brian Murray > Ubuntu Bug Master Would a more descriptive one like apport-hook-code be desirable? Micah From vish at ubuntu.com Tue Jun 7 10:30:12 2011 From: vish at ubuntu.com (Vishnoo) Date: Tue, 07 Jun 2011 16:00:12 +0530 Subject: [Ubuntu Wiki] Update of "Bugs/Tags" by vish In-Reply-To: <20110606161315.GE16423@murraytwins.com> References: <20110603172851.31639.65710@jostaberry.canonical.com> <20110603190612.GZ16423@murraytwins.com> <1307172307.15991.20.camel@Aspire-5670> <20110606161315.GE16423@murraytwins.com> Message-ID: <1307442612.5155.1.camel@Aspire-5670> On Mon, 2011-06-06 at 09:13 -0700, Brian Murray wrote: > On Sat, Jun 04, 2011 at 12:55:07PM +0530, Vish wrote: > > On Fri, 2011-06-03 at 12:06 -0700, Brian Murray wrote: > > > On Fri, Jun 03, 2011 at 05:28:51PM -0000, Ubuntu Wiki wrote: > > > > Dear Wiki user, > > > > > > > > You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. > > > > > > > > The following page has been changed by vish: > > > > http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=177&rev2=178 > > > > > > > > The comment on the change is: > > > > Cheese apport tags , for more info see its /debian/source_cheese.py > > > > + === Cheese Specific === > > > > + Tags Apport adds while collecting information for Cheese Webcam Booth. > > > > + || '''Tag''' || '''Use case''' || > > > > + || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-error|`gstreamer-error`]] || Bug is related to bad drivers and not Cheese; ''Switch bug to related package(`linux` for missing/bad drivers)''|| > > > > > > If these are linux bugs wouldn't the better thing be updating the apport > > > package hook for cheese so that the bugs were filed about linux instead? > > > > > > -- > > > Brian Murray > > > Ubuntu Bug Master > > > > That was precisely my idea too :-) , > > but I could not find anyone with time to spare to write a hook which > > works like that. > > Mitch did excellent work on the apport hook and said he might look into > > it again if he had time. (But I havent seen him around for a while.) > > > > (A little info about this tagging) > > Such bugs were a huge problem when I was cleaning up a backlog of > > unattended Cheese bugs. A lot of the kernel driver bugs were just > > reported as "Cheese does not detect my webcam" or "Cheese displays image > > wrong" when gstreamer input would have the same problem. > > I had to ask reporters to launch the gstreamer stream either via > > terminal or via the multimedia selector and then triage accordingly. > > > > What I do with such bugs is set them to "Incomplete" and ask reporters > > to apport-collect for the Linux package. > > Ideally this could be done by apport itself; Once apport detects it is a > > driver error, collect for linux kernel and file the bug in the kernel. > > > > Would be awesome if someone could fix the hook to file the bug in the > > right place. > > Any takers? :-) > > If you could report a bug about cheese, tag it apport-hook and include > information about what gstreamer command to execute to determine if it > is a driver issue I will see what I can do. > > -- Awesome! Filed the bug for this: -- Cheers, Vish From brian at ubuntu.com Tue Jun 7 15:03:01 2011 From: brian at ubuntu.com (Brian Murray) Date: Tue, 7 Jun 2011 08:03:01 -0700 Subject: Tagging bugs related to apport package hooks In-Reply-To: <4DED1D30.5060907@ubuntu.com> References: <20110606164036.GH16423@murraytwins.com> <4DED03C5.5070706@ubuntu.com> <20110606165517.GI16423@murraytwins.com> <4DED1D30.5060907@ubuntu.com> Message-ID: <20110607150301.GN16423@murraytwins.com> On Mon, Jun 06, 2011 at 01:32:16PM -0500, Micah Gersten wrote: > On 06/06/2011 11:55 AM, Brian Murray wrote: > > On Mon, Jun 06, 2011 at 11:43:49AM -0500, Micah Gersten wrote: > >> On 06/06/2011 11:40 AM, Brian Murray wrote: > >>> I've started tagging bug reports related to modifications or additions of > >>> apport package hooks, found in /usr/share/apport/package-hooks/, > >>> apport-hook. If you happen to know of bug reports like these I'd > >>> appreciate it if you were to also tag them apport-hook. > >>> > >>> Thanks! > >>> -- > >>> Brian Murray > >>> Ubuntu Bug Master > >> Should this be an official distro tag? > > I think having it be an official distribution tag may lead to lots of > > bugs being incorrectly tagged, particularly because apport-hook isn't > > very descriptive and lots of bugs get tagged apport-something. > > > > -- > > Brian Murray > > Ubuntu Bug Master > Would a more descriptive one like apport-hook-code be desirable? So my concern is the auto completion feature of the tags interface in Launchpad because both of these tags start with the word apport. Apport is a confusing thing and since lots of bugs get tagged apport something there is a risk of the tag being used incorrectly. We could start with the word package, like package-hook-apport, but again the word package can be confusing. So maybe if we start with hook like hook-for-apport? -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From pedro at ubuntu.com Tue Jun 7 15:01:50 2011 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 07 Jun 2011 11:01:50 -0400 Subject: Announcing the Next Ubuntu Bug Day! - 09 June 2011 Message-ID: <1307458910.2938.5.camel@wombat> Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Nautilus! * 50 New bugs need a hug * 44 Incomplete bugs need a status check * 50 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * 09 June 2011 * https://wiki.ubuntu.com/UbuntuBugDay/20110609 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, pedro. From noreply at ubuntu.com Mon Jun 6 16:41:58 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 06 Jun 2011 16:41:58 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_brian-murray?= Message-ID: <20110606164158.20377.4509@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=179&rev2=180 ------------------------------------------------------------------------------ || '''Tag''' || '''Use case''' || || [[https://launchpad.net/ubuntu/+bugs?field.tag=a11y|`a11y`]] || This bug is an accessibility problem. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=apport-hook|`apport-hook`]] || This bug is about modifying or adding an apport hook for a package. || || [[https://launchpad.net/ubuntu/+bugs?field.tag=dxteam|`dxteam`]] || This bug is specifically targeted by Canonical developers, only to be associated with the 'notifications' tag. || || [[https://launchpad.net/ubuntu/+bugs?field.tag=ec2-images|`ec2-images`]] || This bug is related to Ubuntu on [[https://help.ubuntu.com/community/EC2StartersGuide|EC2]]. || || [[https://launchpad.net/ubuntu/+bugs?field.tag=java-headless|`java-headless`]] || This bug is related to a Java program or library that could run headless but depends on a full Java environment (including graphics and sound) || From noreply at ubuntu.com Mon Jun 6 19:57:19 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 06 Jun 2011 19:57:19 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Unity/FilingBugs=22_by_jorge?= Message-ID: <20110606195719.7319.67933@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by jorge: http://wiki.ubuntu.com/Unity/FilingBugs?action=diff&rev1=43&rev2=44 ------------------------------------------------------------------------------ || [[https://launchpad.net/ubuntu/+bugs?field.tag=running-unity|`running-unity`]] || Bugs reported by people who are running Unity || || [[https://launchpad.net/unity/+bugs?field.tag=bitesize|`bitesize`]] || Smaller bugs that would be ideal for new contributors. || || [[https://launchpad.net/unity/+bugs?field.tag=needs-design|`needs-design`]] || A bug that needs UI design done first. || + || [[https://launchpad.net/unity/+bugs?field.tag=backlog|`backlog`]] || Things that design has done and has finished on that needs to be implemented. || || ... || ... || From costamagnagianfranco at yahoo.it Wed Jun 8 14:35:55 2011 From: costamagnagianfranco at yahoo.it (Gianfranco Costamagna) Date: Wed, 8 Jun 2011 15:35:55 +0100 (BST) Subject: Regression in linux kernel Message-ID: <31419.51641.qm@web26703.mail.ukl.yahoo.com> https://bugs.launchpad.net/bugs/794462 I found a serious regression in the kernel (proposed). Please take care of it before it is released to stable.   Just my 0.02 $ Gianfranco -------------- next part -------------- An HTML attachment was scrubbed... URL: From om26er at ubuntu.com Wed Jun 8 14:40:36 2011 From: om26er at ubuntu.com (Omer Akram) Date: Wed, 8 Jun 2011 19:40:36 +0500 Subject: Regression in linux kernel In-Reply-To: <31419.51641.qm@web26703.mail.ukl.yahoo.com> References: <31419.51641.qm@web26703.mail.ukl.yahoo.com> Message-ID: Hi Gianfranco, The bug status was confirmed by Brad so I think the kernel team is aware of the problem. On Wed, Jun 8, 2011 at 7:35 PM, Gianfranco Costamagna wrote: > https://bugs.launchpad.net/bugs/794462 > I found a serious regression in the kernel (proposed). > Please take care of it before it is released to stable. > > > Just my 0.02 $ > > Gianfranco > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > From cjk at teamcharliesangels.com Wed Jun 8 15:05:03 2011 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Wed, 8 Jun 2011 09:05:03 -0600 Subject: Regression in linux kernel In-Reply-To: <31419.51641.qm@web26703.mail.ukl.yahoo.com> References: <31419.51641.qm@web26703.mail.ukl.yahoo.com> Message-ID: <20110608090503.20b59446@teamcharliesangels.com> On Wed, 8 Jun 2011 15:35:55 +0100 (BST) Gianfranco Costamagna wrote: > https://bugs.launchpad.net/bugs/794462 > I found a serious regression in the kernel (proposed). > > Please take care of it before it is released to stable. > > >   > > Just my 0.02 $ > > > Gianfranco thanks. The kernel team has already confirmed this issue for you. -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] From harish.b310 at gmail.com Wed Jun 8 16:04:33 2011 From: harish.b310 at gmail.com (Harish Babu) Date: Wed, 8 Jun 2011 21:34:33 +0530 Subject: No subject Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: From vish at ubuntu.com Fri Jun 10 17:48:00 2011 From: vish at ubuntu.com (Vishnoo) Date: Fri, 10 Jun 2011 23:18:00 +0530 Subject: Admin List in Bugsquad Mentoring team Message-ID: <1307728080.1836.48.camel@Aspire-5670> Hi, Not many seem to know that there are a lot of Admins on the mentoring team. During the last BugSquad meeting, I had taken an action item to list out the Admins in the team. So.. Apart from me there are other mentors who can add new members or help with any other admin tasks. Feel free to ping anyone of us regarding mentoring. ---Name ----------------- IRC nick Brian Murray ------------ bdmurray C de-Avillez ------------ hggdh Charlie Kravetz --------- charlie-tca Draycen DeCator --------- ddecator Duane Hinnen ------------ duanedesign Kamus ------------------- Kamusin Mohamed Amine Ilidrissi - devildante Pedro Villavicencio ----- pedro_ Teej -------------------- xteejx From: -- Cheers, Vish From noreply at ubuntu.com Mon Jun 13 23:31:57 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 13 Jun 2011 23:31:57 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingScreenLocking/HowScreen?= =?utf-8?q?LockingWorks=22_by_mdeslaur?= Message-ID: <20110613233157.18714.53096@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by mdeslaur: http://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks?action=diff&rev1=11&rev2=12 ------------------------------------------------------------------------------ (Ref.: gnome-panel/panel-util.c in gnome-panel) + === "Lock screen" keyboard shortcut (usually Ctrl-Alt-L) === + + gnome-settings-daemon handles the keyboard shortcuts. When the "Lock screen" keyboard shortcut is pressed, gnome-settings-daemon performs the following actions: + + * Checks if gnome-screensaver-command is available, or else falls back to xscreensaver-command + * Calls the appropriate command with the "--lock" parameter + + (Ref.: plugins/media-keys/gsd-media-keys-manager.c in gnome-settings-daemon) + == Screensaver Inhibiting == Prior to Karmic, applications that wished to temporarily suspend the screensaver from coming up could periodically send the "poke" command to gnome-screensaver, either using the DBus API, or with the gnome-screensaver-command tool. This would cause gnome-screensaver to reset the idle counter, preventing it from reaching the preset value. From pedro at ubuntu.com Tue Jun 14 18:38:28 2011 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 14 Jun 2011 14:38:28 -0400 Subject: Announcing the Next Ubuntu Bug Day! - Thursday 16th June 2011 Message-ID: <1308076708.2695.2.camel@wombat> Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Totem! * 50 New bugs need a hug * 8 Incomplete bugs need a status check * 9 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 16th June 2011 * https://wiki.ubuntu.com/UbuntuBugDay/20110616 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, pedro. From noreply at ubuntu.com Tue Jun 14 18:35:48 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 14 Jun 2011 18:35:48 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_pvillavi?= Message-ID: <20110614183548.17758.47634@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by pvillavi: http://wiki.ubuntu.com/Bugs/Events?action=diff&rev1=252&rev2=253 ------------------------------------------------------------------------------ || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/20110616| Nautilus]] || hugday-20110616 || || [[UbuntuBugDay/20110609| Nautilus]] || hugday-20110609 || || [[UbuntuBugDay/20110602| Evolution]] || hugday-20110602 || || [[UbuntuBugDay/20110526| Compiz]] || hugday-20110526 || From noreply at ubuntu.com Wed Jun 15 18:35:40 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 15 Jun 2011 18:35:40 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/CommonTasks=22_by_brian-mur?= =?utf-8?q?ray?= Message-ID: <20110615183540.3758.41944@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/Bugs/CommonTasks?action=diff&rev1=70&rev2=71 The comment on the change is: Its always linux now ------------------------------------------------------------------------------ === Finding the proper source package === Assigning bugs to packages helps direct bug reports to the developer(s) most likely to be able to help. By ensuring that this information is accurate, you can increase the chances of the bug being fixed promptly. Often, it is unclear which package contains the bug, and in these cases it is appropriate to file the bug in {{{Ubuntu}}}. If a bug is assigned to a package which is clearly not correct, and you don't know the correct package, change it to {{{Ubuntu}}}. Some hints on finding the right package can be found in [[Bugs/FindRightPackage]]. - - The correct package for bugs in the Linux kernel is dependent upon the release of Ubuntu being used. - - * For Dapper (6.06) the correct package is {{{linux-source-2.6.15}}} - * For Edgy (6.10) the correct package is {{{linux-source-2.6.17}}} - * For Feisty (7.04) the correct package is {{{linux-source-2.6.20}}} - * For Gutsy (7.10) the correct package is {{{linux-source-2.6.22}}} - * For Hardy (8.04) and later releases the correct package is {{{linux}}} === Confirming problems === From noreply at ubuntu.com Mon Jun 20 17:04:00 2011 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 20 Jun 2011 17:04:00 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProgramCrash=22_by_mter?= =?utf-8?q?ry?= Message-ID: <20110620170400.3416.21216@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingProgramCrash" page has been changed by mterry: http://wiki.ubuntu.com/DebuggingProgramCrash?action=diff&rev1=110&rev2=111 Comment: Prune pre-hardy details This document describes how to install debug packages on Ubuntu, which will aid in providing information for bugs. + == Debug Symbol Packages == - == Hardy 8.04 and Newer == - - Use this section only if you are using Ubuntu '''Hardy 8.04''' or more recent versions (the command {{{cat /etc/issue}}} will tell you). See the following section if you are using a prior version. First, check if there is a package with a -dbg suffix in the main Ubuntu repositories. These are the debug symbol packages, and are equivalent to '-dbgsym' described below. You can safely use either one, but not both at once. Try installing the package, adding -dbg to its name, for example: {{{ @@ -92, +90 @@ * Announcement: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2006-September/000195.html - == Prior Ubuntu versions == - - Use this section if you are using an Ubuntu version prior to Gutsy 7.10. - - 1. Check if the package has a debugging version available. In general, debugging packages will be named with a `-dbg` suffix - 1. If not, you can generally* build one this way: - - Something to keep in mind: if you would like to create a build you're going to need to have the relevant deb-src lines in your /etc/apt/sources.list - - a. Install the development scripts: - {{{ - sudo apt-get install devscripts fakeroot - }}} - - a. Find out to which package your program belongs to: - {{{ - dpkg --search - }}} - - a. Install the build-time dependencies for the package: - {{{ - sudo apt-get build-dep - }}} - a. Build .debs for debugging: - {{{ - export DEB_BUILD_OPTIONS="debug nostrip noopt" - fakeroot apt-get source -b - }}} - a. Install the needed .debs (they will be in the current working directory if the build succeeded): - {{{ - sudo debi *.changes - }}} - - - * Most packages support the build of debugging version in this way. If this process doesn't work for a package, please open a bug against it. - - == The Xorg server == The X server will by default trap its own crashes and dump a stack trace in /var/log/Xorg.0.log. However, this stack trace is modified by the signal handler itself. To get a "normal" crash, which will trigger a core dump (and ''apport'' reporting), add this to your /etc/X11/xorg.conf: {{{ From pedro at ubuntu.com Wed Jun 22 13:02:18 2011 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Wed, 22 Jun 2011 09:02:18 -0400 Subject: Announcing the Next Ubuntu Bug Day! - Thursday 23 June 2011 Message-ID: <1308747738.3496.1.camel@wombat> Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Unity! * 50 New bugs need a hug * 50 Incomplete bugs need a status check * 50 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 23 June 2011 * https://wiki.ubuntu.com/UbuntuBugDay/20110623 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, pedro. From brian at ubuntu.com Wed Jun 22 17:20:45 2011 From: brian at ubuntu.com (Brian Murray) Date: Wed, 22 Jun 2011 10:20:45 -0700 Subject: grab-attachments Message-ID: <20110622172045.GV28048@murraytwins.com> There is this great tool in ubuntu-dev-tools called grab-attachments[1] which allows you to download all the attachments from a bug report to your local system. This is quite handy as you don't have to download each log file individually. I've made it a bit more handy[2] as you can now also pass it a package name, e.g. grab-attachments --package nautilus, and it'll download all the attachments attached it to any bug reports with an open nautilus bug task. Just make sure you have some free space! [1] http://bazaar.launchpad.net/~ubuntu-dev/ubuntu-dev-tools/trunk/view/head:/grab-attachments [2] http://www.murraytwins.com/blog/?p=104 -- Brian Murray -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From brian at ubuntu.com Wed Jun 22 18:15:00 2011 From: brian at ubuntu.com (Brian Murray) Date: Wed, 22 Jun 2011 11:15:00 -0700 Subject: Package Status Pages Message-ID: <20110622181500.GW28048@murraytwins.com> I've made some recent updates to the package status pages at: http://status.qa.ubuntu.com/qapkgstatus/ that you will hopefully find useful. There is now a link and count for the quantity of apport-package bug reports, bugs tagged about the development release, bugs needing a bug pattern and those tagged regression-proposed. Please let me know if you think of any other useful additions. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From noreply at ubuntu.com Wed Jun 22 19:44:05 2011 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 22 Jun 2011 19:44:05 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_brian-murra?= =?utf-8?q?y?= Message-ID: <20110622194405.4659.58008@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Responses" page has been changed by brian-murray: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=333&rev2=334 Comment: Removed medibuntu reply ||Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! <
><
>If you are interested in learning more about software repositories and Ubuntu the following pages should be informative:<
><
>1. http://www.ubuntu.com/project/about-ubuntu/components - information about Ubuntu repositories<
>2. https://help.ubuntu.com/community/Repositories - information regarding managing repositories|| - === Packages provided by Medibuntu === - - While not supported by Ubuntu, it might be more helpful to a user if we can point them in the right direction if they are looking for something that's in Medibuntu. - A package list can be found here: http://packages.medibuntu.org/ - Common Packages people are looking for are: - Google Earth, Real Player, and Skype - - Here's a simple response for one of those packages (Note PKG is a placeholder): - - ||You can get deb packages compatible with Ubuntu for PKG from Medibuntu: <
>https://help.ubuntu.com/community/Medibuntu <
><
>If you encounter any bugs with Medibuntu, report them here:<
>https://launchpad.net/medibuntu/+filebug <
><
>If you have questions about Medibuntu, you can ask them here:<
>https://answers.launchpad.net/medibuntu/|| - == Fixed in Development release while still existing in a previous release == The bug's state should become '''Fix Released''' and if the package qualifies for a [[https://wiki.ubuntu.com/StableReleaseUpdates#Procedure|Stable Release Update (SRU)]]: From noreply at ubuntu.com Thu Jun 23 15:37:38 2011 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 23 Jun 2011 15:37:38 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/HowToTriage=22_by_yofel?= Message-ID: <20110623153738.29697.36540@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/HowToTriage" page has been changed by yofel: http://wiki.ubuntu.com/Bugs/HowToTriage?action=diff&rev1=149&rev2=150 Comment: fix links for new moinmoin || ''' <> ''' || - ||Contents<
>    1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Bug%20Types|Bug Types]]<
>        1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20reports|Apport reports]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20crash%20reports|Apport crash reports]]<
>        2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Confirmed%20bugs|Confirmed bugs]]<
>        3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Feature%20Requests|Feature Requests]]<
>        4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Regressions|Regressions]]<
>        5. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Untriaged%20bugs|Untriaged bugs]]<
>        6. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Bug%20reports%20not%20in%20English|Bug reports not in English]]<
>        7. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Special%20types%20of%20bugs|Special types of bugs]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Developer%20Process%20Bugs|Developer Process Bugs]]<
>            2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Needs%20Packaging%20Bugs|Needs Packaging Bugs]]<
>            3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Security%20Bugs|Security Bugs]]<
>            4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Translation%20Bugs%20and%20Launchpad%20integration|Translation Bugs and Launchpad integration]]<
>    2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Actions|Actions]]<
>        1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Confirming|Confirming]]<
>        2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Forwarding%20upstream|Forwarding upstream]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Marking%20a%20Bug%20as%20Requiring%20Forwarding|Marking a Bug as Requiring Forwarding]]<
>        3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Marking%20duplicate|Marking duplicate]]<
>        4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Improving%20a%20bug%20report|Improving a bug report]]<
>        5. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Converting%20a%20bug%20report%20to%20a%20question|Converting to a question]]<
>        6. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Invalidating|Invalidating]]<
>    3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Status%20and%20Importance|Status and Importance]]<
>    4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Looking%20through%20your%20bugs|Looking through your bugs]]|| + ||Contents<
>    1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Bug_Types|Bug Types]]<
>        1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Apport_reports|Apport reports]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Apport_crash_reports|Apport crash reports]]<
>        2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Confirmed_bugs|Confirmed bugs]]<
>        3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Feature_Requests|Feature Requests]]<
>        4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Regressions|Regressions]]<
>        5. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Untriaged_bugs|Untriaged bugs]]<
>        6. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Bug_reports_not_in_English|Bug reports not in English]]<
>        7. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Special_types_of_bugs|Special types of bugs]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Developer_Process_Bugs|Developer Process Bugs]]<
>            2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Needs_Packaging_Bugs|Needs Packaging Bugs]]<
>            3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Security_Bugs|Security Bugs]]<
>            4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Translation_Bugs_and_Launchpad_integration|Translation Bugs and Launchpad integration]]<
>    2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Actions|Actions]]<
>        1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Confirming|Confirming]]<
>        2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Forwarding_upstream|Forwarding upstream]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Marking_a_Bug_as_Requiring_Forwarding|Marking a Bug as Requiring Forwarding]]<
>        3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Marking_duplicate|Marking duplicate]]<
>        4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Improving_a_bug_report|Improving a bug report]]<
>        5. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Converting_a_bug_report_to_a_question|Converting to a question]]<
>        6. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Invalidating|Invalidating]]<
>    3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Status_and_Importance|Status and Importance]]<
>    4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Looking_through_your_bugs|Looking through your bugs]]|| In a hospital, triage happens the instant a patient arrives through the emergency room doors. His vital signs are checked, his status assessed, and he gets sorted in amongst all the other patients waiting for treatment. @@ -14, +14 @@ Every bug report is a conversation with the reporter. The first contact any reporter usually has with the Ubuntu community is through a bug triager, who tries to put together a complete bug report. It's very important that we give a good impression, so please be polite and try to use your best English. - Working on simple, untriaged bugs is a good way to get started and become acquainted with the triaging procedure since you'll have to deal with every aspect of the life cycle of a bug. The section [[https://wiki.ubuntu.com/Bugs/HowToTriage#Untriaged%20bugs|Untriaged bugs]] explains where to find them. + Working on simple, untriaged bugs is a good way to get started and become acquainted with the triaging procedure since you'll have to deal with every aspect of the life cycle of a bug. The section [[https://wiki.ubuntu.com/Bugs/HowToTriage#Untriaged_bugs|Untriaged bugs]] explains where to find them. <> ||{{attachment:bugsquad.png}}||'''Bug Types'''|| @@ -47, +47 @@ If the bug adheres to '''ALL''' of the following criteria it can be considered triaged: * Does the bug report describe a valid bug? - * Does the bug report contain [[https://wiki.ubuntu.com/Bugs/HowToTriage#Improving%20a%20bug%20report|enough details]]? + * Does the bug report contain [[https://wiki.ubuntu.com/Bugs/HowToTriage#Improving_a_bug_report|enough details]]? - * If necessary, is the bug report [[https://wiki.ubuntu.com/Bugs/HowToTriage#Forwarding%20upstream|forwarded upstream]]? + * If necessary, is the bug report [[https://wiki.ubuntu.com/Bugs/HowToTriage#Forwarding_upstream|forwarded upstream]]? * Is the bug report ready to be worked on by a developer? Only if '''ALL''' of these conditions are satisfied, you can set the status of the bug report to 'Triaged'. To do this: From hggdh2 at ubuntu.com Fri Jun 24 00:25:32 2011 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Thu, 23 Jun 2011 19:25:32 -0500 Subject: Package Status Pages In-Reply-To: <20110622181500.GW28048@murraytwins.com> References: <20110622181500.GW28048@murraytwins.com> Message-ID: <4E03D97C.7000504@ubuntu.com> On 06/22/2011 01:15 PM, Brian Murray wrote: > I've made some recent updates to the package status pages at: > > http://status.qa.ubuntu.com/qapkgstatus/ > > that you will hopefully find useful. There is now a link and count for the > quantity of apport-package bug reports, bugs tagged about the > development release, bugs needing a bug pattern and those tagged > regression-proposed. Please let me know if you think of any other > useful additions. Coreutils should be there, I think, under Low-Level. Nice work, Brian, thank you. ..C.. From micahg at ubuntu.com Fri Jun 24 01:57:36 2011 From: micahg at ubuntu.com (Micah Gersten) Date: Thu, 23 Jun 2011 20:57:36 -0500 Subject: Package Status Pages In-Reply-To: <20110622181500.GW28048@murraytwins.com> References: <20110622181500.GW28048@murraytwins.com> Message-ID: <4E03EF10.805@ubuntu.com> On 06/22/2011 01:15 PM, Brian Murray wrote: > I've made some recent updates to the package status pages at: > > http://status.qa.ubuntu.com/qapkgstatus/ > > that you will hopefully find useful. There is now a link and count for the > quantity of apport-package bug reports, bugs tagged about the > development release, bugs needing a bug pattern and those tagged > regression-proposed. Please let me know if you think of any other > useful additions. > > -- > Brian Murray > Ubuntu Bug Master Brian this is very nice. I was wondering if we could autogenerate some of these pages/categories based on package sets. Thanks, Micah From rouxelval at yahoo.fr Thu Jun 30 21:38:19 2011 From: rouxelval at yahoo.fr (valentin rouxel) Date: Thu, 30 Jun 2011 22:38:19 +0100 (BST) Subject: getting involved in triage bugs Message-ID: <1309469899.81047.YahooMailClassic@web28004.mail.ukl.yahoo.com> Hello, I am a French student in computer science and I use Ubuntu since 4 years. I would like involve to triage bugs. I have read the wiki about getting involved, how triage and how select a packet but I am not sure to know how begin. Moreover I have begun to look the list of bugs filed without a package and it seems difficult to select a package. It seemed more simple in reading the wiki. Maybe I have not yet the knowledge to involve. I would be pleased if someone could help me to begin or say me what I need to know to involve so I could learn the missing knowledge. Regards. Valentin Rouxel P.S Excuse my bad English, I am working to improve it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From komputes at gmail.com Thu Jun 30 22:31:40 2011 From: komputes at gmail.com (komputes) Date: Thu, 30 Jun 2011 18:31:40 -0400 Subject: getting involved in triage bugs In-Reply-To: <1309469899.81047.YahooMailClassic@web28004.mail.ukl.yahoo.com> References: <1309469899.81047.YahooMailClassic@web28004.mail.ukl.yahoo.com> Message-ID: <4E0CF94C.8050106@gmail.com> On 06/30/2011 05:38 PM, valentin rouxel wrote: > > > > > > > > > > Hello, > > > > I am a French student in > computer science and I use Ubuntu since 4 years. I would like involve > to triage bugs. I have read the wiki about getting involved, how > triage and how select a packet but I am not sure to know how begin. > Moreover I have begun to look the list of bugs filed without a > package and it seems difficult to select a package. It seemed more > simple in reading the wiki. Maybe I have not yet the knowledge to > involve. I would be pleased if someone could help me to begin or say > me what I need to know to involve so I could learn the missing > knowledge. > > > > Regards. > > > > Valentin Rouxel > > > > P.S Excuse my bad > English, I am working to improve it. > > Hello Valentin, Welcome to Ubuntu and thank you for wanting to get involved. If you need a mentor to better learn to triage bugs, you can get in touch with me by email or on IRC and I would be happy to help you out. -komputes (]( -. .- )[)