[00:58] <niadh> Anyone know how I should mark bugs that are packaging requests? I have at least a dozen here.
[00:59] <bdmurray> niadh: for example?
[00:59] <niadh> Just look at this page for all the [needs packaging] bugs: https://bugs.launchpad.net/ubuntu/+bugs?field.status%3Alist=NEW&field.importance%3Alist=UNDECIDED&assignee_option=none&field.has_no_package=on&start=1500
[01:00] <niadh> for example R4Calc
[01:00] <niadh> Here is the example: https://bugs.launchpad.net/ubuntu/+bug/271351
[01:01] <bdmurray> niadh: it's fine the way it stands, it could be set to confirmed (if it isn't packaged) and an importance of wishlist
[01:02] <niadh> I can't set wishlist, I'm not approved as a bug hunter yet, I'm signed up to the team, and have been marking packages as and where I can, but I can't set wishlist
[01:03] <bdmurray> I wouldn't really worry about the needs-packaging bugs at this point in the release cycle
[01:03] <niadh> Well, I figure if I can assign them to a package or something then it's less orphaned bugs
[01:04] <bdmurray> niadh: needs-packaging bugs are actually one of the only ones that shouldn't have a package
[01:04] <niadh> Oh, fair enough.
[01:04] <niadh> I shall leave them as they are then.
[01:06] <niadh> Also I couldn't actually attach some packages, even though I could search for them
[01:06] <niadh> one was acpi
[01:06] <niadh> also madwifi I couldn't set as a package
[01:08] <bdmurray> you probably wanted acpi-support
[01:08] <bdmurray> for madwifi do you mean a wireless driver?
[01:09] <niadh> I shall try acpi-support
[01:09] <niadh> uhm, they listed an issue as being with madwifi, so that's what I attempted to set the package to
[01:10] <niadh> It is correct that I was told that anything to do with suspend/resume/sleep/wake is an acpi thing?
[01:11] <bdmurray> no, not really
[01:11] <niadh> Oh, then, I shall not mark the package as acpi then.
[01:12] <niadh> I watched a few screen casts of bug hunting and read an IRC transcript and someone said that acpi covers that stuff, file systems are a kernel thing and drivers largely are too.
[01:14] <bdmurray> you might https://wiki.ubuntu.com/DebuggingACPI helpful
[01:14] <bdmurray> find that helpful
[05:35] <dholbach> good morning
[05:39] <greg-g> good morning dholbach
[05:39] <dholbach> hi greg-g!
[05:39] <greg-g> just heading off to bed, you take it from here! ;)
[05:40] <dholbach> sleep tight, Greg! :)
[05:41] <greg-g> thanks, dholbach
[05:50] <maco> hi dholbach
[05:50] <dholbach> hiya maco
[06:03] <crimsun> not even a dent in the pie chart, sigh.
[06:06] <maco> crimsun: at all? :(
[06:07] <maco> crimsun: incomplete has gone back from 16% to 17% this week
[06:07] <crimsun> maco: well, I'm sure I'm contributing to that latter "statistic"
[06:08] <maco> just as i contributed to it going from 17 to 16 2 weeks ago?
[06:09] <crimsun> no clear idea, but likely
[06:22] <maco> crimsun: so you stopped triaging here, took the metro home, and went back to triaging?
[06:23] <maco> is there a way to unsubscribe someone from a bug?
[06:24] <crimsun> only if you're an admin of a team that someone is a member of or if you're that someone
[06:24] <crimsun> (the former is only for teams)
[06:25] <maco> bug 207883 someone wants to be unsubscribed (or rather "stop emailing me i dont know what's going on!")
[06:25] <crimsun> said person has the ability to unsubscribe himself
[06:25] <maco> yeah, i'm trying to explain that
[06:26] <crimsun> "how do I unsub from this mailing list that sends e-mails containing subscription information at the bottom of each bulk?"
[06:26] <maco> exactly
[06:29] <maco> crimsun: your location in lp is *definitely* south-east of me. which is also definitely wrong.
[06:29] <persia> There's actually a bug related to that: although I'm not sure if it applies in this case.  If someone is subscribed to all bugs for a package, and there is a bug with multiple tasks, it may not be possible for the subscriber to unsubscribe unless they unsubscribe from all bugs for that package.  An example in this case might be someone who cares about alsa-driver, but doesn't care about pulseaudio.
[06:31] <maco> persia: the person says they know nothing about computers
[06:31] <persia> This case is particularly odd, as the complainant has somehow chosen to be art of the "Ubuntu Audio Team".
[06:32] <persia> maco: Indeed, but they also aren't specifically subscribed to this bug, but rather a member of a notified team (and not through a bug subscription), which means there is no option to unsubscribe from that bug.
[06:33] <maco> oh. wait so shouldn't they be getting like 50 billion emails from launchpad anyway?
[06:33] <RAOF> Is this the same person that I'm thinking of...
[06:33]  * RAOF checks
[06:33] <maco> why are they only complaining on that bug?
[06:33] <persia> Well, it's only the Ubuntu Audio Team, so probably on the order of 10 million or so...
[06:34] <RAOF> maco: They're not complaining on just that bug :)
[06:34] <persia> But, yeah, unsubscribe doesn't work for a user with that configuration.
[06:34] <maco> RAOF: they complain everywhere?
[06:34] <crimsun> maco: deliberate obfuscation thanks to LP?
[06:34] <maco> RAOF: i havent seen it on any of the other audio bugs i'm subscribed to.  which as of this week is a lot.
[06:34] <RAOF> Certainly on a bug that I was subscribed to (and I wrote them an email).
[06:35] <maco> crimsun: your location? i thought you put our favourite bakery as your location, but it's got you down in like anacostia or something
[06:35] <persia> It's somewhat related to bug #83488 and bug #204980  I think more 204980 in this case
[06:35] <RAOF> Saying "you seem to have associated your email address with a this launchpad accound (link) and then subscribed to the audio team (link).  Unsubscribe from the audio team (link)"
[06:38] <maco> yelling at people to stop emailing you when they aren't emailing you specifically and you signed up doesn't exactly make sense in my mind
[06:41] <crimsun> mmm, alsa-driver bugs are nearly manageable
[06:41] <crimsun> unfortunately, the same can't be said regarding linux (well, formerly alsa-driver), alsa-lib, alsa-plugins, alsa-utils, pulseaudio, flashplugin-nonfree, libflashsupport, ...
[06:45] <maco> well yeah, now that all the linux bugs that were misfiled against alsa-driver have been put in their proper place
[06:46] <maco> oh yeah, hey anyone who hasn't read it, here's the updated version of the wiki sound page:  https://wiki.ubuntu.com/DebuggingSoundProblems
[07:17] <maco> 21098 new bugs...insane
[08:59]  * thekorn hopes dholbach has a good email filter, moving all buglog-data mails to trash
[09:00] <dholbach> thekorn: it's all good - thanks for your good work! :)
[09:00] <dholbach> thekorn: when is 0.3 supposed to land?
[09:02] <thekorn> dholbach, it's in intrepid, I'm preparing ppa packages for >feisty right now
[09:02] <dholbach> thanks :)
[09:03] <thekorn> let see what I still remember of your packaging sessions
[10:07] <Hew_> I'm getting a system freeze that happens very rarely (once or twice a week and I'm a heavy user) for an unknown reason (been happening since I started with alpha 1). Even alt-sysrq-k doesn't work. Any idea what this is / if it's known / how I can debug it?
[12:25] <murdok> How can I unmark a bug duplicate?
[12:28] <Ampelbein> murdok: click on "mark as duplicate" and delete the number
[12:29] <murdok> Ampelbein: done, thanks
[12:29] <murdok> :)
[15:18] <bddebian> Boo
[16:05] <[fFf]> what do you think about https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/273552
[16:05] <[fFf]> ?
[16:48] <dholbach> pedro_: what do you think about having the next hug day in the topic of #ubuntu-bugs? :)
[16:48] <dholbach> and on the fridge! :)
[16:48] <pedro_> dholbach: that'd be great, we only need someone to set it ;-)
[16:48] <pedro_> bdmurray:  ^ ? ;-)
[16:49] <dholbach> :-)
[16:49] <pedro_> yay!
[16:49] <dholbach> pedro_: do you know if ubuntu-news-team@lists.u.c is regularly mailed when a hug day is?
[16:50] <dholbach> popey: that's the right mailing list, right?
[16:50] <pedro_> mm according to https://wiki.ubuntu.com/UbuntuBugDay/Draft
[16:50] <pedro_> they should
[16:51] <dholbach> great
[16:52] <dholbach> was just wondering because there's no hug day on http://fridge.ubuntu.com/event
[16:52] <popey> dholbach: yeah, i think so
[16:53] <pedro_> dholbach: right, I'll send an email now
[16:53] <bdmurray> didn't they switch the name?
[16:53] <dholbach> bdmurray: I think that's the new one
[16:53] <dholbach> it was called fridge-devel@ before
[16:53] <bdmurray> cool, I probably updated it too ;)
[16:53] <popey> it is
[16:54] <pedro_> yes http://fridge.ubuntu.com/about <-
[16:55] <dholbach> ROCK
[16:55] <dholbach> more hug day marketing! :)
[17:22] <chrisccoulson> i'm not quite sure what pitti is asking me for in bug 271364 (comment 9) - i don't know whether anyone here could shed some light before i contact him?
[17:26] <bdmurray> chrisccoulson: I think he'd like you to submit a bug to debian regarding POT building
[17:27] <chrisccoulson> the 'POT building' was the bit i was unsure about;)
[17:30] <bdmurray> chrisccoulson: I'd check with him then.
[17:31] <chrisccoulson> no problem. thanks
[17:36] <bdmurray> pedro_: I wonder if we should incorporate http://status.qa.ubuntu.com/qapkgstatus/update-manager/ into the bug day wiki page
[17:38] <bdmurray> or maybe just the triaging graph - http://people.ubuntu.com/~brian/complete-graphs/update-manager/plots/update-manager-1day-triaging.png
[17:39] <pedro_> bdmurray: yeah!, the second one it's better for the task
[17:39] <pedro_> bdmurray: i'll update the page with it
[17:39] <bdmurray> pedro_: great!
[18:11] <maco> apachelogger: looking at 5aday stats, i must say: O_O
[18:12]  * apachelogger didn't add since 2008-08-17 ;-)
[18:14] <maco> ah
[18:14] <maco> i was just calculating it, and to do 455 bugs at one bug a minute, it'd take 7 hours solid
[18:22] <maco> apachelogger: i do find it quite odd though that you're not showing in the "ever" list when you should be number 15
[18:23] <apachelogger> maco: I pipe the bug mails to a file then process the file witha  script which spits out all the bugs I was working on
[18:24] <apachelogger> in fact, I think 5aday should do this
[18:24] <apachelogger> adding bugs manually is not exactly very productive
[18:26] <greg-g> apachelogger: +1 !
[18:27] <greg-g> I mean, 5-a-day should just be a subset of information which is used for LP Karma
[18:27] <apachelogger> *nod*
[18:40] <jcastro> what would be awesome would be if someone used the lp bugs api to make it so we don't need the 5-a-day app at all.
[18:40] <jcastro> it should just say "jorge touched this bug and he's in the lp team, bugcount++"
[18:44] <salty-horse> anyone else seeing "Unknown media type" warn configuring packages? e.g. "Unknown media type in type 'interface/x-winamp-skin'"
[19:07] <sven__> I found an intrepid kubuntu bug for the "resize and rotate display" control pannel, and I wish to see if the bug is arleady in the system but i'm not sure whit package it's in.
[19:23] <greg-g> sven__: you can search all the bug reported against Ubuntu (including Kubuntu) by searching here: https://bugs.launchpad.net/ubuntu
[19:24] <greg-g> hey! the "new" bugs part of the pie chart is down to 48%! it was stuck at 49% for what feels like forever
[19:25] <greg-g> the fact that I never see that pie chart might have something to do with that ;)
[19:30] <jjesse> yay
[19:30] <jjesse> is the pie chart on the "main" bug page?
[19:32] <greg-g> jjesse: yeah
[19:32] <greg-g> for Ubuntu, of course.
[19:43] <bdmurray> thekorn: what is the unsupported contenttype error about in py-lp-b?
[21:42] <thekorn> bdmurray, sorry, which one?
[21:43] <bdmurray> thekorn: I think I got it - I was getting an error with a content type of "text/x-log"
[21:44] <bdmurray> so I added that to to the list of allowable content types
[21:44] <thekorn> "text/x-log"? - what a strange contenttype
[21:44] <bdmurray> the attachment name ended in ".log"
[21:47] <bdmurray> Its unfortunate the error doesn't say which bug was causing the problem
[21:47] <thekorn> hmm, It should give you a bugnumber, let me check
[21:49] <thekorn> bdmurray, oh, I see, it's a bug, but can be fixed easily
[21:51] <thekorn> will fix it tomorrow morning
[21:51] <bdmurray> great, thanks!
[22:10] <thekorn> bdmurray, as a start, but have to improve it a bit tomorrow: http://paste.ubuntu.com/49842/
[23:05] <chrisccoulson> ping maco
[23:10] <mrooney> Is anyone aware of a metabug regarding ath5k_pci CPU usage / poor wireless performance?
[23:11] <Ampelbein> mrooney: i think there is one. sounds familiar.
[23:13] <Ampelbein> bug 267761 is yours?
[23:13] <mrooney> Ampelbein: yeah, I was just about to link to it :)
[23:14] <mrooney> I can't figure out if I should be blacklisting something or, what I should be trying, or if other users are experiencing similar things I can't find the dupe
[23:15] <chrisccoulson> i can't find any other performance related bugs for ath5k_pci
[23:15] <Ampelbein> perhaps there is none and i just remembered wrongly
[23:16] <mrooney> chrisccoulson: isn't there something I can blacklist to get a different driver?
[23:17] <chrisccoulson> i'm not sure actually
[23:19] <chrisccoulson> have you tried blacklisting ath5k_pci?
[23:19] <mrooney> I seem to perhaps recall similar bug reports for similar speed issues relating to atheros + intrepid
[23:19] <bdmurray> mrooney: is this an upgrade or a fresh install?
[23:19] <mrooney> bdmurray: A fresh install of Intrepid Alpha..4 I think
[23:20] <mrooney> originally linux 2.6.26, which had the same exact issues
[23:20] <bdmurray> mrooney: is there anything configured in /etc/network/interfaces?
[23:21] <mrooney> bdmurray: just "auto lo\niface lo inet loopback"
[23:21] <bdmurray> mrooney: okay, I'd had similar issues on a system of mine that I haven't had time to investigate
[23:22] <mrooney> ahh yes, I believe I did a fresh install of A4, had the issues, then did a fresh install A5 to get a fresh 27 kernel, and have the same issues
[23:22] <mrooney> bdmurray: oh, okay, perhaps I am not alone!
[23:22] <mrooney> bdmurray: is my interfaces file indicative of an issue?
[23:24] <bdmurray> mrooney: I had some configuration in e-n-i that probably was causing my issue
[23:24] <mrooney> oh okay
[23:25] <mrooney> ah yes my bug description explains what I did fairly well
[23:25] <mrooney> well, I hope someone knowledgeable takes a look at it or can direct me to the next step
[23:25] <mrooney> otherwise I guess no Intrepid for me
[23:26] <bdmurray> the latest madwifi update in tim's ppa seems to be from sept 5th
[23:26] <bdmurray> so I don't think that would help
[23:27] <bdmurray> ath5k phy0: noise floor calibration timeout (2417MHz)
[23:27] <bdmurray> that looks interesting
[23:27] <mrooney> hmmmm
[23:28] <mrooney> bdmurray: oh yeah there are a bunch of things around there
[23:28] <bdmurray> ogasawara: can you lend a hand?
[23:29] <mrooney> wow, there's so many of them and other "unable to reset..."
[23:31] <bdmurray> mrooney: so googling for that message was somewhat helpful
[23:31] <bdmurray> http://kerneltrap.org/mailarchive/linux-ath5k-devel/2008/7/20/2580364
[23:31] <ogasawara> mrooney, bdmurray:  I'll take a peek as well
[23:32] <bdmurray> hmm, that's in the intrepid ath5k driver though
[23:33] <mrooney> bdmurray: I also found http://madwifi.org/ticket/2083 though I can't tell if those "errors" I see are normal or not, so I don't know if it is logical to find them in other places
[23:42] <mrooney> I'll be right back