[00:15] <arand> The "Additional plugins are required" firefox message, that part of the firefox package, or something else in ubuntu?
[00:51] <arand> I had a (for screen-reader, fatal) at-spi crash, however apport refused to report it, is there any way to make sure to catch it?
[01:21]  * sjn is wondering if he's found a dependency bug in the perl-modules package
[01:23] <sjn> CPAN.pm isn't very useful out-of-the box without libwww-perl and libyaml-perl
[05:51] <bbordwell> Is there anyone here VERY familiar with debugging using gdb that is willing to help me?
[06:50] <dholbach> Packaging Training: Fixing small bugs in Ubuntu: in 10 minutes in #ubuntu-classroom - http://is.gd/bLixO
[07:04] <thekorn> good morning, and happy {release,hug}-day everybody!
[07:05] <kklimonda> hey :)
[07:05] <ddecator> oh hey, it's a bug day..
[07:11] <nigelbabu> ddecator: also release day ;)
[07:11] <nigelbabu> hence the no-package bugs I suppose
[07:11] <ddecator> nigelbabu: right. that i don't care as much about since i've been on lucid since a3 =p
[07:14] <thekorn> is it out? is it out?
[07:20] <ddecator> -_-
[07:32] <ddecator> anyone here that can help me with valgrind?
[07:37] <ara> morning all!
[07:38] <ddecator> morning ara
[07:41]  * vish wonders why valgrind was named so.. since /grind/ things to a halt?
[07:47] <ddecator> ha, first bugday bug in a while...i'm actually kind of ashamed of that =\
[07:50] <vish> ddecator: running valgrind for firefox ?
[07:51] <ddecator> vish: nah, nautilus bug i filed. the valgrind process was ending before nautilus crashed, but the log was full and had a ton of errors, so i just attached it as-is to my report
[07:59] <vish> anyone receiving same bug mail twice or more?
[08:00] <vish> i'm noticing Bug 571181 , which has confused folks in #launchpad they mention it might be yahoo related
[08:00] <ubot4> Launchpad bug 571181 in malone "LP sends same mail several times [bug mail and maling list mails] (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/571181
[08:04] <ddecator> vish: i haven't noticed anything like that
[08:04] <vish> might be stupid yahoo :/
[08:05] <ddecator> gmail =)
[08:10] <Rune> Whenever I use dch -i it grabs my name from /etc/passwd and uses username@host as my email despite that I have set DEBEMAIL="some@mail.net" and DEBFULLNAME="name" in ~/.devscripts
[08:10] <Rune> Anyone else that have the same problem?
[08:10] <bbordwell> rune, do you have "export debmail=some@mail.net"?
[08:12] <aburch> Rune: IIRC that are environment variables, not variables set in devscripts.conf
[08:23] <Rune> aburch, indeed thanks
[08:25] <Rune> though I don't quite understand the decision not to have them read from .devscripts
[08:33] <ddecator> Rune: #ubuntu-packaging has a lot of people good with that kind of stuff. they might not know the answer to that question, but packaging-related questions you have are more likely to get answered there =)
[08:37] <Rune> ddecator, thanks
[08:47] <mistrynitesh> please have a look at bug 570734, I had marked it against gnome-power-manager and asked the original reporter to do 'apport-collect 570734'
[08:47] <ubot4> Launchpad bug 570734 in gnome-power-manager (Ubuntu) "Screen brightness can not be set to maximum (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/570734
[08:48] <mistrynitesh> original reporter has attached the reports--- so what is the next step? --- should i mark it triaged?
[08:50] <ddecator> mistrynitesh: you can look for dupes, see if you can reproduce it and possibly add more information that narrows down the cause
[08:51] <mistrynitesh> ddecator: yes, it seems there would be duplicates, but can't reproduce as I don't have a laptop
[08:52] <ddecator> mistrynitesh: well then you can look for dupes at least. it can't be set to triaged until there is enough detailed information for the developers to be able to know what needs to be fixed. generally, apport information really helps that, but it's a lot of info to look through, so if we can find a way to narrow down the possibilities it can help them a lot =)
[08:52] <BUGabundo_remote> hey hey huckle barry
[08:53] <ddecator> heya BUGabundo_remote
[08:53] <bbordwell> mistrynitesh, also if the bug needs to be forwarded upstream you should do so
[08:53] <bbordwell> if you can reproduce it, otherwise ask the original reporter to do so
[08:53] <ddecator> bbordwell: good point, forgot this was a gnome report, haha
[08:54]  * ddecator is a little tired
[08:57] <ddecator> actually, on that note, i'm gonna get to bed. night/morning all, enjoy the release, but don't forget about the bug day =)
[09:01] <kermiac> night ddecator :)
[10:05] <bilalakhtar> I just now applied to join the bugsquad team and have sent a mail to the mailing list.
[10:09] <bilalakhtar> I just now applied to join the bugsquad team and have sent a mail to the mailing list. Can someone approve my request to join the team?
[10:15] <om26er> bilalakhtar, you could wait for a few hours. someone will certainly do that
[10:15] <bilalakhtar> om26er: thanks for that.
[10:15] <om26er> np :)
[10:26] <vish> bilalakhtar: have you tried lp to join .. iirc it was open for new members to autojoin [not sure how it works though]
[10:26] <bilalakhtar> vish: I have already applied to join in lp
[10:37] <nigelbabu> vish: bug squad is moderated now
[10:38] <vish> nigelbabu: there was some mention of allowing auto-join due the the mail load
[10:38] <nigelbabu> vish: it was auto-renew
[10:38] <nigelbabu> argh self renew
[10:41] <keffie_jayx> hello guys, I just got a friend to file a report on some issues with the kernel and 10.04, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/545339, i can't seem to find the wiki entry on how to improve bug reports and specifically the part for kernel
[10:41] <ubot4> Launchpad bug 545339 in linux (Ubuntu) "irq 20: nobody cared (try booting with the "irqpoll" option) (affects: 2) (heat: 12)" [Medium,Triaged]
[10:41] <keffie_jayx> could anyone poing me in the right direction with the improving a bug report?
[10:56] <kermiac> keffie_jayx: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
[10:56] <keffie_jayx> thanks
[10:56] <kermiac> np :)
[11:30] <BUGabundo_remote> anyone looking at https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/570765
[11:30] <ubot4> Launchpad bug 570765 in ubiquity (Ubuntu) (and 1 other project) "[Lucid] no GRUB menu entry for other operating systems (affects: 6) (heat: 46)" [Critical,Confirmed]
[13:26] <nigelbabu> bug 423252
[13:26] <ubot4> Launchpad bug 423252 in sudo (Kairos Linux) (and 14 other projects) "NSS using LDAP+SSL breaks setuid applications like su and sudo (affects: 29) (heat: 218)" [High,Confirmed] https://launchpad.net/bugs/423252
[13:27] <pvandewyngaerde> hello,   is anyone else having the problem that on a console you cannot use the loadkeys command  and it gives a long list of error messages ? one line for keyboard layout 0 -> 127,  and then : access denied,   KDSKBENT: action not allowed, loadkeys cannot release keyboard layout 128
[13:29] <pvandewyngaerde> as root it does work
[13:36] <pvandewyngaerde> hello anyone ?
[13:40] <aburch> nigelbabu: Hehe, that one is fun.  But upstream considers it a feature.
[13:41] <nigelbabu> aburch: hehe, I was doing nothing with the bug.  It turns twice when I queried LP via API
[13:41] <nigelbabu> turns out it has a karmic and lucid task
[13:47] <aburch> Well, I guess I can at least link to the Debian bug report in libgcrypt for this.
[14:03] <BUGabundo_remote> yay for more mono rant :(
[14:05] <kklimonda> where?
[14:05] <kklimonda> BUGabundo_remote: ^
[14:17] <BUGabundo_remote> +1
[14:17] <BUGabundo_remote> kklimonda: ^
[15:01] <thebishop> any news on the GLX memory leak issue?  will it be fixed today?
[15:02] <Pici> thebishop: er, that was already fixed.
[15:02] <thebishop> Pici, yeah?  do I need to manually reinstall glx?
[15:03] <Pici> thebishop: if you've been updating you should already have the update.
[15:03] <thebishop> Pici, that's what i'd expect, but it's not what happened for me
[15:04] <yofel> thebishop: what does 'glxinfo | grep GLX\ version' give you?
[15:05] <thebishop> yofel, The program 'glxinfo' is currently not installed.  You can install it by typing:
[15:05] <thebishop> sudo apt-get install mesa-utils
[15:06] <yofel> then install it and check if you have glx 1.2 or 1.4, you're only affected by the GEM leak if you have 1.4
[15:07] <thebishop> yofel, ok
[15:53] <simar> is not today the bugday
[15:59] <vish> thebishop: what do you get with ~$ cat /sys/kernel/debug/dri/0/gem_objects
[16:00] <thebishop> vish, objects \ 1715 objects \ 75587584 object bytes \ 19 pinned \ 12902400 pin bytes \ 59248640 gtt bytes \ 234881024 gtt total
[16:00] <vish> thebishop: no leak there ;)
[16:00] <vish> " 75587584 object bytes " is OK
[16:01] <vish> heh better than mine even ;p
[16:01] <thebishop> vish, yeah, i didn't think I was affected by the leak per se, but i am affected by not having GLX
[16:02] <vish> there is another leak in the kernel though! well atleast for me .. if i use .33 no problems for me
[16:03] <vish> similar happened during karmic as well . :s the karmic kernel was a problem and only the lucid one was good for me.. [had nautilus problems due to kernel]
[16:04] <thebishop> vish, do you know offhand if atl1c supports gigabit ethernet yet in *33?
[16:04] <vish> thebishop: nope..
[16:04] <vish> thebishop: i mean , i dont know :)
[16:04] <thebishop> gotcha
[16:05] <qense> Congratulations to all of you for this wonderful release! Without the Bug Squad Lucid wouldn't have been what it has become.
[16:06] <yofel> simar: sure is: https://wiki.ubuntu.com/UbuntuBugDay/20100429
[16:06] <micahg> qense: not released yet AFAIK
[16:07] <qense> micahg: Ah, well, then I'll congratulate you with this morning's build. ;)
[16:08] <yofel> well, not much difference from out point of view
[16:08] <BUGabundo_remote> lol
[16:08] <yofel> next week is open week and then I'll have some time to work on the backlog :)
[17:15] <dgtombs> anybody know what program handles an XF86Eject key press?
[17:15] <dgtombs> in gnome
[17:16] <om26er> gsd?
[17:16] <dgtombs> that's my first guess
[17:25] <dgtombs> looks like it's g-s-d from the source (part of media keys)
[17:37] <mistrynitesh> does xubuntu also uses gnome-power-manager? if there is a problem in setting brightness in xubuntu, which package should it be reported against?
[17:37] <charlie-tca> depends on the version, 9.10 uses xfce4-power-manager
[17:38] <mistrynitesh> for lucid?
[17:38] <charlie-tca> yup
[17:38] <charlie-tca> same, xfce4-power-manager
[17:42] <mistrynitesh> in bug 555709 the reporter uses xubuntu, yet it is reported against gnome-power-manager. Should it be changed to xfce4-power-manager
[17:42] <ubot4> Launchpad bug 555709 in xorg (Ubuntu) (and 1 other project) "Laptop display maximum dim at startup (affects: 5) (heat: 30)" [Undecided,Confirmed] https://launchpad.net/bugs/555709
[17:43] <charlie-tca> Need to make sure he did not add gnome-power-manager.
[17:43] <charlie-tca> If you add Xubuntu-desktop to gnome, you still have it
[17:45] <mistrynitesh> actually looking at the list of bugs having problem with brightness setting https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager?field.searchtext=bright&orderby=-datecreated&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&f
[17:46] <mistrynitesh> oops! how do i post this long link?
[17:46] <yofel> mistrynitesh: http://tinyurl.com
[17:47] <mistrynitesh> http://tinyurl.com/3yo3kqj
[17:47] <mistrynitesh> :)
[17:48] <mistrynitesh> so coming to the point, if all the variants of ubuntu has the problem regarding brightness settings, should it be reported against g-p-m, or something more basic?
[17:53] <charlie-tca> It could be hardware related, gnome-power-manager, xfce4-power-manger, or the kernel, actually. There is no universal package without checking the logs to find out where the issue is in each report
[18:04] <malev> ping om26er
[18:23] <bbordwell> alright I have bug 571021 which is a dup of 546655, but Sebastian bacher has changed the importance of bug 571021 to high so I am not sure if I should mark it as a dup since he is looking at it. I told him in a comment that it was a dup but he did not mark it as such
[18:23] <bbordwell> https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/546655
[18:23] <bbordwell> https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/571021
[18:23] <ubot4> Launchpad bug 571021 in brasero (Ubuntu) "Eject's CD with error when trying to burn mp3 (affects: 2) (dups: 1) (heat: 20)" [High,New] https://launchpad.net/bugs/571021
[18:23] <ubot4> Launchpad bug 546655 in brasero (Ubuntu) (and 1 other project) "Creating an audio CD fails (affects: 2) (heat: 10)" [Low,Triaged]
[18:23] <ubot4> Launchpad bug 571021 in brasero (Ubuntu) "Eject's CD with error when trying to burn mp3 (affects: 2) (dups: 1) (heat: 20)" [High,New]
[18:27] <bbordwell> Anyone know what I should do?
[18:27] <om26er> bbordwell, you could mark the other one duplicate of the high priority one
[18:28] <bbordwell> om26er, will that automatically reassign the upstream bug?
[18:29] <om26er> bbordwell, no you will have to do that by hand
[18:29] <om26er> bbordwell, and you sure both are same?
[18:30] <BUGabundo_remote> Ubuntu 10.04 LTS released
[18:30] <BUGabundo_remote> congrats everyone
[18:31] <_0R10N> :)
[18:31] <bbordwell> oh well, I can do it manualy if it does not
[19:52] <thekorn> congrats to the hardest working team in show-business - the bugsquad - for the best ubuntu ever (tm)
[19:52] <thekorn> thanks everybody ;)
[20:10] <strada> Hi.  I can't login to launchpad/openID because of an internal server error :-(
[20:11] <persia> The servers are massively overloaded just now.  Try again tomorrow.
[20:12] <yofel> at least the wiki opens again
[20:13] <strada> ok. not a good time to take part at the Bug Day... I guess all world is downloading ubuntu 10.04 ;-)
[20:14] <persia> Yeah, that's about it.
[20:17] <Damascene> congratulation, well done
[20:20] <yofel> hm, is there a rough estimate on when bugs expiration will be turned on by the way? I follow the bug report, but nobody mentions anything else than 'probably soon'
[20:37] <JFo> yofel, Expiration already works on edge. or do you mean automatic expiration?
[20:37] <yofel> automatic expiration
[20:37] <JFo> ah, not sure about that
[20:38] <persia> yofel: I think "never".  It was on before, and lots of folks (including me) protested loudly.
[20:38] <JFo> heh
[20:38] <persia> yofel: Some other projects use it though.
[20:39] <JFo> I use expiration on kernel bugs
[20:39] <JFo> but not automatically
[20:44] <yofel> persia: they do seem to want to turn it on again if you trust bug 333521
[20:44] <ubot4> Launchpad bug 333521 in malone "Enable bugs expiration for Ubuntu (affects: 1) (heat: 22)" [High,Fix committed] https://launchpad.net/bugs/333521
[20:44] <persia> Looks like I have to complain again.
[20:45] <persia> Last time it closed >100 of my bugs that were still replicable and valid in the stable release just because nobody looked at them except to do the automated "please try again", which I ignored because they were pointlessly obvious things like spelling errors or misconfigurations which were completely unchanged.
[20:46] <persia> It's also philosophically a bad idea because instead of listing the bugs as known open bugs that nobody has gotten around to yet, it falsely implies that they are either fixed or not bugs.  This annoys users.
[20:47] <deryck> persia, hi. that's the point of the "expired" status being added.  to make these bugs easier to find now, not treat them as invalid.
[20:48] <persia> Beyond just being annoying, it actively reinforces the concept of separation between users and those who help make the distribution happen: rather than folks asking "Nobody is looking at my bug: how can I help get it fixed" folks get told "Your bug is bad" and select a different software solution.
[20:48] <persia> deryck: That doesn't help the user experience in any way.
[20:49] <deryck> persia, I think it helps some.  To what degree it helps could be debatable, sure.
[20:49] <persia> deryck: It helps the triagers experience, but triagers tend to be fairly comfortable working around things: it's the new user to whom we have to present the idea that 1) we care, and 2) we're budy and would appreciate their help.
[20:50] <persia> deryck: Tell me a story about an end user who is happy with a bug being marked expired.
[20:50] <persia> I may just not be imaginative enough.
[20:51] <deryck> persia, I'm not saying anyone will dance in the street saying "yay, my bug expired."
[20:51] <deryck> but it can be done in a way that is informative and not offensive, IMO.
[20:52] <persia> I don't need dancing in the streets :)  I just have not been able to come up with any way in which it improves the experience for end-users, and have a number in which it makes it less pleasing.
[20:52] <persia> Any example of how an end-user's total experience is improved by bug expiry would reduce my vociferousness.
[20:53] <persia> Even a small improvement.
[20:54] <deryck> persia, the user sees the email saying the bug expired, thinks "oh, I meant to add a comment explaining FOO and never did," and updates the bug and moves it forward.
[20:54] <persia> Does it move it forward?  Do we have any means of capturing this data?
[20:55] <persia> Do we have a way that triagers can examine recently unexpired bugs to avoid them timing out again?
[20:55] <deryck> persia, hypothetically moves it forward, i.e. it's no longer expired and someone is able to look at it again with new info.
[20:56] <persia> Most of the expirable bugs I've encountered suffered from lack of triager time, not lack of reporter feedback.
[20:58] <deryck> persia, we have another bug about toggling to confirmed automatically when the reporter responds.  this will help the case you cite here, I think.  it could be made to work with expired status, too.
[20:58] <deryck> toggle from Incomplete-->Confirmed is the current plan, which is why I mean it could be made to work with Expired, too.
[20:58] <persia> Would it be possible to roll that out at the same time as reenbling expiry?  Consider the difficulties inherent in attempting to roll out a third time if it's turned off again due to complaints.
[21:01] <deryck> persia, I think we could, yes.  The Expired status is rolling out with next week's LP release, but automatic expiring is not happening until we have time to communicate it well.
[21:02] <persia> Oh, good.  That sounds like something that could work.
[21:02] <persia> Thinking about it, I wonder if they shouldn't move back to New: just because a reporter responded doesn't mean that it's confirmed not to be a local issue (e.g. PPA software).
[21:03] <deryck> I'm looking for the bug now to update with that suggestion.
[21:03] <deryck> as for Confirmed vs. New that seemed to me to be the common convention, but if not, I'm not wedded to Confirmed.
[21:04] <persia> Do you happen to know that bug number?  I'd like to comment there on the Confirmed/New bit, but I'm not firmly attached to any specific answer.
[21:06] <deryck> persia, looking for it now.  At a coffee shop, so terribly slow connection.
[21:06] <deryck> an lp speed doesn't help that
[21:06] <persia> deryck: No worries.  If you bump into it next week, and tell me then, it's just as good :)
[21:07] <persia> Asking LP to search for it now would be painful if you were sitting in the data centre.
[21:08]  * deryck hears the browser saying "I think I can, I think I can..."
[21:11] <deryck> persia, bug 569298
[21:11] <ubot4> Launchpad bug 569298 in malone "Toggle to CONFIRMED for bugs with response from bug reporter (affects: 1) (heat: 6)" [Low,Triaged] https://launchpad.net/bugs/569298
[21:11] <persia> Wow!  Thanks for hunting.
[21:12] <deryck> np
[21:21] <simar> Could anyone help me ... plz
[21:27] <yofel> simar: what's your problem?
[22:07] <BUGabundo> everning ppl of the intertubes! we came to conquer
[22:15] <bbordwell> Does anyone know what the deal is with bugs showing up twice in launchpad?
[22:17] <charlie-tca> Got an example?
[22:18] <charlie-tca> BUGabundo: we conquered, I think?
[22:18] <BUGabundo> well, I lost +1 :|
[22:18] <BUGabundo> can't stay with 1800 users screaming in #ubuntu
[22:20] <charlie-tca> heh
[22:20] <charlie-tca> I know that feeling
[22:20] <charlie-tca> bad enough with 500 in =1
[22:21] <charlie-tca> fingers must be tired. missed the shift
[22:21] <charlie-tca> bbordwell: if they have more than one package under 'affects' they will show up once for each package
[22:22] <bbordwell> 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
[22:22] <bbordwell> most of the new bugs there show up twice for me, same bug number, only affecting one package
[22:22] <kklimonda> BUGabundo: I've already left +1 few days ago - too much noise
[22:23] <BUGabundo> shame on you
[22:24] <bbordwell> charlie-tca, are you getting the same behavior or is it just some quirk?
[22:24] <charlie-tca> That is weird. Maybe file a bug against launchpad for it
[22:24] <bbordwell> charlie-tca, I have never figured out how to do that....
[22:25] <bbordwell> how do you go about filing a bug against launchpad
[22:25] <charlie-tca> You go to #launchpad and ask them what the package is to file against. They tell you, and then it is just like any other bug
[22:26] <charlie-tca> (at least, that is my way)
[22:46] <yofel> hm, good question, the bugtracker would be the malone project, but I'm not sure how the search works
[22:47] <yofel> bbordwell: can you subscribe me once you've got the bug filed after you get an answer in launchpad? (yofel)
[22:48] <bbordwell> yofel, sure can it may be a while though i have to leave for a couple of hours
[22:48] <yofel> np
[22:52] <yofel> found a nice bug while looking for a similiar report: bug 553946
[22:52] <ubot4> Launchpad bug 553946 in malone "Timeouts in +filebug don't let you recover your bug report (affects: 4) (heat: 16)" [High,Triaged] https://launchpad.net/bugs/553946
[22:52] <yofel> that's annoying...
[23:52] <eldon> i've noticed evolution is really slow and  freezes when my internet connection is really slow, (artificially slow when downloading bittorrent. still, it should not be becoming unresponsive