[00:02] <Burgundavia> Nafallo: you could have had so much fun with danage
[02:09] <bucket529> ﻿Could I get somebody to change bug 210766 to Wishlist? It's a feature request.
[02:09] <bucket529> correction: bug 210776, sorry
[02:36] <bucket529> Still hoping for help changing 210776 to Wishlist
[02:54] <mrooney> Does anyone know if there is any reason not to try fglrx 8.543 in Intrepid?
[02:55] <greg-g> no, but your question makes me wonder :)
[02:59] <persia> mrooney, I think I heard that ATI finally ported it to X 1.5, although I don't have the HW to test.  Worth a try.
[02:59] <mrooney> Well, I'll try it!
[02:59] <persia> bucket529, I'm not sure that's wishlist.  Why wouldn't it be Low?
[03:00] <bucket529> persia: That's a very good question, and why I brought it up here....
[03:00] <persia> bucket529, My reasoning being that it works as expected for another flavour (Kubuntu).
[03:00] <persia> bucket529, OK.  Pick a status, and defend the reasoning for that status.
[03:01] <persia> s/status/importance/
[03:02] <bucket529> persia: Hmmm. I thought Wishlist becasue I'd never heard of the feature until I picked the bug out of the pile. And I haven't seen reference anywhere else
[03:02] <bucket529> persia: Of course, it could exist without me knowing about it. Lots of things do.
[03:03] <persia> bucket529, Right.  None of us understand everything in Ubuntu :)  Try looking at https://wiki.ubuntu.com/Bugs/Importance as a guide
[03:05] <greg-g> that is a great take-away: none of us know everything, so never be too shy to ask a question.
[03:06] <mrooney> okay, installed them on my rv350, here goes a restart...
[03:06] <bucket529> persia: I think confirmed/wishlist. My xubuntu has no option for a fallback language, and there's nothing useful (that I find) matching that pattern in Launchpad, Ubuntu.com, ubuntuforums.com, or Google
[03:06] <persia> bucket529, See, you're looking for information again.
[03:07] <persia> The critical lines are "request to add a new feature to one of the programs in Ubuntu" vs. "A cosmetic/usability issue that does not limit the functionality of an application".
[03:08] <persia> So you want to make a judgement as to which one applies.  Googling isn't likely to help.
[03:08] <persia> As an example, there are thousands of blog articles, HOWTOs, etc. about using VSTs with Ubuntu.  Nonetheless, adding VST support is wishlist.
[03:08] <persia> (and blocked by licensing issues)
[03:15] <bucket529> persia: I'd still say Wishlist - the described feature isn't broken - AFAIK it simply isn't there and the requestor wants it added.
[03:17] <persia> bucket529, And you don't feel it affects the cosmetic appearance or usability of Xubuntu?
[03:19] <bucket529> persia: Indeed it does, but many new features do.
[03:19] <mrooney> Hm, no dice on the fglrx, bug 283836 got me
[03:21] <persia> bucket529, Well, let's look at something else then : if I say that I can't play audio with my headset, because my laptop only activates the headphone jack when the appropriate bit is set in software, and the driver doesn't recognise the input, is that a bug in the driver, or a feature that I'm requesting?
[03:23] <mrooney> yes, I think feature request vs bug can get sticky
[03:23] <mrooney> I thought from reading the wiki somewhere, it comes down to intention
[03:24] <bucket529> persia: (riffling through notebook)(raising hand) When we see the whole story, I'd say driver bug. Looking at it from 'I have a headphone jack that never worked and I don't know why', it looks like an added feature.
[03:24] <persia> localisation bugs too, as they can render things harder to use for some people, and estimating the size of that group is dufficult.
[03:25] <persia> bucket529, I'd say it's either a driver bug or Invalid (and a question), depending on the underlying issue.
[03:26] <persia> Essentially, I say it's not Wishlist because something is really broken (although the hypothetical example is probably low under "Ones that affect unusual configurations or uncommon hardware ").
[03:26] <persia> Just because it's always been broken doesn't make it less of a bug.
[03:27] <bucket529> persia: Most interesting. Aim improves with practice.
[03:27] <persia> bucket529, Indeed :)  Now, back to 210776.  What's the importance (and why)?
[03:27] <charlie-tca> But doesn't a bug against the diratives that they chose not to implement become wishlist?
[03:28]  * persia will argue against either choice, just to belabour the process point
[03:28] <persia> charlie-tca, No, that'd be wontfix.
[03:28] <persia> Or, if it was choose-not-to-implement-at-the-current-time, just an open bug
[03:28] <charlie-tca> Very good. Thanks for your explanations.
[03:29] <persia> charlie-tca, Note the differentiation between "Choose not to implement" as "We don't want that" vs. "We don't have the time for that".
[03:30] <charlie-tca> Yes, you are correct in that. I'm learning too.
[03:30] <charlie-tca> You give the best explanation of importance I have seen.
[03:32] <bucket529> persia: Since I lack data on the developer's intent to offer this feature, have found no discussion of it in the search for that data, and have no gauge of the affected number of users...I'm still saying wishlist. Of course, with data about any of those it could go up or down.
[03:33] <persia> bucket529, Why does the intent of any given developer impact the importance of the bug?
[03:38] <bucket529> persia: (flipping pages) The square root of...wait...the rain falls in...no....If the intent of software is to do functions foo and bar, then the unusability of those functions to the user should have a higher importance.
[03:39] <persia> The rule of thumb for free software developers is "fix the bugs you feel like fixing".  Some people do this for money, which makes this "fix the bugs your boss/client wants fixed".  Some people want to improve user experience, which makes this "fix the bugs users complain about".
[03:40] <persia> That said, I don't see how the "Importance" of a bug is related which gets done in terms of intent.  The best we can do is to set the importance based on the agreed guidelines, so that those developers who fix bugs based on importance will have a well described selection on which to work.
[03:41] <persia> So, If I make a calculator that can multiply and divide, is it a bug or feature that someone wants to be able to add or subtract?  They can always multiply by the appropriate factor.
[03:42] <persia> Personally, I claim that if the application is branded as a general purpose calculation, that's a bug.  If the developers *really* don't want to fix it, they can set Status to WontFix.
[03:42] <persia> s/calculation/calculator/
[03:44] <bucket529> persia: So, are you talking me into 'low' for bug 210776? Or just seeing how well I can back up whatever I choose? (Both are much more interesting than washing the dishes)
[03:46] <persia> Mostly seeing how well you can back up your choice, and arguing against any basis for that choice with which I disagree.
[03:47] <persia> For this specific bug, it doesn't matter much, as it's non-trvial to do, and will probably get done or not depending on things other than the importance selected.
[03:48] <bucket529> persia: Agreed
[03:48] <persia> However, it's worth making sure you are setting it for the right reasons, and this is a good bug to review that, because it's not entirely clear which is the right status.
[03:48] <persia> That improves hundreds of future bugs :)
[03:49] <persia> (and it's had at least one interesting side discussion regarding wontfix already)
[03:51]  * charlie-tca nods
[03:51] <bucket529> persia: Well, the next step is to figure out which package or project I should put it in. Any advice from the gallery?
[03:52] <persia> bucket529, In which tool is the user describing the problem?
[03:54] <bucket529> persia: Unstated in the bug. (Assumption: System --> Language Support)
[03:55] <persia> The user states "When selecting ... inside the session manager".  That would point at the session manager.  The user also states they are using Xubuntu, so it would be the Xubuntu session manager.
[03:56] <persia> So, if you're not running xubuntu, you might ask someone who is (e.g. charlie-tca) to help figure out which application is affected.
[04:02] <bucket529> Well, I'm running Xubuntu (why I picked this bug). Session manager (xfce4-session) just doesn't look right. The description "it appears to be impossible to pick several choices and sort them in order of preference" resembles language-selector more than anything else.
[04:03] <persia> Well defended :)  That'd be the package then.  Since you have Xubuntu, I suspect you can probably do the replication test to set Status as well, which brings us back to Importance.
[04:04]  * greg-g applauds the work going on in here
[04:06] <bucket529> language-selector/confirmed (yes, I checked and commented)/wishlist...Of course, I can do only the first two. I lack permission to change importance.
[04:06] <persia> But if you can argue that either wishlist or low is correct, I'll set it for you :)
[04:08] <bucket529> Wishlist, please. There is another 'fallback' wishlist item (not a duplicate) so it will have a friend.
[04:09] <persia> Which one?
[04:09] <bucket529> The other is bug 72952
[04:11] <persia> OK.  I'll change 210776 to wishlist.  Showing that a developer who works on language selector previously set such a thing to wishlist is a convincing argument.
[04:11] <persia> Next question : is "incomplete" the correct status for 72952?
[04:11] <bucket529> I suppose 72952 could be a duplicate - reading further. 210776 seems clearer. There might be an argument that 72952 could be a duplicate (en- subset) of 210776.
[04:12] <persia> I think they aren't duplicates.  210776 is about the UI not permitting it, 72952 is about the initial base data not having the right defaults for NZ and AU.
[04:13] <persia> So there's no single action that could be taken to fix both bugs.
[04:13] <bucket529> Ahhhhh.
[04:18] <bucket529> Back to the 'Incomplete' question for 72952. Flipping through the Wiki....
[04:20] <bucket529> My time has expired. Must go....
[04:22] <persia> OK.  Quick answer to 72952 : there's no information requested, so Incomplete is an odd status.  Since it was set by a developer who is assigned to it, it's best practice to check with the developer before changing it.  The status is probably wrong, but the assignee is the best person to provide guidance on the correct status to use, or what additional information may be required.
[04:22]  * persia types too slowly, but hopes the summation is useful for someone else.
[04:23]  * charlie-tca nods
[04:23] <greg-g> persia deserves a hug for that lesson.
[04:23]  * charlie-tca nods
[04:23]  * charlie-tca gives persia a *big* hug
[04:24] <charlie-tca> persia sure is patient, too
[04:25] <persia> charlie-tca, You mistake laziness for patience.  This way all I have to do is comment on IRC, and someone else does the triage of the tricky bugs :)
[04:25] <charlie-tca> I see. I think it takes patience to explain all that you did, though
[04:27] <charlie-tca> Now I'm off to bed...
[04:27] <greg-g> persia is also right in that now that bucket529 knows more and actually understands it they will be doing more and better quality work, most likely, which helps us all.
[04:27]  * charlie-tca too
[04:28] <greg-g> good deal
[07:13] <dholbach> good morning
[07:18] <maco> mornin
[07:18] <dholbach> hi maco
[07:41] <thekorn> dholbach: hi, can you please extend my ~5-a-day membership?
[07:42] <dholbach> thekorn: errrrrrrrrr, I thought I disabled it totally
[07:42] <dholbach> thekorn: it says "renew membership automatically" right now
[07:44] <dholbach> done... *shrug*
[07:44] <thekorn> dholbach: thanks
[10:32] <waldenasta> hello all
[11:25] <waldenasta_> I am having a problem with ubuntu evolution and my system mail. I have setup my system to retrieve mail with mailx but when the mail arrives it says : "Could not create lock file for /var/spool/mail/wald: Permission denied"
[11:26] <waldenasta_> anyone have any ideas?
[14:07] <bucket529> Hmmm. Looking for advice on bug 216267 - Some apps use the USB speakers, others use the onboard speakers. Been through the wiki, but it deals mostly with stuff not recognized. So, what smart questions should I ask?
[14:09] <Treenaks> bucket529: - Ask him about the settings in System -> Preferences -> Sound
[14:10] <Treenaks> bucket529: and also if it's still a problem in hardy/intrepid
[14:11] <bucket529> Treenaks: Thanks
[14:55] <jwendell> how many days bugs marked as 'incomplete' go to 'invalid'?
[14:56] <persia> jwendell, No set value.  Usually a couple months for stuff on the default CD, and no more than a year for most other things.
[14:56] <jwendell> one year???!!
[14:57] <persia> Needs a human to review it, and make sure that it's still incomplete, and nobody can add the required information.
[14:57] <jwendell> I was almost sure that it was around 60 days
[14:57] <persia> Sure.  Some packages don't get a lot of attention.
[14:57] <persia> There's a counter that starts from 60 days.  Sometimes it gets into high negative numbers.
[15:00] <seb128> jwendell: some weeks is enough usually
[15:00] <jwendell> for instance: bug 255919
[15:00] <jwendell> it has more than 60 days
[15:00] <jwendell> can i close it?
[15:00] <seb128> jwendell: close it
[15:00] <jwendell> seb128, thanks
[15:01] <persia> I'm not sure about closing that one.
[15:02] <persia> Err.  Never mind.  I can't count.
[15:02] <persia> Good to close because if it affected lots of people, there'd be more info, and information was requested a couple months ago, for an application on the default CDs.
[15:04] <jwendell> done :)
[15:05] <seb128> jwendell: thanks for triaging the vino bugs open on launchpad
[15:05] <jwendell> :)
[15:05] <afflux> I often use 30 days for expiring my bugs
[15:06] <afflux> Bugs/Responses has a "Incomplete bugs without a response from submitter" response with the following description: "In the event that a bug has been in the "Incomplete" state for more than 4 weeks, meaning it has not received a response to a request for more information, the bug status should be changed to "Invalid" with a comment similar to: ... "
[15:06] <afflux> maybe that should be updated, if we generally use 60 days
[15:08] <persia> afflux, For many packages, 4 weeks is plenty.
[15:08] <Hew> If they don't respond in 30 days, they're not going to respond in 60. I find that if they ignore your request for information, they will sometimes reopen the bug as soon as you close it, and actually post what you asked for.
[15:08] <persia> It's really about what kind of information is required, and who needs to provide it.
[15:08] <afflux> yeah indeed
[15:09] <persia> Hew, I find that as well.  When I'm asking the submitter something, I'm happy to close in 30 days.  When I ask them to test with the new release, or some such, I'll wait until the new release happens, and then close it.
[15:09] <seb128> closing all the useless bugs as invalid directly asking to reopen when adding informations could make sense
[15:09] <persia> seb128, It's determining whether it's useless.
[15:09] <seb128> crashes without a stacktrace or a description of what the user was doing for example
[15:09] <persia> I've seen a number of bugs with good stacktraces become invalid just because the person triaging them didn't understand that there was enough information.
[15:10] <seb128> there is too many bugs anyway
[15:10] <persia> I think those should be set invalid initially, without an incomplete period.  I'd rather get a clean apport report than some user uploading gdb output.
[15:10] <seb128> right
[15:10] <persia> I disagree.  I think more bugs would be good, as long as they were good bugs.  There are too many unactionable bugs.
[15:11] <seb128> not sure I agree
[15:11] <persia> Not surprising.  Most people don't :)
[15:11] <Hew> yea I'd rather have less bugs than more :P
[15:11] <seb128> we have load of crashes which happened once 3 years ago and never got a duplicate in launchpad or upstream since
[15:11] <persia> Hew, I'll agree with that, but I'd rather have bugs be visible.
[15:11] <seb128> I'm wondering if keeping all those is valuable, for what we know half of those could be fixed since or deprecated or have been a local corruption
[15:12] <persia> seb128, That doesn't count as actionable in my book.  If it can't be reproduced for several years, then it ought go through incomplete and invalid.
[15:12] <seb128> well, they sometimes have valid debug stacktraces
[15:13] <seb128> there is just so many of those and the code changed so much, etc that probably nobody will ever act on those bugs anyway
[15:13] <persia> Right.  That's why I say they aren't actionable.  If they can't be reproduced by anyone after a couple years, and they don't qualify for SRU, there's no point keeping them around.
[15:14] <persia> On the other hand, for packages that haven't changed in three years, I don't have that opinion.
[15:14] <persia> It really depends on the package.
[15:15] <persia> http://qa.ubuntuwire.com/multidistrotools/unchanged/unchanged_since_warty has a list of packages where even the oldest stacktrace is still interesting, as an example.
[15:16] <G__81> hi all
[15:17] <Hew> G__81: Hi
[15:17] <G__81> Hi Hew
[15:18] <G__81> i joined the team yesterday so have started with triaging so could do that today to continue it so can you please give me the link for the ubuntu bugs that needs to be triaged?
[15:20] <Pici> G__81: Anything marked as 'New' would need triaging.
[15:20] <G__81> Pici, yes the link for the bugs where do i find that list
[15:21] <persia> G__81, Start from http://bugs.launchpad.net/ubuntu/+bugs
[15:21] <persia> From there, I believe you can search on "New" bugs.
[15:21] <G__81> oh you here too persia :) thanks
[15:21] <Hew> G__81: Any of the bugs in Launchpad. The new/undecided bugs can be found at https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&field.status%3Alist=New&field.importance%3Alist=Undecided&assignee_option=none&field.assignee=&field.owner=&field.component=1&field.component=2&field.component-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_no_package.used=&search=Search
[15:22] <G__81> Hew, the link that you have given me is for Ibex right ?
[15:22] <persia> Or less verbosely ps://launchpad.net/ubuntu/+bugs?field.status%3Alist=New&field.importance%3Alist=Undecided&search=Search
[15:23] <persia> It's all the bugs open against Ubuntu right now.  A mix of releases, but many are for intrepid.
[15:24] <G__81> ok but the first one is for 8.04 so let me see whether i am able to reproduce it
[15:24] <Hew> G__81: Bugs are primarily filed against the current development release. So for now, the status of the bug is the status in Intrepid.
[15:24] <G__81> and then change the status if required
[15:24] <G__81> This one is for 8.04
[15:24] <G__81> https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/286428
[15:27] <Hew> G__81: See if you can reproduce it with Intrepid. If you can't, ask for more information, or if they can test with Intrepid. If you can reproduce it, you can confirm the bug (and maybe leave a clear explanation of what the problem is exactly).
[15:27] <G__81> Hew, i am not able to reproduce it in Hardy
[15:27] <G__81> as the reporter has got this in 8.04
[15:27] <G__81> i am able to double click and open the pdf file
[15:27] <Hew> G__81: Always test with the latest version of Ubuntu. Perhaps it has already been fixed in Intrepid?
[15:28] <Hew> G__81: but in that case, ask for more info
[15:28] <persia> Well, when I have it available, I like to first test with the same version as the reporter uses, and then test with the latest version.  I'm only certain it was fixed if it was broken for me before, and fixed for me later.
[15:28] <G__81> Hew, but the reporter has given sufficient info i gugess
[15:28] <G__81> persia, yeah exactly
[15:28] <G__81> true
[15:28] <G__81> i am not able to reproduce it
[15:29] <persia> If you can't reproduce it in the submitters environment, ask for more information.
[15:29] <G__81> if you dont mind you could try it for yourself as the person is using 8.04 i am sure you would be running 8.04 so that i can close it if it not reproducible for you too
[15:30] <Hew> G__81: I'm on Intrepid 8.10
[15:30] <G__81> persia, you ?
[15:31] <Hew> G__81: Say you cannot reproduce the problem, ask for more info (eg. can they still reproduce the problem), and mark it incomplete.
[15:31] <G__81> ok sure will do it
[15:33] <G__81> done changed it to incomplete added a comment too
[15:33] <G__81> :)
[15:35] <Hew> G__81: cool, thanks for your help triaging :-). Looks like pedro beat you to it by a minute though haha :P
[15:36] <Hew> G__81: Maybe try some bugs lower on the list so they are less likely to have the attention of others.
[15:37] <Hew> Pidgin 2.5.2 bugfix release is out - bug 286163. Who should I subscribe to get this looked at? u-m-s or ubuntu-release (or both)?
[15:37] <G__81> you want me to look into this ?
[15:38] <Hew> G__81: No, it was a general question to the channel.
[15:38] <G__81> oh sorry
[15:38] <G__81> didnt read it properly
[15:38] <G__81> its a bug fix release
[15:38] <G__81> ok :)
[15:38] <Hew> G__81: No worries :-)
[15:38] <G__81> have a question here
[15:38] <G__81> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/286426
[15:39] <G__81> The reporter says that he had a different keyboard layout and then upgraded to Ibex and didnt work and again changed it back to default still does not
[15:42] <G__81> i have already upgraded to Ibex with keyboard set to US i just changed it to US MAC and still i am able to use the down arrow key and again changed it to US it still works
[15:42] <G__81> i am not able to reproduce it in Ibex
[15:43] <Hew> G__81: There have been some weird keyboard mapping issues with the new xorg in Intrepid. They mentioned they changed keyboard layouts, but they didn't say what to. What happens if they reset the layout in keyboard-properties? What happens if they use evdev? Is it only the down arrow, or are other keys affected?
[15:44] <G__81> you mean again using the default US standard ?
[15:44] <G__81> i did that and i am able to type as usual
[15:44] <G__81> let me check it once again
[15:45] <G__81> what i do is i select US MAC click on apply system wide and then it asks me the password, i give it and then i tried pressing down arrow it works
[15:45] <G__81> i tried pressing others it works still
[15:46] <G__81> now let me reset the keyboard
[15:46] <Hew> G__81: Ask the reporter this.
[15:47] <G__81> it works
[15:47] <G__81> still
[15:47] <G__81> yeah sure what should i ask him
[15:47] <Hew> G__81: You are on Hardy right? They said it's an issue with upgrading to Intrepid, so I'm not sure how you would be able to reproduce it.
[15:47] <Hew> G__81: Ask the questions I said above
[15:48] <G__81> Hew, no i have ibex too
[15:48] <G__81> Hew, running on Virtual Box
[15:48] <G__81> i installed 8.04 in VBox upgraded to 8.10
[15:49] <Hew> G__81: As a triager, you just need to get the bug report into a state that is good enough for a developer to work on. If someone describes a problem, you have to assume it's a legitimate issue. If you cannot reproduce it, it doesn't mean the reporter cannot.
[15:49] <Hew> G__81: Ask the reporter those questions, and set the status to incomplete.
[15:57] <jibel> G__81: Hi, the reporter is mpt, an interface designer working for Canonical, you can assume that his request is legitimate. Read bug 255008 , ask him for any missing information and set the status to incomplete
[15:58] <G__81> jibel, this bug 286426 ?
[15:59] <jibel> G__81: Yes, both bugs are very close.
[15:59] <G__81> yeah jibel its similar
[16:00] <jibel> G__81: But don't assume they are duplicates until you've collected enough informations.
[16:00] <G__81> yeah sure
[16:03] <G__81> if its a crash which a person has reported with proper logs, i can change the bug status right ?
[16:05] <G__81> just subscribed to Ubuntu-bugsquad
[16:05] <G__81> is it a very high traffic list ?
[16:05] <jibel> G__81: Crash reports should be handled like normal bugs in terms of duplicate searching/marking, upstream forwarding, etc
[16:07] <G__81> its not a duplicate
[16:07] <G__81> just searched this crash has happened in almost all the releases of ubuntu , the prior releases :)
[16:20] <G__81> jibel, if a bug is crash and everything is proper, i would make it confirmed
[16:20] <G__81> assuming there are no duplicates
[16:20] <G__81> right ?
[16:23] <persia> G__81, Only if you can reproduce it, or can confirm that the stackrace contains sufficient information that you're certain it's a problem.
[16:23] <G__81> yeah
[16:23] <G__81> when do i mark it as upstream forwarding
[16:23] <G__81> i am not able to understand that point alone
[16:24] <persia> If you can find the identical bug upstream, link to the upstream bug.  If you can't find the bug upstream, and you're sure it's an upstream bug, you can file a bug upstream, and link it.
[16:25] <persia> Unless you've previously worked with some specific upstream bugtracker, I recommend triaging a bunch of bugs first, and starting to link to upstream once you have a feel for things.
[16:26] <G__81> yeah sure :)
[16:26] <G__81> thanks persia
[16:51] <G__81> is Bug #286197 duplicate of #32450
[16:51] <G__81> can someone look into it and let me know coz in the latter report i am not able to find the release no
[16:52] <G__81> Oh sorrty
[16:52] <G__81> sorry it has got the release name
[16:53] <pedro_> G__81: no, traces are different
[16:56] <G__81> yes
[16:56] <G__81> just when i saw this for the first time
[16:56] <G__81> i saw it was a duplicate
[16:56] <G__81> and now LP is not workin
[17:05] <Awsoonn> ping bdmurray Hugday hursday onward
[17:06] <Awsoonn> got any great ideas of what could happen?
[17:24] <julian> hello all, just got this great article about the power of what we do in the opensource community:>http://news.zdnet.com/2424-9595_22-242593.html
[17:28] <G__81> i guess my 5 a day is done for today :)
[17:31] <chrisccoulson> no need to stop at 5;)
[17:32] <G__81> :) yeah
[17:32] <G__81> is there something like you triage 200 + bugs and then you are eligible for applying membership ?
[17:39] <G__81> hi pedro_ you there ?
[17:55] <ronj> hello
[17:56] <calc> anyone happen to remember the url to see the full top 100 bug stats on LP?
[17:56] <calc> its the one that shows triaged percentage, etc
[17:57] <james_w> calc: +upstreamreport?
[17:57] <ronj> uptream report ?
[17:57] <ronj> https://edge.launchpad.net/ubuntu/+upstreamreport
[17:57] <calc> yea! thanks guys :)
[17:59] <G__81> what do these stats show http://daniel.holba.ch/5-a-day-stats/
[19:10] <bdmurray> mvo: ping
[19:10] <mvo> bdmurray: pong
[19:11] <bdmurray> I was just wondering if bug 113658 was an easy fix or something for Jaunty.
[19:14] <mvo> bdmurray: reading
[19:14] <mvo> (if launchpad lets me)
[19:23] <mvo> bdmurray: I look at it tomorrow, I need to leave for today
[19:25] <james_w> gpg: unable to open "/tmp/tmpJLrld7/intrepid.tar.gz.gpg" <- there was an apt-cacher patch that I may have sponsored that fixed that
[19:25] <james_w> or was supposed to at least
[19:26] <james_w> I'll try and find the bug
[19:27] <james_w> bug 156070
[19:30] <bdmurray> james_w: sweet! thanks
[20:24] <mrooney> Can you do strikethru on the ubuntu wiki?
[20:36] <didrocks> jwendell: around?
[20:36] <jwendell> didrocks, yep
[20:36] <didrocks> jwendell: seb128 told me you are the upstream for vinagre
[20:36] <jwendell> right
[20:36] <didrocks> I have an issue building 2.24.1 (http://ubuntu.pastebin.com/m4aff6ae0)
[20:37] <bucket529> Could someone please change bug 280844 from 'Undecided' to 'Wishlist'?
[20:37] <chrisccoulson> done
[20:38] <jwendell> didrocks, it built fine here
[20:38] <azimout> launchpad is kinda slow today...
[20:39] <didrocks> jwendell: I do not think that it is my connection… (it wgets successfully the others one)
[20:39] <didrocks> jwendell: hum, it failed now on another file
[20:39] <didrocks> maybe an erratic slow connection :/
[20:40] <jwendell> yep
[20:43] <seb128> didrocks, jwendell: internet should not be required to build a tarball
[20:43]  * jwendell knows nothing about autotools
[20:44] <seb128> jwendell: that's not an autotools issue but a documentation dtd one apparently
[20:44] <jwendell> even worse
[20:44] <jwendell> :(
[20:44] <jwendell> hehe
[20:50] <bucket529> ﻿Could someone please change bug 281839 from 'Undecided' to 'Wishlist'?
[20:52] <jwendell> seb128, didrocks, I just built vinagre 2.24.1 without internet here
[20:52] <didrocks> that's strange, is my pbuilder putting on my leg? :)
[21:13] <LimCore> in a bug report,  how to set remote watch to debian bug tracker?
[21:19] <mrooney> LimCore: just click "Also affects project"
[21:19] <mrooney> and the first option should have a url input for the upstream link
[21:19] <bdmurray> actually distribution
[21:19] <mrooney> Oh, sorry :)
[21:20] <mrooney> ah yes, then just choose the distro from the drop-down, and enter the URL below
[21:21] <bucket529> Still looking for help to ﻿change bug 281839 from 'Undecided' to 'Wishlist'.
[21:25] <LimCore> intel gfx fails epicaly it seems, confirmed, and debian bug; Can someone set importance of this?  https://bugs.launchpad.net/debian/+source/xserver-xorg-video-intel/+bug/285298
[21:26] <LimCore> hmm actually.. it looks like a duplicate of anoter
[21:26] <LimCore> or not. mine is timeout
[21:29] <bdmurray> james_w: I found a bug that may be related to your bug 251482
[21:35] <jibel> bdmurray: Hi, I've sent my application to bugcontrol 2 weeks ago. Did you receive it ?
[21:40] <bdmurray> jibel: I'm looking but not finding it
[21:41] <jibel> bdmurray:  It was sent on the 13rd Oct.
[22:19] <charlie-tca> Looking at three bugs, look like duplicates to me. Can someone else take a look for me?
[22:20] <charlie-tca> Bug #248062, Bug #211721, Bug #249323
[22:20] <charlie-tca> I want to make 211721 the confirmed bug, with the other two as duplicates
[22:44] <Arby> bdmurray: my membership of ubuntu-bugcontrol expired a while ago due to me being away from (k)ubuntu for a bit. what do I need to do to have it renewed?
[22:46] <james_w> hey bdmurray, which did you find?
[22:47] <bdmurray> james_w: bug 286172
[22:49] <bdmurray> Arby: nothing, I'll readd you to the team
[22:49] <Arby> bdmurray: excellent thanks :)
[22:50] <james_w> bdmurray: thanks, nice spot. If they come back with the same permissions issue I'm sure you'll ask if it is a Dell factory install.
[22:51] <bdmurray> james_w: hopefully ;)  I wonder if some package would change the ownership of those files
[22:51] <james_w> yeah, perhaps
[23:21] <RicardoPerez> Hi! Can anybody test if left-arrow key goes slower than right-arrow key when you previously do: xset r rate 10 50
[23:21] <RicardoPerez> Thanks in advance