[00:07] <bdmurray> it looks like there are only ~60 New 2.6.22 bugs now
[00:07] <secretlondon> :)
[00:08] <secretlondon> I saw all the green on the hug day page - I wondered if there were any left!
[00:08] <bdmurray> I don't think we put them all on.
[00:08] <bdmurray> right ogasawara?
[00:09] <secretlondon> yeah - only 75
[00:09] <ogasawara> bdmurray: right
[00:09] <secretlondon> so all .22 have gone, I'm working on .20
[00:09] <bdmurray> right, I was thinking we might be able to finish off the .22 New bugs though
[00:09] <ogasawara> secretlondon:  great :)  there are more .22 ones, may 30-40 more?
[00:10] <secretlondon> would you prefer me to look at the .22s?
[00:10] <bdmurray> I just thought it would be exciting to have .22 at 0
[00:11] <secretlondon> agreed
[00:11] <secretlondon> i'll have a look
[00:11] <ogasawara> secretlondon: either .20 or .22 is fine.  I just think the .22 ones might be more useful since they are closer to Hardy
[00:11] <secretlondon> :)
[00:12] <bdmurray> hmm, yeah it's a 44 and the graph is behind
[00:14] <bdmurray> -1
[00:16] <bdmurray> -1 more even
[00:21] <bdmurray> ogasawara: how do I find the xen config?
[00:23] <ogasawara> bdmurray: I'm guessing linux/debian/binary-custom.d/xen
[00:26] <bdmurray> ogasawara: you winner
[00:26] <ogasawara> :)
[00:30] <bdmurray> secretlondon: oops, I was looking at 148900
[00:30] <secretlondon> sorry
[00:30] <bdmurray> secretlondon: it's okay, it is actually fixed
[00:30] <secretlondon> oh cool
[00:30] <secretlondon> I've been going through with the "please test on hardy" boilerplate
[00:31] <bdmurray> That one actually had enough info to research
[00:32] <secretlondon> ok
[00:39] <secretlondon> bdmurray: so ones that could have enough info to research I should leave rather than asking them to check?
[00:40] <bdmurray> secretlondon: Do you have an example?
[00:41] <secretlondon> bdmurray bug #152741
[00:41] <ubotu> Launchpad bug 152741 in linux-source-2.6.22 "network performance and cpu usage in gutsy vs feisty" [Undecided,New] https://launchpad.net/bugs/152741
[00:44] <bdmurray> secretlondon: that one has enough for ogasawara or me to look at it I think
[00:44] <bdmurray> Thanks for bringing it up
[00:44] <secretlondon> ok
[00:47] <ogasawara> bdmurray: I've actually been asking to test against hardy since I'd rather 1 - get a response to make sure I'm not gonna waste my time, and 2 - I'd rather investigate against current hardy kernel which is under development
[00:47] <bdmurray> that bug seemed important enough to me that I thought it would be worth researching
[00:48] <bdmurray> the lkml thread has a patch too
[00:48] <ogasawara> bdmurray: holly cow I didn't even see the link to lkml
[00:48] <ogasawara> I think it blended in with the "Offer to mentor someone. . ." link
[00:49] <bdmurray> That almost seems SRU worthy to me for Gutsy
[00:49] <secretlondon> I had a quick look but didn't get as far as the patch
[00:50] <bdmurray> secretlondon: I cheated and only read certain posts from people's names that I have heard of before
[00:50] <secretlondon> ah! I'd not heard of any of them ;)
[00:52] <bdmurray> ogasawara: so it looks fixed in Hardy and not in gutsy
[00:52] <ogasawara> bdmurray: I didn't look at the patch, is it intrusive?
[00:54] <bdmurray> ogasawara: 6 lines, 5 of which are comments but it's in random.c
[00:55] <bdmurray> but it's well tested I'd say
[00:55] <ogasawara> bdmurray: that's sounds harmless enough.  care to post a comment it's fixed in hardy and just inline the patch or add the git commit id.  I'll add it to the buglist.
[00:55] <ogasawara> bdmurray: gotta run though (literally)
[00:55] <bdmurray> ogasawara: see ya!  should I save the graphs later or will you?
[00:56] <ogasawara> bdmurray: I'll save em later tonight.  thanks!
[00:59] <Jimerson> Hello all.
[00:59] <bdmurray> hello Jimerson
[00:59] <secretlondon> hi
[01:00] <secretlondon> Jimerson: you came yesterday and wanted to get involved with bug triage?
[01:01] <Jimerson> secretlondon, thats correct, I know I am a little late.
[01:01] <secretlondon> Jimerson: bdmurray is your man :)
[01:02] <bdmurray> It's not late here.
[01:02] <Jimerson> I see :)
[01:02] <Jimerson> How are you sir?
[01:04] <bdmurray> I'm doing pretty well.
[01:04] <Jimerson> as secretlondon said, I am looking to try and help with bugs.
[01:04] <Jimerson> And I am trying to find someone to give me a kick in the right direction.
[01:05] <bdmurray> One the problems I have with getting people started is that there are so places you could go.  Do you have a particular area of interest or type of role you'd like to fulfil?
[01:06] <Jimerson> I eventually would like to build packages, I don't know if I have the skills for that, but I was told to start here before doing anything else.
[01:07] <bdmurray> Is there a particular piece of software in Ubuntu that you like to use or are familiar with?
[01:08] <Jimerson> Nothing in particular, I'm willing to work with anything and go where I am needed.
[01:12] <bdmurray> Jimerson: okay, I'm trying to find us something to look at
[01:13] <Jimerson> bdmurray, great.
[01:14] <bdmurray> If we look at http://people.ubuntu.com/~brian/reports/yesterday/ we'll see bug reports that came in "yesterday"
[01:14] <Jimerson> ok
[01:16] <bdmurray> lets just take bug 199306 as an example
[01:16] <ubotu> Launchpad bug 199306 in ubuntu "Trac "500 - Internal Server Error" for Help/Guide" [Undecided,New] https://launchpad.net/bugs/199306
[01:16] <Jimerson> Ok, I am looking at it.
[01:18] <bdmurray> well, its actually a kind of crazy bug.  does it make much sense to you?
[01:19] <Jimerson> Not really, he took a config file from a bsd machine. getting some weird errors.
[01:20] <Jimerson> Is this even supported as it is not a clean install?
[01:20] <bdmurray> I think it should be fine but can't say for certain.
[01:20] <Jimerson> ok
[01:21] <bdmurray> It sounds like getting his configs might be useful tough.
[01:21] <bdmurray> Additionally, this bug isn't filed about a package bug all of Ubuntu rather
[01:21] <Jimerson> for lighthttpd and trac?
[01:21] <Jimerson> I saw that.
[01:22] <bdmurray> Assigning it to a package will help a lot as then other people like the package maintainer will be subscribed to the bug report.
[01:22] <Jimerson> I don't see trac or lighthttpd in the packages.
[01:22] <bdmurray> And yes in regards to which config files to ask for.
[01:22] <Jimerson> When I did a search.
[01:25] <bdmurray> a search?
[01:25] <Jimerson> Perhaps I am getting ahead of myself.
[01:25] <Jimerson> I thought you said it needed to be assigned to a package.
[01:26] <bdmurray> yes, that's correct
[01:26] <Jimerson> What should it be assigned to?
[01:26] <bdmurray> we can do that as a separate step.  what do you think it should be assigned to?
[01:26] <Jimerson> Trac I would assume.
[01:27] <Jimerson> Error looks like something wrong with trac, not the server, unless I read it incorrectly.
[01:27] <bdmurray> That sounds right to me and the trac maintainer / bug triager would know if it belonged somewhere else
[01:29] <Jimerson> So I'm going to take a guess here, assign it to package trac, post requesting config files and is that it?
[01:29] <bdmurray> That'd be the, for lack of a better word, minimum
[01:29] <Jimerson> ok
[01:30] <Jimerson> Could you elaborate then please :)
[01:31] <bdmurray> We could check that the have the latest version of trac installed.
[01:32] <bdmurray> We could also look at the list of files included in trac.
[01:32] <Jimerson> He is running the latest version of trac.
[01:34] <bdmurray> yep, just out of curiousity how did you check?
[01:34] <Jimerson> Went to the site to downloads, and checked for latest version :)
[01:35] <bdmurray> there is this neat script called rmadion where you can do things like 'rmadison -u ubuntu trac'
[01:36] <bdmurray> and if you go to packages.ubuntu.com you can see the list of files in the trac package
[01:36] <bdmurray> http://packages.ubuntu.com/gutsy/all/trac/filelist
[01:37] <bdmurray> I'd personally use packages.ubuntu.com rather than install it - in this case
[01:37]  * secretlondon had no idea rmadison existed
[01:39] <bdmurray> secretlondon: I feel there are lots tools like rmadison that aren't well advertised
[01:39] <secretlondon> I'm sure
[01:40] <bdmurray> secretlondon: Do you think mailing the bugsquad mailing list about that would be helpful?
[01:40] <secretlondon> yes, but I think the wiki more so
[01:41] <bdmurray> which page? I'm personally fond of BugSquad/KnowledgeBase
[01:42] <secretlondon> I use debuggingprocedures all the time
[01:43] <bdmurray> okay, I'll think about how to fit in there
[01:45] <bdmurray> Jimerson: still there?
[01:46] <Jimerson> sure am.
[01:47] <bdmurray> Does what I've said make sense so far?
[01:47] <Jimerson> so far yes.
[01:50] <bdmurray> I'm not so sure about the error any more and the usefulness of the file list.
[01:51] <bdmurray> So assigning the bug to the trac package and asking for config files would help.
[01:51] <Jimerson> I can't make sense of it.
[01:51] <Jimerson> The only thing I could find online about the error, he tried the fix for.
[01:52] <bdmurray> we could look for duplicates too
[01:52] <bdmurray> https://bugs.launchpad.net/ubuntu/+source/trac/+bugs
[01:52] <bdmurray> those are all the trac bugs in Ubuntu
[01:52] <bdmurray> I didn't see anything promising there
[01:53] <Jimerson> Does not appear to be anything.
[01:54] <bdmurray> The package is auto-synced with debian so we could look there too
[01:54] <bdmurray> but there isn't anything there either as far as I could tell
[01:54] <Jimerson> How do you know that?
[01:54] <Jimerson> That it is synced.
[01:54] <bdmurray> https://launchpad.net/ubuntu/+source/trac/
[01:55] <bdmurray> You can get there by clicking on Overview from the bug listing
[01:55] <bdmurray> the name at the end of the changelog is Ubuntu Archive Auto-Sync
[01:56] <Jimerson> Got ya.
[01:57] <secretlondon> it's also on the package uploader isn't it, on the main bug page
[01:57] <secretlondon> if the package uploader is autosync, we haven't touched it
[01:57] <secretlondon> and no xubuntuy ending
[01:58] <bdmurray> secretlondon: that's right on a specific bug's web page it will show you too
[01:58] <bdmurray> and the ~ubuntu package name is a good point too
[02:00] <bdmurray> I still really suspect something goofy with their copied over configs
[02:00] <Jimerson> They took track and the lighthttpd config from freebsd.
[02:00] <bdmurray> Jimerson: so most bug triaging is investigation into issues
[02:01] <Jimerson> So is there anything else we can do without their config's?
[02:02] <Jimerson> Seeing as no ones else seems to be having this issue.
[02:03] <bdmurray> Maybe look into how python is setup on FreeBSD?
[02:03] <bdmurray> That seems like a stretch to me though.
[02:03] <secretlondon> I'm a total deadend on the ancient Bug #24776 - similar bugs submitted all over the place, non fixed
[02:03] <ubotu> Launchpad bug 24776 in linux-source-2.6.22 "ipw2100 error Fatal interrupt. Scheduling firmware restart." [Undecided,Invalid] https://launchpad.net/bugs/24776
[02:05] <secretlondon> bugs that appeared in breezy and are still open in gutsy's kernel..
[02:07] <bdmurray> Jimerson: so assigning the package, asking for configs, setting the status to Incomplete and subscribing to the bug will help a lot
[02:07] <secretlondon> hi bddebian
[02:07] <Jimerson> I should do that?
[02:08] <bdmurray> yeah, that'd be great
[02:08] <secretlondon> you'll find at least 50% never reply
[02:08] <Jimerson> Should I assign the bug to someone or leave it unassigned?
[02:08] <bdmurray> Assignment is generally used when someone is working on a fix and the bug's status is In Progress
[02:09] <bddebian> Hi secretlondon
[02:10] <Jimerson> Woohoo!
[02:11] <bdmurray> Jimerson: Great!
[02:11] <Jimerson> Look good to you?
[02:11] <bdmurray> Well, my dinner is ready I'll be back in a bit.
[02:12] <Jimerson> Enjoy.
[02:12] <Jimerson> I'll be back in a bit as well.
[02:12] <bdmurray> Jimerson: Yeah, I usually thank people for helping to make Ubuntu better or something along those lines.
[02:12] <Jimerson> Ahh. I'll remember that next time.
[02:13] <bdmurray> Jimerson: we have some standard replies that we use at http://wiki.ubuntu.com/Bugs/Responses
[02:13] <Jimerson> Thank you so much for your help.
[02:14] <bdmurray> Jimerson: Thank you!  I'm here almost all the time so stop by if you have any questions.
[02:14] <Jimerson> I'll be bugging you in a bit after I have some dinner.
[03:22] <bdmurray> secretlondon: I've done a bit of research into the ipw2100 issue
[03:23] <secretlondon> bdmurray: thanks. it looks like that error is a standard barf
[03:23] <bdmurray> it seems documented in the last tarball upstream made
[03:23] <bdmurray> in January of 2007
[03:23] <secretlondon> ah jan 07 :(
[03:24] <secretlondon> so it's a known bug - and on the driver?
[03:24] <bdmurray> afaict so far my firefox just locked up though
[03:27] <secretlondon> I've confirmed #50431 as I can see that the acpi chip isn't supported, and googling for the ID doesn't show anyone supporting in linux (and it's ancient)
[03:27] <bdmurray> secretlondon: this is the right upstream bug
[03:28] <bdmurray> http://bughost.org/bugzilla/show_bug.cgi?id=329
[03:28] <ubotu> bughost.org bug 329 in __UNSPECIFIED__ "Fatal interrupt error appear when the least congested channel is selected on AP." [Major,Assigned]
[03:28] <secretlondon> thanks
[03:28] <bdmurray> and it just seems stuck
[03:28] <bdmurray> I'd guess intel isn't working on it anymore
[03:29] <secretlondon> is it old hardware?
[03:29] <bdmurray> I also imagine we have some duplicates of it.
[03:29] <secretlondon> yeah I'm sure. probably filed on all sorts
[03:30] <bdmurray> The web page for the project was last updated 1/31/2007 and some newer hardware by intel is the 2200 2915 and 3945
[03:31] <secretlondon> it's kinda out of our hands really, the firmware is closed souurce too which won't help
[03:33] <secretlondon> some of these bugs are *ancient*, pre dapper even
[03:40] <bdmurray> so its still a valid bug for 2.6.24 and won't fix for earlier versions
[03:41] <secretlondon> ok
[03:41] <bdmurray> and we can point people at the upstream bug but I don't anything would happen
[03:45] <secretlondon> bug #86859 you closed at fixed, someone reopened as occurring in feisty and opened on gutsy's kernel instead. they do seem to have the right sort of chip to be affected by it
[03:45] <ubotu> Launchpad bug 86859 in pitivi "Pitivi doesn't start / program doesn't open" [Medium,Invalid] https://launchpad.net/bugs/86859
[03:46] <secretlondon> bug #68659
[03:46] <ubotu> Launchpad bug 68659 in linux-source-2.6.15 "Certain VIA-based chipsets erroneously enable DXS support" [Undecided,Fix committed] https://launchpad.net/bugs/68659
[04:12] <crimsun> hmm
[04:12] <crimsun> 68659 sounds like my wording
[04:13] <crimsun> heh, yep.
[04:13] <crimsun> and I don't think that patch was pushed upstream..?
[04:13] <secretlondon> I don't know
[04:14] <crimsun> (I'm looking now)
[04:14] <secretlondon> thanks
[04:15] <crimsun> nope, it wasn't
[04:15] <crimsun> so the issue remains relevant to feisty, gusty, and hardy
[04:15] <crimsun> and if only hardy will be addressed, ...
[04:18] <secretlondon> rest won't fix I guess
[04:18] <secretlondon> tis is presuming that upstream hasn't fixed independently of us
[04:23] <crimsun> it hasn't
[04:23] <crimsun> I just checked upstream's VCS
[04:23] <secretlondon> okay thanks
[04:25] <secretlondon> bah I can hear bird song
[04:43] <techno_freak> kewl, i can hear only crows singing
[04:43] <techno_freak> or rather, communicating
[04:43] <secretlondon> 4.40am here
[04:44] <techno_freak> 10.14am here
[04:51] <secretlondon> night all
[06:36] <techno_freak> is there anything in the wiki on debugging gnomebaker or the CD/DVD drive? what logs should i ask from the orig reporter?
[08:27] <harrisony> Can i get someone to renew my subscription in ubuntu-bugcontrol
[09:17] <harrisony> oh yeah forgot the url https://edge.launchpad.net/~harrisony
[11:53] <Iulian> Heya
[11:58] <techno_freak> heya
[14:49] <bddebian> Boo
[14:49] <ogra_cmpc> bee
[14:50] <bddebian> ;-)
[15:16] <jdstrand> bdmurray: fyi-- I created a patch for bug #192575 (it's in the report)
[15:16] <ubotu> Launchpad bug 192575 in python-launchpad-bugs "HTTPConnection: Firefox 3 stores cookies in sqlite database" [Medium,New] https://launchpad.net/bugs/192575
[16:23] <bdmurray> jdstrand: I noticed
[16:24]  * jdstrand nods
[16:24] <bdmurray> I'm excited to check it out
[16:26] <hggdh> ahhhh bugs-announce lives...
[16:32] <bdmurray> harrisony: You are all set.
[18:59] <intellectronica> bdmurray: ping
[19:02] <bdmurray> intellectronica: hello
[19:03] <intellectronica> bdmurray: hi, just wanted to let you know that shortly those missing launchpad notifications will start making their way into your mailing list, so you may experience a bit of traffic here
[19:03] <bdmurray> intellectronica: we moved the bot to another channel, but thanks for letting us know.
[19:04] <intellectronica> bdmurray: cool. which channel, b.t.w?
[19:04] <bdmurray> intellectronica: ubuntu-bugs-announce
[19:05] <Laibsch> Hi, is there a dedicated mozilla/firefox team?
[19:05] <bdmurray> Laibsch: yes, there is see https://wiki.ubuntu.com/MozillaTeam for more information
[19:08] <Laibsch> I believe bug 144560 describes expected behaviour.
[19:08] <ubotu> Launchpad bug 144560 in mozilla-firefox "doesn't prompt for certificate" [Undecided,New] https://launchpad.net/bugs/144560
[19:08] <Laibsch> bdmurray: Thanks for pointing that out
[21:23] <sdh> bugs!
[21:23] <sdh> bugs, everywhere
[21:24] <h3sp4wn> Yep can anyone give me any advice in what I need to put in a bug report regarding the keys on a Sun usb keyboard not working right (its meta I am bothered about but having undo , cut , paste , copy working might be nice)
[21:25] <h3sp4wn> In emacs meta is mapped to s- and alt is mapped to meta still
[21:26] <h3sp4wn> (Dunno exactly what people need - I guess I can test under ubuntu sparc as well but afaik there are no drivers for my video card in xorg at all (so not much use to me)
[21:28] <secretlondon> h3sp4wn my sun foo isn't great (I have an ultra 1 but thats it) but I'm surprised your video doesn't give any output in xorg
[21:29]  * secretlondon flicks bugs at sdh
[21:29] <h3sp4wn> secretlondon: Its an XVR-1000
[21:29] <h3sp4wn> Only XSun has drivers
[21:29] <secretlondon> please bug report the lack of video support
[21:30] <secretlondon> and I'll look at it
[21:30] <secretlondon> I'll just look to see what we need for keyboards
[21:31] <h3sp4wn> I can get a console but just not X
[21:32] <h3sp4wn> http://www.sun.com/desktop/products/graphics/xvr1000/ (cost me £200 second hand)
[21:32] <secretlondon> ok. please still bug report it so we know its an issue
[21:33] <h3sp4wn> Ok - I don't think it would be easy even with the specs to make a decent driver
[21:33] <h3sp4wn> (considering probably how few people use them)
[21:33] <secretlondon> sure, but its still useful
[21:34] <secretlondon> https://wiki.ubuntu.com/DebuggingKeyboardDetection
[21:35] <secretlondon> and https://wiki.ubuntu.com/X/Debugging for the x issue
[21:42] <h3sp4wn> dunno what I can do about the sparc X issue easily I would have to reformat the disks again
[21:42] <h3sp4wn> to get the information
[21:42] <h3sp4wn> unless there is a sparc-desktop cd somewhere
[21:44] <secretlondon> I don't think so - I think spacr is just a server cd
[21:44] <sdh> what does it mean when it says "Binary package hint" in launchpad ?
[21:44] <h3sp4wn> secretlondon: sort of implies no one cares anyway (they expect you to just use serial console)
[21:44] <secretlondon> h3sp4wn if you stuck solaris on it I undestand. Could you still give us a bug so we know?
[21:45] <h3sp4wn> secretlondon: Its running Solaris on it now - I can give you a bug but it won't have those logs
[21:45] <secretlondon> well I use X on my suns..
[21:45] <h3sp4wn> XSun ? or Xorg ?
[21:45] <secretlondon> please give us the bug and I'll go looking
[21:46] <h3sp4wn> k
[21:46] <secretlondon> actually logs from XSun would also be cool
[21:51] <h3sp4wn> ok, just had an idea - I will try a nexenta live cd (If they fixed it in their Xorg perhaps the patches can be got)
[21:52] <secretlondon> cool - actually comparing one that works with one that doesn't would be useful
[21:52] <h3sp4wn> thanks I will sort that stuff out tonight or tommorow morning
[21:56] <bdmurray> sdh: I believe it means someone picked a source package that is part of a larger binary package.  What bug were you looking at?
[21:56] <sdh> bdmurray: i see it around a lot, let me find an example
[21:56] <sdh> bdmurray: https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/59297 <- random example
[21:56] <ubotu> Launchpad bug 59297 in kdebase "kwin crashes when eclipse is started. sometimes." [Undecided,New]
[21:59] <bdmurray> sdh: kdebase provides a lot of packages
[21:59] <yuriy> bdmurray: i think you mean vice-versa
[22:00] <sdh> bdmurray: does the submitted put that "binary hint" stuff there or is it automagic?
[22:00] <yuriy> someone picked a binary package that is part of a larger source package
[22:01] <bdmurray> yuriy: right, my bad
[22:01] <bdmurray> sdh: the launchpad bug tracker adds it to the description
[22:02] <sdh> bdmurray: cool, thanks for the info!
[22:04] <bdmurray> sdh: no problem
[22:18] <blueyed> Should bugs in the network stack get assigned to "linux" first? (instead of "apport")
[22:21] <blueyed> secretlondon: you've been locking the 5-a-day-data branch quite often for me lately.. ;)
[22:21] <blueyed> cheers.
[22:21] <secretlondon> blueyed: locking?
[22:21]  * secretlondon has no idea how the backend works
[22:22] <blueyed> secretlondon: what tool do you use? "add-5-a-day" on cli?
[22:22] <secretlondon> the applet
[22:22] <blueyed> ah, but it does basically the same AFAIK.
[22:22] <blueyed> commit the change right away.
[22:22] <blueyed> that only means that you are committing quite some.. :)
[22:23] <secretlondon> when I've finished with a bug I make a new tab and drag the bugs tab over the applet
[22:23]  * blueyed suggests adding some mode which does commit only once a day (cron job?)
[22:23] <secretlondon> or saving them up and doing a few at once
[22:23] <secretlondon> say every hour
[22:23] <blueyed> I often collect bug numbers in a shell, then execute the command.
[22:24] <blueyed> yes
[22:24] <secretlondon> I know I forget to submit some
[22:24] <secretlondon> how long does it lock after each submit?
[22:24] <blueyed> during commit..
[22:25] <blueyed> ..or if a prompt for the ssh passphrase is waiting: as long as you notice it, even days probably.. :/
[22:25] <secretlondon> well that's only a few seconds I hope
[22:28] <blueyed> sure.
[22:29] <blueyed> Wasn't apport putting backtraces in the bug report for python tracebacks before? At least it should..
[22:44] <bdmurray> blueyed: do you have an example of a network stack bug?
[22:49] <sdh> blueyed: ah, there you are - thanks for the help with acpi-support earlier ;-)
[22:52] <RAOF> Hm.  Is the amd64 apport retracer known-broken?  It's stripped the needs-amd64-retrace tag from bug #199392 (twice!) but hasn't added any retrace.
[22:52] <ubotu> Bug 199392 on http://launchpad.net/bugs/199392 is private
[22:53] <blueyed> bdmurray: bug 196439
[22:53] <ubotu> Launchpad bug 196439 in linux "while uploading the reports apport lags the rest of the internet" [Medium,Confirmed] https://launchpad.net/bugs/196439
[22:54] <blueyed> sdh: bug 161745 ?
[22:54] <ubotu> Launchpad bug 161745 in acpi-support "Why isn't thinkpad-brightness-down.sh used for Lenovo thinkpads?" [Low,Confirmed] https://launchpad.net/bugs/161745
[22:55]  * blueyed tends to have to do quite a lot with acpi-support lately, after cherrypicking all the patches.. but no sponsor yet.. and in the meantime I fear it may miss Hardy even..
[22:55] <sdh> blueyed: yeah
[22:55] <sdh> what does the sponsor bit mean?
[22:55] <secretlondon> 'apport lags the rest of the internet' - what worldwide ;)
[22:56] <sdh> blueyed: if it doesn't make hardy, that will be very sad - i feel hardy could be really good on laptops if it's polished up a bit
[22:57] <blueyed> sdh: bug 193842 has a set of cherrypicked patches for acpi-support, but not for your bug yet..
[22:57] <ubotu> Launchpad bug 193842 in acpi-support "Please sponsor cherrypicked fixes for acpi-support into Hardy" [Medium,Triaged] https://launchpad.net/bugs/193842
[22:59] <sdh> blueyed: similar issues with pm-utils imho
[23:00] <sdh> blueyed: who can sponsor then?
[23:00] <bdmurray> blueyed: the kernel seems best but that report looks like a mess to me
[23:01] <blueyed> bdmurray: yes, unfortunately.. there should be similar reports though (=> gets duped hopefully)
[23:02] <blueyed> sdh: ubuntu-main-sponsors (a team of core-devs) can sponsor them.. but there are probably still issues..
[23:02] <blueyed> sdh: "incomplete" does not mean "not confirmed", but rather "need more info"..
[23:04] <bdmurray> blueyed: what do you mean?  the original reporter didn't put their release or hardware information.  Savvas might be running Hardy but it isn't clear.
[23:05] <sdh> blueyed: you mean incomplete on 161745? i confirmed because i had the same and can provide info
[23:05] <blueyed> sdh: yes, then please answer there :)
[23:05] <blueyed> bdmurray: are you talking about 161745, too?
[23:06] <bdmurray> blueyed: no bug 196439 that you brought up
[23:06] <ubotu> Launchpad bug 196439 in linux "while uploading the reports apport lags the rest of the internet" [Medium,Confirmed] https://launchpad.net/bugs/196439
[23:09] <blueyed> bdmurray: "In gutsy I didn't have this sort of problems, ..."
[23:10] <blueyed> I've changed the title to "hardy: uploading causes network lag"
[23:11] <sdh> blueyed: good questions on that bug, i've tried that already and will post
[23:12] <bdmurray> blueyed: okay, thanks.  I think kernel team would probably want their standard information
[23:17] <bdmurray> blueyed: by the way what needs to happen with bug 179492 now?
[23:17] <ubotu> Launchpad bug 179492 in exuberant-ctags "exuberant-ctags: python variables starting with "def" are shown as functions" [Unknown,Fix released] https://launchpad.net/bugs/179492