[00:45] <mrooney> just FYI, #ubuntu-bugs-announce is announcing again
[02:58] <mcisternas>  /whois pedro_
[12:02] <Iulian> Heya
[12:05] <siretart> could someone please triage bug #163481?
[12:06] <siretart> It currently has 4 bugtasks, the wpasupplicant one is definitly not confirmed, and apart from that pretty speculative comment #12, I cannot see how wpasupplicant can be related to that issue
[12:06] <siretart> moreover, the task on network-manager is set to 'in progress' without assignee
[12:06] <siretart> that bug is currently a real mess, and I'm unsure how to deal with it properly
[12:34] <thekorn> siretart, in my opinion it won't hurt to mark all task, apart the intitial linux-source-2.6.20 one, as 'incomplete' and ask people why they added/changed the tasks
[12:42] <siretart> thekorn: the people who have done this might or might not be subscribed at all to that bug, so they are likely to miss my question. which would rather confuse the reporter
[12:43] <siretart> I hoped the bugsquad would have procedures for such bugs
[14:24] <hggdh> siretart, thekorn_ in this case the assignments were entered by Eric Kuzmenko, who is subscribed to the bug
[14:32] <siretart> hggdh: I've now invalidated the wpasupplicant task only, since I care for wpasupplicant. I didn't touch the other bugtasks mainly because I feel unfamiliar with bug triaging procedures.
[14:33] <siretart> so anyone, feel free to triage that bug.
[14:34] <hggdh> siretart: I have added a question to the person that added the tasks and changed the stati and assignment. I also reverted the "in progress' for n-am. The bug is still officially new, waiting for someone with experience on n-am to trial it. Thank you
[14:35] <hggdh> siretart: your help *is* appreciated
[14:37] <siretart> hggdh: :)
[14:37] <siretart> hggdh: but now the bug is back in untriaged state, isn't it?
[14:38] <siretart> I'm still trying to understand this whole process
[14:39] <qense> God, I hate mIRC
[14:40] <qense> I don't like using Windows ;)
[14:58] <hggdh> siretart: it is, and it is the actual status for this bug
[14:58] <hggdh> siretart: this is one of our issues: too few people dealing with triages
[14:59] <siretart> hggdh: right. and too few people actually fixing bugs
[15:00] <siretart> btw, I've finally found out how I can get a list from launchpad that contains bugs needing triage for package I'm bug contact for
[15:00] <siretart> and managed to get that list to below a dozen
[15:01] <siretart> perhaps the bugsquad team could use the number of that list to implement a metric for developers?
[15:03] <hggdh> siretart -- what do you mean by 'number of that list'?
[15:04] <siretart> hggdh: I mean the number of untriaged bugs in package the person is bug contact for
[15:04] <hggdh> oh, OK.
[15:04] <hggdh> hum
[15:04] <hggdh> why not?
[15:04] <siretart> so, go for it! :)
[15:05] <hggdh> siretart -- you said you finally found out how to get the list... mind sharing with poor me? ;-)
[15:06] <siretart> go to https://bugs.edge.launchpad.net/ubuntu/+bugs?advanced=1
[15:06] <siretart> select status 'New', enter LP id in 'Bug supervisor'. Then click 'search'
[15:09] <hggdh> siretart: dammit, this is what 'bug supervisor' means...
[15:10]  * hggdh thinks about a launchpad bug re. 'bug contact' and 'bug supervisor'
[15:14] <siretart> hggdh: it was recently announced to be renamed
[15:23] <bddebian> Boo
[15:40] <wolfx> the only way for me to bring up my wireless card w/ static ip is to change my pairwise and group settings to CCMP and back to TKIP (my actual router setting), and after reboot i have to do the same thing.  any thoughts?
[17:07] <Ienorand> Is this the right place to ask for assistance when filing bugs?
[17:07] <Pici> Sure, why not?
[17:09] <Ienorand> Okay, I've recently filed a bug against the new *-17 kernel, is there anything more i should include in my Bug #235462 ?
[17:14] <bdmurray> Ienorand: the correct package is linux for your bug
[17:15] <bdmurray> Ienorand: additionally if you could include https://wiki.ubuntu.com/KernelTeamBugPolicies that would be helpful
[17:15] <greg-g> bdmurray: welcome back!
[17:16] <bdmurray> greg-g: hey, thanks I have an answer to your question regarding pedro_'s upstream stacktraces too
[17:16] <greg-g> bdmurray: awesome
[17:16] <Ienorand> okay, I'm changing package to linux then, and gonna check with that later.
[17:17] <bdmurray> greg-g: he installed the debug symbol packages, recreated the bug and got a stack trace with gdb.  Does that help?
[17:17] <greg-g> bdmurray: that does.  the stacktrace that I was using was just the one from apport
[17:20] <bdmurray> okay, great!
[18:52] <bdmurray> thekorn: hello
[18:55] <thekorn> bdmurray, hi, did you have a good flight back home?
[18:55] <bdmurray> thekorn: it was a bit rough with the party but the flight itself was fine
[18:55] <thekorn> cool
[18:56] <bdmurray> I was looking at bug 233948 today.  Does it require an lp cookie or is this a separate file?
[18:59] <thekorn> bdmurray, it is just a seperate file in $HOME
[18:59] <thekorn> with only a username
[18:59] <thekorn> maybe the name of this file is a bit misleading
[18:59] <bdmurray> yeah, it could be confused with lp-cookie
[19:03] <thekorn> bdmurray, hmm, in the branch for the unittests there is also a config-file required, so maybe let's merge this two files into one,
[19:03] <thekorn> and call it ~/.python-launchpad-bugs.cfg
[19:22] <ffm> bdmurray: ping (bugcontrol request)
[19:25] <bdmurray> ffm: Hi, I've been swamped with UDS, FOSScamp and travel but still have your application
[19:25] <ffm> bdmurray: Ok.
[19:35] <bdmurray> ffm: can you give me a status update of bug 194029?
[19:42] <bdmurray> norsetto: How are you involved with SRU work?
[20:15] <rpedro_> I get this error when using strace according to the wiki, to attach to a hanged program using 99% cpu:
[20:15] <rpedro_> attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted
[20:18] <rpedro_> is there another way to debug a hanged program besides strace?
[20:18] <rpedro_> way to get usable debug information, I mean
[20:19] <bdmurray> rpedro_: did you try strace vis sudo?
[20:19] <bdmurray> s/vis/via/
[20:19] <rpedro_> hm no
[20:20] <rpedro_> not yet :)
[20:20] <rpedro_> ah works :-)
[20:21] <rpedro_> thanks bdmurray, I never would have thought of that since it is a process running regular user
[20:28] <norsetto> bdmurray: just trying to get rid of some
[20:29] <bdmurray> norsetto: I guess I meant are you on the release team?  I've a bug I think is worth targetting to Hardy
[20:30] <norsetto> bdmurray: you mean the motu-sru team? Not, I'm not, but what bug is that?
[20:30] <bdmurray> bug 194029
[20:33] <ffm> bdmurray: sure
[20:36] <ffm> bdmurray: unfortunately I'm not on ubuntu ATM, I'm on the other os.
[20:37] <bdmurray> ffm: there were just a lot of comments to read I'm trying to understand its current status
[20:37] <ffm> bdmurray: last time I checked it still occured.
[20:38] <bdmurray> and its not a kernel bug because the updated kernel doesn't fix it?
[20:38] <ffm> bdmurray: I can test it at 0100h.
[20:38] <ffm> bdmurray: Yeah.
[20:39] <norsetto> bdmurray: I don't see any possible applicable fix in there?
[20:39] <bdmurray> It's interesting that one person mentions the kernel update fixed it for them.
[20:42] <ffm> bdmurray: Again, I'll retest with all the updates in 5hrs.
[20:53] <bdmurray> norsetto: I was looking at https://wiki.ubuntu.com/RCBugTargetting and thought it could be nominated and become a target of opportunity
[20:55] <norsetto> bdmurray: I'd rather check if the kernel released yesterday fixes the problem already
[20:57] <bdmurray> sounds good
[21:04] <wouterh> hi, how should I mark https://bugs.launchpad.net/ubuntu/+source/psi/+bug/228146 ? Invalid seems appropriate
[21:10] <thekorn_> wouterh, maybe 'won't fix' with a hint to the workarounds
[21:24] <wouterh> thekorn_: I can't choose 'won't fix'
[21:28] <thekorn_> wouterh, oh, sorry this status can only be set by members of ubuntu-bugcontrol, I will change the status now
[21:28] <thekorn_> thanks for working on this bug
[21:30] <wouterh> no problem
[21:31] <jibel> Hi bugsquad, could a member of bugcontrol take a look at bug 229043 and set an importance ?
[21:34] <thekorn_> jibel, I did not read the bugreport, but why should we boost the importance if a fix is already available?
[21:40] <jibel> because v2.3 of the intel driver need to be pushed in 8.04.1 or earlier, should I assign Bryce Harrington directly ?
[21:40] <aks_> hello all
[21:40] <bdmurray> jibel: there is an #ubuntu-x channel
[21:41] <jibel> ok, I'll ask there
[21:41] <bdmurray> thanks bryce should be there too
[21:42] <aks_> older versions of Ubuntu had a nasty bug with hibernation and sleep on my laptops such as mine (HP zv5000)
[21:42] <aks_> I'm wondering if this has been resolved in Hardy
[21:42] <aks_> I'm finding some contradictory posts online about the issue
[21:43] <aks_> any clues?
[21:45] <aks_> hmm perhaps this is not the place to ask this sort of question?
[21:46] <bdmurray> aks_: its a bit vague so far but you should be able to test suspend, not hibernate, with the livecd
[21:46] <aks_> yes, that's what I was thinking
[21:47] <aks_> this post claims that both hibernate and sleep work "slowly
[21:47] <aks_> http://weblog.xanga.com/silverpentech/654740966/item.html
[21:47] <aks_> but work nonetheless
[21:47] <aks_> thanks
[21:53] <mgunes> aks, if it's slow it may be linked to bug #139045 (ata_piix driver issue, probably not brand specific but has to do with certain SATA controllers)
[23:12] <mrooney> whoa, there isn't a #nautilus?
[23:12] <mrooney> that is literally the first time ever there hasn't been a freenode channel for whatever noun or verb I need help with
[23:12] <ffm> mrooney: they use irc.gnome.org
[23:13] <mrooney> ffm: aaahh, thanks