[00:12] <layn> Hi!
[02:25] <CarlFK> (veyepar)juser@dhcp42:~$ atftp shaz  <<< "get pxelinux.cfg/default"
[02:25] <CarlFK> tftp> get pxelinux.cfg/default
[02:25] <CarlFK> Overwite local file [y/n]? Segmentation fault
[02:25] <CarlFK> (veyepar)juser@dhcp42:~$ apport-cli
[02:25] <CarlFK> No pending crash reports. Try --help for more information.
[02:26] <CarlFK> natty install
[02:26] <CarlFK> shouldn't the segfault = crash report?
[02:27] <yofel> CarlFK: apport needs to be enabled in /etc/default/apport
[02:28] <CarlFK> Segmentation fault (core dumped)
[02:28] <CarlFK> (veyepar)juser@dhcp42:~$ apport-cli
[02:28] <CarlFK> No pending crash reports. Try --help for more information.
[02:29] <CarlFK> where is the core dump file?
[02:30] <yofel> CarlFK: apport needs to be enabled in /etc/default/apport
[02:31] <CarlFK> yofel: did that (which I am guessing is why I now get "core dumped")
[02:31] <yofel> CarlFK: 'initctrl status apport' shows it as started?
[02:32] <CarlFK> (veyepar)juser@dhcp42:~$ initctl status apport
[02:32] <CarlFK> apport start/running
[02:33] <yofel> are you running natty? I think there was some issue there, can't remember the details though at the moment
[02:33] <CarlFK> yes natty
[02:33] <CarlFK> (veyepar)juser@dhcp42:~$ ls /var/crash/
[02:33] <CarlFK> _usr_bin_atftp.1000.crash
[02:33] <CarlFK> so 'that' works (i guess)
[02:34] <yofel> hm, then just file that, there's bug 683367 too, but that's about not even creating the .crash file
[02:34] <ubot2> Launchpad bug 683367 in apport (Ubuntu Natty) (and 1 other project) "apport fails to create crash file during upgrade to 11.04 (affects: 1) (heat: 6)" [High,New] https://launchpad.net/bugs/683367
[13:46] <vish> pedro_: hi … any decision on the mentor question i had asked yesterday? c2tarun is very eager to start bug triaging.. where shall we start grinding him? ;)
[13:48] <pedro_> hello vish
[13:48] <vish> heya
[13:48] <pedro_> vish, could you add him to the group A ?
[13:49] <pedro_> to start with that and see how it goes
[13:49] <c2tarun>  yesterday i saw on wiki page that there are some mentors mentoring which tallies with my time slot. is there any way i can share that time with them??
[13:49] <vish> pedro_: ^
[13:49] <pedro_> well that's the idea of the team-A :-)
[13:49] <pedro_> you'll have like 5 mentors to help you out there
[13:49] <vish> so team A it is. :)
[13:51] <c2tarun> what is team A??
[13:52] <vish> pedro_: thanks.. i'll add him there, and send a mail with his info.
[13:52] <pedro_> c2tarun, is a subteam of the bugsquad-mentorship with 5 mentors on it that can help you out during your learning phase :-)
[13:52] <vish> c2tarun: sssh! its top secret, dont let others know ;)
[13:53] <pedro_> but don't let hggdh know about it
[13:53] <pedro_> is a secret
[13:53] <c2tarun> sure :)
[13:53] <vish> yes! not hggdh
[13:53] <cdbs> revealing secrets on a public channel and naming a person to whom it should not be revealed?
[13:54] <c2tarun> yeah that is what i was about to ask!!
[13:54] <cdbs> :E
[13:54] <vish> cdbs: you missed the secret too.. so ;p
[14:02] <hggdh> pedro_, vish: don't let me know?
[14:03] <vish> hggdh: this cycle's newest secret.. :)
[14:04] <pedro_> lol
[14:16] <nigelb> pedro_: oh, we have a new secret for hggdh!
[14:17] <nigelb> pedro_: QA sprint is going on? ;)
[14:18] <charlie-tca> pedro_ vish hggdh did we pick a logo and put it on launchpad to go with team A?
[14:19] <vish> charlie-tca: nope.. atleast not that i'm aware of.. :)
[14:19] <pedro_> i don't think so... but any admin can change it
[14:19] <charlie-tca> Then we need to. Who gets to decide?
[14:20]  * vish checks link again..
[14:20]  * charlie-tca wants to close the action item for UDS
[14:23] <vish> https://wiki.ubuntu.com/Artwork/Specs/0003_Bugsquad_Icon
[14:24] <vish> pedro_, hggdh ^: so charlie-tca had the neat idea of using the 64px of 4/5 and the 14px of 1 , which seems a good option
[14:24] <charlie-tca> leogg - 5
[14:25] <nigelb> hehe, I like the icons
[14:25] <vish> yup.. 5 was my pick too :)
[14:27] <c2tarun> cute icons :)
[14:30] <charlie-tca> Here is 1 without the A - http://imagebin.ca/view/BD27lGe.html
[14:30] <vish> charlie-tca: once pedro_ and hggdh decide, could you mail the ML that we need to icons? .. right now, it is a banner, but we need the individual icons to add to the lp team.
[14:30] <charlie-tca> sure
[14:31] <vish> charlie-tca: that one, would fit quite well, for bugsquad :)
[14:31] <charlie-tca> I didn't realize they weren't individaul items yet
[14:32] <pedro_> i like the orange one with the A on it ;-)
[14:32] <pedro_> let me see the number...
[14:32] <pedro_> heh i like leogg 1
[14:32] <pedro_> but 5 is also good
[14:33] <pedro_> so we can use leogg 1 to replace the old bugsquad logo :-P
[14:33] <vish> pedro_: i think we can use 1 for BugSquad..
[14:33] <vish> :)
[14:34] <vish> the 14px without the A would also work for BSquad..
[14:34] <vish> BugSquad..
[14:34] <pedro_> indeed
[14:34] <vish> argh! there is no way BugSquad can be shortened … and not sound bad ;p
[14:36] <vish> so we are waiting for honorable hggdh to decide.. :)
[14:37] <devildante> vish: BgSqd, maybe?
[14:37] <vish> devildante: yay! better, i hate typing.. :)
[14:49] <charlie-tca> By the way - Kernel Bug Day today! Everyone invited to help
[14:58] <c2tarun> i was going through bug triaging page, who can change the importance of a bug.
[14:59] <drosenbe> every day is kernel bug day
[15:00] <drosenbe> i think i'm going to stay in userland for the week
[15:00] <drosenbe> except for maybe a few upstream patches
[15:01] <charlie-tca> this is a planned kernel bug day. Everyday is a good day for bug triage, though
[15:02] <drosenbe> i'm just giving you a hard time ;)
[15:02] <charlie-tca> c2tarun: bug-control members can change importance. You can give a bug number using bug ##### here, and someone will look at it if you tell us the importance you want.
[15:06] <c2tarun> how can we look that a newly reported bug is duplicate or not??
[15:08] <charlie-tca> You can search through launchpad bugs for a similar issue and you compare stacktraces.
[15:08] <devildante> c2tarun: you have to search for similar bug reports
[16:03] <c2tarun> i just read bug triaging page. where can i get some examples??? and from where should i start?
[16:48] <c2tarun> can anyone please help me in triaging this bug # 686651
[16:48] <c2tarun> can anyone please help me in triaging this bug #686651
[16:48] <ubot2> Launchpad bug 686651 in firefox-3.5 (Ubuntu) "Firefox crashed after downloading add on (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/686651
[16:49] <charlie-tca> c2tarun: works better to leave off the #
[16:50] <Pici> w/22
[16:50] <charlie-tca> I do real bad on firefox bugs
[16:51] <c2tarun> sure. in this bug report reported did not mentioned about the addon he/she was trying to install. in bug triaging i read that all the necessary info should be provided.
[16:54] <charlie-tca> Great! Have you found this page yet? https://wiki.ubuntu.com/Bugs/Responses#Debugging%20Firefox
[16:55] <charlie-tca> You can copy and paste the text in the dark box to the bug report, and set the status to incomplete. Subscribe so when the reporter answers you will know it.
[16:56] <charlie-tca> Thank you for helping with bugs. We do appreciate it very much
[16:56] <c2tarun> i am just learning. this is my first one. :)
[16:57] <bdmurray> Does anybody know if there is a policy regarding consolidating duplicate debian bug reports?
[16:59] <c2tarun> charlie: can you please take a look at the bug page please.
[17:02] <bdmurray> jcastro: what's that debian & ubuntu irc channel?
[17:02] <micahg> bdmurray: #debian-ubuntu on oftc
[17:03] <micahg> charlie-tca: c2tarun: FTR, I don't think the retracers are running on karmic anymore
[17:04] <c2tarun> micahg: so does that mean that comment i posted is wrong. it needs some modification??
[17:08] <micahg> c2tarun: yes, also, we don't take firefox crash reports anymore
[17:08]  * micahg needs to update the wiki docs
[17:08] <charlie-tca> Thanks, micahg
[17:08] <c2tarun> micahg: very sorry, i was not aware of that.
[17:09] <charlie-tca> So that should be a 'invalid unless you can reproduce this issue in Firefox 3.6' comment?
[17:09] <micahg> charlie-tca: well, for karmic, we're kinda SOL
[17:09] <c2tarun> SOL??
[17:10] <charlie-tca> I thought we upgraded firefox in karmic to 3.6 too, didn't we?
[17:10] <micahg> So Outta Luck :)
[17:10] <micahg> charlie-tca: yes, but we're not pushing symbols up to mozilla nor are enabling the crash reporter
[17:11] <c2tarun> So that bug is invalid right??? just curious can you please tell why we dont take firefox crash reports anymore??
[17:11] <charlie-tca> c2tarun: The only thing we can do then is ask them to please try to reproduce the issue using the development release of Natty Narwhal.
[17:11] <c2tarun> ok charlie
[17:12] <charlie-tca> use this one - https://wiki.ubuntu.com/Bugs/Responses#Needing%20testing%20in%20the%20development%20release
[17:12] <charlie-tca> If they can't reproduce it, we can close the report next month
[17:12]  * charlie-tca was right. He does suck at firefox
[17:13] <micahg> charlie-tca: well, we could ask for reproduce steps and try to reproduce a crash locally, then get a retrace locally, but that's a lot of work
[17:13] <charlie-tca> Let's let them try and do it in natty. That is always a good way to go, anyway
[17:16] <c2tarun> micahg: it is mention on the bug responses page that to check in Natty we have to download the live CD and boot into it and then check it.   this will be lot of work and the person reported is using 3.5 and now the version released is 3.6 + if we want to reproduce the bug, we still need to know the add on.
[17:17] <charlie-tca> c2tarun: yes, we expect them to do that work.
[17:18] <micahg> c2tarun: no, version is 3.6 source package is firefox-3.5, and natty version is 4.0b7
[17:18] <charlie-tca> If a bug can not be verified in Natty or Maverick, it normally becomes fixed
[17:18] <micahg> actually, it should probably be invalid unless is was a confirmed bug
[17:19] <c2tarun> ok. so i should just mark it invalid and as reporter to reproduce in Natty??
[17:20] <micahg> c2tarun: no, I meant if it works in natty it should be invalid
[17:21] <c2tarun> micahg: sorry not gettting. if reporter reproduced it in natty as well then also bug is invalid??
[17:26] <jcastro> bdmurray: #debian-ubuntu on OFTC
[17:26] <bdmurray> jcastro: yes I sorted it out
[17:26] <bdmurray> jcastro: thanks
[17:27] <c2tarun> micahg: sorry not gettting. if reporter reproduced it in natty as well then also bug is invalid??
[17:28] <charlie-tca> c2tarun: mark it incomplete. If the reporter can reproduce it natty, it will be confirmed
[17:28] <charlie-tca> If it can not be reproduced in Natty, it is invalid
[17:29]  * charlie-tca thinks we confused c2tarun pretty good today.
[17:29] <c2tarun> charlie: :P ok i'll mark it incomplete, do i have to post a new comment to try to reproduce the bug with natty??
[17:32] <charlie-tca> taking care of it.
[17:32] <charlie-tca> doen
[17:32] <charlie-tca> done, too
[17:33] <charlie-tca> thank you, c2tarun
[17:33] <c2tarun> no thank you all :)
[17:33] <c2tarun> i'll try better next tym
[17:35] <charlie-tca> We will too. Trying to explain sometimes is more difficult than the actual report
[17:40] <micahg> c2tarun: sorry, lost connection there
[17:41] <c2tarun> micahg: np, i think triaging is done. If possible please take a look. if its all correct than it will b a good example for me
[17:53] <rsalveti> can someone help reviewing and sponsoring bug 686320?
[17:53] <ubot2> Launchpad bug 686320 in network-manager (Ubuntu) "NetworkManager crashes with SIGSEGV while loading the usb0 interface on Panda (affects: 1) (heat: 10)" [High,In progress] https://launchpad.net/bugs/686320
[17:54] <rsalveti> it blocks network-manager on arm, and as a result the network doesn't work normally at our images
[17:54] <rsalveti> it's just a backport from nm upstream
[17:54] <rsalveti> this is for natty
[17:55] <TeTeT> rsalveti: you want to talk to cyphermox on #nm
[17:57] <rsalveti> TeTeT: cool, thanks
[18:13] <njin_> hello, where i can found the 2.6.37-rc3 for maverick ? Thanks
[18:15] <yofel> njin_: that sounds like a mainline build http://kernel.ubuntu.com/~kernel-ppa/mainline/
[18:18] <njin_> yofel: thanks but the last is 2.6.37-rc2, i'm going to reread the post, if i'll found again.
[18:18] <yofel> njin_: the maverick/natty suffixes are which kernel configuration is used for the mainline builds, they don't build the same kernel with different configurations, use the natty one
[18:19] <crimsun> i.e., http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37-rc5-natty/
[18:19] <njin_> yofel: are you meaning that i can use a natty kernel in maverick ?
[18:19] <crimsun> yes, it works fine
[18:20] <crimsun> I use the mainline builds consistently
[18:20] <njin_> yofel, crimsun: thanks
[18:20] <crimsun> then again, all my work is upstream, so I dogfood so that there aren't uncaught regressions
[18:23] <njin_> crimsun: after installing 2.6.37-rc2 in xorg we have (EE) RADEON(0): Unable to map MMIO aperture. Invalid argument (22)
[18:23] <njin_> . Is this related to this ?
[18:24] <njin_> to rc2
[18:27] <crimsun> njin_: could be, but you'll want to reproduce that in -rc5
[18:28] <njin_> crimsun: ok i'm going to suggest to install it
[20:15] <c2tarun> vish: can u help me in triaging but 686736
[20:15] <njin_> crimsun: in the rc5 is whorse  http://launchpadlibrarian.net/60284304/Xorg.0.log_20101207_2
[20:22] <c2tarun> vish: ^_^
[20:22] <yofel> lp 686736
[20:22] <ubot2> Launchpad bug 686736 in ubuntu "GNOME applets stopped when I switch between Unity and classic desktop interface. (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/686736
[20:23] <c2tarun> yofel: this error is on gnome desktop of natty. is there any way to reproduce it??
[20:24] <yofel> can't help there I fear, I haven't used gnome in ages and don't know anything about unity
[20:25] <c2tarun> thats better coz i used GNOME only and still dont know about unity :(
[20:26] <yofel> njin_: you need fglrx from natty, or possibly x-updates ppa if you use 2.6.37
[20:26] <yofel> njin_: see lp 671868
[20:26] <ubot2> Launchpad bug 671868 in fglrx-installer (Ubuntu) "package fglrx 2:8.780-0ubuntu2 failed to install/upgrade: fglrx kernel module failed to build (affects: 1) (heat: 150)" [High,Fix released] https://launchpad.net/bugs/671868
[20:43] <njin_> yofel: thanks, i've suggested to install an intermediate version of upstream kernels, as he has net problems
[20:44] <yofel> well, testing upstream kernels is part of the kernel bug workflow, it's just that fglrx is very easy to break
[20:46] <JFo> njin, what is the issue?
[20:47] <njin_> crimsun: one moment
[20:47] <njin_> JFo:http://launchpadlibrarian.net/60284304/Xorg.0.log_20101207_2
[20:48] <njin_> i suggest install rc5 but fglrx is missed seems
[20:49] <JFo> njin, what is the bug number?
[20:49] <njin_> bug 688924
[20:49] <ubot2> njin_: Error: Bug #688924 not found.
[20:50] <njin_> bug 668924
[20:50] <ubot2> Launchpad bug 668924 in ubuntu "No wireless for Atheros AR9285 (affects: 1) (heat: 12)" [Undecided,Incomplete] https://launchpad.net/bugs/668924
[21:38] <bdmurray> hggdh: https://wiki.ubuntu.com/Bugs/HowToTriage#Converting%20a%20bug%20report%20to%20a%20question
[21:39] <hggdh> bdmurray: what gives there?
[21:40] <hggdh> bdmurray: oh
[21:41] <hggdh> bdmurray: good!
[21:41] <micahg> bdmurray: do you mind if we discuss the foreign bugs again at the bugsquad meeting next week?
[21:41] <bdmurray> micahg: could you be a wee bit more specific?
[21:42] <micahg> bdmurray: oh, it was one of your criteria for converting to question, also someone brought it up a few days ago, I wanted to start a discussion on teh ML, but the meeting is next week and figured it might be a good topic
[21:43] <bdmurray> micahg: there was a thread on the mailing a bit ago and it was discussed at UDS a lot
[21:43] <micahg> bdmurray: right, but the conclusions I remember differ from what's on teh wiki, or maybe I wasn't paying enough attention
[21:44] <bdmurray> micahg: okay as long as there is a specific question and not a general what do we do discussion again
[21:45] <felipe_c> hey everybody, i was trying out natty and found a couple of "bugs" they aren't critical, but I wasn't sure where to post them (which package)
[21:45] <micahg> bdmurray: ok, maybe I should do it on the ML list then, it was more to clarify what do we do :-D
[21:46] <charlie-tca> felipe_c: where are the bugs?
[21:46] <felipe_c> well, it's the installer
[21:46] <bdmurray> micahg: okay, the mailing list would likely get a wider audience
[21:46] <charlie-tca> desktop cd or alternate cd?
[21:47] <felipe_c> desktop
[21:47] <charlie-tca> ubiquity
[21:47] <felipe_c> thanks
[21:47] <charlie-tca> report them using     ubuntu-bug ubiquity     from the live desktop
[21:47] <yofel> bdmurray: we want to use questions for non-english bugs too right
[21:47] <yofel> ?
[21:48] <charlie-tca> n
[21:48] <bdmurray> yofel: yes non-english bugs should become questions in the answer tracker with the correct language specified
[21:48] <micahg> oh, hmm, I see I forgot to read the end of the old thread :-/
[21:49] <yofel> k, I remembered seeing https://wiki.ubuntu.com/Bugs/Responses#Not%20reported%20in%20English which needs an update too
[22:40] <layn> Hi!
[23:13] <hggdh> argh! Got a beating from a mix of Hudson, couchdb, and firewalls :-(
[23:24] <hggdh> and dnsmasq...
[23:25] <charlie-tca> well, at least they all hit together ;-)
[23:36] <hggdh> sort of. each one of them stopped at a time -- and figuring out all the failures was hell
[23:36] <hggdh> I am still trying, though :-)
[23:41] <hggdh> oh, and I forgot libvirt-bin and disk space
[23:43] <charlie-tca> May as well get the whole basket full if you are going to go through hell
[23:47] <hggdh> LOL
[23:47] <hggdh> thank you for your support, charlie-tca :-)
[23:49] <micahg> charlie-tca: do they offer  discounts at checkout?
[23:49] <charlie-tca> You are welcome :-)
[23:50] <charlie-tca> micahg: if take a double load of it