[00:01] <greg-g> "#ubuntu-bugs finding and triaging bugs in the English language since 2008."
[00:01] <maco> greg-g: find another bug in Elvish?
[00:01] <hggdh> in an *expanded* English language...
[00:04] <hggdh> not nessicerilie better one, BTW
[00:08] <Chorca> I have a bit of a question. I've got an issue where power/brightness status are updating very slowly, wondering if that's an acpi-support bug or under something else.
[00:09] <greg-g> Chorca: most likely acpi, yeah
[00:10] <Chorca> Alrighty. The dell i have takes like 30 seconds or so to update the status of the power (ac/battery/battery status, brightness) after something's changed, so i was assuming it was acpi.
[00:11] <Chorca> latest update broke things even more, so yeah, lol.
[00:11] <greg-g> yep, there are some acpi debugging documents on the wiki, if they might help you with reporting the bug.
[00:11] <greg-g> well that is unfortunate that the updates hurt instead of helped!
[00:12] <Chorca> Yeah, right now its plugged into the wall, the icon on the statusbar shows it's on battery.
[00:13] <Chorca> lol and the power history graph says my battery is at 556.0V :D
[00:13] <Chorca> this is one insane battery
[00:16] <greg-g> I've had those issues before, myself
[00:21] <Chorca> hmm.. now i'm wondering if it might have to do with GPM
[00:23] <Chorca> you know what, it might just be gnome.. HAL seems to be reporting the changes quickly, but after pulling the ac adaptor out, the power icon in the systray locks up.
[00:24] <greg-g> Chorca: interesting, check out Launchpad and search tos ee if you can find a similar bug, if not, go ahead and report that against g-p-m (from what you have told me)
[00:30] <Chorca> gnome-power-manager the same as g-p-m?
[00:31] <greg-g> Chorca: yep
[00:31] <greg-g> sorry, I like abbreviations ;)
[00:31] <Chorca> lol, i saw it in the bugs too, and i was just making sure. :)
[00:32] <Chorca> flippin' through the bugs there right now, seein' if there's something similar.
[00:33] <greg-g> Chorca: cool.
[00:34] <Chorca> Heh, do you know if the screen brightness OSD is handled by GPM as well?
[00:34] <greg-g> Chorca: for when you submit your bug report (if you don't find a duplicate) see this page, under "Filing a Bug report" https://wiki.ubuntu.com/DebuggingACPI
[00:35] <greg-g> I'm not sure, actually
[00:35] <Chorca> It's cool, just wondering. That seems to be affected when the icon locks up, so i was assuming. ;)
[00:35] <greg-g> could be then
[00:39] <Chorca> Found another bug.. it's about brightness zooming to full on it's own, but someone else mentioned the power manager hanging.
[00:39] <Chorca> guess there were some significant code changes upstream
[00:58] <thekorn> ./bugnumbers -p bughelper --parsemode api --cookie=~/cred_staging.txt
[00:58] <thekorn> argh, sorry
[02:46] <Hobbsee> Bug #95152
[03:37] <Hobbsee> drat, nullack's not here.
[03:41] <RAOF> Oh, why?
[03:44] <Hobbsee> was wondering if he was going to apply for uds sponsorship.
[05:28] <unifoundry> Would anybody like a super-easy bug to close today?
[05:30] <unifoundry> The following bug is no longer a bug: #122565.  You can install the latest version of the unifont package (unifont-1:5.1.20080914-1) on Hardy Heron/8.04 or later and you'll see that what is described there no longer happens.
[05:53] <dholbach> good morning
[05:55] <Hew> dholbach: good afternoon
[05:56] <greg-g> maco: what the second screenshot shows
[05:56] <dholbach> hi Hew
[05:56]  * greg-g waves to dholbach 
[05:56] <maco> greg-g: :-/ well that's freaky
[05:56] <maco> greg-g: install dd-wrt. fix it right up ;)
[05:56] <dholbach> hi greg-g :)
[05:56] <greg-g> you're telling me! I can't fix my wireless settings becuase of it
[05:57] <Hew> unifoundry: I have closed bug 122565. In future, you can close bugs yourself by changing the status at the top of the page.
[05:58] <sbeattie> Hew: heh, oops. I was just poking at that one, too; turns out it's a dupe of bug 185321
[05:59] <Hew> sbeattie: Even better :-)
[07:33] <thekorn_> good morning
[07:34] <dholbach> hiya thekorn_
[07:38] <thekorn_> hi dholbach,
[07:38] <thekorn_> the launchpad api has now a method to search and list bugs, it looks promising
[07:39] <dholbach> nice :)
[08:11] <Yasumoto> thekorn_: morning thekorn_ :)
[08:17] <thekorn_> hi Yasumoto
[09:20]  * Fallenou content ^_^
[09:33] <elmargol> bug #259278 is someone working on this?
[11:17] <Hew> elmargol: Although bug 259278 is not assigned to anyone, it is marked as release critical for Intrepid beta, so my guess is yes, someone is working on it.
[12:34] <elmargol> Any suggestions on bug #274357 ?
[13:31] <murdok> this is my first BugDay and it's not going so bad.. hehe
[13:31] <murdok> :)
[14:22] <wst> against which package should I file a bug about the newhuman theme in intrepid?
[14:23] <pedro_> wst: human-theme
[14:23] <hggdh> wst, probably against human-theme
[14:25] <wst> that includes newhuman too?
[14:26] <seb128> hi wst
[14:26] <wst> hi
[14:26] <seb128> could you stop tagging all the bugs which have not been reported before as potential regressions, that doesn't really makes sense
[14:27] <wst> I only tagged bugs in which the reporter stated that something was working in hardy or other earlier versions and is now broken in intrepid
[14:28] <wst> do you think that is wrong?
[14:29] <seb128> yes
[14:29] <wst> why?
[14:29] <seb128> what are those tags useful for?
[14:29] <wst> See https://wiki.ubuntu.com/QATeam/RegressionTracking
[14:30] <seb128> bug #193739 for example
[14:30] <wst> and http://people.ubuntu.com/~sbeattie/regression_tracker.html
[14:30] <seb128> sometime I've the impression the bugsquad team is creating work rather than doing some
[14:31] <wst> well I don't'know I didn't come up with that idea
[14:31] <seb128> what would you expect the tag to add on the bug just listed?
[14:31] <wst> but it seems useful to keep track of regressions
[14:32] <seb128> right, but "focus doesn't change on tab since cairo is used to display graphs rather than using the old widget" is a tiny detail, not likely trivial to change
[14:32] <seb128> what does the tag bring there?
[14:33] <seb128> bug #58661
[14:33] <wst> no matter if it is a tiny detail, it is still a regression, right?
[14:33] <seb128> this bug is there since edgy
[14:33] <wst> yes way too long
[14:33] <seb128> is there really a need to tag it as a regression now?
[14:34] <wst> it is regression-release
[14:34] <seb128> I'm questionning what you call regression
[14:34] <wst> a regression in a released version
[14:34] <seb128> every tiny graphical change is not a regression because some people don't like it
[14:34] <seb128> well, you could tag the whole launchpad as regression
[14:34] <wst> well than it can probably be closed as won't'fix
[14:34] <seb128> all those bugs didn't exist in 0.0.0 of softwares which had no feature
[14:35] <wst> ok well maybe on some of the tagged bugs you could debate wether it is a regression
[14:35] <hggdh> wst, this was not a regression, it is a change in presentation
[14:35] <wst> but I think most are right
[14:35] <seb128> nothing personnal against you, I just taking those example to start a discussion there ;-)
[14:35] <wst> no [problem
[14:35] <seb128> I'm asking what is the purpose
[14:35] <seb128> to find regression that should be fixed
[14:35] <seb128> or tag any tiny detail as regression for the pleasure of tagging
[14:36] <seb128> because it seems currently people just tag for tagging
[14:36] <seb128> and that doesn't make sense to me
[14:36] <seb128> ie a regression in edgy which is not a supported version doesn't make sense to report now
[14:36] <wst> henrik nilsen omma send out a mail to ubuntu-devel specifically asking for this
[14:36] <seb128> tag now rather
[14:36] <wst> tagging regrssions I mean
[14:37] <wst> perhaps it is good to discuss with him how useful this is?
[14:37] <wst> and what the scope should be
[14:37] <wst> and adjusting the wiki page accordingly
[14:37] <seb128> right as said I raise the topic on the chan for discussion
[14:37] <seb128> that was not especially with you
[14:38] <wst> yes ok
[14:39] <Hobbsee> hm, someone else has used launchpad for a bug with many tasks.
[14:39] <seb128> Hobbsee: hey ;-)
[14:39] <Tech2000> hi, could anyone explain what 'telepathy-butterfly' is doing? -or point me in the right direction where I can find that info...
[14:39] <Hobbsee> hey seb128!
[14:39] <Hobbsee> asac: looks like it was you!
[14:39] <Tech2000> telepathy-butterfly does crash very often without any interferance from the user..
[14:40] <seb128> Tech2000: apt-cache show telepathy-butterfly, it's basically a connection manager allowing you to use msn using pymsn for that
[14:40] <asac> Hobbsee: yeah. is that a problem?
[14:40] <asac> ;)
[14:40] <Hobbsee> asac: yes.
[14:40] <Tech2000> seb128: thx..
[14:40] <Hobbsee> asac: 272772 has a few comments indicating this, and it can also make launchpad fall over, so as someone who actually needs to man the queue occasionally, i'd ask that you refrain from filing bugs with many tasks :)
[14:40] <seb128> Tech2000: you probably use an instant messenger connecting to msn and using it
[14:41] <Hobbsee> asac: it's both the spam problem, and how it affects areas of launchpad in general.  It's better than it used to be, but stuff like that will probably still make it fall over.
[14:41] <Tech2000> seb128:  yeah..   I have just made the switch from Pidgin 2.5.1 to Empathy 2.24.0 and after that all problems with telepathy-butterfly started...
[14:41] <asac> Hobbsee: well. those were all from the ubuntu-docs package
[14:42] <asac> Hobbsee: which probably has a special audience
[14:42] <Hobbsee> asac: noted, but others have done it too.
[14:42] <seb128> Tech2000: that's it then
[14:42] <asac> Hobbsee: have done what?
[14:42] <asac> complained about bug mail?
[14:42] <Hobbsee> asac: yes
[14:42] <Hobbsee> asac: and it has stopped me being able to accept packages during hardy freezes too, incidently.
[14:43] <asac> Hobbsee: i dont think its a problem. in this case its unfortunate that a package which has a audience not used to bugmail was involved in a transition
[14:43] <asac> Hobbsee: hmm
[14:43] <Hobbsee> asac: getting a whole stack of bugmail about something completely unrelated to you isn't a problem?  I'm sorry, but i'm going to have to disagree with you there :)
[14:44] <Hobbsee> I'm getting really bored of getting random java mail, for a start.
[14:44] <asac> Hobbsee: maybe i am just used to bug mail. as i said its unfortunate that ubuntu-docs was in this transition
[14:45] <asac> Hobbsee: why do you get java mail?
[14:45] <asac> did you investigate?
[14:45] <Hobbsee> asac: yes, I'd say the effects were enhanced, due to the teams that were involved.  However, that doesn't make me inclined to think that other people should have to put up with it.
[14:45] <asac> Hobbsee: well. i definitly agree that launchpad has a bug or missing feature here. but i dont think its a big problem in general
[14:45] <Hobbsee> asac: because i'm one fo the maintainers of ubuntu-restricted-extras, and people sometimes add it to bugs that involve java, as that's how they got java.  They're just metapackages.
[14:46] <asac> Hobbsee: you can remove packages nowadays i think
[14:46] <asac> by just unsetting the package name of the "ubuntu-restricted-extras" task
[14:47] <Hobbsee> i think i tried that.  it didn't work.
[14:47] <Hobbsee> shouldn't we avoid this in the first place?
[14:47] <asac> Hobbsee: it didnt work in the past. yes. but i have used it a bunch
[14:47] <asac> Hobbsee: avoid what? document work you are doing?
[14:47] <Hobbsee> asac: i meant avoiding multiple bugs, which generate a lot more mail than the particular part people are subscribed to.
[14:48] <Hobbsee> er, multiple-status, single bugs
[14:48] <asac> multiple tasks is the right term i think
[14:49] <Hobbsee> right, yes.
[14:49] <asac> Hobbsee: launchpad lacks features
[14:49] <Hobbsee> asac: yes, many of them :-S
[14:49] <asac> Hobbsee: one feature that would help would be the ability to set dependencies of bugs
[14:49] <asac> e.g. blocks/depends
[14:50] <asac> in that way you could create a meta transition bug with individual bugs for each package
[14:50] <Hobbsee> asac: that'd be nice, yeah.  I wish :)
[14:50] <Hobbsee> asac: try to propose it to the LP guy sfor UDS, so it might get implemented for jaunty+1?
[14:50] <Hobbsee> or +2?
[14:50] <asac> Hobbsee: anotherw feature that would help would be to say that people that get "implicitly" subscribed through packages should only get "written" messages + automated mail related to their package
[14:50] <Hobbsee> asac: that's true
[14:51] <asac> e.g. people that come in from ubuntu-docs would only get all the human messages and the status messages for their package
[14:51] <asac> including the "fix uploaded" message only for ubuntu-docs
[14:51] <Hobbsee> asac: yeah, that would be cool.  I'd hope LP would implement that one day, but I have no (real) power to get it implemented.
[14:51] <asac> Hobbsee: i have given up on launchpad bugs ;)
[14:51] <Hobbsee> for now, i guess we just have to work around it
[14:51] <Hobbsee> asac: i didn't think you were allowed to say that publically :)
[14:53] <asac> Hobbsee: why not :) ... i dont say that launchpad bugs is a bad thing. in fact it has great features. unfortunately, for my case the missing features hit me hart
[14:53] <asac> hard
[14:53] <Hobbsee> asac: what are you using instead?
[14:53] <Tech2000> there seems to be a bug with dualhead and running the second screen in a 'separate x screen'   my primary screen is running a 4 sided cube while the second screen just have 2 sides while it's configured to have 4...
[14:53] <asac> Hobbsee: imo its perfect to do bugs for packages with low bug volume and an active upstream that is close to what we release with their trunk
[14:54] <Tech2000> should I report this as a bug?   if so.. where  -at launchpad?
[14:54] <Hobbsee> asac: that's true.  it works very nicely for smallish projects.
[14:55] <asac> Hobbsee: i am using launchpad ... how couldnt i
[14:55] <asac> but its not effective for me anymore
[14:55] <asac> i cant find duplicates
[14:55] <asac> in firefox
[14:55] <asac> which makes the buglist grow longer and longer
[14:55] <asac> which makes it even harder to find duplicates
[14:55] <Hobbsee> heh, that's true.  I was just hoping you had a solution
[14:55] <Hobbsee> i used to use bughelper a fair bit, but i don't think i have the newer runes
[14:55] <asac> Hobbsee: well. the solution is to run a script to import everything in your own local db i guess
[14:56] <asac> so you can do your own queries
[14:56] <asac> but i havent found time to do that
[14:56] <Hobbsee> hmmm....
[14:56] <asac> bughelper is cumbersome. its just too slow and you usually dont know which strings will be used in duplicates
[14:56] <asac> its too much trial and error to use something that gives you results like 3 hours later
[14:57] <Hobbsee> that's true.
[14:57] <Hobbsee> i wonder what QA can do to help with that, particularly with the new APIs
[14:58] <asac> Hobbsee: they could provide us with regular db snapshots :) (and of course code the bot that fills the db)
[14:59] <Hobbsee> hmmm....
[15:09] <hggdh> question: who interfaces with repositories mirror adminstrators?
[15:12] <Hobbsee> er, i think there's a team for that on LP
[15:13] <hggdh> The "Ubuntu Mirror Admins"?
[15:14] <Hobbsee> hggdh: yeah, https://edge.launchpad.net/~ubuntu-mirror-admins
[15:15] <hggdh> ok, thanks. And, of course, hello, Hobbsee ;-)
[15:15] <Hobbsee> hggdh: hey there!
[15:54] <Hobbsee> damn.  my sound broke
[15:56] <Hobbsee> gstalsasink.c(528): set_hwparams (): /play/abin/audiosinkbin/audio-sink/bin4/alsasink1:
[15:56] <Hobbsee> Unable to set hw params for playback: Invalid argument
[15:58] <bdmurray> mvo: I set bug 87914 to Fix Released based off the test you included in it, is that correct?
[15:59] <mvo> bdmurray: yes, thanks!
[15:59] <bdmurray> mvo: great, your test case was quite helpful ;)
[16:00] <bdmurray> mvo: I also added a patch to bug 272726, but wasn't sure if it is too late in the release cycle.
[16:02] <mvo> thanks bdmurray, I think that is ok as long as I unfuzzy the string by hand in the translations
[16:02] <mvo> (or someone else ;)
[16:03] <bdmurray> you mean update all the po files?  I could do that.
[16:07] <bdmurray> mvo: I was looking at the update-manager bugs with patches and noticed that bug 33505 was listed but those patches are for the apt task not for the update-manager one correct?
[16:16] <bdmurray> mvo: ?
[16:35] <bdmurray> mvo: bug 228510 has received a few duplicates today and is curious
[16:37] <mvo> bdmurray: sorry, got distracted for a moment
[16:37] <mvo> bdmurray: I check the two ones you posted
[16:47] <ara> bdmurray: one quick question, https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/95327 seems to be fixed in intrepid. should i mark it as invalid or fix released?
[16:48] <mvo> ara: fix released, I vaguely remember it and that it got fixed some time ago
[16:48] <ara> mvo: ta!
[16:50] <bdmurray> ara: In your Fix Released comment if you could document the steps you took to verify it was fixed that'd be helpful too.
[16:50] <ara> bdmurray: sure
[16:51] <mvo> bdmurray: 228510> I have a look, I think this is a long standing bug in the kde part of the code, that it can not deal with this error condition, but I double check to be sure
[16:51] <bdmurray> mvo: the dpkg interupt?
[18:15] <bdmurray> mvo: so what should happen with bug 228510?
[18:15] <mvo> bdmurray: I need to look at it and see if I can reproduce it
[18:16] <bdmurray> mvo: okay, its kubuntu specific though correct?
[18:20] <mvo> bdmurray: yes
[18:21] <mvo> bdmurray: the gtk version deals with that automatically and fixes it
[18:59] <bdmurray> mvo: I've added another patch to bug 272726, is that what you are looking for?
[19:17] <bdmurray> murdok: you made bug 161922 a duplicate of 46245?
[19:17] <bdmurray> I'm not certain that's correct
[19:22] <bdmurray> mvo: bug 46245 is really about connecting via ftp correct?
[19:30] <mvo> bdmurray: let me check
[19:53] <mvo> bdmurray: bug 46245 seems to mix unreleated issues, comment 11 for exmaple looks fine
[19:54] <bdmurray> mvo: right, I think people were looking at the message, not the reason for the message
[19:55] <bdmurray> which in 46245 is due to ftp correct?  I went through the update-manager changelog and didn't see anything though
[19:55] <mvo> bdmurray: yeah, I think the original bug is fixed, but because the message can be caused by different reaons, the duplicates needs careful checking too
[19:55] <bdmurray> mvo: okay, I'll take care of that and cleanup the title of 46245
[19:55] <mvo> bdmurray: yes, that was about the ftp stuff, the reason was that it didn't consider the ftp site a valid mirror and therefore commented it out on upgrade.
[19:55] <mvo> bdmurray: I think the fix was simply to update the mirror list
[19:55] <mvo> bdmurray: thanks a lot for this!
[19:57] <mvo> bdmurray: re bug 272726> yes, that is perfect
[19:59] <mvo> bdmurray: patch commited, thanks
[19:59] <bdmurray> mvo: \o/
[20:11] <bdmurray> mvo: are there any free space checks of /tmp done?
[20:11] <mvo> bdmurray: no, I don't think so
[20:12] <mvo> bdmurray: is there a bug about this?
[20:12] <bdmurray> I thought I saw a kernel bug yesterday where there wasn't enough free space in tmp when doing something
[20:15] <bdmurray> mvo: bug 273889 is the one I was thinking about
[20:16] <bdmurray> hmm, I think ubottu has a bug
[20:18] <mvo> bdmurray: hm, it seems like it happend on a regular update, I wonder if /tmp was on a tmpfs or something - but nothing indicates it was
[20:20] <bdmurray> mvo: but if /tmp if used by some packages should it be checked for free space?
[20:20] <hggdh> bdmurray, I will look at eeebotu's logs...
[20:21] <hggdh> darn, this is not -announce...
[20:35] <mvo> bdmurray: yes, however I have no idea right now how much is actually required in tmp by e.g. the kernel
[20:36] <bdmurray> mvo: okay, I'll submit a bug and see what I can find out
[21:09] <Hamra> hi i'm new in the bugsquad, and would like to ask if this is considered a wishlist or not? https://bugs.launchpad.net/ubuntu/+source/network-manager-vpnc/+bug/262191
[21:13] <bdmurray> Hamra: Welcome and thanks for helping out!
[21:14] <bdmurray> Hamra: with regards to the bug you've pointed out I don't think so.  Why do you ask?
[21:16] <Hamra> i'm just new to triaging, and wasn't sure how to sort this out.
[21:18] <bdmurray> Well, that particular bug looks a bit special
[21:19] <murdok> bdmurray: Yes i marked bug duplicates of 46245
[21:19] <Hamra> yes, i noticed, it's a regression, maybe i should start with simpler stuff, like the new with no package list
[21:19] <murdok> bdmurray: the same error occurred
[21:20] <bdmurray> Hamra: that and they are running a ppa version version of the package which is a bit strange
[21:20] <bdmurray> Hamra: yeah, I'd move on to another bug but if you any questions feel free to ask
[21:21] <murdok> bdmurray:  I have read what mvo said: multiple bugs could cause the same output :-/
[21:21] <bdmurray> murdok: the error message is a bit different than the cause of the issue.  I've updated 46425 a bit
[21:21] <bdmurray> murdok: and I've unmarked some duplicates but if you could check the others that would help a lot
[21:21] <murdok> :S im really sorry
[21:21] <murdok> so what should i check?
[21:22] <bdmurray> murdok: it's okay, everyone makes mistakes!  why don't we look at bug 155394 together
[21:23] <murdok> what should I look at, to see if its duplicate or it's another bug?
[21:25] <bdmurray> murdok: they've included a lot of log files and main.log should be the most helpful
[21:26] <murdok> Okay I'll see what I can do. I'm sorry again
[21:26] <bdmurray> they were trying to upgrade from feisty to gutsy
[21:26] <bdmurray> and that other bug was fixed in dapper at least
[21:27] <bdmurray> at the end of the log we see an issue installing the ubuntu-desktop meta package so it isn't a duplicate
[21:29] <mvo> I need to leave (bedtime here in my TZ) - thank you all for your excellent work on the update-manager bugs!
[21:29] <bdmurray> mvo: thanks for the assistance!
[21:29] <mvo> my pleasure!
[21:29]  * mvo waves
[21:30] <bdmurray> murdok: so we can unduplicate that bug and tag it feisty2gutsy
[21:31] <bdmurray> additionally Niels main.log looks like a different issue than the original reporter's
[21:31] <bdmurray> notice the "short read in buffer_copy" message
[21:33] <bdmurray> murdok: does that help a bit?
[21:34] <murdok> yes, i'm reading the logs
[21:35] <murdok> the error is usually at the end
[21:35] <bdmurray> usually, sometimes you have to work backwards to figure what is going on
[21:36] <bdmurray> well, to figure out the root cause
[21:39] <james_w> bdmurray: can a pattern search in attachments?
[21:39] <james_w> bdmurray: the "short read in buffer_copy" is common in upgrade failures, and I believe it indicates a local problem.
[21:39] <bdmurray> james_w: bughelper -A
[21:40] <bdmurray> james_w: yeah, I'd think hardware or disc errors
[21:40] <james_w> cool
[21:42] <bdmurray> james_w: I'll give it a try
[21:45] <charlie-tca> I'm setting up a Xubuntu HugDay for Saturday, 9/25/2008. Will anyone be around to help out?
[21:46] <bdmurray> charlie-tca: 9/25 is today
[21:46] <charlie-tca> My mistake, 9/27
[21:52] <murdok> bdmurray: I'll be right back soon
[21:52] <bdmurray> I won't really be available
[22:02] <james_w> I'm sure bug 271513 is a duplicate, does anyone know where the master is?
[22:08] <bdmurray> james_w: not me, did you check the milestone lists?
[22:08] <james_w> this is from the +nominations
[22:09] <chrisccoulson> james_w: is bug 262605 the one you're after?
[22:10] <james_w> thanks chrisccoulson
[22:10] <chrisccoulson> you're welcome
[22:14] <pochu> bdmurray: looks like ubuntu-meta could have a hug-day, I think most of those reports don't belong to that package: https://bugs.edge.launchpad.net/ubuntu/+source/ubuntu-meta
[22:14] <chrisccoulson> can anyone think of any sane reason why update-manager would cause the system beep to sound?
[22:15] <chrisccoulson> just looking at bug 213805. i can get the beep when changing tabs for the first time, if i have system beeps enabled
[22:15] <chrisccoulson> no errors though
[22:24] <bdmurray> chrisccoulson: were is the system beeps bit again?
[22:25] <chrisccoulson> on Hardy, it's System -> Preferences -> Sound, but I think the relevant tab has gone in Intrepid hasn't it?
[22:26] <bdmurray> If it is a whole tab, then yeah
[22:27] <chrisccoulson> yeah, it doesn't appear to be there in intrepid
[22:36] <bdmurray> chrisccoulson: I don't hear it in Intrepid fwiw
[22:37] <chrisccoulson> i can't get it to happen in intrepid either, but i don't know if that is because i don't have system beeps enabled though
[22:37] <bdmurray> pochu: noted
[22:42] <thekorn> chrisccoulson,  I can reproduce it in hardy
[22:42] <chrisccoulson> thanks. i'll confirm it for now, and i'll try and think of a test case for intrepid too
[23:23] <murdok> the today's bugday page shows me a nice 'Internal Server Error'
[23:23] <murdok> :S
[23:38] <bdmurray> murdok: hmm, I still have it open in a tab if you'd like a bug to look at
[23:41] <murdok> bdmurray: thanks but don't worry
[23:43] <murdok> bdmurray: I have unmarked all duplicates. It's very hard to check duplicates, nobody has installed the same packages
[23:44] <bdmurray> murdok: right and there are a lot of packages out there
[23:44] <bdmurray> The wiki seems better now
[23:45] <bdmurray> murdok: thanks for taking of the duplicates
[23:45] <hggdh> anyone seen a u-m issue where (after the release of 8.04 the user is not told there is a release update available?
[23:46] <bdmurray> tagging the release upgrade bugs with dapper2hardy is quite helpful too for splitting the bugs up
[23:46] <bdmurray> hggdh: how recent is that report?
[23:55] <Hamra> i haven't noticed any info about the [needs packaging] bugs in the triaging process, what am i supposed to do with these?
[23:56] <crimsun> I'm noticing a few people triaging ALSA bugs who are wrongly assigning bugs to alsa-driver and alsa-lib.  I asked maco to clarify the DebuggingSoundProblems wiki page last week to try and help clarify which source packages should be affected by default (and I'll go and clean up afterward as necessary).
[23:57] <maco> (and i did clean up the page)
[23:57] <crimsun> somewhat.  I haven't gone through my master guidelines list.
[23:58] <bdmurray> Hamra: just confirm that they aren't already packaged
[23:58] <maco> yeah you only told me what to put for the only time it gets marked as alsa-driver
[23:58] <maco> no guidelines on the libasound2-* stuff
[23:58] <Hamra> crimsun: now that you mentioned it, i passed by an ALSA bug few mins ago, is using apt-file an approved way of finding out what package we need to assign?
[23:59] <crimsun> maco: some of the nuances require a slightly more tragic^Wintimate knowledge of ALSA.
[23:59] <crimsun> Hamra: how do you mean, "using apt-file"?