[01:14] hello, I hate to progress my own bugs so could someone make sure this bug is reproducible? it should only take a few seconds: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/671948 [01:14] Launchpad bug 671948 in indicator-sound (Ubuntu) "Indicator-sound closes rhytmbox if opened soon after closing (affects: 1) (heat: 6)" [Undecided,New] === locobot_2_2 is now known as locobot_2 === mistrynitesh is now known as geekosopher [10:21] Does update-manager have an apport-hook? [10:22] micahg: ^^^ ? [10:32] RedSingularity: from what I see - no [10:32] yofel: where did you go to look? [10:32] RedSingularity, I confirm it doesn't have one. [10:33] RedSingularity: /usr/share/apport/package-hooks/ (if you have it installed), and I checked the source package [10:36] yofel,jibel: Thanks [10:37] no problem [11:28] can someone please find a solution to logitech mx5500 kb and mouse combos, as bluez and bluetooth monolithic progress in kubuntu the support get worse [11:28] 64 bit [11:32] https://bugs.launchpad.net/ubuntu/+source/bluedevil/+bug/650603 [11:32] Launchpad bug 650603 in bluedevil (Ubuntu) "bluedevil does not recognize my bluetooth dongle at all mx 5500 kb and mouse (affects: 1) (heat: 96)" [Undecided,New] === jorge is now known as jcastro [14:10] hggdh, ping === jdstrand_ is now known as jdstrand [14:33] hggdh, at the meeting, I won't be able to attend (seminar at that time). When it comes time for mentor reports will you let them know I need my current two removed from program due to no response of emails and I can be assigned a couple more? [14:40] bcurtiswx_: will do, thanks for the heads up [14:41] hggdh, much appreciated [14:46] nightmare coming: http://blog.launchpad.net/general/launchpad-bug-jam-december-2010 [14:46] Why do people think bugs "must" be closed? [14:48] cause they get in the way of work [14:48] at least for me [14:49] at work, seeing an empty queue is better [14:50] So, of the hundreds/thousands of bugs you have filed, can we close all of them? [15:13] kamusin, hey! great work on the bug day :-) [15:14] :) heh [15:15] hey pedro_ [15:15] you get my mail about a unity section for status.qa.ubuntu.com? [15:16] jcastro, hey!, yes i got it, but bdmurray has the rights to add stuffs there [15:16] ok [15:16] I will go after him then! [15:16] pedro_: will you be doing unity triaging this cycle? [15:17] jcastro, he's probably already looking at it ;-) [15:17] jcastro, yeah i'll be helping didrocks and the guys with that [15:17] ok [15:17] we already discussed some bits on UDS [15:17] workflow etc [15:17] nice [15:17] hey so, I just need to make sure you guys are feeding me bitesize ones [15:17] so just tag em as you see them [15:17] will do it === kirrus_ is now known as kirurs === kirurs is now known as kirrus === apw` is now known as apw [16:24] jcastro: so what packages exactly? [16:25] bdmurray: a bunch, I take it you need a list? [16:25] jcastro: yeah [16:25] on it [16:25] jcastro: cool, thanks [16:25] is the meeting at 17:00? [16:29] bdmurray: source packages or binary? [16:30] jcastro: source because that is what launchpad uses [16:33] bdmurray: http://paste.ubuntu.com/528773/ [16:33] micahg: as far as I know [16:37] bdmurray: we'll have to adjust it a little bit when the compiz stuff lands but that should be good for now [16:37] bdmurray: also, do you have the ability to graph specific tags in bugs? [16:37] I'd like to keep track of "bitesize" ones in unity [16:40] jcastro: I'll have to look at tags for a specific package [16:41] bdmurray: is that hard/alot of work? [16:41] ideally if the bug line could also show which ones of those are bitesize that would rock [16:59] o/ === yofel_ is now known as yofel [17:00] hey hey , do we have a meeting now? [17:01] yes, we should (I think) [17:01] ping hggdh [17:01] ah :) [17:01] er [17:01] am I the leader today? [17:01] :-) [17:01] the wiki says you are [17:01] oh [17:01] hggdh, looks like it :-P [17:02] https://wiki.ubuntu.com/BugSquad/Meeting <- Agenda [17:02] #startmeeting [17:02] Meeting started Tue Nov 9 17:02:51 2010 UTC. The chair is hggdh. Information about MeetBot at http://wiki.ubuntu.com/AlanBell. [17:02] Useful Commands: #topic #action #link #idea #voters #vote #chair #action #agreed #help #info #endmeeting. [17:03] OK. Here we go, sorry for the delay [17:03] topics as as shown here: [17:03] [LINK] https://wiki.ubuntu.com/BugSquad/Meeting [17:03] so [17:03] btw, who manages the dates for the weekly newsletter? #217 said our meeting is at 18:00UTC [17:04] the following actions were set last meeting: [17:04] # [17:04] * Bug Day to be created for regression-potential tags [17:04] * bdmurray to remove regression-potential as an official bug tag for Ubuntu [17:04] * hggdh to prepare a bug day excepting kernel [17:04] * hggdh to clean up the Regression wiki pages [17:04] * nigelb to edit bugsquad headers to be similar or link to each other appropriately [17:04] * [17:04] devildante to split HowToTriage page up into a simple page and an advanced page [17:04] * devildante to start e-mail thread in mailing list about translations of bug reports [17:05] of those, the first four were done [17:05] nigelb: there? [17:06] devildante is MIA right now... [17:06] so I will mark these actions as pending, and re-activate for next meeting [17:06] [ACTION] nigelb to edit bugsquad headers to be similar or link to each other appropriately [17:06] ACTION: nigelb to edit bugsquad headers to be similar or link to each other appropriately [17:07] [ACTION] devildante to split HowToTriage page up into a simple page and an advanced page [17:07] ACTION: devildante to split HowToTriage page up into a simple page and an advanced page [17:08] devildante *did* start a thread on the ML, and we discussed translations more during UDS [17:08] pedro_: do you have a summary of what was decided in UDS? [17:08] hggdh, yeah [17:08] that's blueprint https://blueprints.edge.launchpad.net/ubuntu/+spec/ubuntutheproject-qa-n-handling-nonenglish-bugs [17:09] we agreed that the best place where to handle such reports is the answer tracker [17:09] at least for now, yes (now I remember ;-) [17:09] so they can ask the questions in their native language there, then it can be translated and converted into a bug report [17:10] all: any comments on that? [17:10] there's a couple of work items : [17:10] [brian-murray] Recommend that people ask a question in their native language in Answers (best stop-gap move): TODO [17:10] [brian-murray] Modify Luanchpad to allow one to specify the language when converting a bug into a question: TODO [17:11] so the detail to fix is to have the option in the "convert to question" to specify the language [17:11] because right now you have to convert the question and then go to the question on the answer tracker and change the language [17:11] hggdh: so the workflow is "foreign bug is reported -> we convert it into a question -> it gets translated and reported again" ? [17:11] kklimonda: the ideal would be for them to start in the answer tracker [17:12] or the original report is just re-opened? [17:12] sorry, seem to be late again [17:12] kklimonda, for already filed reports and if it's a bug, yes [17:12] is it currently possible to change the language of a question? [17:12] kklimonda: reopened once complete in english [17:12] yofel: yes [17:12] yofel, yeah, but only in the answer tracker [17:13] LP dev is considering localisation, but it will take a time (lots to do) [17:13] that's what I wanted to know, thanks. So I'm fine with converting those to questions if we can set the proper language afterwards [17:14] I think it makes sense - it definitely beats alternatives. [17:14] yofel: I'm looking at setting the proper language during conversion. [17:14] bdmurray: that would be nice indeed, thanks [17:14] and that' would be a *neat* feature [17:15] we still will need to communicate this, when the infrastructure is in place [17:15] convert to question is still broken AFAIK, but it's at the top of the LP Bugs work list [17:15] micahg: when you say broken do you mean times out? [17:15] yes [17:15] micahg, it sort of works here, the first time i get a time out, but if you click back and then convert again it works [17:16] odd but that's the only way i can convert a bug to a question right now [17:16] pedro_: happens on edge only? [17:16] incidentally there is not an edge anymore really [17:16] hggdh, just tried on edge [17:17] total time is around 100 seconds for convert to question hence the failure [17:17] ok so it might be the same on the normal lp, haven't tried though [17:17] progress can be tracked in bug 438116 [17:17] Launchpad bug 438116 in launchpad-foundations "Timeout when converting bug into question (BugTask:+create-question) (affects: 6) (dups: 3) (heat: 50)" [High,Triaged] https://launchpad.net/bugs/438116 [17:17] thanks micahg [17:18] subscribed, thank you micahg [17:18] any other comments on this? [17:18] so... [17:18] [TOPIC] Mentorship program update from Mentors [17:18] TOPIC: Mentorship program update from Mentors [17:19] from me: [17:19] ojap pings me once per week [17:19] from bcurtiswx_ (asked me to relay this): no response from his two mentees, recommends dropping them [17:20] (also from me: kangorooo asked for an extention and vanished again) [17:20] again? wow [17:20] other mentorship updates? [17:20] o/ [17:20] i only have 1 student now: elopio and he's busy with school at the moment so i might take a couple more [17:20] yes, my two mentees vanished :( [17:21] this is really not working :-( [17:21] it seems I don't have luck with this mentorship program [17:21] btw where's fish? [17:21] i mean vish ;-) [17:21] bish? [17:21] algnod, is there from time to time. online/offline/online/offline/... [17:22] during UDS we had agreed on trying a different approach (creating LP teams with some mentors/mentees) [17:22] jibel, is he/she working at all? [17:22] yes is active [17:22] cool [17:22] s/is/he is/ [17:23] ;-) [17:23] at least that -- one out of 5 so far... [17:23] hggdh, indeed and that's a TODO task :-) [17:23] pedro_: OK, cool [17:23] hggdh: right, as I couldn't make it to UDS, what exactly did you decide on there (about [sense] create a bugsquad-mentor-team-alpha in launchpad with a mailing list, have 2 to 3 members join the team and add mentees to that. Try it for 3 months and report back. Members - brian-murray, hggdh, vish, sense with 8 students: TODO) [17:24] yofel: exactly that ;-) [17:24] yup [17:24] when will it happen? [17:25] we will try this approach (exclusive mentorship is not working), and then see how it behaves [17:25] yofel, the idea is to have a central place where students could ask to different mentors instead of having just one person to ask to [17:25] ok, so put severaly mentors and studends into a LP team and discuss things over the team ML? [17:25] yofel: yep, [17:25] ok, sounds useful [17:25] yes. Plus IRC (I personally would require it) [17:25] IRC is a requirement, yes [17:26] yofel: the idea is to have one explanation hitting all the mentees in a group [17:26] good idea, agreed [17:26] well and to build a classroom type environment [17:26] instead of repeating the same thing ad nauseum for each mentee [17:26] yes [17:27] hopefully this will spur exchange of ideas and doubts [17:27] OK. Anything else on the mentorship? [17:28] [TOPIC] Open Discussions [17:28] TOPIC: Open Discussions [17:28] yofel pointed out at the beginning that the newsletter still has theis meeting at 1800 [17:29] is that the UWN ? [17:29] yes [17:29] currently it says http://paste.ubuntu.com/528800/ [17:30] taken from #217 [17:30] they are probably grabbing that from the fridge [17:30] I'll contact the folks there to have that updated [17:30] thanks [17:30] thanks for raising it yofel [17:30] yw [17:31] anything else? Anyone? Huh? [17:31] just a quick announcement [17:32] remember we're having a bug day on Thursday 11! [17:32] * kamusin wohoo! [17:32] https://wiki.ubuntu.com/UbuntuBugDay/20101111 [17:32] kamusin and komputes are doing a *extraordinary* work [17:32] oh, our old friend, bugs without a package [17:32] thanks [17:33] kamusin komputes you guys are heroes :-) [17:33] I would like to remind all that the Ubuntu Beginners Team would like to draw on our knowledge there [17:34] and as always we're looking for new targets so if you have one, please add it to https://wiki.ubuntu.com/UbuntuBugDay/Planning [17:34] oh good call hggdh :-) [17:35] so -- having time, please drop by #ubuntu-beginners-team, and ask how you can help [17:36] joined, how exactly do they want to help us (or we help them) here? [17:36] They would be willing to help teach triaging [17:36] they also have (or are planning) a triger's class/group/effort. We should probably try to converge/standardise [17:36] charlie-tca: heh. You beat me ;-) [17:37] * charlie-tca thought I was missing today [17:37] oh, nice to have some more help there, I'll idle around there then :P [17:37] thanks yofel. [17:37] I guess I will too [17:38] * charlie-tca got to report that xchat bug [17:38] BTW -- one thing I noticed is new triagers somehow try to tackle kernel, sound, and X bugs first [17:38] agreed [17:39] how can we tell them this is Not A Good Idea (TM)? [17:39] They are picking on the hardest bugs they can find to learn with. [17:39] well, I guess that's since those are usually at the top of the bugs stats lists with the most bug numbers - usually because they're so hard to do [17:40] yes. But I always tell folks to start on something (1) simple (2) that they use... somehow I am not successful in passing this over [17:40] recommend that people pick software they like / use a lot [17:41] and explicitly recommend they do not get kernel/sound/X? [17:41] make https://wiki.ubuntu.com/Bugs/EasyTasks a bit more useful as a recommendation point? [17:42] nice... [17:42] great! [17:42] +1 [17:42] do we have any place in how to triage or helping with bugs that refers to that page? [17:43] that page currently just lurks around in the knowledge base without many knowing about It I guess [17:43] charlie-tca: not to my knowledge [17:43] it should be in, I guess [17:44] Would be nice to see it where it will be used [17:44] wait, it's not even in the Knowledge base [17:44] * yofel wonders how he found that page in the first place... [17:44] heh, one of those neat things you wander into [17:44] I'll add it there at least [17:45] i've created that page for the UGBJ but i don't remember if i linked it to others... [17:45] bad me [17:45] LOL [17:46] ok [17:46] btw. is there *any* convention what goes to 'Bugs/' and what to 'BugSquad/' on the wiki? [17:46] any other comments? [17:46] um, pretty much where ever it lands, I think [17:48] there is an effort on consolidating/rewrting/cleaning-up our pages [17:48] team stuff should goto BugSquad and Bugs stuff is generic to bugs [17:48] Perhaps both sections could be combined. That would cut out a lot of duplication, and make it easier to maintain [17:48] so really the majority of the stuff should be in Bugs [17:49] ack [17:49] If bugsquad is the team that works on bugs, why are they separate in the wiki? [17:49] k [17:49] because you do not need to be in bugsquad to triage [17:49] charlie-tca: BugSquad stuff would be stuff like meetings, how to join etc [17:50] okay [17:50] developers might read Bugs stuff and not be interested in the BugSquad [17:50] which is their loss ;-) [17:50] and yet we make them bugcontrol? [17:50] yes -- for *some* teams, not all [17:51] like core-devs [17:51] I've always felt that bugsquad is the team charged with doing the obvious triage work so that devs can focus on the hard stuff. [17:51] well, they should read status, importance and other things, which is under bugs/ and doesn't have much to do with the team [17:51] hggdh: all ubuntu-devs are member of bug-control [17:52] micahg: yes. But not *all* dev teams [17:52] but that doesn't mean they read/know any of the procedures bug-control non-devs must follow [17:52] the reasoning was (at the time, IIRC, bdmurray may correct me ;-) if they are already ubuntu-devs/core-devs, they *know* what to do [17:53] and they are still expected to abide by the rules [17:53] and have signed the CoC etc... [17:54] we do accept new teams for -control (but none have applied so far) [17:55] but the teams must be moderated/restricted and CoC is a requirement [17:55] Are we good with this topic? [17:55] sure [17:55] I think so [17:55] as such [17:55] #endmeeting [17:55] Meeting ended Tue Nov 9 17:55:48 2010 UTC. Information about MeetBot at http://wiki.ubuntu.com/AlanBell . (v 0.1.4) [17:55] Minutes: http://mootbot.libertus.co.uk/ubuntu-bugs/2010/ubuntu-bugs.2010-11-09-17.02.moin.txt [17:55] thank you all [17:56] * hggdh goes for the next meeting [17:56] hggdh: Thanks for chairing [17:56] thank you hggdh [17:57] thanks [17:57] thanks [18:01] jcastro: what is nux? I can't seem to find it [18:05] bdmurray: it's some library that will be there eventually [18:06] jcastro: ah okay [18:07] jcastro: and compiz-plugins-main will be an new package too? [18:07] bdmurray: when it all lands I can double check each one, just getting them started would be best [18:07] yeah, probably [18:08] jcastro: okay [18:10] bdmurray: I suspect the bug numbers will all be skewed for the first week since they're rewriting the buggy parts but I figure it's best to get them going now [18:27] bdmurray: out of curiosity do you just add packages to a list or is it there more to it than that? [18:28] jcastro: one list and then classify them by category in a different list [18:29] ah [18:29] and measuring the bitesize tag? Will that be a problem? [18:30] there would be some more work involved so I'll look at it later [18:30] * jcastro nods [18:30] bdmurray: so basically, the bug people triaging unity bugs will determine if anything is bitesize, and then I'm going to start a drive around getting new contributors interested in bitesize bugs [18:31] it'll likely be modelled in a gnome-love/papercut like manner [18:31] so any way I can measure successes with bugs with those tags would help me out [18:49] hi everyone [18:49] can anybody take a look at the bug 670592 [18:49] Launchpad bug 670592 in compiz (Ubuntu) "compiz crashes when screensaver activates (affects: 1) (heat: 6)" [Undecided,Confirmed] https://launchpad.net/bugs/670592 [18:50] flipefr, a backtrace is needed, could you ask the reporter to enable apport and submit a new report? [18:51] flipefr, there's a stock response for that here: https://wiki.ubuntu.com/Bugs/Responses#Missing%20a%20crash%20report%20or%20having%20a%20.crash%20attachment [18:51] pedro_, ok [18:52] btw , you can close the bug after asking for the new one [18:52] thank you flipefr [18:54] pedro_, how can i close the bug? [18:54] flipefr, just set it to Invalid [18:55] to bug is no use without a backtrace anyways [18:55] ok [18:55] done [18:59] does anyone mind if I rewrite that response a bit? the !gnome invocation instructions are just wrong [19:00] yofel, feel free to edit it [19:00] * yofel gets to work [19:00] but the wiki seems down to me now [19:00] I need to make a draft anyway first [19:01] is working again [19:03] any xubuntu user here? can't you open a crash report in thunar with a double click? [19:04] * micahg uses Xubuntu [19:04] let's see [19:05] sure I can. [19:05] in Xubuntu 10.04 [19:05] yofel: if the crash is owned by the user, yes [19:05] charlie-tca, micahg: thanks [19:05] that's correct [19:06] if owned by root, it errors [19:06] same goes for gnome and kde === CaioAlonso_ is now known as CaioAlonso