From om26er at ubuntu.com Tue Jan 1 17:21:41 2013 From: om26er at ubuntu.com (Omer Akram) Date: Tue, 1 Jan 2013 22:21:41 +0500 Subject: Low bug triage activity all around Message-ID: Hey all, I have been involved in bug triage for a while in Ubuntu and it seems this scene is not that active it used to be although alot of great folks from our community are highly devoted. I am not sure about the reason behind that but one thing I am sure is that previously we had running efforts like "Bug Days" where a certain package was selected and all of the Ubuntu Bug Squad was invited to participate in triaging those bugs. Another reason which could be related is that now there is no one in the Ubuntu desktop team (or Canonical) to lead the effort of Bug management and community involvement previously Pedro played a big role there. So I think we need to think of some ways to improve the situation and get more people involved into this effort. Does anyone have suggestions/comments about this matter. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From ubuntu at treblig.org Tue Jan 1 17:46:22 2013 From: ubuntu at treblig.org (Dr. David Alan Gilbert) Date: Tue, 1 Jan 2013 17:46:22 +0000 Subject: Low bug triage activity all around In-Reply-To: References: Message-ID: <20130101174622.GA22665@gallifrey> * Omer Akram (om26er at ubuntu.com) wrote: > Hey all, > > I have been involved in bug triage for a while in Ubuntu and it seems this > scene is not that active it used to be although alot of great folks from > our community are highly devoted. > > I am not sure about the reason behind that but one thing I am sure is that > previously we had running efforts like "Bug Days" where a certain package > was selected and all of the Ubuntu Bug Squad was invited to participate in > triaging those bugs. > > Another reason which could be related is that now there is no one in the > Ubuntu desktop team (or Canonical) to lead the effort of Bug management and > community involvement previously Pedro played a big role there. > > So I think we need to think of some ways to improve the situation and get > more people involved into this effort. Does anyone have > suggestions/comments about this matter. Most of the irc seems to have been pretty dead over xmas, I'm guessing there aren't many of us doing it just for the heck of it at the moment. There is also the danger that perhaps some of the others got a life and we aren't getting new ones in. I've been trying to fix things like universe packages that seg at startup; but with Debian in freeze it's nigh on impossible to get any fix into debian unless it also breaks Debian which for a lot of our Fortify triggered bugs they don't; and for a non-debian dev it's also hard going. There are also a heck of a lot of unreviewed patches in the system; so perhaps it's time for another round of patch triaging. I don't know what the numbers are, but I think the lack of an 'alpha' for Raring (as opposed to the dailies) makes me think there are less people trying it; there certainly doesn't seem to be much activity on +1. I'm also seeing signs there are a few of the regulars who've tried Raring on their machine and find it's failed very early on in the kernel and haven't been able to find a working solution to carry on, and have just gone and ignored it for the moment. One thing I am starting to do is pick a random point in the bug list rather than starting at either end; just adding a 1000 or another random number to the bug list and instead of next/last just add a few more - lots of people look at the latest bugs; but there are a few year old untriaged bugs that are still broken on Raring; it just takes someone to spot them and try them - if the description in the bug is a seg-at-startup then I tend to try it myself rather than asking the user to reverify, since the user has probably moved on. Dave -- -----Open up your eyes, open up your mind, open up your code ------- / Dr. David Alan Gilbert | Running GNU/Linux | Happy \ \ gro.gilbert @ treblig.org | | In Hex / \ _________________________|_____ http://www.treblig.org |_______/ From om26er at ubuntu.com Tue Jan 1 18:04:53 2013 From: om26er at ubuntu.com (Omer Akram) Date: Tue, 1 Jan 2013 23:04:53 +0500 Subject: Low bug triage activity all around In-Reply-To: <20130101174622.GA22665@gallifrey> References: <20130101174622.GA22665@gallifrey> Message-ID: On Tue, Jan 1, 2013 at 10:46 PM, Dr. David Alan Gilbert wrote: > * Omer Akram (om26er at ubuntu.com) wrote: > > Hey all, > > > > I have been involved in bug triage for a while in Ubuntu and it seems > this > > scene is not that active it used to be although alot of great folks from > > our community are highly devoted. > > > > I am not sure about the reason behind that but one thing I am sure is > that > > previously we had running efforts like "Bug Days" where a certain package > > was selected and all of the Ubuntu Bug Squad was invited to participate > in > > triaging those bugs. > > > > Another reason which could be related is that now there is no one in the > > Ubuntu desktop team (or Canonical) to lead the effort of Bug management > and > > community involvement previously Pedro played a big role there. > > > > So I think we need to think of some ways to improve the situation and get > > more people involved into this effort. Does anyone have > > suggestions/comments about this matter. > > Most of the irc seems to have been pretty dead over xmas, I'm guessing > there aren't many of us doing it just for the heck of it at the moment. > There is also the danger that perhaps some of the others got a life > and we aren't getting new ones in. > That may be a factor but I have seen closely no activity in #ubuntu-bugs for a while which is not good > > I've been trying to fix things like universe packages that seg at startup; > but with Debian in freeze it's nigh on impossible to get any fix into > debian > unless it also breaks Debian which for a lot of our Fortify triggered > bugs they don't; and for a non-debian dev it's also hard going. > > There are also a heck of a lot of unreviewed patches in the system; so > perhaps > it's time for another round of patch triaging. > > > I don't know what the numbers are, but I think the lack of an 'alpha' > for Raring (as opposed to the dailies) makes me think there are less people > trying it; there certainly doesn't seem to be much activity on +1. > I am not currently affected by this but maybe a bit more time at this will produce better result. > > I'm also seeing signs there are a few of the regulars who've tried > Raring on their machine and find it's failed very early on in the kernel > and haven't been able to find a working solution to carry on, and have > just gone and ignored it for the moment. > then I am lucky raring works just fine for me just few glitches here and there but thats expected at this stage i guess. > > One thing I am starting to do is pick a random point in the bug list > rather than starting at either end; just adding a 1000 or another > random number to the bug list and instead of next/last just add a few > more - lots of people look at the latest bugs; but there are a few > year old untriaged bugs that are still broken on Raring; it just > takes someone to spot them and try them - if the description > in the bug is a seg-at-startup then I tend to try it myself > rather than asking the user to reverify, since the user has probably > moved on. > > Yeah, I has been disucussed in the past that people don't know which bugs to start with, the above problem sounds related. > Dave > -- > -----Open up your eyes, open up your mind, open up your code ------- > / Dr. David Alan Gilbert | Running GNU/Linux | Happy \ > \ gro.gilbert @ treblig.org | | In Hex / > \ _________________________|_____ http://www.treblig.org |_______/ > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From marconifabio at hotmail.it Tue Jan 1 19:43:49 2013 From: marconifabio at hotmail.it (Fabio Marconi) Date: Tue, 1 Jan 2013 20:43:49 +0100 Subject: Low bug triage activity all around In-Reply-To: References: Message-ID: On 01/01/2013 18:21, Omer Akram wrote: > Hey all, > > I have been involved in bug triage for a while in Ubuntu and it seems > this scene is not that active it used to be although alot of great > folks from our community are highly devoted. > > I am not sure about the reason behind that but one thing I am sure is > that previously we had running efforts like "Bug Days" where a certain > package was selected and all of the Ubuntu Bug Squad was invited to > participate in triaging those bugs. > > Another reason which could be related is that now there is no one in > the Ubuntu desktop team (or Canonical) to lead the effort of Bug > management and community involvement previously Pedro played a big > role there. > > So I think we need to think of some ways to improve the situation and > get more people involved into this effort. Does anyone have > suggestions/comments about this matter. > > Thanks > > Yes, pedro_ place still actually vacant, I cannot see any other person with his charisma andcommunicativity at the moment, I cannot perceive enthusiasm in this group. Was a great fault for a group that was growing up, now seems to me that everyone stay on its own, without willingness to mentor, explain and create a positive group around him. Just my 5 cents. Have a great year Fabio -------------- next part -------------- An HTML attachment was scrubbed... URL: From fco.plj at gmail.com Tue Jan 1 22:39:13 2013 From: fco.plj at gmail.com (Javier P.L.) Date: Tue, 01 Jan 2013 16:39:13 -0600 Subject: Low bug triage activity all around In-Reply-To: References: <20130101174622.GA22665@gallifrey> Message-ID: <50E36591.2070802@gmail.com> +1 for the patching triage round, maybe it's time for another operation cleansweep [0] too. I'll start checking out the bugs with patches as soon as new year parties end. Any help is welcome. [0] https://wiki.ubuntu.com/OperationCleansweep On 01/01/2013 12:04 PM, Omer Akram wrote: > > > > On Tue, Jan 1, 2013 at 10:46 PM, Dr. David Alan Gilbert > > wrote: > > * Omer Akram (om26er at ubuntu.com ) wrote: > > Hey all, > > > > I have been involved in bug triage for a while in Ubuntu and it > seems this > > scene is not that active it used to be although alot of great > folks from > > our community are highly devoted. > > > > I am not sure about the reason behind that but one thing I am > sure is that > > previously we had running efforts like "Bug Days" where a certain > package > > was selected and all of the Ubuntu Bug Squad was invited to > participate in > > triaging those bugs. > > > > Another reason which could be related is that now there is no one > in the > > Ubuntu desktop team (or Canonical) to lead the effort of Bug > management and > > community involvement previously Pedro played a big role there. > > > > So I think we need to think of some ways to improve the situation > and get > > more people involved into this effort. Does anyone have > > suggestions/comments about this matter. > > Most of the irc seems to have been pretty dead over xmas, I'm guessing > there aren't many of us doing it just for the heck of it at the moment. > There is also the danger that perhaps some of the others got a life > and we aren't getting new ones in. > > > That may be a factor but I have seen closely no activity in #ubuntu-bugs > for a while which is not good > > > I've been trying to fix things like universe packages that seg at > startup; > but with Debian in freeze it's nigh on impossible to get any fix > into debian > unless it also breaks Debian which for a lot of our Fortify triggered > bugs they don't; and for a non-debian dev it's also hard going. > > There are also a heck of a lot of unreviewed patches in the system; > so perhaps > it's time for another round of patch triaging. > > > > I don't know what the numbers are, but I think the lack of an 'alpha' > for Raring (as opposed to the dailies) makes me think there are less > people > trying it; there certainly doesn't seem to be much activity on +1. > > > I am not currently affected by this but maybe a bit more time at this > will produce better result. > > > I'm also seeing signs there are a few of the regulars who've tried > Raring on their machine and find it's failed very early on in the kernel > and haven't been able to find a working solution to carry on, and have > just gone and ignored it for the moment. > > > then I am lucky raring works just fine for me just few glitches here and > there but thats expected at this stage i guess. > > > One thing I am starting to do is pick a random point in the bug list > rather than starting at either end; just adding a 1000 or another > random number to the bug list and instead of next/last just add a few > more - lots of people look at the latest bugs; but there are a few > year old untriaged bugs that are still broken on Raring; it just > takes someone to spot them and try them - if the description > in the bug is a seg-at-startup then I tend to try it myself > rather than asking the user to reverify, since the user has probably > moved on. > > > Yeah, I has been disucussed in the past that people don't know which > bugs to start with, the above problem sounds related. > > Dave > -- > -----Open up your eyes, open up your mind, open up your code ------- > / Dr. David Alan Gilbert | Running GNU/Linux | Happy \ > \ gro.gilbert @ treblig.org | > | In Hex / > \ _________________________|_____ http://www.treblig.org |_______/ > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > Thanks > > > From ag.restringere at gmail.com Tue Jan 1 22:49:16 2013 From: ag.restringere at gmail.com (AG Restringere) Date: Tue, 1 Jan 2013 17:49:16 -0500 Subject: Low bug triage activity all around In-Reply-To: References: Message-ID: Hello, I'm just getting started with bug reports as I a recently joined Ubuntu-X and am starting to get the hang of it. One of the issues I'm having is the fact that many of the old bugs are for versions of Ubuntu that have already reached "end of life" such as 11.10 or 10.04 and are no longer supported. I feel like telling these bug reporters to upgrade and see if it's fixed but I don't know if that's the way to go. Best, Alex On Tue, Jan 1, 2013 at 2:43 PM, Fabio Marconi wrote: > On 01/01/2013 18:21, Omer Akram wrote: > > Hey all, > > I have been involved in bug triage for a while in Ubuntu and it seems > this scene is not that active it used to be although alot of great folks > from our community are highly devoted. > > I am not sure about the reason behind that but one thing I am sure is > that previously we had running efforts like "Bug Days" where a certain > package was selected and all of the Ubuntu Bug Squad was invited to > participate in triaging those bugs. > > Another reason which could be related is that now there is no one in the > Ubuntu desktop team (or Canonical) to lead the effort of Bug management and > community involvement previously Pedro played a big role there. > > So I think we need to think of some ways to improve the situation and > get more people involved into this effort. Does anyone have > suggestions/comments about this matter. > > Thanks > > > Yes, pedro_ place still actually vacant, I cannot see any other person > with his charisma and communicativity at the moment, I cannot perceive enthusiasm > in this group. > Was a great fault for a group that was growing up, now seems to me that > everyone stay on its own, without willingness to mentor, explain and create > a positive group around him. > Just my 5 cents. > Have a great year > Fabio > > -- > 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: From teward at ubuntu.com Tue Jan 1 23:36:31 2013 From: teward at ubuntu.com (Thomas Ward) Date: Tue, 1 Jan 2013 18:36:31 -0500 Subject: Low bug triage activity all around In-Reply-To: References: <20130101174622.GA22665@gallifrey> Message-ID: On Tue, Jan 1, 2013 at 1:04 PM, Omer Akram wrote: > That may be a factor but I have seen closely no activity in #ubuntu-bugs for > a while which is not good In the time since i started lurking there, there's been a decent bit of activity. From my observations (and courtesy of a very-long-and-time-consuming grep on over 500MB of log files for freenode), your username (om26er) is not in the channel 24/7, thereby your username is not usually active in the channel if/when there's activity. I've witnessed a substantial (not huge amount, but still substantial) quantity of activity related to bugs, or related to bug documentation, or related to bugsquad bug handling things, in #ubuntu-bugs, whether initiated by bugsquad, or initiated by a bug control member, or initiated by a member of some other team. There's sufficient activity in the channel to qualify it as "active". It is true, the past month or so there's little or no activity, however there is still sufficient activity there that its "active". But, remember, it IS the holidays right now, so there's bound to be less activity. Usually, bug work tends to drag me out of #ubuntu-bugs and into other channels, such as #kubuntu or #lubuntu or #ubuntuforums or #ubuntu or others. So while #ubuntu-bugs is not always active, there is triaging going on behind the scenes. Not all Ubuntuers use IRC, and those that do usually get forwarded to the bugsquad channel where applicable. But BugSquad isn't limited to just that channel. They're all over the place: they're on QA, they're on developers, they're on Ubuntu+1, they're on MOTU, they're on the Server Team ... i could go on with that list but I won't, because the list is extremely extensive. >> >>I'm also seeing signs there are a few of the regulars who've tried >>Raring on their machine and find it's failed very early on in the kernel >>and haven't been able to find a working solution to carry on, and have >>just gone and ignored it for the moment. > > >then I am lucky raring works just fine for me just few glitches here and there but thats expected at this stage i guess. While BugSquaders should indeed be on the latest dev release (or at the very least have a VM with it), not all of us do. I personally do not because my primary work on Bugs drags me to server packages in Quantal and Precise, and because I don't have a system that can run Raring or Raring in a VM without technical troubles. I also have old testing systems I usually install the latest dev release to at some point, but the kernel doesn't have drivers for the hardware in those systems, so Raring doesn't work (these're OLD systems). >> I have been involved in bug triage for a while in Ubuntu and it seems this >> scene is not that active it used to be although alot of great folks from >> our community are highly devoted. Okay, I know i'm digging up logs somewhat far back in the email chain about this, but a lot of triaging happens behind-the-scenes. And its not just Bug Squad that does the triaging. Most server packages were shunted off to the Server Team a while ago, and I can guarantee you there is extremely high activity levels for triaging those. I've been one of those people, at least with certain packages. Usually I don't do desktop triaging work, short of filing bugs. ------ Okay, enough with me responding to you, Omer. As for suggestions, I agree with David that we need another round of patch triaging. There's a ton of patches that have gone unprocessed / unchecked. But as David said, these patches won't make it into Debian for a while, especially since they're under a freeze. As for the rest of my suggestions, we should probably start looking at Universe packages for a while. There's a lot of bugs in universe packages that have not been fixed, nor sent up to Debian, nor sent upstream. As well, there's also packages that have not been updated in years which suggests that there's not been any work done on those packages, upstream or otherwise. We may want to coordinate with MOTU and start figuring out which Universe packages are no longer maintained in Debian or otherwise, and perhaps work with the Security team to see whether security bugs in Universe packages are causing substantial security holes, and work to patch, or find patches, for those packages. Just my two cents on this matter :) ------ Thomas Ward Ubuntu Member Ubuntu BugSquader From persia at ubuntu.com Wed Jan 2 02:37:04 2013 From: persia at ubuntu.com (Emmet Hikory) Date: Wed, 2 Jan 2013 11:37:04 +0900 Subject: Low bug triage activity all around In-Reply-To: References: Message-ID: <20130102023704.GA14331@gerdhr.shipstone> Omer Akram wrote: > I have been involved in bug triage for a while in Ubuntu and it seems this > scene is not that active it used to be although alot of great folks from > our community are highly devoted. Bug triage is something that is inherently wearing, and we've always had some fair degree of turnover within the team (including many members returning after spending some time with testing, development, documentation, or other distractions). In previous lulls, my observation is that it doesn't take much to restore a sense of activity: there's lots of folk who are lurking that might participate if activity was visible and a steady stream of new folk who come with their own bugs and are generally happy to trade triage when stuck on their specific issue. > I am not sure about the reason behind that but one thing I am sure is that > previously we had running efforts like "Bug Days" where a certain package > was selected and all of the Ubuntu Bug Squad was invited to participate in > triaging those bugs. I've always found these to be one of the best ways to restore activity: whether the choice is a package, or a class of issues (I remember one bug day called "fixing time itself" where we focused on all classes of clocks, dates, and timing issues), highlighting a set of bugs and making clear progress against them always makes the team feel good, incenting us to do still more. There's been various discussions over the years about how often to have bug days, or when to have bug days, with various results. Some folk seem to prefer weekdays, others have more time on weekends. Some folk want to have a regular schedule (e.g. every Thursday), whilst others would prefer something less fixed (once a month, on different days, to account for different folks' schedules). I don't think there is a right answer for this, and suggest that we try a few different efforts, depending on when our most communicative members currently have time: unless folk are feeling very pressured, we'll likely do better to have too many bug days than too few, and by having a few small ones, we'll get a better understanding of when we might have resources for a large one. > Another reason which could be related is that now there is no one in the > Ubuntu desktop team (or Canonical) to lead the effort of Bug management and > community involvement previously Pedro played a big role there. We've had a variety of folk lead the bugsquad in the past, and I don't think we should look exclusively to the Ubuntu Desktop Team or Canonical to select our leaders. For the events (bug days, etc.), we can probably do as well if someone interested in running one just announces they will do so on some given (future) date, and points folks at the relevant LP queries. For general channel activity, I've always found that if I start talking about what I'm doing on the channel, others join in the discussion, regardless of the time of day or year: the best way to get this back is just to do it. For developer coordination: there's a few developers who are regularly present in our communications channels, but it never hurts for us to reach out on the development channels to ask for a couple folk to be around if we're going to focus on their stuff as part of an event: this can probably be delegated to the event coordinators in the short term. Through a combination of the above, if we succeed in having regular events and noticable channel/mailing list activity for a few months, the sense of limited activity should diminish (without that much more work on the part of those of us who are already doing so much), and I would be surprised if we did not discover that we have some quite capable leaders amoung us, who might not replace Pedro, but at least remove any sense of leaderlessness. -- Emmet HIKORY From micahg at ubuntu.com Wed Jan 2 03:44:10 2013 From: micahg at ubuntu.com (Micah Gersten) Date: Tue, 01 Jan 2013 21:44:10 -0600 Subject: EOL release bug triage (was: Re: Low bug triage activity all around) In-Reply-To: References: Message-ID: <50E3AD0A.6080307@ubuntu.com> On 01/01/2013 04:49 PM, AG Restringere wrote: > > I'm just getting started with bug reports as I a recently joined > Ubuntu-X and am starting to get the hang of it. One of the issues I'm > having is the fact that many of the old bugs are for versions of > Ubuntu that have already reached "end of life" such as 11.10 or 10.04 > and are no longer supported. I feel like telling these bug reporters > to upgrade and see if it's fixed but I don't know if that's the way to > go. > Ubuntu 11.10 and 10.04 are both supported still. 11.10 and 10.04 desktop reach end-of-life in April 2013, 10.04 server is supported until April 2015. Just because a bug is filed against an old release, doesn't mean that it's not valid. We have [1], but if you notice, it mentions testing the issue before replying. If the submitter gave us a proper reproducer in the bug or if the reproducer is obvious, we should try to see if the issue still exists as they already did their part. Asking them to upgrade every 6 months or having a reply such as "Does your problem still exist" is very demotivating and will encourage people not to report bugs since we don't "do" anything useful with them anyways. A bug does not magically disappear in a newer release, it either is fixed, or the code/environment causing the issue is removed or changed; otherwise, it will linger forever. If you don't want to test old bugs, work on something else, we have no shortage of bugs in Launchpad to look at (115k+). Please don't punish those users that have done their due diligence. Thanks, Micah [1] https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_EOL From ag.restringere at gmail.com Wed Jan 2 04:00:52 2013 From: ag.restringere at gmail.com (AG Restringere) Date: Tue, 1 Jan 2013 23:00:52 -0500 Subject: EOL release bug triage (was: Re: Low bug triage activity all around) In-Reply-To: <50E3AD0A.6080307@ubuntu.com> References: <50E3AD0A.6080307@ubuntu.com> Message-ID: Thank you for the Responses article link this was exactly what I was looking for. I'll make sure to take a look at that and think a bit before posting a response to a bug in the future... On Tue, Jan 1, 2013 at 10:44 PM, Micah Gersten wrote: > On 01/01/2013 04:49 PM, AG Restringere wrote: > > > > I'm just getting started with bug reports as I a recently joined > > Ubuntu-X and am starting to get the hang of it. One of the issues I'm > > having is the fact that many of the old bugs are for versions of > > Ubuntu that have already reached "end of life" such as 11.10 or 10.04 > > and are no longer supported. I feel like telling these bug reporters > > to upgrade and see if it's fixed but I don't know if that's the way to > > go. > > > Ubuntu 11.10 and 10.04 are both supported still. 11.10 and 10.04 > desktop reach end-of-life in April 2013, 10.04 server is supported until > April 2015. > Just because a bug is filed against an old release, doesn't mean that > it's not valid. We have [1], but if you notice, it mentions testing the > issue before replying. If the submitter gave us a proper reproducer in > the bug or if the reproducer is obvious, we should try to see if the > issue still exists as they already did their part. Asking them to > upgrade every 6 months or having a reply such as "Does your problem > still exist" is very demotivating and will encourage people not to > report bugs since we don't "do" anything useful with them anyways. > A bug does not magically disappear in a newer release, it either is > fixed, or the code/environment causing the issue is removed or changed; > otherwise, it will linger forever. > If you don't want to test old bugs, work on something else, we have no > shortage of bugs in Launchpad to look at (115k+). Please don't punish > those users that have done their due diligence. > > Thanks, > Micah > > [1] https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_EOL > > -- > 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: From tetvet1967 at yahoo.com Wed Jan 2 05:14:57 2013 From: tetvet1967 at yahoo.com (Walrus) Date: Tue, 1 Jan 2013 21:14:57 -0800 (PST) Subject: remove me from the mailing list Message-ID: <1357103697.78538.YahooMailClassic@web163501.mail.gq1.yahoo.com> remove me from the list please. walrus   -------------- next part -------------- An HTML attachment was scrubbed... URL: From om26er at ubuntu.com Wed Jan 2 11:30:53 2013 From: om26er at ubuntu.com (Omer Akram) Date: Wed, 2 Jan 2013 16:30:53 +0500 Subject: Low bug triage activity all around In-Reply-To: References: Message-ID: For that case I think someone should step in from our community. Anyone willing to lead the effort of creating a stronger community around bug management in Ubuntu? I will surely help where I can. On Wed, Jan 2, 2013 at 12:43 AM, Fabio Marconi wrote: > On 01/01/2013 18:21, Omer Akram wrote: > > Hey all, > > I have been involved in bug triage for a while in Ubuntu and it seems > this scene is not that active it used to be although alot of great folks > from our community are highly devoted. > > I am not sure about the reason behind that but one thing I am sure is > that previously we had running efforts like "Bug Days" where a certain > package was selected and all of the Ubuntu Bug Squad was invited to > participate in triaging those bugs. > > Another reason which could be related is that now there is no one in the > Ubuntu desktop team (or Canonical) to lead the effort of Bug management and > community involvement previously Pedro played a big role there. > > So I think we need to think of some ways to improve the situation and > get more people involved into this effort. Does anyone have > suggestions/comments about this matter. > > Thanks > > > Yes, pedro_ place still actually vacant, I cannot see any other person > with his charisma and communicativity at the moment, I cannot perceive enthusiasm > in this group. > Was a great fault for a group that was growing up, now seems to me that > everyone stay on its own, without willingness to mentor, explain and create > a positive group around him. > Just my 5 cents. > Have a great year > Fabio > > -- > 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: From om26er at ubuntu.com Wed Jan 2 11:43:50 2013 From: om26er at ubuntu.com (Omer Akram) Date: Wed, 2 Jan 2013 16:43:50 +0500 Subject: Low bug triage activity all around In-Reply-To: References: <20130101174622.GA22665@gallifrey> Message-ID: On Wed, Jan 2, 2013 at 4:36 AM, Thomas Ward wrote: > On Tue, Jan 1, 2013 at 1:04 PM, Omer Akram wrote: > > > That may be a factor but I have seen closely no activity in #ubuntu-bugs > for > > a while which is not good > > In the time since i started lurking there, there's been a decent bit > of activity. From my observations (and courtesy of a > very-long-and-time-consuming grep on over 500MB of log files for > freenode), your username (om26er) is not in the channel 24/7, thereby > your username is not usually active in the channel if/when there's > activity. I've witnessed a substantial (not huge amount, but still > substantial) quantity of activity related to bugs, or related to bug > documentation, or related to bugsquad bug handling things, in > #ubuntu-bugs, whether initiated by bugsquad, or initiated by a bug > control member, or initiated by a member of some other team. There's > sufficient activity in the channel to qualify it as "active". It is > true, the past month or so there's little or no activity, however > there is still sufficient activity there that its "active". But, > remember, it IS the holidays right now, so there's bound to be less > activity. > Believe me I have seen far more activity in that channel, though my timing here is just after holidays but the intent of this thread has nothing to do with holidays, I was away for the whole week myself. The real problem is previously people were seeking help in #ubuntu-bugs and asking bug controllers questions and in some cases asking them to set importance of bugs for them, that's not happening as frequent as that used to. Also When I am working I am always online so that's ~40hours a week ;) > > Usually, bug work tends to drag me out of #ubuntu-bugs and into other > channels, such as #kubuntu or #lubuntu or #ubuntuforums or #ubuntu or > others. So while #ubuntu-bugs is not always active, there is triaging > going on behind the scenes. Not all Ubuntuers use IRC, and those that > do usually get forwarded to the bugsquad channel where applicable. > But BugSquad isn't limited to just that channel. They're all over the > place: they're on QA, they're on developers, they're on Ubuntu+1, > they're on MOTU, they're on the Server Team ... i could go on with > that list but I won't, because the list is extremely extensive. > > >> > >>I'm also seeing signs there are a few of the regulars who've tried > >>Raring on their machine and find it's failed very early on in the kernel > >>and haven't been able to find a working solution to carry on, and have > >>just gone and ignored it for the moment. > > > > > >then I am lucky raring works just fine for me just few glitches here and > there but thats expected at this stage i guess. > > While BugSquaders should indeed be on the latest dev release (or at > the very least have a VM with it), not all of us do. I personally do > not because my primary work on Bugs drags me to server packages in > Quantal and Precise, and because I don't have a system that can run > Raring or Raring in a VM without technical troubles. I also have old > testing systems I usually install the latest dev release to at some > point, but the kernel doesn't have drivers for the hardware in those > systems, so Raring doesn't work (these're OLD systems). > > >> I have been involved in bug triage for a while in Ubuntu and it seems > this > >> scene is not that active it used to be although alot of great folks from > >> our community are highly devoted. > > Okay, I know i'm digging up logs somewhat far back in the email chain > about this, but a lot of triaging happens behind-the-scenes. And its > not just Bug Squad that does the triaging. Most server packages were > shunted off to the Server Team a while ago, and I can guarantee you > there is extremely high activity levels for triaging those. I've been > one of those people, at least with certain packages. Usually I don't > do desktop triaging work, short of filing bugs. > I would not agree to that because if you dig up bugs for some packages like rhythmbox or Totem you can clearly see the ever increasing number of NEW bugs. Even though your argument about server maybe correct but the situation for the desktop packages which are considered relatively easy for triage could be very much improved > > ------ > > Okay, enough with me responding to you, Omer. As for suggestions, I > agree with David that we need another round of patch triaging. > There's a ton of patches that have gone unprocessed / unchecked. But > as David said, these patches won't make it into Debian for a while, > especially since they're under a freeze. > > As for the rest of my suggestions, we should probably start looking at > Universe packages for a while. There's a lot of bugs in universe > packages that have not been fixed, nor sent up to Debian, nor sent > upstream. As well, there's also packages that have not been updated > in years which suggests that there's not been any work done on those > packages, upstream or otherwise. We may want to coordinate with MOTU > and start figuring out which Universe packages are no longer > maintained in Debian or otherwise, and perhaps work with the Security > team to see whether security bugs in Universe packages are causing > substantial security holes, and work to patch, or find patches, for > those packages. > > > Just my two cents on this matter :) > > ------ > Thomas Ward > Ubuntu Member > Ubuntu BugSquader > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From maarten.bezemer at gmail.com Wed Jan 2 11:47:34 2013 From: maarten.bezemer at gmail.com (Maarten Bezemer) Date: Wed, 02 Jan 2013 12:47:34 +0100 Subject: Low bug triage activity all around In-Reply-To: References: Message-ID: <1984137.KdpRnir6Rx@i7> On Tuesday 01 January 2013 22:21:41 Omer Akram wrote: > So I think we need to think of some ways to improve the situation and get > more people involved into this effort. Does anyone have > suggestions/comments about this matter. Personally, I would love to help out where possible. But, it is quite overwhelming. I think it would help greatly to reinstate mentors again, maybe in another way, so people are willing to become mentor again? Or if mentors are (still) not viable (anymore), it might help to create some kind of (extensive) tutorial, which guides new users through to overwhelming triaging, different project types, testing patches, fixing bugs, etc. Personally, my problem is that I do not know where to start, eventhough I am trying to help out for a long time already... How to find suitable bugs for an inexperienced triager like myself. It basically is all 'too much'. Regards, Maarten From hggdh2 at ubuntu.com Wed Jan 2 14:12:02 2013 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Wed, 02 Jan 2013 08:12:02 -0600 Subject: remove me from the mailing list In-Reply-To: <1357103697.78538.YahooMailClassic@web163501.mail.gq1.yahoo.com> References: <1357103697.78538.YahooMailClassic@web163501.mail.gq1.yahoo.com> Message-ID: <1845268.L4Y6LexoQA@xango3> On Tuesday, January 01, 2013 21:14:57 Walrus wrote: > remove me from the list please. > > walrus > You can remove yourself. Follow the link at the bottom of this email (and of every email in the mailing list. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. URL: From snskeeter0 at gmail.com Wed Jan 2 17:26:12 2013 From: snskeeter0 at gmail.com (steve nordstrom) Date: Wed, 2 Jan 2013 11:26:12 -0600 Subject: ubuntu bug squad Message-ID: remove me from list -------------- next part -------------- An HTML attachment was scrubbed... URL: From notgary at ubuntu.com Wed Jan 2 21:11:03 2013 From: notgary at ubuntu.com (Chris Wilson) Date: Wed, 2 Jan 2013 21:11:03 +0000 Subject: ubuntu bug squad In-Reply-To: References: Message-ID: There's a link at the bottom of this email that you can follow to remove yourself. On 2 January 2013 17:26, steve nordstrom wrote: > remove me from list > > -- > 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: From matthew.fischer at canonical.com Thu Jan 3 01:32:53 2013 From: matthew.fischer at canonical.com (Matt Fischer) Date: Wed, 02 Jan 2013 18:32:53 -0700 Subject: Low bug triage activity all around In-Reply-To: <1984137.KdpRnir6Rx@i7> References: <1984137.KdpRnir6Rx@i7> Message-ID: <50E4DFC5.80902@canonical.com> On 01/02/2013 04:47 AM, Maarten Bezemer wrote: > On Tuesday 01 January 2013 22:21:41 Omer Akram wrote: >> So I think we need to think of some ways to improve the situation and get >> more people involved into this effort. Does anyone have >> suggestions/comments about this matter. > Personally, I would love to help out where possible. But, it is quite > overwhelming. I think it would help greatly to reinstate mentors again, maybe > in another way, so people are willing to become mentor again? > > Or if mentors are (still) not viable (anymore), it might help to create some > kind of (extensive) tutorial, which guides new users through to overwhelming > triaging, different project types, testing patches, fixing bugs, etc. > > Personally, my problem is that I do not know where to start, eventhough I am > trying to help out for a long time already... How to find suitable bugs for an > inexperienced triager like myself. It basically is all 'too much'. > > Regards, > Maarten > I don't know the history of why/when the mentors program was stopped, but I can say that without my MOTU mentor I'd never make as much progress as I have on doing packaging updates and assorted fixes. I'd be happy to volunteer to mentor someone for triaging. As for where to start, my advice to a new person is actually to pick a package and focus on the bugs there. I did this when I started on gnome-nettool, one that had a manageable number of bugs and then I triaged it and cleaned up the list of open bugs substantially (did some patches too). This may not work for everyone, but it worked well for me. It also helps if the package you pick is in a programming language/toolkit you know if you plan on doing fixes. -- Matthew (Matt) Fischer LP: http://launchpad.net/~mfisch IRC: mfisch From slickymaster at gmail.com Thu Jan 3 09:22:50 2013 From: slickymaster at gmail.com (David Manuel Pires) Date: Thu, 3 Jan 2013 09:22:50 +0000 Subject: Low bug triage activity all around In-Reply-To: <50E4DFC5.80902@canonical.com> References: <1984137.KdpRnir6Rx@i7> <50E4DFC5.80902@canonical.com> Message-ID: On 01/02/2013 04:47 AM, Maarten Bezemer wrote:* * *"Or if mentors are (still) not viable (anymore), it might help to create some kind of (extensive) tutorial, which guides new users through to overwhelming triaging, different project types, testing patches, fixing bugs, etc. Personally, my problem is that I do not know where to start, eventhough I am trying to help out for a long time already... How to find suitable bugs for an inexperienced triager like myself. It basically is all 'too much'."* +1 Personally, I am facing the same problem. Even though I' willing to help, I do not know how to start and the existence of a good tutorial/guide to the new users would surely increase the number of participants in bugsquad. On Thu, Jan 3, 2013 at 1:32 AM, Matt Fischer wrote: *I don't know the history of why/when the mentors program was stopped, but I can say that without my MOTU mentor I'd never make as much progress as I have on doing packaging updates and assorted fixes. I'd be happy to volunteer to mentor someone for triaging.* Will there be the possibility of returning to rebuild the mentors program? I, for one, would be glad to have one, not only to help me getting things started but also to provide me some assistance along the way. Regards, David Manuel Pires On Thu, Jan 3, 2013 at 1:32 AM, Matt Fischer wrote: > On 01/02/2013 04:47 AM, Maarten Bezemer wrote: > >> On Tuesday 01 January 2013 22:21:41 Omer Akram wrote: >> >>> So I think we need to think of some ways to improve the situation and get >>> more people involved into this effort. Does anyone have >>> suggestions/comments about this matter. >>> >> Personally, I would love to help out where possible. But, it is quite >> overwhelming. I think it would help greatly to reinstate mentors again, >> maybe >> in another way, so people are willing to become mentor again? >> >> Or if mentors are (still) not viable (anymore), it might help to create >> some >> kind of (extensive) tutorial, which guides new users through to >> overwhelming >> triaging, different project types, testing patches, fixing bugs, etc. >> >> Personally, my problem is that I do not know where to start, eventhough I >> am >> trying to help out for a long time already... How to find suitable bugs >> for an >> inexperienced triager like myself. It basically is all 'too much'. >> >> Regards, >> Maarten >> >> > I don't know the history of why/when the mentors program was stopped, but > I can say that without my MOTU mentor I'd never make as much progress as I > have on doing packaging updates and assorted fixes. I'd be happy to > volunteer to mentor someone for triaging. > > As for where to start, my advice to a new person is actually to pick a > package and focus on the bugs there. I did this when I started on > gnome-nettool, one that had a manageable number of bugs and then I triaged > it and cleaned up the list of open bugs substantially (did some patches > too). This may not work for everyone, but it worked well for me. It also > helps if the package you pick is in a programming language/toolkit you know > if you plan on doing fixes. > > > > -- > > Matthew (Matt) Fischer > LP: http://launchpad.net/~mfisch > IRC: mfisch > > > -- > 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: From walter.garcia at upf.edu Thu Jan 3 10:18:27 2013 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Thu, 3 Jan 2013 11:18:27 +0100 Subject: Low bug triage activity all around In-Reply-To: References: Message-ID: <20130103101826.GE6293@upf.edu> * Omer Akram, om26er at ubuntu.com [02/01/13 12:35]: > For that case I think someone should step in from our community. Anyone > willing to lead the effort of creating a stronger community around bug > management in Ubuntu? I will surely help where I can. > I'm one of the lurkers, and it is true that without the "bug days" and similar initiatives it is harder for people like me to contribute. I can only step in occasionally when my other activities go down, but with those initiatives I could do quite a lot of work, I remember once closing around 80 bugs in little more than one hour on update-manager after a suggestion by Brian Murray. Instead when I open Launchpad directly and browse bugs I only manage to deal with very few bugs. Another thing holding me back is that apport is not working for me in my two main systems, my desktop and my laptop. When I hit a bug myself I do quite a lot of triage finding duplicates, miss-files bugs, and such. Something that in my case has also created confusion is, if I explain it right, the division between QA and other groups in the bug team, I never got how things work after that initiative that I believe happened some months ago. In my opinion mentoring is not very useful, the more useful thing is somebody suggesting targeted bug triage trough a weekly wiki page, the way Pedro or Brian were doing at some time, where one can access the bugs just by a click, plus friendly assistance at the IRC channel, when in doubt, which I believe is still available but without the other initiatives is less useful. -- Walter Garcia-Fontes From om26er at ubuntu.com Thu Jan 3 12:13:33 2013 From: om26er at ubuntu.com (Omer Akram) Date: Thu, 3 Jan 2013 17:13:33 +0500 Subject: Low bug triage activity all around In-Reply-To: <50E4DFC5.80902@canonical.com> References: <1984137.KdpRnir6Rx@i7> <50E4DFC5.80902@canonical.com> Message-ID: On Thu, Jan 3, 2013 at 6:32 AM, Matt Fischer wrote: > On 01/02/2013 04:47 AM, Maarten Bezemer wrote: > >> On Tuesday 01 January 2013 22:21:41 Omer Akram wrote: >> >>> So I think we need to think of some ways to improve the situation and get >>> more people involved into this effort. Does anyone have >>> suggestions/comments about this matter. >>> >> Personally, I would love to help out where possible. But, it is quite >> overwhelming. I think it would help greatly to reinstate mentors again, >> maybe >> in another way, so people are willing to become mentor again? >> >> Or if mentors are (still) not viable (anymore), it might help to create >> some >> kind of (extensive) tutorial, which guides new users through to >> overwhelming >> triaging, different project types, testing patches, fixing bugs, etc. >> >> Personally, my problem is that I do not know where to start, eventhough I >> am >> trying to help out for a long time already... How to find suitable bugs >> for an >> inexperienced triager like myself. It basically is all 'too much'. >> >> Regards, >> Maarten >> >> > I don't know the history of why/when the mentors program was stopped, but > I can say that without my MOTU mentor I'd never make as much progress as I > have on doing packaging updates and assorted fixes. I'd be happy to > volunteer to mentor someone for triaging. > I am not sure about that either, i do remember a few people getting mentors and later doing great work. > > As for where to start, my advice to a new person is actually to pick a > package and focus on the bugs there. I did this when I started on > gnome-nettool, one that had a manageable number of bugs and then I triaged > it and cleaned up the list of open bugs substantially (did some patches > too). This may not work for everyone, but it worked well for me. It also > helps if the package you pick is in a programming language/toolkit you know > if you plan on doing fixes. Previously we used to have 'adopt a package' where someone or multiple people would adopt a certain package for triage and will take responsibility of moving bugs uptream and getting important bugs cherry picked to Ubuntu by indicating people in the desktop team or in some cases doing that themselves. > > > > > -- > > Matthew (Matt) Fischer > LP: http://launchpad.net/~mfisch > IRC: mfisch > > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.**com > https://lists.ubuntu.com/**mailman/listinfo/ubuntu-**bugsquad > Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From pvillavi at gmail.com Thu Jan 3 12:18:57 2013 From: pvillavi at gmail.com (Pedro Villavicencio Garrido) Date: Thu, 3 Jan 2013 09:18:57 -0300 Subject: Low bug triage activity all around In-Reply-To: <20130103101826.GE6293@upf.edu> References: <20130103101826.GE6293@upf.edu> Message-ID: Hello folks, 2013/1/3 Walter Garcia-Fontes : > * Omer Akram, om26er at ubuntu.com [02/01/13 12:35]: >> For that case I think someone should step in from our community. Anyone >> willing to lead the effort of creating a stronger community around bug >> management in Ubuntu? I will surely help where I can. >> > > I'm one of the lurkers, and it is true that without the "bug days" and > similar initiatives it is harder for people like me to contribute. I > can only step in occasionally when my other activities go down, but > with those initiatives I could do quite a lot of work, I remember once > closing around 80 bugs in little more than one hour on update-manager > after a suggestion by Brian Murray. Instead when I open Launchpad > directly and browse bugs I only manage to deal with very few bugs. > > Another thing holding me back is that apport is not working for me in > my two main systems, my desktop and my laptop. When I hit a bug myself > I do quite a lot of triage finding duplicates, miss-files bugs, and > such. > > Something that in my case has also created confusion is, if I explain > it right, the division between QA and other groups in the bug team, I > never got how things work after that initiative that I believe > happened some months ago. > > In my opinion mentoring is not very useful, the more useful thing is > somebody suggesting targeted bug triage trough a weekly wiki page, the > way Pedro or Brian were doing at some time, where one can access the > bugs just by a click, plus friendly assistance at the IRC channel, > when in doubt, which I believe is still available but without the > other initiatives is less useful. > Mentoring didn't work that well, we had some good students that's true, but (in my experience) they were the minimum (1 out of 10). So i agree with most of the opinions on this matter, maybe the mentoring program wasn't the better for the quantity and the kind of work we do in the team. It seems though that helping out in the channel works a lot better, so instead i think we should be more responsive when someone ask something about a bug in the #ubuntu-bugs . Bug days were a great way to get people to work on a set of bugs together, learn about the product and talk to the developers. If we could revive this initiative that'd be amazing, since I've organized most of them I'm totally available to start with at least the first couple of bug days and to teach how to set up the page, grab the bugs, etc. The BugSquad is still there, lets set up the alarm clock and wake them up! Happy new year everyone, pedro. From om26er at ubuntu.com Thu Jan 3 12:21:11 2013 From: om26er at ubuntu.com (Omer Akram) Date: Thu, 3 Jan 2013 17:21:11 +0500 Subject: Low bug triage activity all around In-Reply-To: <20130103101826.GE6293@upf.edu> References: <20130103101826.GE6293@upf.edu> Message-ID: On Thu, Jan 3, 2013 at 3:18 PM, Walter Garcia-Fontes wrote: > * Omer Akram, om26er at ubuntu.com [02/01/13 12:35]: > > For that case I think someone should step in from our community. Anyone > > willing to lead the effort of creating a stronger community around bug > > management in Ubuntu? I will surely help where I can. > > > > I'm one of the lurkers, and it is true that without the "bug days" and > similar initiatives it is harder for people like me to contribute. I > can only step in occasionally when my other activities go down, but > with those initiatives I could do quite a lot of work, I remember once > closing around 80 bugs in little more than one hour on update-manager > after a suggestion by Brian Murray. Instead when I open Launchpad > directly and browse bugs I only manage to deal with very few bugs. > You are absolutely correct there. I have found myself triaging *alot* of bugs in certain bug days. I even remember a bug day of Banshee which really brought in an extreme level of triage from quite a lot of people. > Another thing holding me back is that apport is not working for me in > my two main systems, my desktop and my laptop. When I hit a bug myself > I do quite a lot of triage finding duplicates, miss-files bugs, and > such. > > Something that in my case has also created confusion is, if I explain > it right, the division between QA and other groups in the bug team, I > never got how things work after that initiative that I believe > happened some months ago. > I think it would make sense to merge #ubuntu-quality and #ubuntu-bugs as both the groups have ultimately the same goal to improve the quality in Ubuntu and there must be many cases where discussions in one channel directly affects the other but same people are not on both. > > In my opinion mentoring is not very useful, the more useful thing is > somebody suggesting targeted bug triage trough a weekly wiki page, the > way Pedro or Brian were doing at some time, where one can access the > bugs just by a click, plus friendly assistance at the IRC channel, > when in doubt, which I believe is still available but without the > other initiatives is less useful. > > -- > Walter Garcia-Fontes Thanks! > > > -- > 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: From lars.duesing at camelotsweb.de Thu Jan 3 12:31:45 2013 From: lars.duesing at camelotsweb.de (Lars Duesing) Date: Thu, 03 Jan 2013 13:31:45 +0100 Subject: Low bug triage activity all around In-Reply-To: References: <20130103101826.GE6293@upf.edu> Message-ID: <50E57A31.9040505@camelotsweb.de> I do see another problem: After canonical told people there would be no alpha/beta-builds and there will be some work behind the scene for doing some "great bang" on unfolding the news, many people (including me) went away from developing/bug fixing because it was clearly shown that help is not wanted. I would never get into that vip-circle, so I cannot help in any way. Period. (Even if these thoughts are clearly rubbish, but human brain...) Lars From om26er at ubuntu.com Thu Jan 3 12:41:42 2013 From: om26er at ubuntu.com (Omer Akram) Date: Thu, 3 Jan 2013 17:41:42 +0500 Subject: Low bug triage activity all around In-Reply-To: <50E57A31.9040505@camelotsweb.de> References: <20130103101826.GE6293@upf.edu> <50E57A31.9040505@camelotsweb.de> Message-ID: Hey On Thu, Jan 3, 2013 at 5:31 PM, Lars Duesing wrote: > I do see another problem: After canonical told people there would be no > alpha/beta-builds and there will be some work behind the scene for doing > some "great bang" on unfolding the news, many people (including me) went > away from developing/bug fixing because it was clearly shown that help is > not wanted. The alpha/beta thing might be playing a role in reduced involvement but for the "great bang" thing it seems that has been happening since 10.04 with all the new branding stuff which just landed. The new skunkwork thing however wanted more people involvement. So the real problem is people not understanding the concept or not being associated with Ubuntu in the past to know that that has been happening for a while. Even though me answering goes offtopic for this list :/ I would never get into that vip-circle, so I cannot help in any way. Period. > (Even if these thoughts are clearly rubbish, but human brain...) > > ;-) > Lars > Thanks! On Thu, Jan 3, 2013 at 5:31 PM, Lars Duesing wrote: > I do see another problem: After canonical told people there would be no > alpha/beta-builds and there will be some work behind the scene for doing > some "great bang" on unfolding the news, many people (including me) went > away from developing/bug fixing because it was clearly shown that help is > not wanted. I would never get into that vip-circle, so I cannot help in any > way. Period. > (Even if these thoughts are clearly rubbish, but human brain...) > > Lars > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slickymaster at gmail.com Thu Jan 3 12:44:42 2013 From: slickymaster at gmail.com (David Manuel Pires) Date: Thu, 3 Jan 2013 12:44:42 +0000 Subject: Low bug triage activity all around In-Reply-To: References: <20130103101826.GE6293@upf.edu> <50E57A31.9040505@camelotsweb.de> Message-ID: On Thu, Jan 3, 2013 at 12:41 PM, Omer Akram wrote: > So the real problem is people not understanding the concept or not being > associated with Ubuntu in the past to know that that has been happening for > a while That's the real problem, here. And that is what really should be addressed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From om26er at ubuntu.com Thu Jan 3 13:02:33 2013 From: om26er at ubuntu.com (Omer Akram) Date: Thu, 3 Jan 2013 18:02:33 +0500 Subject: Low bug triage activity all around In-Reply-To: References: <20130103101826.GE6293@upf.edu> <50E57A31.9040505@camelotsweb.de> Message-ID: On Thu, Jan 3, 2013 at 5:44 PM, David Manuel Pires wrote: > On Thu, Jan 3, 2013 at 12:41 PM, Omer Akram wrote: > >> So the real problem is people not understanding the concept or not being >> associated with Ubuntu in the past to know that that has been happening for >> a while > > > That's the real problem, here. And that is what really should be addressed. > That may be a problem but not the problem or real cause of the problem. After a discussion on IRC with Emmet Hikory (persia) yesterday, he suggested (which I agree to) that we should quickly get started with bug days by asking some of the experienced people to volunteer to stay available for helping other people. It might have a low turn over at first but eventually things will get ripped and more people will hopefully participate. There are a lot of hours in a day considering all the different timezones so we would need people of different time zones. So for that we would need few people to show interest and ensure they will stay on IRC to help any people asking questions. Please show yourself if you would like to. If all agree we can quickly start a bug hug day as soon as Monday or something by announcing on this list. We should select some simple package like transmission (or you have other suggestions?) for the day. More suggestions/objections welcome. > -- > 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: From om26er at ubuntu.com Thu Jan 3 13:14:53 2013 From: om26er at ubuntu.com (Omer Akram) Date: Thu, 3 Jan 2013 18:14:53 +0500 Subject: Proposal to merge #ubuntu-quality and #ubuntu-bugs Message-ID: Hi All Just recently there started a discussion on Ubuntu bug squad list about less people getting involved in bug triage along the discussion there were a few points raised which let me to put the idea of merging #ubuntu-quality and #ubuntu-bugs into one. Ultimately both have the same goal that is talking about quality in Ubuntu. At time people testing Ubuntu ISO will raise their bugs in #ubuntu-quality and discussions may take place there. People may or may not be available in both channels but since I believe people do talk mostly about bug reports in those channels (though #ubuntu-quality do have other topics as well) but I think merging them will make a few things easier one will be that there will be mostly a unified place for people to talk about bugs (i know people may talk in #ubuntu+1 or #ubuntu-desktop as well but those channels have their own reasons for exisitance) Here I might not have a lot of point to argue plus I am never great with words but the overall notion is that I believe that it will result in a benefit for Ubuntu due to having a concentrated place to talk bugs. Thoughts/Suggestions/Pros/Cons all welcome and appreciated Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From fitoschido at ubuntu.com Thu Jan 3 14:00:08 2013 From: fitoschido at ubuntu.com (Adolfo Jayme Barrientos) Date: Thu, 3 Jan 2013 08:00:08 -0600 Subject: Proposal to merge #ubuntu-quality and #ubuntu-bugs In-Reply-To: References: Message-ID: On Thu, Jan 3, 2013 at 7:14 AM, Omer Akram wrote: > Just recently there started a discussion on Ubuntu bug squad list about less > people getting involved in bug triage along the discussion there were a few > points raised which let me to put the idea of merging #ubuntu-quality and > #ubuntu-bugs into one. Ultimately both have the same goal that is talking > about quality in Ubuntu. Yeah, why not? From webmaster at ubuntu.com Thu Jan 3 13:08:39 2013 From: webmaster at ubuntu.com (Help Ubuntu) Date: Thu, 03 Jan 2013 13:08:39 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_penalvch?= Message-ID: <20130103130839.9706.86556@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by penalvch: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=221&rev2=222 Comment: Added note on hardware firmware updating due to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1034248 Thank you for reading this article. This will guide you on how best to present your bug report so that it gets addressed as soon as possible. Here are a few guiding principles that lead to success in getting bugs fixed: <
><
> - Before filing any hardware related reports on Launchpad, please update your BIOS to the newest available from your vendor. Outdated and buggy BIOS firmware is a common cause of a variety of hardware issues (ex. intermittent wireless, suspend not working, certain keys on keyboard not working correctly, and kernel panics after plugging USB drive in). + Before filing any hardware related reports on Launchpad, please update your BIOS, and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). <
><
> Please do not quote Wikipedia and other non-primary resource information as fact on [[Launchpad]]. <
><
> From mss at mawhrin.net Thu Jan 3 13:45:55 2013 From: mss at mawhrin.net (Mikhail Sobolev) Date: Thu, 3 Jan 2013 16:45:55 +0300 Subject: Proposal to merge #ubuntu-quality and #ubuntu-bugs In-Reply-To: References: Message-ID: <20130103134555.GA26641@mawhrin.net> Hi, On Thu, Jan 03, 2013 at 06:14:53PM +0500, Omer Akram wrote: > Just recently there started a discussion on Ubuntu bug squad list about > less people getting involved in bug triage along the discussion there were > a few points raised which let me to put the idea of merging #ubuntu-quality > and #ubuntu-bugs into one. Ultimately both have the same goal that is > talking about quality in Ubuntu. As long as the "merge" results in ubuntu-quality, I'd agree. Yes, the goal seems to be the same, however "quality" has a bit broader meaning than just "bugs". My 0.02 [euro]cents, "quality" aims to define how the things can be made the best, while "bugs" show whether the way of doing it has any deficiencies (and, yes, testing is one of the possible ways to not only find discrepancies in the actual software but also to identify what's missing from "the way" to ensure that the result of the anticipated quality). > Here I might not have a lot of point to argue plus I am never great with > words but the overall notion is that I believe that it will result in a > benefit for Ubuntu due to having a concentrated place to talk bugs. I agree that a "concentrated place" to talk about _quality_ would be of a better value as people would be able not only to see what's not working as expected, but also to generalise and suggest how to avoid that in future. -- Misha -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From micahg at ubuntu.com Thu Jan 3 14:40:02 2013 From: micahg at ubuntu.com (Micah Gersten) Date: Thu, 03 Jan 2013 08:40:02 -0600 Subject: Proposal to merge #ubuntu-quality and #ubuntu-bugs In-Reply-To: References: Message-ID: <50E59842.5020906@ubuntu.com> On 01/03/2013 07:14 AM, Omer Akram wrote: > Hi All > > Just recently there started a discussion on Ubuntu bug squad list > about less people getting involved in bug triage along the discussion > there were a few points raised which let me to put the idea of merging > #ubuntu-quality and #ubuntu-bugs into one. Ultimately both have the > same goal that is talking about quality in Ubuntu. > > At time people testing Ubuntu ISO will raise their bugs in > #ubuntu-quality and discussions may take place there. People may or > may not be available in both channels but since I believe people do > talk mostly about bug reports in those channels (though > #ubuntu-quality do have other topics as well) but I think merging them > will make a few things easier one will be that there will be mostly a > unified place for people to talk about bugs (i know people may talk in > #ubuntu+1 or #ubuntu-desktop as well but those channels have their own > reasons for exisitance) > > Here I might not have a lot of point to argue plus I am never great > with words but the overall notion is that I believe that it will > result in a benefit for Ubuntu due to having a concentrated place to > talk bugs. > > Thoughts/Suggestions/Pros/Cons all welcome and appreciated > > Thanks! > I'm not sure I agree with this. #ubuntu-bugs is specifically for bug triage, whereas #ubuntu-quality seems to not have a defined topic. Whereas I'm likely to watch #ubuntu-bugs for people who need help with triage, I'm not necessarily interested in most of what happens with image testing and the issues that arise from it. This is not to say that I don't care, rather that I'm not necessarily going to commit my time to such issues. You could in theory condense #ubuntu-devel, -desktop, and -release into quality as well as the goal is quality, but I don't see that as being productive. Thanks, Micah From teward at ubuntu.com Thu Jan 3 16:01:37 2013 From: teward at ubuntu.com (Thomas Ward) Date: Thu, 3 Jan 2013 11:01:37 -0500 Subject: Proposal to merge #ubuntu-quality and #ubuntu-bugs In-Reply-To: <50E59842.5020906@ubuntu.com> References: <50E59842.5020906@ubuntu.com> Message-ID: On Thu, Jan 3, 2013 at 9:40 AM, Micah Gersten wrote: > On 01/03/2013 07:14 AM, Omer Akram wrote: >> Hi All >> >> Just recently there started a discussion on Ubuntu bug squad list >> about less people getting involved in bug triage along the discussion >> there were a few points raised which let me to put the idea of merging >> #ubuntu-quality and #ubuntu-bugs into one. Ultimately both have the >> same goal that is talking about quality in Ubuntu. >> >> At time people testing Ubuntu ISO will raise their bugs in >> #ubuntu-quality and discussions may take place there. People may or >> may not be available in both channels but since I believe people do >> talk mostly about bug reports in those channels (though >> #ubuntu-quality do have other topics as well) but I think merging them >> will make a few things easier one will be that there will be mostly a >> unified place for people to talk about bugs (i know people may talk in >> #ubuntu+1 or #ubuntu-desktop as well but those channels have their own >> reasons for exisitance) >> >> Here I might not have a lot of point to argue plus I am never great >> with words but the overall notion is that I believe that it will >> result in a benefit for Ubuntu due to having a concentrated place to >> talk bugs. >> >> Thoughts/Suggestions/Pros/Cons all welcome and appreciated >> >> Thanks! >> > I'm not sure I agree with this. #ubuntu-bugs is specifically for bug > triage, whereas #ubuntu-quality seems to not have a defined topic. > Whereas I'm likely to watch #ubuntu-bugs for people who need help with > triage, I'm not necessarily interested in most of what happens with > image testing and the issues that arise from it. This is not to say > that I don't care, rather that I'm not necessarily going to commit my > time to such issues. > You could in theory condense #ubuntu-devel, -desktop, and -release into > quality as well as the goal is quality, but I don't see that as being > productive. > Thanks, > Micah > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad I am in full agreement with Micah, what #ubuntu-quality does is ISO testing and other ISO/image related testing, and not necessarily bug triage. I lurk in both #ubuntu-bugs and #ubuntu-quality. The channels have separate goals. And in #ubuntu-bugs, I'm also more than happy to help out with bug triaging, but I don't want to see ISO testing bugs and related stuff in #ubuntu-bugs either. Since not everyone's responding to both the BugSquad and ubuntu-quality lists, I've sent this response to both. ------ Thomas Ubuntu BugSquad Member From om26er at ubuntu.com Thu Jan 3 16:08:44 2013 From: om26er at ubuntu.com (Omer Akram) Date: Thu, 3 Jan 2013 21:08:44 +0500 Subject: Proposal to merge #ubuntu-quality and #ubuntu-bugs In-Reply-To: References: <50E59842.5020906@ubuntu.com> Message-ID: I would say that then the word ubuntu-quality is a bit too broad than its actual purpose, i should have researched more but i did think they were not limited to ISO testing only. As you stated that's not the case then its a bit of misunderstanding about #ubuntu-quality on my end. On Thu, Jan 3, 2013 at 9:01 PM, Thomas Ward wrote: > On Thu, Jan 3, 2013 at 9:40 AM, Micah Gersten wrote: > > On 01/03/2013 07:14 AM, Omer Akram wrote: > >> Hi All > >> > >> Just recently there started a discussion on Ubuntu bug squad list > >> about less people getting involved in bug triage along the discussion > >> there were a few points raised which let me to put the idea of merging > >> #ubuntu-quality and #ubuntu-bugs into one. Ultimately both have the > >> same goal that is talking about quality in Ubuntu. > >> > >> At time people testing Ubuntu ISO will raise their bugs in > >> #ubuntu-quality and discussions may take place there. People may or > >> may not be available in both channels but since I believe people do > >> talk mostly about bug reports in those channels (though > >> #ubuntu-quality do have other topics as well) but I think merging them > >> will make a few things easier one will be that there will be mostly a > >> unified place for people to talk about bugs (i know people may talk in > >> #ubuntu+1 or #ubuntu-desktop as well but those channels have their own > >> reasons for exisitance) > >> > >> Here I might not have a lot of point to argue plus I am never great > >> with words but the overall notion is that I believe that it will > >> result in a benefit for Ubuntu due to having a concentrated place to > >> talk bugs. > >> > >> Thoughts/Suggestions/Pros/Cons all welcome and appreciated > >> > >> Thanks! > >> > > I'm not sure I agree with this. #ubuntu-bugs is specifically for bug > > triage, whereas #ubuntu-quality seems to not have a defined topic. > > Whereas I'm likely to watch #ubuntu-bugs for people who need help with > > triage, I'm not necessarily interested in most of what happens with > > image testing and the issues that arise from it. This is not to say > > that I don't care, rather that I'm not necessarily going to commit my > > time to such issues. > > You could in theory condense #ubuntu-devel, -desktop, and -release into > > quality as well as the goal is quality, but I don't see that as being > > productive. > > Thanks, > > Micah > > > > -- > > Ubuntu-bugsquad mailing list > > Ubuntu-bugsquad at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > I am in full agreement with Micah, what #ubuntu-quality does is ISO > testing and other ISO/image related testing, and not necessarily bug > triage. I lurk in both #ubuntu-bugs and #ubuntu-quality. The > channels have separate goals. And in #ubuntu-bugs, I'm also more than > happy to help out with bug triaging, but I don't want to see ISO > testing bugs and related stuff in #ubuntu-bugs either. > > Since not everyone's responding to both the BugSquad and > ubuntu-quality lists, I've sent this response to both. > > ------ > Thomas > Ubuntu BugSquad Member > > -- > 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: From nicholas.skaggs at canonical.com Thu Jan 3 16:35:02 2013 From: nicholas.skaggs at canonical.com (Nicholas Skaggs) Date: Thu, 03 Jan 2013 11:35:02 -0500 Subject: Proposal to merge #ubuntu-quality and #ubuntu-bugs In-Reply-To: References: <50E59842.5020906@ubuntu.com> Message-ID: <50E5B336.8050608@canonical.com> Thanks for the lovely chat on irc Omer. I wish you the best on your efforts to help the bug squad. As we spoke about, while our end goals are similar (as with all the ubuntu teams), our focus is different and should remain separate to allow us to work effectively. Cheers, Nicholas On 01/03/2013 11:08 AM, Omer Akram wrote: > I would say that then the word ubuntu-quality is a bit too broad than > its actual purpose, i should have researched more but i did think they > were not limited to ISO testing only. As you stated that's not the > case then its a bit of misunderstanding about #ubuntu-quality on my end. > > > On Thu, Jan 3, 2013 at 9:01 PM, Thomas Ward > wrote: > > On Thu, Jan 3, 2013 at 9:40 AM, Micah Gersten > wrote: > > On 01/03/2013 07:14 AM, Omer Akram wrote: > >> Hi All > >> > >> Just recently there started a discussion on Ubuntu bug squad list > >> about less people getting involved in bug triage along the > discussion > >> there were a few points raised which let me to put the idea of > merging > >> #ubuntu-quality and #ubuntu-bugs into one. Ultimately both have the > >> same goal that is talking about quality in Ubuntu. > >> > >> At time people testing Ubuntu ISO will raise their bugs in > >> #ubuntu-quality and discussions may take place there. People may or > >> may not be available in both channels but since I believe people do > >> talk mostly about bug reports in those channels (though > >> #ubuntu-quality do have other topics as well) but I think > merging them > >> will make a few things easier one will be that there will be > mostly a > >> unified place for people to talk about bugs (i know people may > talk in > >> #ubuntu+1 or #ubuntu-desktop as well but those channels have > their own > >> reasons for exisitance) > >> > >> Here I might not have a lot of point to argue plus I am never great > >> with words but the overall notion is that I believe that it will > >> result in a benefit for Ubuntu due to having a concentrated > place to > >> talk bugs. > >> > >> Thoughts/Suggestions/Pros/Cons all welcome and appreciated > >> > >> Thanks! > >> > > I'm not sure I agree with this. #ubuntu-bugs is specifically > for bug > > triage, whereas #ubuntu-quality seems to not have a defined topic. > > Whereas I'm likely to watch #ubuntu-bugs for people who need > help with > > triage, I'm not necessarily interested in most of what happens with > > image testing and the issues that arise from it. This is not to say > > that I don't care, rather that I'm not necessarily going to > commit my > > time to such issues. > > You could in theory condense #ubuntu-devel, -desktop, and > -release into > > quality as well as the goal is quality, but I don't see that as > being > > productive. > > Thanks, > > Micah > > > > -- > > Ubuntu-bugsquad mailing list > > Ubuntu-bugsquad at lists.ubuntu.com > > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > I am in full agreement with Micah, what #ubuntu-quality does is ISO > testing and other ISO/image related testing, and not necessarily bug > triage. I lurk in both #ubuntu-bugs and #ubuntu-quality. The > channels have separate goals. And in #ubuntu-bugs, I'm also more than > happy to help out with bug triaging, but I don't want to see ISO > testing bugs and related stuff in #ubuntu-bugs either. > > Since not everyone's responding to both the BugSquad and > ubuntu-quality lists, I've sent this response to both. > > ------ > Thomas > Ubuntu BugSquad Member > > -- > 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: From brian at ubuntu.com Thu Jan 3 16:46:10 2013 From: brian at ubuntu.com (Brian Murray) Date: Thu, 3 Jan 2013 08:46:10 -0800 Subject: What to do with Wubi bugs ? In-Reply-To: References: Message-ID: <20130103164610.GG2949@murraytwins.com> On Fri, Dec 28, 2012 at 10:41:21AM -0500, Thomas Ward wrote: > That's what penguin42 (Dave) and I agreed on, and what hggdh also said in > -bugs. The other part of this is whether we should update > https://wiki.ubuntu.com/Bugs/FindRightPackage#During_boot for Wubi-specific > things, such that we tell them "For Wubi bugs, you should file against just > "Ubuntu" and then mention wubi in the subject" or something, so that > bugcontrollers or bug triagers can go through and change it to affect Wubi. It seems likely that if people are having problems during boot that they are not able to get to a point where they can use 'ubuntu-bug' to file the bug report. Subsequently, filing the bug about the Wubi project would make sense. However, if they can use ubuntu-bug they should as it may provide helpful debugging information. > I think we do need to update the wiki for that, but as I don't like > changing things without discussion (go sift through bugsquad mailing list's > history for "core" vs. "non-core", we had a discussion on that), I thought > it'd be prudent to discuss it on the mailing list, and if need be include > devel or some other list in the discussion. The particular discussion you mention was a rather tricky and contentious one. The vast majority of them will not be and everyone should feel free to update the wiki, especially since the mailing list is, or should be, subscribed to changes about wiki pages we care about. -- 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 hggdh2 at ubuntu.com Thu Jan 3 16:50:16 2013 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Thu, 03 Jan 2013 10:50:16 -0600 Subject: Low bug triage activity all around In-Reply-To: References: <20130103101826.GE6293@upf.edu> Message-ID: <7352632.qIQUP0O8ND@xango3> On Thursday, January 03, 2013 09:18:57 Pedro Villavicencio Garrido wrote: > Mentoring didn't work that well, we had some good students that's > true, but (in my experience) they were the minimum (1 out of 10). So i > agree with most of the opinions on this matter, maybe the mentoring > program wasn't the better for the quantity and the kind of work we do > in the team. It seems though that helping out in the channel works a > lot better, so instead i think we should be more responsive when > someone ask something about a bug in the #ubuntu-bugs . What we found out was a mix of two main issues: (1) triaging is not that easy, no matter what people say (and they use to state, everywhere, that this is an easy way to get started); (2) most of the mentees expected the mentors to hold their hands the whole time. For the first one: triaging is continuously confused with level 1 support. It is *not*. There is no script we can follow that will cover the majority of the bugs. A triager needs to learn to understand what was written/passed on, to find root cause(s), and to correctly determine packages. This is not an easy way to start up, but it is a fantastic way to understand what is going on. (In a different reality, long time ago and with a different outfit, I put forth the requirement that developers should do at least a month of triaging every year; with open source, a lot of developers automatically do that.) For the second... this was a surprise to some of us. We expected to answer questions, doubts, to help. We did NOT expect to see one bug per week worked on, and only because we pinged the mentees about what they were doing -- and did it for them. Mentoring could still work, but would require changes. ..C.. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. URL: From brian at ubuntu.com Thu Jan 3 16:51:23 2013 From: brian at ubuntu.com (Brian Murray) Date: Thu, 3 Jan 2013 08:51:23 -0800 Subject: What to do with Wubi bugs ? In-Reply-To: References: Message-ID: <20130103165123.GH2949@murraytwins.com> On Sat, Dec 29, 2012 at 12:26:46AM +0800, Ho Wan Chan wrote: > Well since it is indeed difficult to report bug using apport if it is about > Wubi (there aren't something like a wubi package) so I think that why don't > we tell them to indeed report bugs against Ubuntu, but then add a Wubi tag > to the bug while reporting? That might be easier for bug triagers to change > the specific project to Wubi. If we can determine a way to know whether or not a system is using Wubi it'd be better to have apport automatically add this tag to the bug report rather than requiring the reporter to add it. I'm happy to help with this effort whether it be searching bug attachments or adding the code to apport - just let me know for what to look. However, not all bugs with this tag should be moved over to the Wubi project as the majority of bugs reported by Wubi users will be regular Ubuntu software bugs. (For example a bug about gnumeric is not related to them using Wubi.) -- 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 cjk at teamcharliesangels.com Thu Jan 3 17:07:39 2013 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Thu, 3 Jan 2013 10:07:39 -0700 Subject: Proposal to merge #ubuntu-quality and #ubuntu-bugs In-Reply-To: References: <50E59842.5020906@ubuntu.com> Message-ID: <20130103100739.6f1bca8b@teamcharliesangels.com> On Thu, 3 Jan 2013 21:08:44 +0500 Omer Akram wrote: > I would say that then the word ubuntu-quality is a bit too broad than its > actual purpose, i should have researched more but i did think they were not > limited to ISO testing only. As you stated that's not the case then its a > bit of misunderstanding about #ubuntu-quality on my end. > > > On Thu, Jan 3, 2013 at 9:01 PM, Thomas Ward wrote: > > > On Thu, Jan 3, 2013 at 9:40 AM, Micah Gersten wrote: > > > On 01/03/2013 07:14 AM, Omer Akram wrote: > > >> Hi All > > >> > > >> Just recently there started a discussion on Ubuntu bug squad list > > >> about less people getting involved in bug triage along the discussion > > >> there were a few points raised which let me to put the idea of merging > > >> #ubuntu-quality and #ubuntu-bugs into one. Ultimately both have the > > >> same goal that is talking about quality in Ubuntu. > > >> > > >> At time people testing Ubuntu ISO will raise their bugs in > > >> #ubuntu-quality and discussions may take place there. People may or > > >> may not be available in both channels but since I believe people do > > >> talk mostly about bug reports in those channels (though > > >> #ubuntu-quality do have other topics as well) but I think merging them > > >> will make a few things easier one will be that there will be mostly a > > >> unified place for people to talk about bugs (i know people may talk in > > >> #ubuntu+1 or #ubuntu-desktop as well but those channels have their own > > >> reasons for exisitance) > > >> > > >> Here I might not have a lot of point to argue plus I am never great > > >> with words but the overall notion is that I believe that it will > > >> result in a benefit for Ubuntu due to having a concentrated place to > > >> talk bugs. > > >> > > >> Thoughts/Suggestions/Pros/Cons all welcome and appreciated > > >> > > >> Thanks! > > >> > > > I'm not sure I agree with this. #ubuntu-bugs is specifically for bug > > > triage, whereas #ubuntu-quality seems to not have a defined topic. > > > Whereas I'm likely to watch #ubuntu-bugs for people who need help with > > > triage, I'm not necessarily interested in most of what happens with > > > image testing and the issues that arise from it. This is not to say > > > that I don't care, rather that I'm not necessarily going to commit my > > > time to such issues. > > > You could in theory condense #ubuntu-devel, -desktop, and -release into > > > quality as well as the goal is quality, but I don't see that as being > > > productive. > > > Thanks, > > > Micah > > > > > > -- > > > Ubuntu-bugsquad mailing list > > > Ubuntu-bugsquad at lists.ubuntu.com > > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > > I am in full agreement with Micah, what #ubuntu-quality does is ISO > > testing and other ISO/image related testing, and not necessarily bug > > triage. I lurk in both #ubuntu-bugs and #ubuntu-quality. The > > channels have separate goals. And in #ubuntu-bugs, I'm also more than > > happy to help out with bug triaging, but I don't want to see ISO > > testing bugs and related stuff in #ubuntu-bugs either. > > > > Since not everyone's responding to both the BugSquad and > > ubuntu-quality lists, I've sent this response to both. > > > > ------ > > Thomas > > Ubuntu BugSquad Member > > > > -- > > Ubuntu-bugsquad mailing list > > Ubuntu-bugsquad at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > I was against the name change for testing to quality when it happened, and I still believe the main results is confusion. quality in most places is short for "quality assurance" or "quality control". Neither applies to ubuntu testing alone. However, in Ubuntu, ubuntu-quality is simply a new name for testing. It is not a name to cover all quality of the product. With this definition in mind, to combine both quality and bug-triage would be wrong, since triage and testing do not mean the same things. Until Canonical decides once again that Quality means more than testing a product, this can not happen. -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] From slickymaster at gmail.com Thu Jan 3 17:41:09 2013 From: slickymaster at gmail.com (David Manuel Pires) Date: Thu, 3 Jan 2013 17:41:09 +0000 Subject: Low bug triage activity all around In-Reply-To: References: <20130103101826.GE6293@upf.edu> <50E57A31.9040505@camelotsweb.de> Message-ID: On Thu, Jan 3, 2013 at 1:02 PM, Omer Akram wrote: > > > So for that we would need few people to show interest and ensure they will > stay on IRC to help any people asking questions. Please show yourself if > you would like to. > > If all agree we can quickly start a bug hug day as soon as Monday or > something by announcing on this list. We should select some simple package > like transmission (or you have other suggestions?) for the day. > > More suggestions/objections welcome. > > > > As for me I'm willing to help, at least asking questions and showing tons of doubts. Regards. David Manuel Pires -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Thu Jan 3 17:20:40 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 03 Jan 2013 17:20:40 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Valgrind=22_by_brian-murray?= Message-ID: <20130103172040.26752.11569@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Valgrind" page has been changed by brian-murray: http://wiki.ubuntu.com/Valgrind?action=diff&rev1=16&rev2=17 This makes it ideal for tracking down segmentation faults, bus errors, and general memory leaks. - Please ensure you have packages with debug symbols installed. You can do this by following the instructions at DebuggingProgramCrash. + /!\ Please ensure you have packages with debug symbols installed. You can do this by following the instructions at DebuggingProgramCrash. 1. Make sure Valgrind is installed. {{{ sudo apt-get install valgrind @@ -20, +20 @@ 1. Remove any old Valgrind logs: {{{ rm valgrind.log* }}} - 1. Start the program under control of `memcheck` (valgrind can't solve paths, so you should feed it the full program path, to get it: `which `): {{{ + 1. Start the program under control of `memcheck`: + {{{ - G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log + G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log $(which ) }}} + 1. N.B. valgrind can't solve paths, so you should feed it the full program path, to get it: $(which ) 1. The program will start. It may take a while; this is normal, because Valgrind must perform extensive checking to detect memory errors. 1. Perform any actions necessary to reproduce the crash. 1. Package up the log files (no need if there is only one): {{{ From hggdh2 at ubuntu.com Thu Jan 3 18:25:01 2013 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Thu, 03 Jan 2013 12:25:01 -0600 Subject: Proposal to merge #ubuntu-quality and #ubuntu-bugs In-Reply-To: References: Message-ID: <3073085.7EipBsqSCK@xango3> On Thursday, January 03, 2013 18:14:53 Omer Akram wrote: > Hi All > > Just recently there started a discussion on Ubuntu bug squad list about > less people getting involved in bug triage along the discussion there were > a few points raised which let me to put the idea of merging #ubuntu-quality > and #ubuntu-bugs into one. Ultimately both have the same goal that is > talking about quality in Ubuntu. As said already elsewhere, joining -bugs and -quality is not ideal. Bugs (and triaging) is a subset of quality, and has specific issues; conflating both together is prone to generate more noise, with very specific discussions derailing the overall view of quality control/assurance. Perhaps it would be more productive to review the whole process of bugs, triaging, etc. For example: * lack of quality/detail/references on bugs. A lot of bugs do not state the bare minimum needed (like Ubuntu version, package version, etc). Many, even when set to triaged, lack details on how to reproduce. * lack of responsible parties. We should have teams/groups/whatever-you-want- to-call-them that are responsible for triaging, tagging, raising attention on "areas of interest". One such area of interest could be, for example, the Ubuntu version (bugs that affect Lucid, or Precise, etc), another could be technology (email clients, email servers, browsers, KDE, Gnome (both under the Gnome shell and under Unity)), and so on. * expanding apport hook usage. A *lot* of packages do not have apport hooks. The infrastructure is there, we need to use it. * reviewing the bug work processes, and re-adjusting them. Bugs are technical reports of problems, and should be looked at, and worked on, as such. So, bugs.lp.net should not be the entry point for an user having a problem -- perhaps, answers.ubuntu.com should be it, and bugs would then be "promoted" from a.u.c. And so on. But -- let it be clear -- I agree with Omer: we have to do something. Cheers, ..C.. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. URL: From timo.jyrinki at gmail.com Fri Jan 4 14:31:51 2013 From: timo.jyrinki at gmail.com (Timo Jyrinki) Date: Fri, 4 Jan 2013 16:31:51 +0200 Subject: Low bug triage activity all around In-Reply-To: References: <20130103101826.GE6293@upf.edu> <50E57A31.9040505@camelotsweb.de> Message-ID: 2013/1/2 AG Restringere : > fact that many of the old bugs are for versions of Ubuntu that have already > reached "end of life" such as 11.10 or 10.04 and are no longer supported. I Note that 10.04 is LTS release so still supported until 2013 (desktop) / 2015 (server). 2013/1/3 Omer Akram : > More suggestions/objections welcome. In general regarding the development releases, there is the change of thinking that should be pushed to the community that http://cdimage.ubuntu.com/daily-live/current/ _is_ the new Alpha, available whenever you want it. Maybe the daily should be renamed to alpha... Also in the past when there still were Alpha:s, I noticed many people are fixated on the terminology and don't want to install anything else than the image that has a real name on it. Now +1 has been in alpha-releasable stage all the time for a couple of releases (since https://wiki.ubuntu.com/PlusOneMaintenanceTeam), but there are years of habits of thinking there are real alpha releases and then random snapshots that may be totally broken. -Timo From om26er at ubuntu.com Sat Jan 5 19:54:22 2013 From: om26er at ubuntu.com (Omer Akram) Date: Sun, 6 Jan 2013 00:54:22 +0500 Subject: Low bug triage activity all around In-Reply-To: <50E87A94.4010500@ubuntu.com> References: <20130101174622.GA22665@gallifrey> <50E87A94.4010500@ubuntu.com> Message-ID: On Sun, Jan 6, 2013 at 12:10 AM, Gunnar Hjalmarsson wrote: > On 2013-01-01 19:04, Omer Akram wrote: > > On Tue, Jan 1, 2013 at 10:46 PM, Dr. David Alan Gilbert wrote: > >> On 2013-01-01 18:21, Omer Akram wrote: > >>> So I think we need to think of some ways to improve the > >>> situation and get more people involved into this effort. Does > >>> anyone have suggestions/comments about this matter. > >> > >> Most of the irc seems to have been pretty dead over xmas, I'm > >> guessing there aren't many of us doing it just for the heck of it > >> at the moment. There is also the danger that perhaps some of the > >> others got a life and we aren't getting new ones in. > > > > That may be a factor... > > Well, let's hope that community efforts do not depend on people without > a life. > The intent of that sentence was to make it clear that the issue have been there way before xmas. > > -- > Gunnar Hjalmarsson > https://launchpad.net/~gunnarhj > > -- > ubuntu-desktop mailing list > ubuntu-desktop at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gunnarhj at ubuntu.com Sat Jan 5 19:10:12 2013 From: gunnarhj at ubuntu.com (Gunnar Hjalmarsson) Date: Sat, 05 Jan 2013 20:10:12 +0100 Subject: Low bug triage activity all around In-Reply-To: References: <20130101174622.GA22665@gallifrey> Message-ID: <50E87A94.4010500@ubuntu.com> On 2013-01-01 19:04, Omer Akram wrote: > On Tue, Jan 1, 2013 at 10:46 PM, Dr. David Alan Gilbert wrote: >> On 2013-01-01 18:21, Omer Akram wrote: >>> So I think we need to think of some ways to improve the >>> situation and get more people involved into this effort. Does >>> anyone have suggestions/comments about this matter. >> >> Most of the irc seems to have been pretty dead over xmas, I'm >> guessing there aren't many of us doing it just for the heck of it >> at the moment. There is also the danger that perhaps some of the >> others got a life and we aren't getting new ones in. > > That may be a factor... Well, let's hope that community efforts do not depend on people without a life. -- Gunnar Hjalmarsson https://launchpad.net/~gunnarhj From gunnarhj at ubuntu.com Sat Jan 5 20:55:46 2013 From: gunnarhj at ubuntu.com (Gunnar Hjalmarsson) Date: Sat, 05 Jan 2013 21:55:46 +0100 Subject: Low bug triage activity all around In-Reply-To: References: <20130101174622.GA22665@gallifrey> <50E87A94.4010500@ubuntu.com> Message-ID: <50E89352.8030203@ubuntu.com> On 2013-01-05 20:54, Omer Akram wrote: > On Sun, Jan 6, 2013 at 12:10 AM, Gunnar Hjalmarsson > wrote: >> On 2013-01-01 19:04, Omer Akram wrote: >>> On Tue, Jan 1, 2013 at 10:46 PM, Dr. David Alan Gilbert wrote: >>>> Most of the irc seems to have been pretty dead over xmas, I'm >>>> guessing there aren't many of us doing it just for the heck of it >>>> at the moment. There is also the danger that perhaps some of the >>>> others got a life and we aren't getting new ones in. >>> >>> That may be a factor... >> >> Well, let's hope that community efforts do not depend on people without >> a life. > > The intent of that sentence was to make it clear that the issue have > been there way before xmas. Ok. And I agree on that. My remark was solely due to David's mentioning of people with a life automatically stepping back. But since I didn't receive David's message directly, I replied to your message. ;-) -- Gunnar Hjalmarsson https://launchpad.net/~gunnarhj From es20490446e at gmail.com Mon Jan 7 23:36:30 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Tue, 08 Jan 2013 00:36:30 +0100 Subject: Low bug triage activity all around In-Reply-To: References: Message-ID: <50EB5BFE.7060704@gmail.com> Please, accept me to join Ubuntu BugSquad and BugControl in Launchpad and I will show you what Raring is going to be. If you need more info about me and how familiar I am with the triaging process, you can have a look at my profile in Launchpad . Thank you El 02/01/13 12:30, Omer Akram escribió: > For that case I think someone should step in from our community. > Anyone willing to lead the effort of creating a stronger community > around bug management in Ubuntu? I will surely help where I can. > > > On Wed, Jan 2, 2013 at 12:43 AM, Fabio Marconi > > wrote: > > On 01/01/2013 18:21, Omer Akram wrote: >> Hey all, >> >> I have been involved in bug triage for a while in Ubuntu and it >> seems this scene is not that active it used to be although alot >> of great folks from our community are highly devoted. >> >> I am not sure about the reason behind that but one thing I am >> sure is that previously we had running efforts like "Bug Days" >> where a certain package was selected and all of the Ubuntu Bug >> Squad was invited to participate in triaging those bugs. >> >> Another reason which could be related is that now there is no one >> in the Ubuntu desktop team (or Canonical) to lead the effort of >> Bug management and community involvement previously Pedro played >> a big role there. >> >> So I think we need to think of some ways to improve the situation >> and get more people involved into this effort. Does anyone have >> suggestions/comments about this matter. >> >> Thanks >> >> > Yes, pedro_ place still actually vacant, I cannot see any other > person with his charisma andcommunicativity at the moment, I > cannot perceive enthusiasm in this group. > Was a great fault for a group that was growing up, now seems to me > that everyone stay on its own, without willingness to mentor, > explain and create a positive group around him. > Just my 5 cents. > Have a great year > Fabio > > -- > 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: -------------- 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: From hggdh2 at ubuntu.com Tue Jan 8 14:10:59 2013 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Tue, 08 Jan 2013 08:10:59 -0600 Subject: Low bug triage activity all around In-Reply-To: <50EB5BFE.7060704@gmail.com> References: <50EB5BFE.7060704@gmail.com> Message-ID: <2061598.D0So4SbAHO@xango3> On Tuesday, January 08, 2013 00:36:30 Alberto Salvia Novella wrote: > Please, accept me to join Ubuntu BugSquad and BugControl in Launchpad > and I will show you what Raring is going to be. If you need more info > about me and how familiar I am with the triaging process, you can have a > look at my profile in Launchpad . My fault there regarding the Ubuntu-BugSquad. I have added you in (and processed all other pending requests). For Ubuntu BugControl the process is different. You must show you understand how we use status and importance, and you must show bugs you triaged. This process is explained in [1]. Cheers, ..C.. [1] https://wiki.ubuntu.com/UbuntuBugControl -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. URL: From noreply at ubuntu.com Tue Jan 8 15:05:43 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 08 Jan 2013 15:05:43 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_shankao?= Message-ID: <20130108150543.14543.72521@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 shankao: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=364&rev2=365 Comment: Remove broken link Occasionally, bug reporters will report a bug about a version of a package not provided by Ubuntu or less often about software not provided by Ubuntu. In which case we can not help them and the bug should be set to '''Invalid'''. - ||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|| + ||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, check https://help.ubuntu.com/community/Repositories|| == Fixed in Development release while still existing in a previous release == From ispinn at gmail.com Tue Jan 8 17:11:15 2013 From: ispinn at gmail.com (Doug Parker) Date: Tue, 8 Jan 2013 12:11:15 -0500 Subject: Launchpad bug report -- which package? Message-ID: I'm about to submit a Launchpad bug report. I'm on a Mac G5 PowerPC running OS X 10.5.8 and Ubuntu 12.04.01 dual installed using yaboot, and it's about some rfkill output that may solve a b43 broadcom wireless problem for powerpc users. I'm kinda proud of what I've uncovered so far... Here's my question: when opening the Launchpad report, under what package do I submit it? I'm lost on that one... 2nd question: I'm a pretty smart guy, but I can't figure out the doorway in to Launchpad to actually create the bug report. I mean... I can't figure out where on Launchpad to actually get started on the bug report. Can you help, pretty please? Thanks -- Doug www.ispinn.com | ispinn at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From pletendre at gmail.com Tue Jan 8 19:12:44 2013 From: pletendre at gmail.com (Philippe Letendre) Date: Tue, 8 Jan 2013 14:12:44 -0500 Subject: Ubuntu-bugsquad Digest, Vol 79, Issue 9 In-Reply-To: References: Message-ID: <1D1F8E1A-4F5E-4624-BF99-57249E9073FE@gmail.com> Hey Rob I can help you with that no problem just send me a detailed step by step of what you tried to accomplish and I can send you a walk through containing all the necessary steps to resolve this issue. Philippe Letendre On 2013-01-05, at 7:00 AM, ubuntu-bugsquad-request at lists.ubuntu.com wrote: > Send Ubuntu-bugsquad mailing list submissions to > ubuntu-bugsquad at lists.ubuntu.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > or, via email, send a message with subject or body 'help' to > ubuntu-bugsquad-request at lists.ubuntu.com > > You can reach the person managing the list at > ubuntu-bugsquad-owner at lists.ubuntu.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Ubuntu-bugsquad digest..." > > > Today's Topics: > > 1. Re: Low bug triage activity all around (Timo Jyrinki) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 4 Jan 2013 16:31:51 +0200 > From: Timo Jyrinki > To: Omer Akram , AG Restringere > > Cc: Ubuntu BugSquad > Subject: Re: Low bug triage activity all around > Message-ID: > > Content-Type: text/plain; charset=UTF-8 > > 2013/1/2 AG Restringere : >> fact that many of the old bugs are for versions of Ubuntu that have already >> reached "end of life" such as 11.10 or 10.04 and are no longer supported. I > > Note that 10.04 is LTS release so still supported until 2013 (desktop) > / 2015 (server). > > 2013/1/3 Omer Akram : >> More suggestions/objections welcome. > > In general regarding the development releases, there is the change of > thinking that should be pushed to the community that > http://cdimage.ubuntu.com/daily-live/current/ _is_ the new Alpha, > available whenever you want it. Maybe the daily should be renamed to > alpha... > > Also in the past when there still were Alpha:s, I noticed many people > are fixated on the terminology and don't want to install anything else > than the image that has a real name on it. Now +1 has been in > alpha-releasable stage all the time for a couple of releases (since > https://wiki.ubuntu.com/PlusOneMaintenanceTeam), but there are years > of habits of thinking there are real alpha releases and then random > snapshots that may be totally broken. > > -Timo > > > > ------------------------------ > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > End of Ubuntu-bugsquad Digest, Vol 79, Issue 9 > ********************************************** From shankao at gmail.com Wed Jan 9 04:28:51 2013 From: shankao at gmail.com (shankao at gmail.com) Date: Wed, 9 Jan 2013 12:28:51 +0800 Subject: Launchpad bug report -- which package? In-Reply-To: References: Message-ID: In order to report a bug, take a look to https://help.ubuntu.com/community/ReportingBugs I have noticed that there is not a direct link to do that in Ubuntu's official website. Shouldn't it provide one? 2013/1/9 Doug Parker > I'm about to submit a Launchpad bug report. > > I'm on a Mac G5 PowerPC running OS X 10.5.8 and Ubuntu 12.04.01 dual > installed using yaboot, and it's about some rfkill output that may solve a > b43 broadcom wireless problem for powerpc users. I'm kinda proud of what > I've uncovered so far... > > Here's my question: when opening the Launchpad report, under what package > do I submit it? I'm lost on that one... > > 2nd question: I'm a pretty smart guy, but I can't figure out the doorway > in to Launchpad to actually create the bug report. I mean... I can't figure > out where on Launchpad to actually get started on the bug report. Can you > help, pretty please? > > Thanks > > -- > Doug > www.ispinn.com | ispinn at gmail.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: From alessandro.menti at hotmail.it Wed Jan 9 07:12:05 2013 From: alessandro.menti at hotmail.it (Alessandro Menti) Date: Wed, 9 Jan 2013 08:12:05 +0100 Subject: Launchpad bug report -- which package? In-Reply-To: References: , Message-ID: > I have noticed that there is not a direct link to do that in Ubuntu's > official website. Shouldn't it provide one? There is a direct link, although it is a bit buried deep into the bug filing instructions ([1]). It is reserved, however, for the infrequent cases when ubuntu-bug can not be used, as debugging information and log files must be attached manually in that case. Alessandro Menti [1] https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_at_Launchpad.net -- A neutron walks into a bar and asks how much for a drink. The bartender replies "for you, no charge".      -- Sheldon Cooper, The Big Bang Theory From brian at ubuntu.com Wed Jan 9 15:46:01 2013 From: brian at ubuntu.com (Brian Murray) Date: Wed, 9 Jan 2013 07:46:01 -0800 Subject: Launchpad bug report -- which package? In-Reply-To: References: Message-ID: <20130109154601.GI28601@murraytwins.com> On Wed, Jan 09, 2013 at 08:12:05AM +0100, Alessandro Menti wrote: > > I have noticed that there is not a direct link to do that in Ubuntu's > > official website. Shouldn't it provide one? > There is a direct link, although it is a bit buried deep into the bug > filing instructions ([1]). It is reserved, however, for the infrequent > cases when ubuntu-bug can not be used, as debugging information and log > files must be attached manually in that case. I believe they meant that there is no link from www.ubuntu.com to the wiki page regarding how to report bugs. -- 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 Jan 9 15:48:49 2013 From: brian at ubuntu.com (Brian Murray) Date: Wed, 9 Jan 2013 07:48:49 -0800 Subject: Launchpad bug report -- which package? In-Reply-To: References: Message-ID: <20130109154849.GJ28601@murraytwins.com> On Tue, Jan 08, 2013 at 12:11:15PM -0500, Doug Parker wrote: > I'm about to submit a Launchpad bug report. > > I'm on a Mac G5 PowerPC running OS X 10.5.8 and Ubuntu 12.04.01 dual > installed using yaboot, and it's about some rfkill output that may solve a > b43 broadcom wireless problem for powerpc users. I'm kinda proud of what > I've uncovered so far... > > Here's my question: when opening the Launchpad report, under what package > do I submit it? I'm lost on that one... > > 2nd question: I'm a pretty smart guy, but I can't figure out the doorway in > to Launchpad to actually create the bug report. I mean... I can't figure > out where on Launchpad to actually get started on the bug report. Can you > help, pretty please? The ideal way to report a bug is using the command 'ubuntu-bug' on the affected system as it will gather detailed information regarding the system which will aid developers in debugging the issue. A good package to use with ubuntu-bug for this particular issue is linux - so 'ubuntu-bug linux'. -- 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 noreply at ubuntu.com Wed Jan 9 05:02:56 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 09 Jan 2013 05:02:56 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/FindRightPackage=22_by_shan?= =?utf-8?q?kao?= Message-ID: <20130109050256.3511.62201@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=122&rev2=123 Comment: Open a new section to hint reporters If a piece of hardware is malfunctioning, typically the problem package is [[#Kernel|the kernel]]. ''However'', if the problem is with a storage device (internal or external) in 9.10 Karmic Koala or above, problems should be reported with `ubuntu-bug storage`. (If triaging, see the "Use Storage Symptom" standard reply.) + === Network === + + Usual candidate packages are the kernel (fill bugs under the "linux" package) and network-manager. + === Suspend, Hibernate, and Resume === Suspend, hibernate, and resume functionality is provided by three different packages: From oakram at gnome.org Tue Jan 15 19:52:25 2013 From: oakram at gnome.org (Omer Akram) Date: Wed, 16 Jan 2013 00:52:25 +0500 Subject: Announcing the Next Ubuntu Bug Day! - Thursday 17, Jan Message-ID: Hello Everyone, In an attempt to restore the glory of Ubuntu bug squad we are rebooting the effort of Hug Days, A hug day is a day where all of us focus on a single thing for the whole day to triage bug. The package for this Bug Hug day is Transmission . Are you looking for a way to start giving some love back to your 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! On 17th January together we will focus on triaging all the bugs of transmission with NEW status (link). Please mark off the bug that you triaged here < https://wiki.ubuntu.com/UbuntuBugDay/20130117> 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 I missed something please add that) Thanks!, see you then. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chilicuil at ubuntu.com Thu Jan 17 16:51:35 2013 From: chilicuil at ubuntu.com (Javier P.L.) Date: Thu, 17 Jan 2013 10:51:35 -0600 Subject: Announcing the Next Ubuntu Bug Day! - Thursday 17, Jan In-Reply-To: References: Message-ID: Hi Omer, Pretty cool initiative, I'll be triaging in the afternoon in my timezone, in addition to #ubuntu-bugs, I'll triage bugs on a hangout, if anyone of the team want to join, you're welcome. https://plus.google.com/u/0/events/cv48ig6bfbuehpj07imst7kuhr4 Have fun On Tue, Jan 15, 2013 at 1:52 PM, Omer Akram wrote: > Hello Everyone, > > In an attempt to restore the glory of Ubuntu bug squad we are rebooting > the effort of Hug Days, A hug day is a day where all of us focus on a > single thing for the whole day to triage bug. > The package for this Bug Hug day is Transmission > . > > Are you looking for a way to start giving some love back to your 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! > > On 17th January together we will focus on triaging all the bugs of > transmission with NEW status (link). > Please mark off the bug that you triaged here < > https://wiki.ubuntu.com/UbuntuBugDay/20130117> > > 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 I missed something please add that) > Thanks!, see you then. > > > -- > 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: From oakram at gnome.org Fri Jan 18 13:59:08 2013 From: oakram at gnome.org (Omer Akram) Date: Fri, 18 Jan 2013 18:59:08 +0500 Subject: We had a successful bug day, Thank you Message-ID: Hi! Yesterday we had our first bug after quite a while. The results of that are quite fascinating. When we started we had 71 bug with the status NEW now at time of this writing they are 3. That's quite motivating. Now the question is what lies a head, I think now we should decide when do we want to do our next bug day, which package we want to target and suggest any improvements that could be made. Thank you all. -------------- next part -------------- An HTML attachment was scrubbed... URL: From walter.garcia at upf.edu Fri Jan 18 14:15:48 2013 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Fri, 18 Jan 2013 15:15:48 +0100 Subject: We had a successful bug day, Thank you In-Reply-To: References: Message-ID: <20130118141548.GA1356@upf.edu> * Omer Akram, oakram at gnome.org [18/01/13 14:59]: > Now the question is what lies a head, I think now we should decide when do > we want to do our next bug day, which package we want to target and suggest > any improvements that could be made. I think that ideally they should be weekly, but of course this can cause attrition of the triagers. In any case if the group is large enough even if there is some rotation it could work. As for packages they are easy to choose now that there haven't been hug days for a while, I checked today "totem" for instance and there were more than 100 "new" bugs. It's harder to come up with more imaginative lists, like "bugs without a package" or similar, there is where more experienced triagers can help. And these more targeted bugs sometimes are the easiest to triage. As for suggestions, I think we should also include "confirmed" bugs, as a good amount of these are also untouched. I remember there used to be two lists at the wiki page, one for new and the other one for confirmed bugs. Of course it is useful to start with the new ones, but a review of the confirmed bugs is also helpful. -- Walter Garcia-Fontes From es20490446e at gmail.com Fri Jan 18 14:27:49 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Fri, 18 Jan 2013 15:27:49 +0100 Subject: We had a successful bug day, Thank you In-Reply-To: <20130118141548.GA1356@upf.edu> References: <20130118141548.GA1356@upf.edu> Message-ID: <50F95BE5.7050102@gmail.com> Perhaps performing monthly? El 18/01/13 15:15, Walter Garcia-Fontes escribió: > * Omer Akram, oakram at gnome.org [18/01/13 14:59]: >> Now the question is what lies a head, I think now we should decide when do >> we want to do our next bug day, which package we want to target and suggest >> any improvements that could be made. > I think that ideally they should be weekly, but of course this can > cause attrition of the triagers. In any case if the group is large > enough even if there is some rotation it could work. > > As for packages they are easy to choose now that there haven't been hug > days for a while, I checked today "totem" for instance and there were > more than 100 "new" bugs. > > It's harder to come up with more imaginative lists, like "bugs without > a package" or similar, there is where more experienced triagers can > help. And these more targeted bugs sometimes are the easiest to triage. > > As for suggestions, I think we should also include "confirmed" bugs, > as a good amount of these are also untouched. I remember there used to be > two lists at the wiki page, one for new and the other one for > confirmed bugs. Of course it is useful to start with the new ones, but > a review of the confirmed bugs is also helpful. > -------------- 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: From brian at ubuntu.com Fri Jan 18 16:30:07 2013 From: brian at ubuntu.com (Brian Murray) Date: Fri, 18 Jan 2013 08:30:07 -0800 Subject: We had a successful bug day, Thank you In-Reply-To: <20130118141548.GA1356@upf.edu> References: <20130118141548.GA1356@upf.edu> Message-ID: <20130118163006.GA28601@murraytwins.com> On Fri, Jan 18, 2013 at 03:15:48PM +0100, Walter Garcia-Fontes wrote: > * Omer Akram, oakram at gnome.org [18/01/13 14:59]: > > Now the question is what lies a head, I think now we should decide when do > > we want to do our next bug day, which package we want to target and suggest > > any improvements that could be made. > > I think that ideally they should be weekly, but of course this can > cause attrition of the triagers. In any case if the group is large > enough even if there is some rotation it could work. > > As for packages they are easy to choose now that there haven't been hug > days for a while, I checked today "totem" for instance and there were > more than 100 "new" bugs. > > It's harder to come up with more imaginative lists, like "bugs without > a package" or similar, there is where more experienced triagers can > help. And these more targeted bugs sometimes are the easiest to triage. > > As for suggestions, I think we should also include "confirmed" bugs, > as a good amount of these are also untouched. I remember there used to be > two lists at the wiki page, one for new and the other one for > confirmed bugs. Of course it is useful to start with the new ones, but > a review of the confirmed bugs is also helpful. Keeping in mind that Launchpad automatically marks bugs as Confirmed that have received a duplicate Confirmed bugs may actually be a better starting point than New bugs. Because although the bug is Confirmed this may have been done automatically and there may be missing information in the bug report. It is also possible to order a group of bug tasks by the date they were confirmed so one could create a table of bugs with the most recently confirmed at the top. -- 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 matthew.fischer at canonical.com Fri Jan 18 16:31:39 2013 From: matthew.fischer at canonical.com (Matt Fischer) Date: Fri, 18 Jan 2013 09:31:39 -0700 Subject: We had a successful bug day, Thank you In-Reply-To: <50F95BE5.7050102@gmail.com> References: <20130118141548.GA1356@upf.edu> <50F95BE5.7050102@gmail.com> Message-ID: <50F978EB.4060107@canonical.com> +1 to monthly On 01/18/2013 07:27 AM, Alberto Salvia Novella wrote: > Perhaps performing monthly? > > > El 18/01/13 15:15, Walter Garcia-Fontes escribió: >> * Omer Akram, oakram at gnome.org [18/01/13 14:59]: >>> Now the question is what lies a head, I think now we should decide >>> when do >>> we want to do our next bug day, which package we want to target and >>> suggest >>> any improvements that could be made. >> I think that ideally they should be weekly, but of course this can >> cause attrition of the triagers. In any case if the group is large >> enough even if there is some rotation it could work. >> >> As for packages they are easy to choose now that there haven't been hug >> days for a while, I checked today "totem" for instance and there were >> more than 100 "new" bugs. >> >> It's harder to come up with more imaginative lists, like "bugs without >> a package" or similar, there is where more experienced triagers can >> help. And these more targeted bugs sometimes are the easiest to triage. >> >> As for suggestions, I think we should also include "confirmed" bugs, >> as a good amount of these are also untouched. I remember there used >> to be >> two lists at the wiki page, one for new and the other one for >> confirmed bugs. Of course it is useful to start with the new ones, but >> a review of the confirmed bugs is also helpful. >> > > > > -- Matthew (Matt) Fischer LP: http://launchpad.net/~mfisch IRC: mfisch -------------- next part -------------- An HTML attachment was scrubbed... URL: From marconifabio at hotmail.it Fri Jan 18 19:07:55 2013 From: marconifabio at hotmail.it (Fabio Marconi) Date: Fri, 18 Jan 2013 20:07:55 +0100 Subject: We had a successful bug day, Thank you In-Reply-To: <50F978EB.4060107@canonical.com> References: <20130118141548.GA1356@upf.edu> <50F95BE5.7050102@gmail.com> <50F978EB.4060107@canonical.com> Message-ID: Hallo everybody. Completely in accord with Brian about the convenience to work on 'Confirmed' bugs. I also think that a 15 days cadence with more than one working day could be a valid option. I've noted that hugday-tool is no more present on raring, so asking if someone can resurrect it, and with a GUI would be great. Thanks Fabio -------------- next part -------------- An HTML attachment was scrubbed... URL: From fco.plj at gmail.com Fri Jan 18 20:26:15 2013 From: fco.plj at gmail.com (Javier P.L.) Date: Fri, 18 Jan 2013 14:26:15 -0600 Subject: We had a successful bug day, Thank you In-Reply-To: References: Message-ID: <20130118202614.GA17787@sup.lan> On 18/01/13 at 06:59pm, Omer Akram wrote: > Hi! > > Yesterday we had our first bug after quite a while. The results of that are > quite fascinating. When we started we had 71 bug with the status NEW now at > time of this writing they are 3. That's quite motivating. > > Now the question is what lies a head, I think now we should decide when do > we want to do our next bug day, which package we want to target and suggest > any improvements that could be made. > > Thank you all. > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad I'd suggest every 15 days with two lists, one for new an another one for confirmed. From matthew.fischer at canonical.com Sun Jan 20 05:41:46 2013 From: matthew.fischer at canonical.com (Matt Fischer) Date: Sat, 19 Jan 2013 22:41:46 -0700 Subject: We had a successful bug day, Thank you In-Reply-To: References: Message-ID: <50FB839A.7010203@canonical.com> On 01/18/2013 06:59 AM, Omer Akram wrote: > Hi! > > Yesterday we had our first bug after quite a while. The results of > that are quite fascinating. When we started we had 71 bug with the > status NEW now at time of this writing they are 3. That's quite > motivating. > > Now the question is what lies a head, I think now we should decide > when do we want to do our next bug day, which package we want to > target and suggest any improvements that could be made. > > Thank you all. > > Do we have a wiki area where we can start a list of suggested Hug Day packages? I'd like to put in my vote for Gnome Terminal. I use it constantly, usually 20 at a time, and there are 176 New bugs and 23 Incompletes (with response) and all of those need action. -- Matthew (Matt) Fischer LP: http://launchpad.net/~mfisch IRC: mfisch -------------- next part -------------- An HTML attachment was scrubbed... URL: From om26er at ubuntu.com Sun Jan 20 07:02:34 2013 From: om26er at ubuntu.com (Omer Akram) Date: Sun, 20 Jan 2013 12:02:34 +0500 Subject: We had a successful bug day, Thank you In-Reply-To: <50FB839A.7010203@canonical.com> References: <50FB839A.7010203@canonical.com> Message-ID: On Sun, Jan 20, 2013 at 10:41 AM, Matt Fischer < matthew.fischer at canonical.com> wrote: > On 01/18/2013 06:59 AM, Omer Akram wrote: > > Hi! > > Yesterday we had our first bug after quite a while. The results of that > are quite fascinating. When we started we had 71 bug with the status NEW > now at time of this writing they are 3. That's quite motivating. > > Now the question is what lies a head, I think now we should decide when > do we want to do our next bug day, which package we want to target and > suggest any improvements that could be made. > > Thank you all. > > > > Do we have a wiki area where we can start a list of suggested Hug Day > packages? I'd like to put in my vote for Gnome Terminal. I use it > constantly, usually 20 at a time, and there are 176 New bugs and 23 > Incompletes (with response) and all of those need action. > Yes here: https://wiki.ubuntu.com/UbuntuBugDay/Planning > > > -- > > Matthew (Matt) Fischer > LP: http://launchpad.net/~mfisch > IRC: mfisch > > > -- > 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: From webmaster at ubuntu.com Sat Jan 19 18:20:36 2013 From: webmaster at ubuntu.com (Help Ubuntu) Date: Sat, 19 Jan 2013 18:20:36 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_penalvch?= Message-ID: <20130119182036.27810.59778@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by penalvch: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=223&rev2=224 Comment: Added support note on not filing bugs against PPAs, as it is a common issue on Launchpad (ex. LP#1101799). <
><
> Many of the triagers and developers who are providing support to you, are volunteers doing so out of altruism. Please keep this in mind when making your comments. <
><
> + In general, please do not report bugs about software in [[PPA]]s on Launchpad. This is because software in PPAs are not provided by the official Ubuntu repositories. Instead, the PPA homepage would have a contact point and preference of the PPA provider. = How to report bugs = From noreply at ubuntu.com Mon Jan 21 20:31:23 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 21 Jan 2013 20:31:23 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProgramCrash=22_by_shna?= =?utf-8?q?tsel?= Message-ID: <20130121203123.14482.60113@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 shnatsel: http://wiki.ubuntu.com/DebuggingProgramCrash?action=diff&rev1=114&rev2=115 Comment: fixed broken link to [[X/Debugging]] (previously DebuggingXorg) Option "NoTrapSignals" "true" EndSection }}} - Please see DebuggingXorg for how to debug Xorg server crashes. + Please see [[X/Debugging]] for how to debug Xorg server crashes. == Info for the BugSquad == From webmaster at ubuntu.com Sat Jan 19 18:12:23 2013 From: webmaster at ubuntu.com (Help Ubuntu) Date: Sat, 19 Jan 2013 18:12:23 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_penalvch?= Message-ID: <20130119181223.27744.61643@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by penalvch: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=222&rev2=223 Comment: Added WORKAROUND on filing crash reports on Launchpad in stable releases as per LP#994921 enabled=1 }}} - Note 1) even when enabled, apport will not upload crash reports to Launchpad for a stable release (this is deliberate, see [[https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921|bug #994921]]). Instead, crash reports are uploaded to [[http://errors.ubuntu.com]]. - + /!\ Even when enabled, apport will not upload crash reports to Launchpad for a stable release. For more on this please see [[https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921|bug #994921]]. Instead, crash reports are uploaded to [[http://errors.ubuntu.com]]. To have a bug report filed on Launchpad anyways, one may open the following file via a command line: {{{ + gksudo gedit /etc/apport/crashdb.conf + }}} and change: {{{ + 'problem_types': ['Bug', 'Package'], + }}} to: {{{ + # 'problem_types': ['Bug', 'Package'], + }}} + Save, close, and try to file the crash report again via: {{{ + ubuntu-bug /var/crash/_my_crash_report.crash - Note 2) apport will appear to upload a crash report, but only actually does so if whoopsie is installed. Whoopsie is installed by default for users of ubuntu-desktop, but for users of alternative desktops, or for server users, whoopsie has to be installed manually with ''apt-get install whoopsie''. See [[https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1001630|bug #1001630]] for details. + }}} /!\ apport will appear to upload a crash report, but only actually does so if whoopsie is installed. Whoopsie is installed by default for users of ubuntu-desktop, but for users of alternative desktops, or for server users, whoopsie has to be installed manually with ''apt-get install whoopsie''. See [[https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1001630|bug #1001630]] for details. === System crash === From om26er at ubuntu.com Wed Jan 23 16:16:46 2013 From: om26er at ubuntu.com (Omer Akram) Date: Wed, 23 Jan 2013 21:16:46 +0500 Subject: We had a successful bug day, Thank you In-Reply-To: References: <50FB839A.7010203@canonical.com> Message-ID: I also think that we should do this more often than once a month, so after 2 weeks sounds great to me. If anyone on the list would like add suggestions for the next bug day this is the place: https://wiki.ubuntu.com/UbuntuBugDay/Planning On Sun, Jan 20, 2013 at 12:02 PM, Omer Akram wrote: > > > On Sun, Jan 20, 2013 at 10:41 AM, Matt Fischer < > matthew.fischer at canonical.com> wrote: > >> On 01/18/2013 06:59 AM, Omer Akram wrote: >> >> Hi! >> >> Yesterday we had our first bug after quite a while. The results of that >> are quite fascinating. When we started we had 71 bug with the status NEW >> now at time of this writing they are 3. That's quite motivating. >> >> Now the question is what lies a head, I think now we should decide when >> do we want to do our next bug day, which package we want to target and >> suggest any improvements that could be made. >> >> Thank you all. >> >> >> >> Do we have a wiki area where we can start a list of suggested Hug Day >> packages? I'd like to put in my vote for Gnome Terminal. I use it >> constantly, usually 20 at a time, and there are 176 New bugs and 23 >> Incompletes (with response) and all of those need action. >> > > Yes here: https://wiki.ubuntu.com/UbuntuBugDay/Planning > >> >> >> -- >> >> Matthew (Matt) Fischer >> LP: http://launchpad.net/~mfisch >> IRC: mfisch >> >> >> -- >> 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: From es20490446e at gmail.com Wed Jan 23 16:28:14 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Wed, 23 Jan 2013 17:28:14 +0100 Subject: We had a successful bug day, Thank you In-Reply-To: References: <50FB839A.7010203@canonical.com> Message-ID: <51000F9E.8060906@gmail.com> An HTML attachment was scrubbed... URL: -------------- 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: From noreply at ubuntu.com Sun Jan 27 10:40:25 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 27 Jan 2013 10:40:25 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22PrintingBugInfoScript=22_by_pasc?= =?utf-8?q?al-devuyst?= Message-ID: <20130127104025.16351.14358@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "PrintingBugInfoScript" page has been changed by pascal-devuyst: http://wiki.ubuntu.com/PrintingBugInfoScript?action=diff&rev1=14&rev2=15 Comment: remove hardy }}} The script will put its output in '''/tmp/printingbuginfo.txt''', please attach this file to the bug report. - - = If you are using Ubuntu 6.06 LTS (Dapper) = - Download the script [[attachment:printingbuginfo]] and then make it executable with following command: - {{{ - $ chmod +x printingbuginfo - }}} - - To run the script, use the following command: - {{{ - $ ./printingbuginfo - }}} - - The script will put its output in '''printingbuginfo.txt''', please attach this file to the bug report. ---- CategoryBugSquad CategoryDebugging From noreply at ubuntu.com Thu Jan 31 17:24:01 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 31 Jan 2013 17:24:01 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22WizardpenTesting=22_by_doctormo?= Message-ID: <20130131172401.25974.80268@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "WizardpenTesting" page has been changed by doctormo: http://wiki.ubuntu.com/WizardpenTesting?action=diff&rev1=7&rev2=8 Please add yourself to this list if you have a wizardpen tablet and you are prepared to test new releases and default configurations. This is a highly important step in making sure these devices work out of the box by default in future: Be sure to join: https://launchpad.net/~wizardpen-testers and make sure you're on the mailing list. + + = Testing Procedure = + + All testing steps are carried out with the wizardpen driver installed from the doctormo ppa. Each step is on the computer terminal, also known as the command line. Look for the program 'Terminal' and launch to get access to the command line to follow these steps: + + == Verify that the graphics tablet was added as a usb device == + + 'lsusb' should display the graphics tablet listed among the USB devices ('UC-Logic ...' here): + + {{{ + user at computer:~$ lsusb + Bus 003 Device 003: ID 5543:0042 UC-Logic Technology Corp. Tablet PF1209 + Bus 003 Device 002: ID 046d:c401 Logitech, Inc. TrackMan Marble Wheel <- TABLE IS FOUND + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 8087:07da Intel Corp. + }}} + + == Verify the details and inputs are assigned to the graphics tablet == + + The 'dmesg' log contains a record of device activity and will show any errors when you plug the device in. Unplug the tablet, then plug it back in and look through output for 'enumeration' of USB graphics tablet: + (This command asks for 50 lines from the tail end of the dmesg log file) + + {{{ + user at computer:~$ tail -50 /var/log/dmesg + ... + [947322.712312] usb 3-1: new full-speed USB device number 18 using xhci_hcd + [947322.738240] usb 3-1: New USB device found, idVendor=5543, idProduct=0042 + [947322.738247] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 + [947322.738252] usb 3-1: Product: TabletPF1209\x14 + [947322.738257] usb 3-1: Manufacturer: + [947322.738686] usb 3-1: ep 0x81 - rounding interval to 32 microframes, ep desc says 40 microframes + [947322.753079] input: TabletPF1209\x14 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/input/input34 + [947322.753452] input: TabletPF1209\x14 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/input/input35 + [947322.753801] input: TabletPF1209\x14 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/input/input36 + [947322.754472] uclogic 0003:5543:0042.0009: input,hidraw1: USB HID v1.10 Mouse [ TabletPF1209\x14] on usb-0000:00:14.0-1/input0 + }}} + + == Examine the details of the driver installation == + + The /var/log/Xorg.0.log file contains the records of how the inputs shown in the dmesg log above, where then understood by the graphical interface (Xorg). + + The program 'less' allows scrolling forward and backwards in the log file, at the prompt ":" type in '/wizardpen' to search for the 'wizardpen' in the log and identify a successful installation. + + note: this listing shows the driver installed then REMOVED (due to version mismatch) + + {{{ + user at computer:~$ less /var/log/Xorg.0.log + ... + [ 96.073] (II) config/udev: Adding input device TabletPF1209^T (/dev/input/event12) + [ 96.073] (**) TabletPF1209^T: Applying InputClass "evdev tablet catchall" + [ 96.073] (**) TabletPF1209^T: Applying InputClass "wizardpen" + [ 96.073] (II) LoadModule: "wizardpen" + [ 96.073] (II) Loading /usr/lib/xorg/modules/input/wizardpen_drv.so + [ 96.082] (II) Module wizardpen: vendor="X.Org Foundation" + [ 96.082] compiled for 1.11.3, module version = 0.8.2 + [ 96.082] Module class: X.Org XInput Driver + [ 96.082] ABI class: X.Org XInput driver, version 16.0 + [ 96.082] (EE) module ABI major version (16) doesn't match the server's version (18) + [ 96.082] (II) UnloadModule: "wizardpen" + [ 96.082] (II) Unloading wizardpen + [ 96.082] (EE) Failed to load module "wizardpen" (module requirement mismatch, 0) + [ 96.082] (EE) No input driver matching `wizardpen' + [ 96.083] (II) config/udev: Adding input device TabletPF1209^T (/dev/input/mouse2) + [ 96.083] (II) No input driver specified, ignoring this device. + [ 96.083] (II) This device may have been added with another device file. + [ 96.087] (II) config/udev: Adding input device TabletPF1209^T (/dev/input/mouse3) + [ 96.087] (II) No input driver specified, ignoring this device. + [ 96.087] (II) This device may have been added with another device file. + :/wizardpen + }}} + + == Calibration == + + The 'wizardpen-calibrate' tool is provided with the wizardpen driver to help set up some ofthe variables for the driver. + + {{{ + user at computer:~$ gksu wizardpen-calibrate /dev/input/event13 + Please, press the stilus at ANY + corner of your desired working area: + .... + }}} + + == Reporting Results == + + When a problem occurs, stop at that step and do not continue. Report how far you got and the output of the log files proceeding the step you're stuck on to the wizardpen-testers mailing list. https://launchpad.net/~wizardpen-testers = People =