From noreply at ubuntu.com Fri Mar 1 07:51:44 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 01 Mar 2013 07:51:44 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/FindRightPackage=22_by_shan?= =?utf-8?q?kao?= Message-ID: <20130301075144.16002.2698@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/FindRightPackage" page has been changed by shankao: http://wiki.ubuntu.com/Bugs/FindRightPackage?action=diff&rev1=124&rev2=125 Comment: Add Ubuntu touch link Issues with Ubuntu [[Mirrors]] (the servers from which you download packages) should be reported to mirrors at ubuntu.com and ''not'' on Launchpad. + === Ubuntu Touch === + + Check the guidelines at: https://wiki.ubuntu.com/Touch/Contribute#How_to_report_bugs + == Package-specific instructions == Some packages have changed names through versions of ubuntu and others need special care while reporting. This section lists these caveats. From marconifabio at hotmail.it Mon Mar 11 18:01:32 2013 From: marconifabio at hotmail.it (Fabio Marconi) Date: Mon, 11 Mar 2013 19:01:32 +0100 Subject: Hugday needed Message-ID: <BLU0-SMTP72F354D9402EBCA9153B0A5E10@phx.gbl> Hallo!! I think that we have done a good work on Totem, Garcia simply great !!! Can we have some others candies for this week?? Thanks Fabio -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130311/42207b43/attachment.html> From walter.garcia at upf.edu Mon Mar 11 19:44:43 2013 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Mon, 11 Mar 2013 20:44:43 +0100 Subject: Hugday needed In-Reply-To: <BLU0-SMTP72F354D9402EBCA9153B0A5E10@phx.gbl> References: <BLU0-SMTP72F354D9402EBCA9153B0A5E10@phx.gbl> Message-ID: <20130311194443.GA15414@upf.edu> * Fabio Marconi, marconifabio at hotmail.it [11/03/13 20:32]: > Hallo!! > > I think that we have done a good work on Totem, Garcia simply great !!! > Can we have some others candies for this week?? Thanks Fabio +1 -- Walter Garcia-Fontes From melchiaros at aol.com Wed Mar 13 13:10:05 2013 From: melchiaros at aol.com (melchiaros) Date: Wed, 13 Mar 2013 14:10:05 +0100 Subject: Hugday needed In-Reply-To: <20130311194443.GA15414@upf.edu> References: <BLU0-SMTP72F354D9402EBCA9153B0A5E10@phx.gbl> <20130311194443.GA15414@upf.edu> Message-ID: <51407AAD.409@aol.com> Am 11.03.2013 20:44, schrieb Walter Garcia-Fontes: > * Fabio Marconi, marconifabio at hotmail.it [11/03/13 20:32]: >> Hallo!! >> >> I think that we have done a good work on Totem, Garcia simply great !!! >> Can we have some others candies for this week?? > Thanks Fabio > > +1 > There is one candidate I would like to suggest. It is more about infrastructure than userspace, but those of you who help out sometimes in the "Answers" section know that there is sometimes heavy trouble caused from. It is the package ubuntu-release-upgrader In my experience it is nothing worser than a system that fails on/after upgrade. Regarding to https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader we have only 99 bugs open and with this much less then on totem(>300 when I remember correct), but they are harder to handle. Mostly users give only a weak description, of the kind of "it do not upgrade". So here would be log reading a task that comes to us, to identifiy what is the same(and I expect that there are some dublicates hidden) and what is not. What do you think about? Handling bugs of the ubuntu-release-upgrader would be of some structural benefit that see wider than only on one release or only the actual daily problems. A more stable release upgrader would decrease the fear of the people to upgrade to the latest Ubuntu version. One consequence would be that we have less bugs on older version, which swamp launchpad. From es20490446e at gmail.com Wed Mar 13 14:49:20 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Wed, 13 Mar 2013 15:49:20 +0100 Subject: Hugday needed In-Reply-To: <51407AAD.409@aol.com> References: <BLU0-SMTP72F354D9402EBCA9153B0A5E10@phx.gbl> <20130311194443.GA15414@upf.edu> <51407AAD.409@aol.com> Message-ID: <514091F0.2020307@gmail.com> I agree with the proposal. El 13/03/13 14:10, melchiaros escribió: > Am 11.03.2013 20:44, schrieb Walter Garcia-Fontes: >> * Fabio Marconi, marconifabio at hotmail.it [11/03/13 20:32]: >>> Hallo!! >>> >>> I think that we have done a good work on Totem, Garcia simply great !!! >>> Can we have some others candies for this week?? >> Thanks Fabio >> >> +1 >> > There is one candidate I would like to suggest. > > It is more about infrastructure than userspace, but those of you who > help out sometimes in the "Answers" section know that there is > sometimes heavy trouble caused from. > > It is the package > > ubuntu-release-upgrader > > In my experience it is nothing worser than a system that fails > on/after upgrade. > > Regarding to > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader > > we have only 99 bugs open and with this much less then on totem(>300 > when I remember correct), but they are harder to handle. > > Mostly users give only a weak description, of the kind of "it do not > upgrade". > > So here would be log reading a task that comes to us, to identifiy > what is the same(and I expect that there are some dublicates hidden) > and what is not. > > What do you think about? > > Handling bugs of the ubuntu-release-upgrader > > would be of some structural benefit that see wider than only on one > release or only the actual daily problems. > > A more stable release upgrader would decrease the fear of the people > to upgrade to the latest Ubuntu version. > > One consequence would be that we have less bugs on older version, > which swamp launchpad. > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130313/9c256ebf/attachment.bin> From chilicuil at ubuntu.com Thu Mar 14 10:03:04 2013 From: chilicuil at ubuntu.com (Javier P.L.) Date: Thu, 14 Mar 2013 04:03:04 -0600 Subject: Hugday needed In-Reply-To: <51407AAD.409@aol.com> References: <BLU0-SMTP72F354D9402EBCA9153B0A5E10@phx.gbl> <20130311194443.GA15414@upf.edu> <51407AAD.409@aol.com> Message-ID: <20130314100303.GB5379@sup.lan> > There is one candidate I would like to suggest. > > It is more about infrastructure than userspace, but those of you who > help out sometimes in the "Answers" section know that there is > sometimes heavy trouble caused from. > > It is the package > > ubuntu-release-upgrader +1 > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad From brian at ubuntu.com Thu Mar 14 14:53:47 2013 From: brian at ubuntu.com (Brian Murray) Date: Thu, 14 Mar 2013 07:53:47 -0700 Subject: Hugday needed In-Reply-To: <51407AAD.409@aol.com> References: <BLU0-SMTP72F354D9402EBCA9153B0A5E10@phx.gbl> <20130311194443.GA15414@upf.edu> <51407AAD.409@aol.com> Message-ID: <20130314145347.GA29575@murraytwins.com> On Wed, Mar 13, 2013 at 02:10:05PM +0100, melchiaros wrote: > Am 11.03.2013 20:44, schrieb Walter Garcia-Fontes: > >* Fabio Marconi, marconifabio at hotmail.it [11/03/13 20:32]: > >>Hallo!! > >> > >>I think that we have done a good work on Totem, Garcia simply great !!! > >>Can we have some others candies for this week?? > >Thanks Fabio > > > >+1 > > > There is one candidate I would like to suggest. > > It is more about infrastructure than userspace, but those of you who > help out sometimes in the "Answers" section know that there is > sometimes heavy trouble caused from. > > It is the package > > ubuntu-release-upgrader > > In my experience it is nothing worser than a system that fails > on/after upgrade. > > Regarding to > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader > > we have only 99 bugs open and with this much less then on totem(>300 > when I remember correct), but they are harder to handle. > > Mostly users give only a weak description, of the kind of "it do not > upgrade". For those bug reports you'll want to have the reporter gather the files from /var/log/dist-upgrade/. There is an apport package hook for ubuntu-release-upgrader which will automatically gather the right files. Also keep in mind that ubuntu-release-upgrader is new package in Quantal so it is only correct package for upgrades from Precise to Quantal or Quantal to Raring. If you were to find a bug regarding an upgrade from Oneiric to Precise the correct package is update-manager. Additionally, were you to go through all 99 open bugs it might be good to look at update-manager bug reports for ones which should really be about ubuntu-release-upgrader. > So here would be log reading a task that comes to us, to identifiy > what is the same(and I expect that there are some dublicates hidden) > and what is not. > > What do you think about? Let me know what day you want to do this and I'll be happy to help out. -- 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: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130314/2453a088/attachment.sig> From melchiaros at aol.com Thu Mar 14 17:36:14 2013 From: melchiaros at aol.com (melchiaros) Date: Thu, 14 Mar 2013 18:36:14 +0100 Subject: Hugday needed In-Reply-To: <20130314145347.GA29575@murraytwins.com> References: <BLU0-SMTP72F354D9402EBCA9153B0A5E10@phx.gbl> <20130311194443.GA15414@upf.edu> <51407AAD.409@aol.com> <20130314145347.GA29575@murraytwins.com> Message-ID: <51420A8E.4030904@aol.com> Am 14.03.2013 15:53, schrieb Brian Murray: > On Wed, Mar 13, 2013 at 02:10:05PM +0100, melchiaros wrote: >> Am 11.03.2013 20:44, schrieb Walter Garcia-Fontes: >>> * Fabio Marconi, marconifabio at hotmail.it [11/03/13 20:32]: >>>> Hallo!! >>>> >>>> I think that we have done a good work on Totem, Garcia simply great !!! >>>> Can we have some others candies for this week?? >>> Thanks Fabio >>> >>> +1 >>> >> There is one candidate I would like to suggest. >> >> It is more about infrastructure than userspace, but those of you who >> help out sometimes in the "Answers" section know that there is >> sometimes heavy trouble caused from. >> >> It is the package >> >> ubuntu-release-upgrader >> >> In my experience it is nothing worser than a system that fails >> on/after upgrade. >> >> Regarding to >> >> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader >> >> we have only 99 bugs open and with this much less then on totem(>300 >> when I remember correct), but they are harder to handle. >> >> Mostly users give only a weak description, of the kind of "it do not >> upgrade". > For those bug reports you'll want to have the reporter gather the files > from /var/log/dist-upgrade/. There is an apport package hook for > ubuntu-release-upgrader which will automatically gather the right files. > > Also keep in mind that ubuntu-release-upgrader is new package in Quantal > so it is only correct package for upgrades from Precise to Quantal or > Quantal to Raring. If you were to find a bug regarding an upgrade from > Oneiric to Precise the correct package is update-manager. Additionally, > were you to go through all 99 open bugs it might be good to look at > update-manager bug reports for ones which should really be about > ubuntu-release-upgrader. > >> So here would be log reading a task that comes to us, to identifiy >> what is the same(and I expect that there are some dublicates hidden) >> and what is not. >> >> What do you think about? > Let me know what day you want to do this and I'll be happy to help out. > > -- > Brian Murray > Ubuntu Bug Master > > Hi to all, if I would do the organisation it would be someday in this month. This is not Precise(:)) and a bit far away. Sorry, but you can not see my desk(->you would understand than). @Fabio Well, have you some timeslots free for organisation Fabio? I am offline now for some days. greetings melchiaros -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130314/c272599b/attachment.html> From marconifabio at hotmail.it Fri Mar 15 17:44:51 2013 From: marconifabio at hotmail.it (Fabio Marconi) Date: Fri, 15 Mar 2013 18:44:51 +0100 Subject: Hugday needed In-Reply-To: <51420A8E.4030904@aol.com> References: <BLU0-SMTP72F354D9402EBCA9153B0A5E10@phx.gbl> <20130311194443.GA15414@upf.edu> <51407AAD.409@aol.com> <20130314145347.GA29575@murraytwins.com> <51420A8E.4030904@aol.com> Message-ID: <BLU0-SMTP56F57D97A9A4DB84AD12B5A5ED0@phx.gbl> On 14/03/2013 18:36, melchiaros wrote: > Am 14.03.2013 15:53, schrieb Brian Murray: >> On Wed, Mar 13, 2013 at 02:10:05PM +0100, melchiaros wrote: >>> Am 11.03.2013 20:44, schrieb Walter Garcia-Fontes: >>>> * Fabio Marconi, marconifabio at hotmail.it [11/03/13 20:32]: >>>>> Hallo!! >>>>> >>>>> I think that we have done a good work on Totem, Garcia simply great !!! >>>>> Can we have some others candies for this week?? >>>> Thanks Fabio >>>> >>>> +1 >>>> >>> There is one candidate I would like to suggest. >>> >>> It is more about infrastructure than userspace, but those of you who >>> help out sometimes in the "Answers" section know that there is >>> sometimes heavy trouble caused from. >>> >>> It is the package >>> >>> ubuntu-release-upgrader >>> >>> In my experience it is nothing worser than a system that fails >>> on/after upgrade. >>> >>> Regarding to >>> >>> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader >>> >>> we have only 99 bugs open and with this much less then on totem(>300 >>> when I remember correct), but they are harder to handle. >>> >>> Mostly users give only a weak description, of the kind of "it do not >>> upgrade". >> For those bug reports you'll want to have the reporter gather the files >> from /var/log/dist-upgrade/. There is an apport package hook for >> ubuntu-release-upgrader which will automatically gather the right files. >> >> Also keep in mind that ubuntu-release-upgrader is new package in Quantal >> so it is only correct package for upgrades from Precise to Quantal or >> Quantal to Raring. If you were to find a bug regarding an upgrade from >> Oneiric to Precise the correct package is update-manager. Additionally, >> were you to go through all 99 open bugs it might be good to look at >> update-manager bug reports for ones which should really be about >> ubuntu-release-upgrader. >> >>> So here would be log reading a task that comes to us, to identifiy >>> what is the same(and I expect that there are some dublicates hidden) >>> and what is not. >>> >>> What do you think about? >> Let me know what day you want to do this and I'll be happy to help out. >> >> -- >> Brian Murray >> Ubuntu Bug Master >> >> > Hi to all, > > if I would do the organisation it would be someday in this month. > > This is not Precise(:)) and a bit far away. > > Sorry, but you can not see my desk(->you would understand than). > > @Fabio > > Well, have you some timeslots free for organisation Fabio? > > I am offline now for some days. > > greetings > > melchiaros > > > > Ok, I'm free starting from today, saturday and sunday, so I can try to pick up something good. @Brian, thanks I will surely ping you. For this first work I propose to run only the ubuntu-release-upgrader package and immediatly after update-manager, are you in accord? (proposal are welcome). Thanks Fabio -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130315/2f302611/attachment.html> From marconifabio at hotmail.it Sat Mar 16 22:00:44 2013 From: marconifabio at hotmail.it (Fabio Marconi) Date: Sat, 16 Mar 2013 23:00:44 +0100 Subject: Announcing the Next Ubuntu Bug Day! Message-ID: <BLU0-SMTP787C25AC1165CE1EA30364A5EE0@phx.gbl> Announcing the Next Ubuntu Bug Day! - 21 March 2013 Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* ubuntu-release-upgrader ! * 59 New bugs need a hug * 8 Incomplete bugs need a status check * 21 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * 21 march 2013 * http://wiki.ubuntu.com/UbuntuBugDay/Ubuntu-release-upgrader-20130321 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! 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, Marconi Fabio [From the BugSquad] -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130316/b125243c/attachment.html> From noreply at ubuntu.com Sat Mar 16 21:34:22 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 16 Mar 2013 21:34:22 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_fabiomarconi?= Message-ID: <20130316213422.14216.60827@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Events" page has been changed by fabiomarconi: http://wiki.ubuntu.com/Bugs/Events?action=diff&rev1=265&rev2=266 || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/Ubuntu-release-upgrader-20130321| ubuntu-release-upgrader]]|| hugday-20130321|| - || [[UbuntuBugDay/20130214| Totem]] hugday-20130214 || + || [[UbuntuBugDay/20130214| Totem]]|| hugday-20130214 || - || [[UbuntuBugDay/20130117| Transmission]] hugday-20130117 || + || [[UbuntuBugDay/20130117| Transmission]]|| hugday-20130117 || || [[UbuntuBugDay/20111027| Nautilus]] || hugday-20111027 || || [[UbuntuBugDay/20111020| Bugs without a package]] || hugday-20111020 || || [[UbuntuBugDay/20110908| Bugs without a package]] || hugday-20110908 || From ag.restringere at gmail.com Sun Mar 17 00:12:31 2013 From: ag.restringere at gmail.com (AG Restringere) Date: Sat, 16 Mar 2013 20:12:31 -0400 Subject: Announcing the Next Ubuntu Bug Day! In-Reply-To: <BLU0-SMTP787C25AC1165CE1EA30364A5EE0@phx.gbl> References: <BLU0-SMTP787C25AC1165CE1EA30364A5EE0@phx.gbl> Message-ID: <CALh9bZ1bjsLVXyZyyE8USfv2ZkOVnxBXb-ButQ8bN_PBtM=3ag@mail.gmail.com> Fabio, Given these two items: - Verify the bug is still not fixed How do you quickly verify if the problem has been fixed? What is the process to be used? -Request any needed info What is the specific log(s) and information needed? Best, AG On Sat, Mar 16, 2013 at 6:00 PM, Fabio Marconi <marconifabio at hotmail.it>wrote: > Announcing the Next Ubuntu Bug Day! - 21 March 2013 > > Fellow Ubuntu Triagers!This week's Bug Day target is *drum roll please* ubuntu-release-upgrader ! * 59 New bugs need a hug * 8 Incomplete bugs need a status check * 21 Confirmed bugs need a review > Bookmark it, add it to your calendars, turn over those egg-timers! * 21 march 2013 * http://wiki.ubuntu.com/UbuntuBugDay/Ubuntu-release-upgrader-20130321Are 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!We are always looking for new tasks or ideas for the Bug Days, if you have oneadd it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/PlanningIf you're new to all this, head to http://wiki.ubuntu.com/BugsHave a nice day, Marconi Fabio[From the BugSquad] > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130316/b5da69f6/attachment.html> From marconifabio at hotmail.it Sun Mar 17 09:42:02 2013 From: marconifabio at hotmail.it (Fabio Marconi) Date: Sun, 17 Mar 2013 10:42:02 +0100 Subject: Announcing the Next Ubuntu Bug Day! In-Reply-To: <CALh9bZ1bjsLVXyZyyE8USfv2ZkOVnxBXb-ButQ8bN_PBtM=3ag@mail.gmail.com> References: <BLU0-SMTP787C25AC1165CE1EA30364A5EE0@phx.gbl> <CALh9bZ1bjsLVXyZyyE8USfv2ZkOVnxBXb-ButQ8bN_PBtM=3ag@mail.gmail.com> Message-ID: <BLU0-SMTP111C6D9EB727FB30D61F96CA5EF0@phx.gbl> On 17/03/2013 01:12, AG Restringere wrote: > Fabio, > > Given these two items: > - Verify the bug is still not fixed > How do you quickly verify if the problem has been fixed? > What is the process to be used? > > -Request any needed info > What is the specific log(s) and information needed? > > Best, > AG > Hallo This is one of the cases where it is not possible to reproduce quickly the issue. The first thing is to search for duplicates, or scrolling down the ubuntu-release-upgrader list <https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader> or googling for: site:bugs.launchpad.net keywordsrelative and in the case mark as duplicate, obviously if the bug is fixed in the yellow strip will appear the green written `Fix released' This particular package is used to upgrade from one release to another, so you can understand that the `launchpad' is highly customized (extra packages, proprietary drivers, personal settings, unsupported packages, ecc. ecc.). The only way that we have to reproduce the bug is to recreate the scenario of the reporter, unless it is not closely hardware related ( video, audio, devices, ecc.), in a virtual machine and run the upgrade. If the bug does not occour to you and it is reported from just one person, then the probabilty to reproduce it again are near to 0. In this case simply tell to the reporter that you are not able to reproduce the issue, ask for more detailed steps to reproduce, subscribe youself to the report and set the status of the bug to incomplete. Apport automatically attach log files, analyzing them we can have hints of what happens during the upgrade. If needed, the relative logfiles can be found on /var/log/dist-upgrade. This is an example of error in apt.log: MarkUpgrade() called on a non-upgrable pkg: 'brasero' ERROR:root:Upgrading 'brasero' failed Log time: 2013-03-15 18:58:20.835223 This is a managed error: Investigating (0) linux-image-extra-3.5.0-18-generic [ amd64 ] < 3.5.0-18.29 > ( kernel ) Broken linux-image-extra-3.5.0-18-generic:amd64 Depends on linux-image-3.5.0-18-generic [ amd64 ] < 3.5.0-18.29 > ( kernel ) Considering linux-image-3.5.0-18-generic:amd64 10001 as a solution to linux-image-extra-3.5.0-18-generic:amd64 -1 Removing linux-image-extra-3.5.0-18-generic:amd64 rather than change linux-image-3.5.0-18-generic:amd64 Done regards Fabio -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130317/9ab4ce66/attachment.html> From melchiaros at aol.com Sun Mar 17 15:08:13 2013 From: melchiaros at aol.com (melchiaros) Date: Sun, 17 Mar 2013 16:08:13 +0100 Subject: Announcing the Next Ubuntu Bug Day! In-Reply-To: <BLU0-SMTP111C6D9EB727FB30D61F96CA5EF0@phx.gbl> References: <BLU0-SMTP787C25AC1165CE1EA30364A5EE0@phx.gbl> <CALh9bZ1bjsLVXyZyyE8USfv2ZkOVnxBXb-ButQ8bN_PBtM=3ag@mail.gmail.com> <BLU0-SMTP111C6D9EB727FB30D61F96CA5EF0@phx.gbl> Message-ID: <5145DC5D.3040708@aol.com> Am 17.03.2013 10:42, schrieb Fabio Marconi: > On 17/03/2013 01:12, AG Restringere wrote: >> Fabio, >> >> Given these two items: >> - Verify the bug is still not fixed >> How do you quickly verify if the problem has been fixed? > >> What is the process to be used? >> >> -Request any needed info >> What is the specific log(s) and information needed? >> >> Best, >> AG >> > Hallo > > This is one of the cases where it is not possible to reproduce quickly > the issue. > The first thing is to search for duplicates, or scrolling down the > ubuntu-release-upgrader list > <https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader> or > googling for: site:bugs.launchpad.net keywordsrelative and in the case > mark as duplicate, obviously if the bug is fixed in the yellow strip > will appear the green written `Fix released' > This particular package is used to upgrade from one release to > another, so you can understand that the `launchpad' is highly > customized (extra packages, proprietary drivers, personal settings, > unsupported packages, ecc. ecc.). > The only way that we have to reproduce the bug is to recreate the > scenario of the reporter, unless it is not closely hardware related ( > video, audio, devices, ecc.), in a virtual machine and run the upgrade. > If the bug does not occour to you and it is reported from just one > person, then the probabilty to reproduce it again are near to 0. > In this case simply tell to the reporter that you are not able to > reproduce the issue, ask for more detailed steps to reproduce, > subscribe youself to the report and set the status of the bug to > incomplete. > Apport automatically attach log files, analyzing them we can have > hints of what happens during the upgrade. > If needed, the relative logfiles can be found on /var/log/dist-upgrade. > This is an example of error in apt.log: > > MarkUpgrade() called on a non-upgrable pkg: 'brasero' > ERROR:root:Upgrading 'brasero' failed > Log time: 2013-03-15 18:58:20.835223 > > This is a managed error: > > Investigating (0) linux-image-extra-3.5.0-18-generic [ amd64 ] < > 3.5.0-18.29 > ( kernel ) > Broken linux-image-extra-3.5.0-18-generic:amd64 Depends on > linux-image-3.5.0-18-generic [ amd64 ] < 3.5.0-18.29 > ( kernel ) > Considering linux-image-3.5.0-18-generic:amd64 10001 as a solution > to linux-image-extra-3.5.0-18-generic:amd64 -1 > Removing linux-image-extra-3.5.0-18-generic:amd64 rather than change > linux-image-3.5.0-18-generic:amd64 > Done > > regards > Fabio > > > > > > > Hi Fabio, thanks for orgasnisation. There is one point I want to discuss: You say: " In this case simply tell to the reporter that you are not able to reproduce the issue, ask for more detailed steps to reproduce, subscribe youself to the report and set the status of the bug to incomplete. " This is a bit problematic. Other projects like ubiquity(the graphical installation system) or the kernel itself has stepped beside the procedure to reproduce the problem that occure. They have good reasons for. Reproducing is often not possible. And a set to incomplete may blame the user, because s/he want to give further information, but is simply not able to because the informations are not available to the user him/herself. As far as I have observed ubiquity has changed the policy of bughandling to set the priority of the report automatically to high when the log gives enough information. The kernel bugs are set automatically to confiremd when they are reported. I think it makes sense to do some similiar here. We should set the status to confirmed if the logs provide enough information. Independed if the user gives additional informations to the problem. (you click on upgrading and it do on every part your system -> the error may be caused by a configuration/software install month or years ago). You have already provided the two cases I can get for quick also in mind. The first is the error message: " MarkUpgrade() called on a non-upgrable pkg: 'brasero' ERROR:root:Upgrading 'brasero' failed Log time: 2013-03-15 18:58:20.835223 " and the second is: Investigating (0) linux-image-extra-3.5.0-18-generic [ amd64 ] < 3.5.0-18.29 > ( kernel ) Broken linux-image-extra-3.5.0-18-generic:amd64 Depends on linux-image-3.5.0-18-generic [ amd64 ] < 3.5.0-18.29 > ( kernel ) Considering linux-image-3.5.0-18-generic:amd64 10001 as a solution to linux-image-extra-3.5.0-18-generic:amd64 -1 Removing linux-image-extra-3.5.0-18-generic:amd64 rather than change linux-image-3.5.0-18-generic:amd64 Done which I have seen more in the form that investigation number is increasing while the upgrader is trying several upgrading routes for a specific package. like investigating(0) ... invertigating(1) ... investigation(2) and so on until the upgrader gives up. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130317/1aaebd70/attachment.html> From marconifabio at hotmail.it Sun Mar 17 16:39:50 2013 From: marconifabio at hotmail.it (Fabio Marconi) Date: Sun, 17 Mar 2013 17:39:50 +0100 Subject: Announcing the Next Ubuntu Bug Day! In-Reply-To: <5145DC5D.3040708@aol.com> References: <BLU0-SMTP787C25AC1165CE1EA30364A5EE0@phx.gbl> <CALh9bZ1bjsLVXyZyyE8USfv2ZkOVnxBXb-ButQ8bN_PBtM=3ag@mail.gmail.com> <BLU0-SMTP111C6D9EB727FB30D61F96CA5EF0@phx.gbl> <5145DC5D.3040708@aol.com> Message-ID: <BLU0-SMTP2202F1E17FC98D0DA33054DA5EF0@phx.gbl> On 17/03/2013 16:08, melchiaros wrote: > Am 17.03.2013 10:42, schrieb Fabio Marconi: >> On 17/03/2013 01:12, AG Restringere wrote: >>> Fabio, >>> >>> Given these two items: >>> - Verify the bug is still not fixed >>> How do you quickly verify if the problem has been fixed? >> >>> What is the process to be used? >>> >>> -Request any needed info >>> What is the specific log(s) and information needed? >>> >>> Best, >>> AG >>> >> Hallo >> >> This is one of the cases where it is not possible to reproduce >> quickly the issue. >> The first thing is to search for duplicates, or scrolling down >> the ubuntu-release-upgrader list >> <https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader> >> or googling for: site:bugs.launchpad.net keywordsrelative and in the >> case mark as duplicate, obviously if the bug is fixed in the yellow >> strip will appear the green written `Fix released' >> This particular package is used to upgrade from one release to >> another, so you can understand that the `launchpad' is highly >> customized (extra packages, proprietary drivers, personal settings, >> unsupported packages, ecc. ecc.). >> The only way that we have to reproduce the bug is to recreate the >> scenario of the reporter, unless it is not closely hardware related ( >> video, audio, devices, ecc.), in a virtual machine and run the upgrade. >> If the bug does not occour to you and it is reported from just one >> person, then the probabilty to reproduce it again are near to 0. >> In this case simply tell to the reporter that you are not able to >> reproduce the issue, ask for more detailed steps to reproduce, >> subscribe youself to the report and set the status of the bug to >> incomplete. >> Apport automatically attach log files, analyzing them we can have >> hints of what happens during the upgrade. >> If needed, the relative logfiles can be found on /var/log/dist-upgrade. >> This is an example of error in apt.log: >> >> MarkUpgrade() called on a non-upgrable pkg: 'brasero' >> ERROR:root:Upgrading 'brasero' failed >> Log time: 2013-03-15 18:58:20.835223 >> >> This is a managed error: >> >> Investigating (0) linux-image-extra-3.5.0-18-generic [ amd64 ] < >> 3.5.0-18.29 > ( kernel ) >> Broken linux-image-extra-3.5.0-18-generic:amd64 Depends on >> linux-image-3.5.0-18-generic [ amd64 ] < 3.5.0-18.29 > ( kernel ) >> Considering linux-image-3.5.0-18-generic:amd64 10001 as a solution >> to linux-image-extra-3.5.0-18-generic:amd64 -1 >> Removing linux-image-extra-3.5.0-18-generic:amd64 rather than >> change linux-image-3.5.0-18-generic:amd64 >> Done >> >> regards >> Fabio >> >> >> >> >> >> >> > > Hi Fabio, > > thanks for orgasnisation. > > There is one point I want to discuss: > > You say: > " > In this case simply tell to the reporter that you are not able to > reproduce the issue, ask for more detailed steps to reproduce, > subscribe youself to the report and set the status of the bug to > incomplete. > " > This is a bit problematic. Other projects like ubiquity(the graphical > installation system) or the kernel itself has stepped beside the > procedure to reproduce the problem that occure. > > They have good reasons for. Reproducing is often not possible. And a > set to incomplete may blame the user, because s/he want to give > further information, but is simply not able to because the > informations are not available to the user him/herself. In the case that the log files aren't useful or not existing we need to investigate in some way, so we have to interact with the reporter to help research some trace. The incomplete status makes the bug autoexpire when no reply is done. > > As far as I have observed ubiquity has changed the policy of > bughandling to set the priority of the report automatically to high > when the log gives enough information. > The kernel bugs are set automatically to confiremd when they are reported. Yes, actually we have automated tools doing this works starting a first triage step. > > I think it makes sense to do some similiar here. > > We should set the status to confirmed if the logs provide enough > information. Independed if the user gives additional informations to > the problem. This things are depending on the degree of experience of the triager, and I'm not in accord to set the status to confirmed till the bug is not reproduced on two machine (unless very particular cases). Regards Fabio -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130317/c35c36f5/attachment.html> From brian at ubuntu.com Mon Mar 18 15:45:16 2013 From: brian at ubuntu.com (Brian Murray) Date: Mon, 18 Mar 2013 08:45:16 -0700 Subject: Announcing the Next Ubuntu Bug Day! In-Reply-To: <5145DC5D.3040708@aol.com> References: <BLU0-SMTP787C25AC1165CE1EA30364A5EE0@phx.gbl> <CALh9bZ1bjsLVXyZyyE8USfv2ZkOVnxBXb-ButQ8bN_PBtM=3ag@mail.gmail.com> <BLU0-SMTP111C6D9EB727FB30D61F96CA5EF0@phx.gbl> <5145DC5D.3040708@aol.com> Message-ID: <20130318154516.GL29575@murraytwins.com> On Sun, Mar 17, 2013 at 04:08:13PM +0100, melchiaros wrote: > Am 17.03.2013 10:42, schrieb Fabio Marconi: > >On 17/03/2013 01:12, AG Restringere wrote: > >>Fabio, > >> > >>Given these two items: > >>- Verify the bug is still not fixed > >>How do you quickly verify if the problem has been fixed? > > > >>What is the process to be used? > >> > >> -Request any needed info > >>What is the specific log(s) and information needed? > >> > >>Best, > >>AG > >> > >Hallo > > > >This is one of the cases where it is not possible to reproduce > >quickly the issue. > >The first thing is to search for duplicates, or scrolling down the > >ubuntu-release-upgrader list > ><https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader> > >or googling for: site:bugs.launchpad.net keywordsrelative and in > >the case mark as duplicate, obviously if the bug is fixed in the > >yellow strip will appear the green written `Fix released' > >This particular package is used to upgrade from one release to > >another, so you can understand that the `launchpad' is highly > >customized (extra packages, proprietary drivers, personal > >settings, unsupported packages, ecc. ecc.). > >The only way that we have to reproduce the bug is to recreate the > >scenario of the reporter, unless it is not closely hardware > >related ( video, audio, devices, ecc.), in a virtual machine and > >run the upgrade. > >If the bug does not occour to you and it is reported from just one > >person, then the probabilty to reproduce it again are near to 0. > >In this case simply tell to the reporter that you are not able to > >reproduce the issue, ask for more detailed steps to reproduce, > >subscribe youself to the report and set the status of the bug to > >incomplete. > >Apport automatically attach log files, analyzing them we can have > >hints of what happens during the upgrade. > >If needed, the relative logfiles can be found on /var/log/dist-upgrade. > >This is an example of error in apt.log: > > > >MarkUpgrade() called on a non-upgrable pkg: 'brasero' > >ERROR:root:Upgrading 'brasero' failed > >Log time: 2013-03-15 18:58:20.835223 > > > >This is a managed error: > > > >Investigating (0) linux-image-extra-3.5.0-18-generic [ amd64 ] < > >3.5.0-18.29 > ( kernel ) > >Broken linux-image-extra-3.5.0-18-generic:amd64 Depends on > >linux-image-3.5.0-18-generic [ amd64 ] < 3.5.0-18.29 > ( kernel ) > > Considering linux-image-3.5.0-18-generic:amd64 10001 as a > >solution to linux-image-extra-3.5.0-18-generic:amd64 -1 > > Removing linux-image-extra-3.5.0-18-generic:amd64 rather than > >change linux-image-3.5.0-18-generic:amd64 > >Done > > > >regards > >Fabio > > > > > > > > > > > > > > > > Hi Fabio, > > thanks for orgasnisation. > > There is one point I want to discuss: > > You say: > " > In this case simply tell to the reporter that you are not able to > reproduce the issue, ask for more detailed steps to reproduce, > subscribe youself to the report and set the status of the bug to > incomplete. > " > This is a bit problematic. Other projects like ubiquity(the > graphical installation system) or the kernel itself has stepped > beside the procedure to reproduce the problem that occure. > > They have good reasons for. Reproducing is often not possible. And a > set to incomplete may blame the user, because s/he want to give > further information, but is simply not able to because the > informations are not available to the user him/herself. > > As far as I have observed ubiquity has changed the policy of > bughandling to set the priority of the report automatically to high > when the log gives enough information. They are automatically set to High if there is a crash found in a bug reported by apport. This is done as an initial sorting method in the bugs to differentiate them from ones like http://launchpad.net/bugs/1155571. > The kernel bugs are set automatically to confiremd when they are reported. I believe this is only done if they are reported by apport and for similar reason to ubiquity. > I think it makes sense to do some similiar here. > > We should set the status to confirmed if the logs provide enough > information. Independed if the user gives additional informations to > the problem. This is changing the definition of Confirmed for this specific package which is not something I want to do. The kernel team does this due to the large volume of bug reports that they receive. -- 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: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130318/9e14ddcc/attachment.sig> From marconifabio at hotmail.it Wed Mar 20 10:53:03 2013 From: marconifabio at hotmail.it (Fabio Marconi) Date: Wed, 20 Mar 2013 11:53:03 +0100 Subject: ubuntu release upgrade hugday Message-ID: <BLU0-SMTP123711AE1E6E6B7BA69BBAAA5EA0@phx.gbl> Hallo fellows Just to remeber that today we are running for https://wiki.ubuntu.com/UbuntuBugDay/Ubuntu-release-upgrader-20130321 Tahnsk Fabio -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130320/f1db79bc/attachment.html> From melchiaros at aol.com Thu Mar 21 12:09:33 2013 From: melchiaros at aol.com (melchiaros) Date: Thu, 21 Mar 2013 13:09:33 +0100 Subject: Hugday wikipage Message-ID: <514AF87D.6010808@aol.com> o.K can someone give a explanation for me. Step by step please(I know it is an idiotic question, but...) How can I mark a bug from https://wiki.ubuntu.com/UbuntuBugDay/Ubuntu-release-upgrader-20130321 as handeled by me(just adding the name). Is it just editing the wiki page? From fitoschido at gmail.com Thu Mar 21 12:11:48 2013 From: fitoschido at gmail.com (Adolfo Jayme Barrientos) Date: Thu, 21 Mar 2013 06:11:48 -0600 Subject: Hugday wikipage In-Reply-To: <514AF87D.6010808@aol.com> References: <514AF87D.6010808@aol.com> Message-ID: <CACQJSg1srZ89gv8DvPrXxjkBdD5EUGMuQhNq5tvyPsNbEqU1fA@mail.gmail.com> Yep, just edit the page, put the green background color and your name in the table. (I think it’d be good if this process was automated…) -- Adolfo From melchiaros at aol.com Thu Mar 21 12:14:14 2013 From: melchiaros at aol.com (melchiaros) Date: Thu, 21 Mar 2013 13:14:14 +0100 Subject: Hugday wikipage In-Reply-To: <CACQJSg1srZ89gv8DvPrXxjkBdD5EUGMuQhNq5tvyPsNbEqU1fA@mail.gmail.com> References: <514AF87D.6010808@aol.com> <CACQJSg1srZ89gv8DvPrXxjkBdD5EUGMuQhNq5tvyPsNbEqU1fA@mail.gmail.com> Message-ID: <514AF996.4050401@aol.com> Am 21.03.2013 13:11, schrieb Adolfo Jayme Barrientos: > Yep, just edit the page, put the green background color and your name > in the table. (I think it’d be good if this process was automated…) > Thaks for the quick clarification. From walter.garcia at upf.edu Thu Mar 21 12:15:01 2013 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Thu, 21 Mar 2013 13:15:01 +0100 Subject: Hugday wikipage In-Reply-To: <514AF87D.6010808@aol.com> References: <514AF87D.6010808@aol.com> Message-ID: <20130321121501.GH23055@upf.edu> * melchiaros, melchiaros at aol.com [21/03/13 13:10]: > o.K can someone give a explanation for me. > > Step by step please(I know it is an idiotic question, but...) There are only idiotic answers... > How can I mark a bug from > > https://wiki.ubuntu.com/UbuntuBugDay/Ubuntu-release-upgrader-20130321 > > as handeled by me(just adding the name). > > Is it just editing the wiki page? Yes, just edit the wiki page. -- Walter Garcia-Fontes From melchiaros at aol.com Thu Mar 21 12:16:56 2013 From: melchiaros at aol.com (melchiaros) Date: Thu, 21 Mar 2013 13:16:56 +0100 Subject: Hugday wikipage In-Reply-To: <20130321121501.GH23055@upf.edu> References: <514AF87D.6010808@aol.com> <20130321121501.GH23055@upf.edu> Message-ID: <514AFA38.7060204@aol.com> Am 21.03.2013 13:15, schrieb Walter Garcia-Fontes: > * melchiaros, melchiaros at aol.com [21/03/13 13:10]: >> o.K can someone give a explanation for me. >> >> Step by step please(I know it is an idiotic question, but...) > There are only idiotic answers... > >> How can I mark a bug from >> >> https://wiki.ubuntu.com/UbuntuBugDay/Ubuntu-release-upgrader-20130321 >> >> as handeled by me(just adding the name). >> >> Is it just editing the wiki page? > Yes, just edit the wiki page. > :) Yes, the think with the idiotic answers... o.K a thank you also to you. Is there a knowledge base entry I have missed? What about the colors of the bars? From walter.garcia at upf.edu Thu Mar 21 12:24:43 2013 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Thu, 21 Mar 2013 13:24:43 +0100 Subject: Hugday wikipage In-Reply-To: <514AFA38.7060204@aol.com> References: <514AF87D.6010808@aol.com> <20130321121501.GH23055@upf.edu> <514AFA38.7060204@aol.com> Message-ID: <20130321122443.GA3298@upf.edu> * melchiaros, melchiaros at aol.com [21/03/13 13:21]: > Is there a knowledge base entry I have missed? What about the > colors of the bars? There used to be some scripts (something in the line of bug-hugday) which would do things automatically, but they broke some years ago and actually it only consists of marking the wiki to keep a track of what we are doing. We used to mark all of the green, but Fabio likes violet... -- Walter Garcia-Fontes From melchiaros at aol.com Thu Mar 21 12:25:57 2013 From: melchiaros at aol.com (melchiaros) Date: Thu, 21 Mar 2013 13:25:57 +0100 Subject: Hugday wikipage In-Reply-To: <20130321122443.GA3298@upf.edu> References: <514AF87D.6010808@aol.com> <20130321121501.GH23055@upf.edu> <514AFA38.7060204@aol.com> <20130321122443.GA3298@upf.edu> Message-ID: <514AFC55.8050708@aol.com> Am 21.03.2013 13:24, schrieb Walter Garcia-Fontes: > * melchiaros, melchiaros at aol.com [21/03/13 13:21]: >> Is there a knowledge base entry I have missed? What about the >> colors of the bars? > There used to be some scripts (something in the line of bug-hugday) > which would do things automatically, but they broke some years ago and > actually it only consists of marking the wiki to keep a track of what > we are doing. > > We used to mark all of the green, but Fabio likes violet... > Aha, that it is. Fabio like violet. I was in doubt that I have missed somethink really essential. From marconifabio at hotmail.it Thu Mar 21 16:29:48 2013 From: marconifabio at hotmail.it (Fabio Marconi) Date: Thu, 21 Mar 2013 17:29:48 +0100 Subject: Hugday wikipage In-Reply-To: <514AFC55.8050708@aol.com> References: <514AF87D.6010808@aol.com> <20130321121501.GH23055@upf.edu> <514AFA38.7060204@aol.com> <20130321122443.GA3298@upf.edu> <514AFC55.8050708@aol.com> Message-ID: <BLU0-SMTP475FC04B6CF8B5676276846A5EB0@phx.gbl> On 21/03/2013 13:25, melchiaros wrote: > Am 21.03.2013 13:24, schrieb Walter Garcia-Fontes: >> * melchiaros, melchiaros at aol.com [21/03/13 13:21]: >>> Is there a knowledge base entry I have missed? What about the >>> colors of the bars? >> There used to be some scripts (something in the line of bug-hugday) >> which would do things automatically, but they broke some years ago and >> actually it only consists of marking the wiki to keep a track of what >> we are doing. >> >> We used to mark all of the green, but Fabio likes violet... >> > Aha, that it is. > > Fabio like violet. > > I was in doubt that I have missed somethink really essential. > LOL. I'm going to see if we can use again hugday tool -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130321/6983e542/attachment.html> From es20490446e at gmail.com Thu Mar 21 23:12:07 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Fri, 22 Mar 2013 00:12:07 +0100 Subject: Hugday wikipage In-Reply-To: <514AFC55.8050708@aol.com> References: <514AF87D.6010808@aol.com> <20130321121501.GH23055@upf.edu> <514AFA38.7060204@aol.com> <20130321122443.GA3298@upf.edu> <514AFC55.8050708@aol.com> Message-ID: <514B93C7.6090708@gmail.com> An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130322/e53bc808/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130322/e53bc808/attachment.bin> From es20490446e at gmail.com Fri Mar 22 04:52:36 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Fri, 22 Mar 2013 05:52:36 +0100 Subject: Application for joining Ubuntu BugControl In-Reply-To: <2061598.D0So4SbAHO@xango3> References: <CAB7xcUmPQR2OzJmfg=c0W5cgQ_Z6-euWrGLSftSZNxsseM8szQ@mail.gmail.com> <CAB7xcUkKduLAvgRx2ct3ayoP3OroJsTOVY2hWx8tmWzCVRJzYw@mail.gmail.com> <50EB5BFE.7060704@gmail.com> <2061598.D0So4SbAHO@xango3> Message-ID: <514BE394.5040708@gmail.com> An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130322/23553625/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130322/23553625/attachment.bin> From melchiaros at aol.com Fri Mar 22 10:44:23 2013 From: melchiaros at aol.com (melchiaros) Date: Fri, 22 Mar 2013 11:44:23 +0100 Subject: What we have learned so far on ubuntu-release upgrader hugday Message-ID: <514C3607.1010506@aol.com> We have done the hugday on ubuntu-release-upgrader yesterday and there are still tickets open, especially for the triaging step -> so you can still come up, e.g with recreation with apt-clone.tar.gz in a VM: http://linuxundich.de/de/ubuntu/mit-apt-clone-die-installation-eines-rechners-auf-andere-ubertragen/ (Sorry, the website is written in german; please use e.g chromium translation popup on entering the website) ). The question arises: What we have seen from the bunch of reports there so far? I start this with one of my observations. A good part of the problems are caused by ppa's that users have nincorporated in their system. Especially the logs shown often to me xorg problems. They have ppa's integrated that provides xorg components for resolving their graphical problems that they have with xorg from the main repositorie. So far we could not say that they do nonsense to their system. Dysfunctional graphics are good reasons for incroporationg not official software. The problem is that the ubuntu-release-upgrader is able to disable ppa's from source.list, but not able to handle the xorg move back to main with success. This makes the upgrade process failing. Is the user the problem? Likely not. I have seen a comment from Sampo555 that points to the policy to deactivate xorg ppa's before upgrading(thank you that you give the people a workarround Sampo). Let us switch for the moment the perspective to that of a user(not anymore a newbie, but also not down to the shoulders in Ubuntu). -> S/he could not see that policy from the front of the computer. The only thing what they see is that without ppa the graphic is a mess. I have read cases on Ubuntu question section where the graphical system was completely not useable. It would affect a good part of the release upgrade problems (may be arround 20%-30%- just a guess on what I have seen in the logs) when it would be possible to teach ubuntu-release-upgrader to handle this. What do you think about? greetings melchiaros From es20490446e at gmail.com Fri Mar 22 11:55:00 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Fri, 22 Mar 2013 12:55:00 +0100 Subject: What we have learned so far on ubuntu-release upgrader hugday In-Reply-To: <514C3607.1010506@aol.com> References: <514C3607.1010506@aol.com> Message-ID: <514C4694.6080406@gmail.com> An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130322/e0d95e3c/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130322/e0d95e3c/attachment.bin> From brian at ubuntu.com Fri Mar 22 15:08:32 2013 From: brian at ubuntu.com (Brian Murray) Date: Fri, 22 Mar 2013 08:08:32 -0700 Subject: What we have learned so far on ubuntu-release upgrader hugday In-Reply-To: <514C4694.6080406@gmail.com> References: <514C3607.1010506@aol.com> <514C4694.6080406@gmail.com> Message-ID: <20130322150832.GY29575@murraytwins.com> On Fri, Mar 22, 2013 at 12:55:00PM +0100, Alberto Salvia Novella wrote: > I thought this myself, since I found that most of the bugs I have triaged > myself were caused by this. On the other hand, I think other things we can > possible learn are: > > > - Confirmed bugs are less likely to be triaged, since are intended to > Ubuntu BugControl members. Perhaps automatically allowing some kinds off > users to access triaging bug controls will be a good idea, also because > most bugs are never assigned priority. > > - Although I think the bug day is a good idea, we were only four users > participating on it. This warns me the Ubuntu community isn't so active. I > also study computer engineering, and I saw many people stopping using > Ubuntu in favour of Windows since they perceived Ubuntu as unstable and not > compromised with freedom. Improving bug handling an incursion of new users > in it seems to be a high priority, perhaps also giving the users the > opportunity of not sowing non free applications in the software center and > deeply explaining why Canonical chose to include them in the system. > > - Many users weren't using the ubuntu-bug command to report bugs. Perhaps > it should be clearly stated in some visible place that manually reporting > bugs in Launchpad is for when is impossible to use this command. This is done by having the "Report a Bug" pages in Launchpad redirect to the wiki page at https://help.ubuntu.com/community/ReportingBugs. Additionally, in most cases the ubuntu-release-upgrader should help you file a bug report (using apport) or by telling you to use 'ubuntu-bug ubuntu-release-upgrader'. > - Editing the wiki took many of time used in the Bug Day, so perhaps > creating good automated tools for it will increase noticeably the quantity > of bugs that can be handled. I'm looking into the hugday tool and from what I can tell so far there is an authentication issue, for me at least, when trying to close bug reports. I'd welcome any help with this though. > - In the incomplete bugs section, some of them needed to be converted to > question. I think this action should be contemplated as valid to mark the > bug off, perhaps also in other sections. Yes, if the bug report is clearly not a bug report and more of a support question then converting the bug to a question is a valid action. Do you have some examples of those? > - The progress section shows nothing, so perhaps it can be removed. I believe that issue is specific to the ubuntu-release-upgrader package and is my fault, sorry about that! -- Brian Murray Ubuntu Bug Master From melchiaros at aol.com Fri Mar 22 15:45:20 2013 From: melchiaros at aol.com (melchiaros) Date: Fri, 22 Mar 2013 16:45:20 +0100 Subject: What we have learned so far on ubuntu-release upgrader hugday In-Reply-To: <20130322150832.GY29575@murraytwins.com> References: <514C3607.1010506@aol.com> <514C4694.6080406@gmail.com> <20130322150832.GY29575@murraytwins.com> Message-ID: <514C7C90.6090403@aol.com> Am 22.03.2013 16:08, schrieb Brian Murray: > On Fri, Mar 22, 2013 at 12:55:00PM +0100, Alberto Salvia Novella wrote: >> I thought this myself, since I found that most of the bugs I have triaged >> myself were caused by this. On the other hand, I think other things we can >> possible learn are: >> >> >> - Confirmed bugs are less likely to be triaged, since are intended to >> Ubuntu BugControl members. Perhaps automatically allowing some kinds off >> users to access triaging bug controls will be a good idea, also because >> most bugs are never assigned priority. >> >> - Although I think the bug day is a good idea, we were only four users >> participating on it. This warns me the Ubuntu community isn't so active. I >> also study computer engineering, and I saw many people stopping using >> Ubuntu in favour of Windows since they perceived Ubuntu as unstable and not >> compromised with freedom. Improving bug handling an incursion of new users >> in it seems to be a high priority, perhaps also giving the users the >> opportunity of not sowing non free applications in the software center and >> deeply explaining why Canonical chose to include them in the system. >> >> - Many users weren't using the ubuntu-bug command to report bugs. Perhaps >> it should be clearly stated in some visible place that manually reporting >> bugs in Launchpad is for when is impossible to use this command. > This is done by having the "Report a Bug" pages in Launchpad redirect to > the wiki page at https://help.ubuntu.com/community/ReportingBugs. > Additionally, in most cases the ubuntu-release-upgrader should help you > file a bug report (using apport) or by telling you to use 'ubuntu-bug > ubuntu-release-upgrader'. > >> - Editing the wiki took many of time used in the Bug Day, so perhaps >> creating good automated tools for it will increase noticeably the quantity >> of bugs that can be handled. > I'm looking into the hugday tool and from what I can tell so far there > is an authentication issue, for me at least, when trying to close bug > reports. I'd welcome any help with this though. > >> - In the incomplete bugs section, some of them needed to be converted to >> question. I think this action should be contemplated as valid to mark the >> bug off, perhaps also in other sections. > Yes, if the bug report is clearly not a bug report and more of a support > question then converting the bug to a question is a valid action. Do > you have some examples of those? > >> - The progress section shows nothing, so perhaps it can be removed. > I believe that issue is specific to the ubuntu-release-upgrader package > and is my fault, sorry about that! > > -- > Brian Murray > Ubuntu Bug Master > Sorry Alberto, my Spam-Filter is a bit overmotivated. I have just seen your mesasage in parts through Brians mail. Your point on the gab between confirmed and triaged is quite correct. In principle everybody on launchpad can do what BugSquad people do with or without membership. I would transform your proposal a bit. In moment the BugControl has a hugh access barrier. The people are forced to present them to someone(well properly also Brian) and ask for permission. This is o.K. But also the other way arround may be accessible. For sure there are people outside that fullfill(also a properly) the requirements for joining BugControl. You see them again and again and over long time. It is also a way to just invite them for a less formal join. The difference is the invitation, and who is not lucky to be invited. Your second point Alberto is going into the wide. Ubuntu v.s. Windows and Canonical monetary approaches.... This is to much for what I have whant here. But one point is absolutely correct. On this one single time event hughday, the activity is very low. Only four people is much to less. I just whant keep this as observation. The hughday-tools may be one cause. Also may be, we should have given a special workflow for handling such bugs(like apt-clone usage). To the third point is to say. It seems to be especially the long year linuxer that try to report without apport. I have some time looked into the launchpad profiles, when I hit such a report. May be the explanation is that they have done so in past and just are willing to do in futhur:) I think a redirect is quite o.K. It is not o.K to force someone to much, even if that makes it easier to us. The consequences for them a much more impressive. A missing raring tag will not show their report for the actual development. Or when we see this they have also extra work. Or .. you know. To resume: I think we may have now tree points: -the ubuntu-release-upgrader behaviour on xorg -the gab between confirmed and triaged -the non working hughday-tools @Brian Fabio has also written to look at the tools in one of the hugday mails on the list(AFAIR). So there is the first on helping out. From es20490446e at gmail.com Fri Mar 22 17:19:58 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Fri, 22 Mar 2013 18:19:58 +0100 Subject: What we have learned so far on ubuntu-release upgrader hugday In-Reply-To: <20130322150832.GY29575@murraytwins.com> References: <514C3607.1010506@aol.com> <514C4694.6080406@gmail.com> <20130322150832.GY29575@murraytwins.com> Message-ID: <514C92BE.40507@gmail.com> An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130322/6a7d8e01/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130322/6a7d8e01/attachment.bin> From brian at ubuntu.com Fri Mar 22 17:31:08 2013 From: brian at ubuntu.com (Brian Murray) Date: Fri, 22 Mar 2013 10:31:08 -0700 Subject: What we have learned so far on ubuntu-release upgrader hugday In-Reply-To: <514C4694.6080406@gmail.com> References: <514C3607.1010506@aol.com> <514C4694.6080406@gmail.com> Message-ID: <20130322173108.GA29575@murraytwins.com> On Fri, Mar 22, 2013 at 12:55:00PM +0100, Alberto Salvia Novella wrote: > I thought this myself, since I found that most of the bugs I have triaged > myself were caused by this. On the other hand, I think other things we can > possible learn are: > > > - Confirmed bugs are less likely to be triaged, since are intended to > Ubuntu BugControl members. Perhaps automatically allowing some kinds off > users to access triaging bug controls will be a good idea, also because > most bugs are never assigned priority. I'm looking at the Confirmed bug reports now and remembered that bug reports get automatically set to Confirmed if someone clicks the 'this bug affects me' link. So while somebody else has experienced the bug, see http://launchpad.net/bugs/1091317, that doesn't make it a useful one yet. So the Confirmed ones should not always been intended for Bug Control members. -- Brian Murray Ubuntu Bug Master From es20490446e at gmail.com Fri Mar 22 17:38:10 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Fri, 22 Mar 2013 18:38:10 +0100 Subject: What we have learned so far on ubuntu-release upgrader hugday In-Reply-To: <20130322173108.GA29575@murraytwins.com> References: <514C3607.1010506@aol.com> <514C4694.6080406@gmail.com> <20130322173108.GA29575@murraytwins.com> Message-ID: <514C9702.4020201@gmail.com> Oh, that's right. El 22/03/13 18:31, Brian Murray escribió: > On Fri, Mar 22, 2013 at 12:55:00PM +0100, Alberto Salvia Novella wrote: >> I thought this myself, since I found that most of the bugs I have triaged >> myself were caused by this. On the other hand, I think other things we can >> possible learn are: >> >> >> - Confirmed bugs are less likely to be triaged, since are intended to >> Ubuntu BugControl members. Perhaps automatically allowing some kinds off >> users to access triaging bug controls will be a good idea, also because >> most bugs are never assigned priority. > I'm looking at the Confirmed bug reports now and remembered that bug > reports get automatically set to Confirmed if someone clicks the 'this > bug affects me' link. So while somebody else has experienced the bug, > see http://launchpad.net/bugs/1091317, that doesn't make it a useful one > yet. > > So the Confirmed ones should not always been intended for Bug Control > members. > > -- > Brian Murray > Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130322/f00af673/attachment.bin> From walter.garcia at upf.edu Sat Mar 23 10:54:22 2013 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Sat, 23 Mar 2013 11:54:22 +0100 Subject: Bugs filed against "linux" that could be filed against "ubuntu-release-upgrader" Message-ID: <20130323105422.GA2829@upf.edu> While reviewing bugs against the upgrader I've noticed some bugs against "linux" that could be upgrader bugs, maybe they could be dupped and managed all together. Please take a look at the following: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1150232 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1110390 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1099848 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090548 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1089138 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1086403 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090548 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1089138 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1086403 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1079846 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071524 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068845 -- Walter Garcia-Fontes From marconifabio at hotmail.it Sun Mar 24 17:46:21 2013 From: marconifabio at hotmail.it (Fabio Marconi) Date: Sun, 24 Mar 2013 18:46:21 +0100 Subject: Hugday Announcement . Message-ID: <BLU0-SMTP283D52E4AA5CFD9F830BB6CA5D60@phx.gbl> Announcing the Next Ubuntu Bug Day! - <<<28 March 2013>>> Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* <<<update-manager>>>! * # 49 New Bugs New bugs need a hug * # 3 Incomplete Bugs Incomplete bugs need a status check * # 8 Confirmed Bugs Confirmed bugs need a review And never seen it before in the world, '''Oh! Grannies !!!''' , 33 bugs that needs to be verified if they still alive... <<<Update manager is an `higly infested' package, meaning that seems that everythings going wrong during an update is caused by this package, but obviously this is not the thruth. It is blamed from 10 to 15 reports at day, so every little help is really appreciated.>>> Bookmark it, add it to your calendars, turn over those egg-timers! * 28 March 2013 * http://wiki.ubuntu.com/UbuntuBugDay/20130328 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! 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, njin [From the BugSquad] From noreply at ubuntu.com Sun Mar 24 17:10:53 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 24 Mar 2013 17:10:53 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_fabiomarconi?= Message-ID: <20130324171053.31225.59082@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Events" page has been changed by fabiomarconi: http://wiki.ubuntu.com/Bugs/Events?action=diff&rev1=266&rev2=267 || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/20130328| update-manager]]|| hugday-20130328 || || [[UbuntuBugDay/Ubuntu-release-upgrader-20130321| ubuntu-release-upgrader]]|| hugday-20130321|| || [[UbuntuBugDay/20130214| Totem]]|| hugday-20130214 || || [[UbuntuBugDay/20130117| Transmission]]|| hugday-20130117 || From matt.hoy at gmail.com Sun Mar 24 22:55:32 2013 From: matt.hoy at gmail.com (Matt Hoy) Date: Sun, 24 Mar 2013 22:55:32 +0000 Subject: UNSUBSCRIBE In-Reply-To: <BLU0-SMTP283D52E4AA5CFD9F830BB6CA5D60@phx.gbl> References: <BLU0-SMTP283D52E4AA5CFD9F830BB6CA5D60@phx.gbl> Message-ID: <020C2D75-7367-4E87-8AF2-072108986061@gmail.com> STOP On 24 Mar 2013, at 17:46, Fabio Marconi <marconifabio at hotmail.it> wrote: > Announcing the Next Ubuntu Bug Day! - <<<28 March 2013>>> > > Fellow Ubuntu Triagers! > > This week's Bug Day target is *drum roll please* <<<update-manager>>>! > * # 49 New Bugs New bugs need a hug > * # 3 Incomplete Bugs Incomplete bugs need a status check > * # 8 Confirmed Bugs Confirmed bugs need a review > > And never seen it before in the world, '''Oh! Grannies !!!''' , 33 bugs that needs to be verified if they still alive... > > <<<Update manager is an `higly infested' package, meaning that seems that everythings going wrong during an update > is caused by this package, but obviously this is not the thruth. It is blamed from 10 to 15 reports at day, > so every little help is really appreciated.>>> > > Bookmark it, add it to your calendars, turn over those egg-timers! > * 28 March 2013 > * http://wiki.ubuntu.com/UbuntuBugDay/20130328 > > 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! > > 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, > njin > [From the BugSquad] > > > -- > ubuntu-devel-announce mailing list > ubuntu-devel-announce at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce From brian at ubuntu.com Tue Mar 26 15:41:29 2013 From: brian at ubuntu.com (Brian Murray) Date: Tue, 26 Mar 2013 08:41:29 -0700 Subject: Bugs filed against "linux" that could be filed against "ubuntu-release-upgrader" In-Reply-To: <20130323105422.GA2829@upf.edu> References: <20130323105422.GA2829@upf.edu> Message-ID: <20130326154128.GI29575@murraytwins.com> On Sat, Mar 23, 2013 at 11:54:22AM +0100, Walter Garcia-Fontes wrote: > While reviewing bugs against the upgrader I've noticed some bugs > against "linux" that could be upgrader bugs, maybe they could be > dupped and managed all together. Please take a look at the > following: Thanks for bringing these bugs up, let's have a look at them individually. > https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1150232 This one really is a dpkg bug. > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1110390 This one appears to be an issue with update-initramfs or grub as you can see in DpkgTerminalLog.txt. Looking at the description again they are trying to update the kernel when running a Live CD. You can tell it is a live CD from the LiveMediaBuild and ProcKernelCmdLine parts. There have been issues with this process in the past and another bug may have appeared. > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1099848 I'm not sure what the issue here as the DpkgTerminalLog isn't rendering properly but this is not a duplicate of 1090548 so I unmarked it as a duplicate. > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090548 This appears to be a syntax error in the reporter's /etc/default/grub. '/usr/sbin/grub-mkconfig: 26: /etc/default/grub: Syntax error: newline unexpected'. > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1079846 > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071524 > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1089138 These are correctly marked as a duplicates. > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1086403 This also looks like misconfigured grub files: /etc/grub.d/41_custom: 8: /etc/grub.d/41_custom: EOF: not found > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068845 I don't believe this is an upgrader bug, unless the wrong kernel was chosen. I'll look into that one though. I'm not certain what lead you to believe that these were the same bug but not many of them are and most should be treated as individual bugs. Having said that, this specific error message does appear in a few of the bugs: Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.5.0-19-generic.postinst line 1010. However, this is non-specific and you need to look the error messages before that to determine what failed. The release upgrader has code written to determine whether or not the bug is with the upgrader or with a specific package and then files the bug in the appropriate place. It usually does the right thing. Thanks again for bringing these up for discussion, I hope this information is helpful. -- Brian Murray Ubuntu Bug Master From walter.garcia at upf.edu Tue Mar 26 16:03:38 2013 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Tue, 26 Mar 2013 17:03:38 +0100 Subject: Bugs filed against "linux" that could be filed against "ubuntu-release-upgrader" In-Reply-To: <20130326154128.GI29575@murraytwins.com> References: <20130323105422.GA2829@upf.edu> <20130326154128.GI29575@murraytwins.com> Message-ID: <20130326160338.GC11009@upf.edu> * Brian Murray, brian at ubuntu.com [26/03/13 16:47]: > bug is with the upgrader or with a specific package and then files the > bug in the appropriate place. It usually does the right thing. > > Thanks again for bringing these up for discussion, I hope this > information is helpful. > Thanks, indeed, very helpful at least for me. -- Walter Garcia-Fontes From maarten.bezemer at gmail.com Wed Mar 27 10:13:47 2013 From: maarten.bezemer at gmail.com (Maarten Bezemer) Date: Wed, 27 Mar 2013 11:13:47 +0100 Subject: Bugs filed against "linux" that could be filed against "ubuntu-release-upgrader" In-Reply-To: <20130326154128.GI29575@murraytwins.com> References: <20130323105422.GA2829@upf.edu> <20130326154128.GI29575@murraytwins.com> Message-ID: <2106069.VvUkp4EMGO@bzr> On Tuesday 26 March 2013 08:41:29 Brian Murray wrote: > Thanks again for bringing these up for discussion, I hope this > information is helpful. Thanks for extensively discussing these reports, it is nice to have examples for beginning triagers! Regards, Maarten From brian at ubuntu.com Wed Mar 27 14:32:52 2013 From: brian at ubuntu.com (Brian Murray) Date: Wed, 27 Mar 2013 07:32:52 -0700 Subject: Bugs filed against "linux" that could be filed against "ubuntu-release-upgrader" In-Reply-To: <2106069.VvUkp4EMGO@bzr> References: <20130323105422.GA2829@upf.edu> <20130326154128.GI29575@murraytwins.com> <2106069.VvUkp4EMGO@bzr> Message-ID: <20130327143252.GM29575@murraytwins.com> On Wed, Mar 27, 2013 at 11:13:47AM +0100, Maarten Bezemer wrote: > On Tuesday 26 March 2013 08:41:29 Brian Murray wrote: > > Thanks again for bringing these up for discussion, I hope this > > information is helpful. > > Thanks for extensively discussing these reports, it is nice to have > examples for beginning triagers! Great! I'm happy to answer any other questions that anyone has. -- 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: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130327/de499473/attachment.sig> From marconifabio at hotmail.it Wed Mar 27 17:55:04 2013 From: marconifabio at hotmail.it (Fabio Marconi) Date: Wed, 27 Mar 2013 18:55:04 +0100 Subject: Hugday remember Message-ID: <BLU0-SMTP83E5A52B705BB19DC19F69A5D10@phx.gbl> Hallo friends This mine just to remember that tomorrow we have the great opportunity to contribute to our fantastic worldtriaging one of the essential package, update-manager. http://wiki.ubuntu.com/UbuntuBugDay/20130328 Feel free to ask for any doubt or help, here in list or on the IRC channel on Freenode #ubuntu-bugs, we love to share knowledge. My best greetings. njin -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130327/0c1fc6d4/attachment.html> From es20490446e at gmail.com Fri Mar 29 12:15:39 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Fri, 29 Mar 2013 13:15:39 +0100 Subject: Please, confirm these bugs Message-ID: <515585EB.2080106@gmail.com> An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130329/64cb12ac/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130329/64cb12ac/attachment.bin> From brian at ubuntu.com Fri Mar 29 17:22:26 2013 From: brian at ubuntu.com (Brian Murray) Date: Fri, 29 Mar 2013 10:22:26 -0700 Subject: Recent Bug Days Message-ID: <20130329172226.GB29575@murraytwins.com> I believe I've reviewed all the work done for the bug days regarding update-manager and ubuntu-release-upgrader. In some cases I added additional information to the bug reports which may provide some guidance on how to triage bug reports about these packages better. Thanks for having a look at both of these packages, I found a few interesting bugs to work on! -- Brian Murray Ubuntu Bug Master From brian at ubuntu.com Fri Mar 29 21:39:20 2013 From: brian at ubuntu.com (Brian Murray) Date: Fri, 29 Mar 2013 14:39:20 -0700 Subject: What we have learned so far on ubuntu-release upgrader hugday In-Reply-To: <514C7C90.6090403@aol.com> References: <514C3607.1010506@aol.com> <514C4694.6080406@gmail.com> <20130322150832.GY29575@murraytwins.com> <514C7C90.6090403@aol.com> Message-ID: <20130329213919.GC29575@murraytwins.com> On Fri, Mar 22, 2013 at 04:45:20PM +0100, melchiaros wrote: > Am 22.03.2013 16:08, schrieb Brian Murray: > >On Fri, Mar 22, 2013 at 12:55:00PM +0100, Alberto Salvia Novella wrote: > >>I thought this myself, since I found that most of the bugs I have triaged > >>myself were caused by this. On the other hand, I think other things we can > >>possible learn are: > >> > >> > >> - Confirmed bugs are less likely to be triaged, since are intended to > >> Ubuntu BugControl members. Perhaps automatically allowing some kinds off > >> users to access triaging bug controls will be a good idea, also because > >> most bugs are never assigned priority. > >> > >> - Although I think the bug day is a good idea, we were only four users > >> participating on it. This warns me the Ubuntu community isn't so active. I > >> also study computer engineering, and I saw many people stopping using > >> Ubuntu in favour of Windows since they perceived Ubuntu as unstable and not > >> compromised with freedom. Improving bug handling an incursion of new users > >> in it seems to be a high priority, perhaps also giving the users the > >> opportunity of not sowing non free applications in the software center and > >> deeply explaining why Canonical chose to include them in the system. > >> > >> - Many users weren't using the ubuntu-bug command to report bugs. Perhaps > >> it should be clearly stated in some visible place that manually reporting > >> bugs in Launchpad is for when is impossible to use this command. > >This is done by having the "Report a Bug" pages in Launchpad redirect to > >the wiki page at https://help.ubuntu.com/community/ReportingBugs. > >Additionally, in most cases the ubuntu-release-upgrader should help you > >file a bug report (using apport) or by telling you to use 'ubuntu-bug > >ubuntu-release-upgrader'. > > > >> - Editing the wiki took many of time used in the Bug Day, so perhaps > >> creating good automated tools for it will increase noticeably the quantity > >> of bugs that can be handled. > >I'm looking into the hugday tool and from what I can tell so far there > >is an authentication issue, for me at least, when trying to close bug > >reports. I'd welcome any help with this though. > > > >> - In the incomplete bugs section, some of them needed to be converted to > >> question. I think this action should be contemplated as valid to mark the > >> bug off, perhaps also in other sections. > >Yes, if the bug report is clearly not a bug report and more of a support > >question then converting the bug to a question is a valid action. Do > >you have some examples of those? > > > >> - The progress section shows nothing, so perhaps it can be removed. > >I believe that issue is specific to the ubuntu-release-upgrader package > >and is my fault, sorry about that! > > > >-- > >Brian Murray > >Ubuntu Bug Master > > > Sorry Alberto, my Spam-Filter is a bit overmotivated. I have just > seen your mesasage in parts through Brians mail. > > Your point on the gab between confirmed and triaged is quite > correct. In principle everybody on launchpad can do what BugSquad > people do with or without membership. > > I would transform your proposal a bit. In moment the BugControl has > a hugh access barrier. The people are forced to present them to > someone(well properly also Brian) and ask for permission. This is > o.K. But also the other way arround may be accessible. For sure > there are people outside that fullfill(also a properly) the > requirements for joining BugControl. You see them again and again > and over long time. It is also a way to just invite them for a less > formal join. The difference is the invitation, and who is not lucky > to be invited. > > Your second point Alberto is going into the wide. Ubuntu v.s. > Windows and Canonical monetary approaches.... This is to much for > what I have whant here. But one point is absolutely correct. On this > one single time event hughday, the activity is very low. Only four > people is much to less. I just whant keep this as observation. The > hughday-tools may be one cause. Also may be, we should have given a > special workflow for handling such bugs(like apt-clone usage). > > To the third point is to say. It seems to be especially the long > year linuxer that try to report without apport. I have some time > looked into the launchpad profiles, when I hit such a report. > > May be the explanation is that they have done so in past and just > are willing to do in futhur:) > > I think a redirect is quite o.K. It is not o.K to force someone to > much, even if that makes it easier to us. The consequences for them > a much more impressive. A missing raring tag will not show their > report for the actual development. Or when we see this they have > also extra work. Or .. you know. > > To resume: > > I think we may have now tree points: > > -the ubuntu-release-upgrader behaviour on xorg > -the gab between confirmed and triaged > -the non working hughday-tools > > @Brian > > Fabio has also written to look at the tools in one of the hugday > mails on the list(AFAIR). So there is the first on helping out. I now have it working for me, I'll send a separate e-mail with the details. -- 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: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130329/f7c35a1a/attachment.sig> From brian at ubuntu.com Fri Mar 29 21:49:06 2013 From: brian at ubuntu.com (Brian Murray) Date: Fri, 29 Mar 2013 14:49:06 -0700 Subject: Hug Day Tool Message-ID: <20130329214906.GD29575@murraytwins.com> I dug into http://launchpad.net/bugs/801288 some more today and believe I found and fixed one bug in the code, but there was one other thing that was preventing it from working for me. I had an outdated moin_id set in my ~/.hugday_config file. I manually changed it to the cookie named MOIN_SESSION_80_ROOT for wiki.ubuntu.com in Firefox using a cookie editor extension. If you haven't used hugday before this should not be an issue for you. Please let me know if you have any issues with it. Thanks, -- Brian Murray Ubuntu Bug Master From alihasanghauri at hotmail.com Fri Mar 29 12:53:42 2013 From: alihasanghauri at hotmail.com (ali hasan ghauri) Date: Fri, 29 Mar 2013 17:53:42 +0500 Subject: Critical Bug on Ubuntu.com Message-ID: <BAY002-W1325CF560D276D292345594DED30@phx.gbl> Hello Sir , I am Ali Hasan Ghauri , I found Vulnerability on ubuntu.com . kindly fix this Vulnerability as soon as possible . Here is Information About Vulnerability : POC : http://brainstorm.ubuntu.com/openofficeorg-writer/ideas_in_preparation/invalid/5%27%22--%3E%3C/style%3E%3C/script%3E%3Cscript%3Ealert%28%22XSS%20By%20Ghauri%22%29%3C/script%3E Vulnerability Type : Cross Site Scripting (XSS) Bug Type : Critical Bug OS : Check this Vulnerability on any Operating System But i have Windows 8 . Platform : Check this Vulnerability on Mozilla Firefox or Opera Browser . I hope You will Fix this Bug and pay me for this reported bug as a reward very soon . Thanks ! Ali Hasan Ghauri , AHPT -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130329/8310c0fb/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: brainstorm.ubuntu.PNG Type: image/png Size: 648903 bytes Desc: not available URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130329/8310c0fb/attachment.png> From teward at ubuntu.com Fri Mar 29 23:45:43 2013 From: teward at ubuntu.com (Thomas Ward) Date: Fri, 29 Mar 2013 19:45:43 -0400 Subject: Critical Bug on Ubuntu.com In-Reply-To: <BAY002-W1325CF560D276D292345594DED30@phx.gbl> References: <BAY002-W1325CF560D276D292345594DED30@phx.gbl> Message-ID: <CAGxLJ_Y+KH=r497g2Xgkoig6nmUgAWZF8goUEYDcvK+EyrM9Kg@mail.gmail.com> What did you do while on the site to run into this? As it stands, the brainstorm site is running perfectly, on Windows, Ubuntu Linux, and a RHEL system I have here, with zero XSS related things. ------ Thomas Ward Ubuntu BugSquad Member On Fri, Mar 29, 2013 at 8:53 AM, ali hasan ghauri < alihasanghauri at hotmail.com> wrote: > Hello Sir , > > I am Ali Hasan Ghauri , I found Vulnerability on ubuntu.com . kindly fix > this Vulnerability as soon as possible . > > Here is Information About Vulnerability : > > POC : > http://brainstorm.ubuntu.com/openofficeorg-writer/ideas_in_preparation/invalid/5%27%22--%3E%3C/style%3E%3C/script%3E%3Cscript%3Ealert%28%22XSS%20By%20Ghauri%22%29%3C/script%3E > > Vulnerability Type : Cross Site Scripting (XSS) > Bug Type : Critical Bug > OS : Check this Vulnerability on any Operating System But i have Windows 8 > . > Platform : Check this Vulnerability on Mozilla Firefox or Opera Browser . > > I hope You will Fix this Bug and pay me for this reported bug as a reward > very soon . > > Thanks ! > > Ali Hasan Ghauri <http://alihassanpenetrationtester.blogspot.com/> , > AHPT <http://alihassanpenetrationtester.blogspot.com/> > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130329/254a71a0/attachment.html> From brian at ubuntu.com Sat Mar 30 00:09:26 2013 From: brian at ubuntu.com (Brian Murray) Date: Fri, 29 Mar 2013 17:09:26 -0700 Subject: Critical Bug on Ubuntu.com In-Reply-To: <CAGxLJ_Y+KH=r497g2Xgkoig6nmUgAWZF8goUEYDcvK+EyrM9Kg@mail.gmail.com> References: <BAY002-W1325CF560D276D292345594DED30@phx.gbl> <CAGxLJ_Y+KH=r497g2Xgkoig6nmUgAWZF8goUEYDcvK+EyrM9Kg@mail.gmail.com> Message-ID: <20130330000926.GF29575@murraytwins.com> On Fri, Mar 29, 2013 at 07:45:43PM -0400, Thomas Ward wrote: > What did you do while on the site to run into this? As it stands, the > brainstorm site is running perfectly, on Windows, Ubuntu Linux, and a RHEL > system I have here, with zero XSS related things. A bug has been opened for this and patch has already landed for it. -- 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: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20130329/8569bef9/attachment.sig>