[00:40] <emma> is the GBJ officially over so that the current stats page is the official results?
[02:36] <duanedesign> could someone who is good with X bugs please take a look at Bug #260847 it was reported 6 monyhs ago and the reporter is still having an issue. Thank You!
[06:08] <dholbach> good morning
[06:15] <fabrice_sp> Hi. I've been notified that Bug #331519 has been marked as duplicates of Bug #322049, but this last one is marked as private. Could someone mark it as public? Thanks!
[06:16] <fabrice_sp> strange: 331519 is marked as private, but I can see it :-/
[07:09] <stefanlsd> dholbach: guess we should talk here rather :)
[07:11] <dholbach> stefanlsd: maybe we could ask for feedback on ubuntu-bugsquad@ and loco-contacts@?
[07:12] <stefanlsd> dholbach: not sure im on either of those. i was thinking like we ran an those sessions before with you about the planning, just to do another online session. but mailing list could work
[07:13] <dholbach> I'll send out a mail about it later on
[07:13] <dholbach> good idea! :)
[07:13] <stefanlsd> dholbach: kk. cause i have a couple of things :)
[07:13] <dholbach> great :)
[07:21] <stefanlsd> dholbach: what happens now with 5 a day stats  since Events arnt there? are you just gonna query everything?
[07:22] <dholbach> stefanlsd: I'll put up some more statistics soon, there just wasn't enough time to do it before
[07:24] <stefanlsd> dholbach: just was wondering about 5-a-day stats without the applet. Will you be able to query LP to do stats without a specific event?
[07:24] <dholbach> stefanlsd: yes
[07:24] <stefanlsd> dholbach: kk. is it a big performance hit?
[07:25] <dholbach> stefanlsd: I'll do another 5-a-day upload that drops all functionality, just leaves the ~/.signature bits
[07:25] <dholbach> stefanlsd: I get it from the ubuntu-bugs@ mailing list
[07:25] <stefanlsd> dholbach: aah ok. nice. i thought you were doing LP api stuffs
[07:29] <dholbach> thekorn: are you fine with the above? :)
[07:34] <thekorn> dholbach, sorry, I did not follow this discussion, but doing some packaging magic to remove/block the applet etc. is a good idea
[07:35] <dholbach> great
[07:35] <dholbach> thanks
[07:35] <dholbach> now it's enough to just join ~5-a-day-participants
[07:41] <thekorn> dholbach, is it possible to temporary participate on 5-a-day, let's say only on hug-days or bug jams
[07:44] <dholbach> thekorn: I'm going to add statistics for teams/people/etc. soon - right now I just wanted to have stats for the global bug jam - there wasn't time to do more than that
[07:46] <thekorn> dholbach, and another question is: is it 5-a-day or total-count-of-bugs-per-day ;)
[07:47] <dholbach> thekorn: I was thinking of having something like "amount of weeks in a row where you managed to do 5-a-day" :)
[07:47] <dholbach> so it's not huge bug number of seb128 / pedro against of the rest of the world :)
[07:48] <thekorn> ok, that's good especially when you think about motivating new contributors by this initiative
[07:49] <dholbach> yeah
[07:55] <Hobbsee> that sounds good
[08:21] <ara> Hey people! Do you want to find bugs in new Jaunty's features? Please, join us in the Ubuntu Testing Day: https://wiki.ubuntu.com/Testing/UbuntuTestingDay/20090223
[08:22] <Ryan52> ara: you sound like a radio advertisement (:
[08:22] <ara> Ryan52: yes, yes, yes, here in KLM Ubuntu Testing Day station
[08:24] <Ryan52> hehe
[08:25]  * thekorn tries to find out how to get this screen-profile thing for intrepid
[08:40] <Laibsch> Hi
[08:40] <Laibsch> How do I reset bug 331222 to just affect ubuntu and not any package?
[08:41] <Laibsch> Ah, got it
[08:46] <Ryan52> so this screen-profiles thing...what happens if you want to install gnu screen also?
[08:47] <Ryan52> oh, am I confused?
[08:48] <Ryan52> yep, I am. weird.
[12:02] <gnomefreak> mvo: something is really freaky with update-manager starting on its own when i use apt-get dist-upgrade
[12:03] <BUGabundo> gnomefreak: did you lose the discussion on the ML?
[12:03] <BUGabundo> gnomefreak: bug 332945
[12:03] <gnomefreak> BUGabundo: i havent checked email in a few days
[12:03] <BUGabundo> ahh that explains It
[12:04] <BUGabundo> this 2 will intereset you
[12:04] <BUGabundo> https://lists.ubuntu.com/archives/ubuntu-devel/2009-February/027416.html
[12:04] <BUGabundo> https://lists.ubuntu.com/archives/ubuntu-devel/2009-February/027434.html
[12:05] <gnomefreak> update-notifier is installed here
[12:06] <BUGabundo> it should have been removed
[12:06] <BUGabundo> by recent updates
[12:06] <gnomefreak> it is from  notification area the titles of bug is a bit misleading
[12:08] <gnomefreak> added my 2cents that people left out ;)
[12:09] <BUGabundo> okay
[12:09] <BUGabundo> nice
[12:13] <gnomefreak> this is a feature :( feature == bug with purpose
[12:14] <BUGabundo> yeah
[12:15] <gnomefreak> i highly doubt they are on the right page. it notifies you only ones updates strated downloading not once update is done
[12:17] <savvas> ubuntu-desktop still depends on update-notifier here as well
[12:18] <savvas> oh.. dist-upgrade :P
[12:21] <BUGabundo> savvas: update-manager -d
[12:24] <savvas> BUGabundo: I've updated to jaunty a month ago unfortunately
[12:26] <savvas> BUGabundo: sudo aptitude why-not update-notifier; sudo aptitude why update-notifier
[12:26] <gnomefreak> they say time is the reason but since i stay updated i cant state it is 2 days
[12:26] <gnomefreak> they handle depends differently however this should be the same for both.
[12:28] <ogra> gnomefreak, you are aware that that actually deserves its own bug ?
[12:28] <gnomefreak> pinning gives an error that it is not a command or something like that but it still pins the package
[12:29] <ogra> (lauching u-m if you call apt-ge dist-upgrade is totally out of discussion in the above bug)
[12:29] <ogra> (though i agree its not noce either if it does that)
[12:29] <ogra> *nice even
[12:31] <gnomefreak> ogra: i can file another one but it can be every 2 days but i notice it most of the time i run dist-upgrade i never even thought of not doing updates every 2 days but i will try it the next few days
[12:32] <ogra> gnomefreak, hmm, i read your comment as: u-m launches if i type "sudo apt-get dist-upgrade" in a terminal
[12:32] <BUGabundo> I do my updates 4+ times a day
[12:32] <ogra> gnomefreak, if you talk about resetting the counter you should probably mention that ;)
[12:33] <gnomefreak> ogra: looking back on it it never happens with upgrade for me, and im not sure if it is "everytime" but i caaaaan say it only happens with dist-upgrade for me
[12:33] <ogra> it sounds like dist-upgrade launches the gui
[12:33] <ogra> (doesnt happen here though)
[12:37] <gnomefreak> it didnt happen yesterday when i did updates but did on saterday nad today, maybe it is time released but why dont i notice it on upgrade i will look at iut the next few days (i do updates when i boot up and close up and sometimes in between but i will look at it. personally if people dont notice icon in notification-area maybe the bubble should be used but u-m should never open>check updates while you are upgrading using term
[12:37] <gnomefreak> damn that was longer than i thought :(
[12:40] <ogra> erm, the point is that ther is no icon anymore, its gone for no replacement
[12:40] <BUGabundo> gnomefreak: the prob there, as mpt said is that the buble has no interaction
[12:40] <BUGabundo> you can't click on it
[12:41] <gnomefreak> than bubble should be fixed dont auto start any app just command
[12:41] <BUGabundo> lunch
[12:41] <BUGabundo> bbl
[13:18]  * ccooke realises he's writing a minor dissertation into a comment on that bug report. 
[13:18] <ccooke> oops. I should find somewhere better for this.
[15:07] <bddebian> Boo
[15:23] <cprofitt> https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/286050
[15:24] <cprofitt> When a person marks a bug as invalid and claims there is a duplicate shouldn't they mark the bug as a duplicate?
[15:25] <seb128> cprofitt: I did that and I could spend my day looking at numbers or actually work on fixing bugs
[15:25] <seb128> cprofitt: I decide to not spend my days looking at number for hundred of duplicates files every week and let users do that
[15:25] <seb128> which is suboptimal but since that's either that or having a buglist we can't work correctly on ...
[15:26] <cprofitt> seb128, There is no need to defend yourself seb128 - I was asking about the procedure....
[15:26] <kirrus> can we have a list of bugs which need to have their dups found... possibly a tag?
[15:26] <seb128> cprofitt: ideally yes, in practice what I said
[15:26] <kirrus> that way we can add it as an easy-level triaging task for those just starting, and getting used to LP
[15:27] <cprofitt> while the reasons for my asking is indeed your bug... I am relatively new to this so wanted to make sure my understanding of the procedure was correct
[15:27] <seb128> we got quite some discussions about that
[15:27] <cprofitt> I would like to find the 'root' bug that there is for this and ensure that the functionality is added as a "wish list"
[15:27] <seb128> and some people disagree with the "closing duplicates without marking those duplicates"
[15:27] <cprofitt> low priority as it really will not affect a lot of people....
[15:28] <cprofitt> but 'wish list' none the less.
[15:28] <seb128> re
[15:28] <seb128> the bug is on gtk and closed
[15:28] <cprofitt> I agree currently it is close to impossible to find duplicates due to how people describe their problems....
[15:29] <seb128> upstream has closed their equivalent bug as not being one but how gtk works
[15:29] <seb128> there is no point to reopen an ubuntu task we are not going to change that over the gtk guys
[15:30] <cprofitt> true...
[15:30] <cprofitt> how would that get wish listed then?
[15:32] <cprofitt> I am going to try and figure out if the difference between my T61 / T42 / T500 is hardware or not... it still seems odd the both the OSD does not work on the T500 and the button is still functional with a menu, but on the T61/T42 I get OSD and the button is not functional with the menu open...
[15:32] <cprofitt> more a curiosity for me than any high-priority issue though
[15:33] <cprofitt> kirrus, I think we could add the information about (frequently reported 'bugs' that are really just the current state of functionality)
[15:34] <cprofitt> that would help with having new people like me know that these are repeat 'non-bugs'
[15:35] <cprofitt> seb128, do you think that is an option - modifying the wiki pages to deal with those situations? (https://wiki.ubuntu.com/Bugs/Responses)
[15:36] <cprofitt> or maybe even make a sep. page for frequent 'non-bugs'
[15:37]  * cprofitt is nervous he is the victim of a netsplit and all his typing has gone unheard
[15:37] <seb128> cprofitt: sorry I was busy on other things
[15:37] <cprofitt> no problem...
[15:37] <cprofitt> just got a ping response...
[15:38] <cprofitt> I too often get net split and my client hangs out for minutes...
[15:38] <seb128> cprofitt: gtk grabs key events for menu if the action is working that's an hardware one
[15:38] <seb128> ie it's some hardware logic doing the change and not the software reacting to key events
[15:39] <seb128> you can't wishlist something against the willing for people writting the code
[15:39] <seb128> argue upstream if you think that's worth starting a battle
[15:39] <seb128> I think that's such of a detail than we have better to do
[15:39] <cprofitt> seb128, what about the suggestions above for the frequent non-bugs?
[15:39] <seb128> what do you want to write a stock reply?
[15:40] <seb128> the issue might be a design decision
[15:40] <seb128> or something to take upstream
[15:40] <seb128> or not a bug
[15:40] <cprofitt> I was thinking more of having list of things that get reported as bugs - that are non-bugs
[15:40] <cprofitt> obviously you knew this one is a frequently reported bug...
[15:40] <seb128> gnome bug #100903
[15:40] <seb128> bug #287040
[15:41] <maco> *snort* like the bugs that are filed for gcalctool by people who can't do math?
[15:41] <cprofitt> if there was a list of those then people like me could mark them as invalid much more easily
[15:41] <cprofitt> my team was about to mark it as invalid until we saw the inconsistency of the results with the T42/61  and the T500
[15:42] <seb128> I've no real opinion about such a list I will let bugsquad people comment about that
[15:42] <cprofitt> but if there was a list on the wiki we would have felt more comfortable with the 'that is the way it works' initial response we had
[15:42] <seb128> I think we have enough to do to not waste energy on non bugs
[15:42] <seb128> but bugsquad is about triaging bugs so they might have an another opinion
[15:42] <seb128> my opinion is a package manager who tries to get work done one ;-)
[15:43] <cprofitt> seb128, well if we have to deal with all reports -- then it would make sense to make it easier to do so.
[15:43] <cprofitt> the canned responses do that...
[15:43] <cprofitt> and a list of non-bugs would likely make the bugsquad more efficient too...
[15:43] <seb128> right
[15:44] <charlie-tca> cprofitt: I think the results would depend greatly on the size of that list
[15:44] <cprofitt> as a community member who wants to contribute I certainly do not want to waste my time trying to  confirm items that will never get looked at.
[15:44] <cprofitt> charlie-tca, the size of the list should really not be an issue - though making the list easy to sort through  and the information easy to find should be
[15:45] <charlie-tca> Trying to run 700 bugs through another list makes triaging a lot slower!
[15:45] <cprofitt> not following charlie-tca
[15:45] <cprofitt> we already use the canned responses.... how would this be any different?
[15:45] <charlie-tca> You would have to run every bug reported through that new list, however big it becomes
[15:46] <charlie-tca> What happens when you have 1000 bugs on it?
[15:48] <cprofitt> Do you run every bug through canned answers?
[15:48] <charlie-tca> I look at the answers when I need to.
[15:49] <cprofitt> Wouldn't a list of frequently reported non-bugs be the same then?
[15:49] <charlie-tca> canned responses has a limited size it will become. Does that list?
[15:50] <cprofitt> I am considering the people that are just getting started... that might spend 1+ hours working on a non-bug because there is no resource
[15:50] <charlie-tca> Maybe I just don't understand
[15:50] <cprofitt> charlie-tca, canned responses still lack responses for several areas....
[15:50] <cprofitt> so it could grow
[15:50] <cprofitt> but it likely deals with the 'frequent' areas 100%
[15:51] <charlie-tca> Yes, and still leaves for you to think and act on your own
[15:51] <cprofitt> I am not sure how many frequently reported non-bugs  get reported as non-bugs...
[15:51] <kirrus> Could we have a bot that automatically checked through all new/incomplete/confirmed bug reports, to see if they look like another 'non-bug' bug report, and then list them on a page with an option to ignore or close with a potted reply?
[15:52] <seb128> cprofitt: I think charlie-tca doesn't understand what canned reply you want to use, did you suggest have a list of all those non-bug issues? which means somebody would have to read the whole list to know if the supposed bug is there?
[15:53] <Laibsch> How are jaunty bugs being tracked in LP?  I mean, what is on the radar of "this ought to be fixed before release"?  I'm not talking bugs of importance critical.
[15:53] <Laibsch> I upgraded to jaunty yesterday and want to help with jaunty bug triage
[15:54] <BUGabundo> humm milestones?
[15:54] <Laibsch> I want to do it efficiently and with focus
[15:54] <seb128> Laibsch: bugs to be fixed are nominated for jaunty and importance > high
[15:54] <Laibsch> can I set milestones or would that be frowned upon?
[15:54] <seb128> you can use milestone for non nominated bugs
[15:54] <Laibsch> I guess I wonder as much as to which bugs to pick as how to "nominate" bugs
[15:54] <cprofitt> Hmm....
[15:55] <Laibsch> OK, thanks
[15:55] <seb128> if you use those for a nominated bug that will be consider as a blocker for this milestone
[15:55] <Laibsch> I'll nominate and set a milestone here and there
[15:55] <seb128> which is likely not up to you to decide
[15:55] <Laibsch> OK, that is what I figured
[15:55] <Laibsch> Can I "nominate for a milestone"?
[15:55] <Laibsch> ;-)
[15:56] <seb128> no, you can nominate for jaunty
[15:56] <Laibsch> Maybe I'll just set the milestone and leave an appropriate comment "feel free ..." directed toward the one who should accept or reject my proposal
[15:56] <cprofitt> I would think that if a person like seb128 sees several 'reports' that are being worked on and they are really 'dead issues' (either upstream or that is how they work) that they could reach out to bug-control and have us make a wiki entry... that entry could be added to the page already in existence for that 'area'
[15:57] <cprofitt> https://wiki.ubuntu.com/DebuggingACPI - adding the commonly reported 'issues' that are not really bugs to this page for instance
[15:57] <Laibsch> I'll use the milestones sparingly, if at all
[15:57] <alex-weej> how do i debug keyboard shortcuts? my eject button doesn't work, but my volume ones do
[15:57] <cprofitt> I do not think charlie-tca and seb128 that that list would become too huge....
[15:58] <seb128> alex-weej: talk to slangasek or pitti on #ubuntu-devel about it
[15:58] <cprofitt> but I am not a developer or package manager so I do not know how many 'issues' that are not bugs get up to their level
[15:58] <seb128> alex-weej: I would guess that first step is to see if xev gets an event when you use it
[15:58] <alex-weej> i get told off whenever i go in there and say "this doesn't work"
[15:59] <alex-weej> xev doesn't see it
[15:59] <cprofitt> I just saw some of the frustrations of the folks working on the global bug jam and would like to, if possible, come up with a way of giving them some guidance similar to the canned responses
[15:59] <seb128> alex-weej: so it's an xorg bug I guess
[15:59] <Laibsch> cprofitt: what are the frustrations?
[16:00] <Laibsch> sorry if this was raised during earlier discussions, I scanned through the backlog, but only quickly
[16:00] <seb128> alex-weej: well, join and say something around the line of "xev doesn't list any key event when using the eject key on computer_model could anybody help me to debug this"
[16:00] <seb128> alex-weej: that's usually better than "doesn't work" comment
[16:01] <alex-weej> seb128: :)
[16:01] <seb128> alex-weej: computer_model was supposed to be your computer ;-)
[16:01] <cprofitt> frequently reported 'issues' that can be 'confirmed', but area actually 'how it works' not bugs
[16:01] <Laibsch> alex-weej: I also think in your case it would be better to report to the freedesktop.org bug tracker
[16:01] <Laibsch> cprofitt: You mean, things that are unintuitive to configure?
[16:02] <Laibsch> And thus generate a high number of bug reports that aren't really valid?
[16:02] <alex-weej> Laibsch: takes too long to test fixes that way
[16:02] <cprofitt> Yes, or items like the bug we were discussing above
[16:02] <Laibsch> cprofitt: Here's what I would do
[16:03] <Laibsch> Leave open one bug report with wishlist: "XY is hard to configure", that is valid.  There you can document workarounds and whatnot.
[16:03] <Laibsch> Everybody gets what they need
[16:03] <Laibsch> The bug stays open and thus visible
[16:03] <Laibsch> "XY hard to configure to do ABC"
[16:03] <Laibsch> Title should be as specific as possible
[16:04] <Laibsch> Dupe the others to this bug
[16:04] <cprofitt> that is one option -- though a wiki  addition under the canned responses could make it easier to find...
[16:04] <cprofitt> both would work...
[16:04] <Laibsch> alex-weej: I don't follow you.  That is actually the quicker route
[16:04] <alex-weej> most of my bugs get ignored on fdo
[16:04] <cprofitt> perhaps Laibsch - have a wiki that links to the bugs as examples could help too...
[16:05] <alex-weej> i have to sign up to mailing lists, and i hate email
[16:05] <Laibsch> alex-weej: Then you should about what that is the case.
[16:05] <Laibsch> alex-weej: Did you offend anyone? Are they actively ignoring you?
[16:05] <cprofitt> alex-weej, take a look at this page -- https://wiki.ubuntu.com/Bugs/Responses
[16:05] <cprofitt> there are some great tips in there to assist you with bug reports...
[16:05] <BUGabundo> alex-weej: you can always just read feeds, or check the archives
[16:05] <Laibsch> alex-weej: If just nobody picks up your reports, then you should consider maybe how to improve your reports with more data or clearer language or whatnot
[16:06] <alex-weej> or i could just use launchpad...!?
[16:06] <Laibsch> alex-weej: And you will need someone gateway'ing for you
[16:06] <cprofitt> they will help make sure that they are complete and you can get a digest for the lists or you can use your launchpad site to follow your reported / triaged bugs
[16:06] <Laibsch> alex-weej: Better is to gateway yourself
[16:06] <Laibsch> which is also why this is quicker
[16:07] <Laibsch> Because most xorg bugs won't be fixed in ubuntu, but in upstream
[16:07] <alex-weej> it's a pain in the arse dealing with upstream trackers. even if it does get fixed upstream i'd have to dig out the fix to test it on my system
[16:07] <alex-weej> or compile upstream sources
[16:08] <alex-weej> obviously the fix will go upstream but it's probably just a quirk, it's not like i'm going to fix it wrongly
[16:08] <alex-weej> working upstream just takes it longer for the results to show in ubuntu
[16:09] <BUGabundo> alex-weej: can't you link the bug upstream to LP?
[16:10] <alex-weej> if i did this for every bug i found i wouldn't have enough time in the day to eat or sleep
[16:10] <BUGabundo> ehehe
[16:10] <BUGabundo> alex-weej: you are not alone
[16:11] <BUGabundo> that means you can't find all the bugs
[16:11] <BUGabundo> I find a bunch of them my self
[16:11] <BUGabundo> and many, I send upstream
[16:11] <BUGabundo> other (when I don't have an account upstream) I just mark it as "needs upstream bug"
[16:12] <BUGabundo> so that a new bug triager can do it for me
[16:12] <alex-weej> the day that i can just click a button to send upstream in launchpad without an account on one of 1000 bugzillas/sourceforget/whatever, is the day i am a happy man :)
[16:12] <BUGabundo> do as I do
[16:12] <BUGabundo> :)
[16:13] <Laibsch> alex-weej: A thousand mile journey begins with a single step.  Better to make that step in the right direction than to try and do it all.  Look up Kaizen.
[16:13] <Laibsch> And follow BUGabundo's advice
[16:13] <Laibsch> It will make for a lot more happy users, you included, I assume
[16:13] <Laibsch> LP users
[16:14] <alex-weej> haha i know what kaizen is. but the thing is, i am supposed to be doing other things. i just wanted to do a quick 2 minute debug of a broken eject key and get a bug reported
[16:14] <alex-weej> but now i sit here 15 minutes later with the CD still inside my computer
[16:15] <alex-weej> and no bug reported :P
[16:34] <Laibsch> I don't understand what you are looking for
[16:34] <Laibsch> @ all: Can anybody help me understand why the Debian task in bug 236041 is still open?
[16:37] <charlie-tca> peers to be because Debian couldn't find the package and so never updated the bug
[16:38] <Laibsch> bug #236041
[16:39] <Laibsch> charlie-tca: Where do you see that?
[16:40] <Laibsch> from the Debian BTS:
[16:40] <charlie-tca> about halfway up before I finished reading all of it.
[16:40] <Laibsch> Found in versions 0.10-1, pastebinit/0.10-1 Fixed in version pastebinit/0.11-1
[16:40] <charlie-tca> But the last comment is : We believe that the bug you reported is fixed in the latest version of
[16:40] <charlie-tca> pastebinit, which is due to be installed in the Debian FTP archive:
[16:40] <Laibsch> charlie-tca: Are we talking about the same thing here?
[16:41] <charlie-tca> launchpad bug 236041
[16:41] <charlie-tca> debbugs 483381
[16:42] <Laibsch> yes
[16:42] <Laibsch> clearly marked as closed
[16:42] <Laibsch> or fixed
[16:42] <charlie-tca> debbugs has the comment I referenced, which leads me to think it isn't quite there yet
[16:42] <hggdh> debian bug 483381
[16:42] <Laibsch> that is a standard comment
[16:43] <charlie-tca> You could close it manually if you want to
[16:43] <Laibsch> see, the tracker has it closed ^^
[16:43] <Laibsch> charlie-tca: I'm trying to understand what happened first
[16:43] <Laibsch> hggdh: Do you have an idea?
[16:43] <hggdh> trying to figure it out
[16:44] <hggdh> well, the debian bug clearly state this was resolved on the specifed version
[16:44] <hggdh> which does not seem to be the case...
[16:45] <hggdh> did you look at the diff?
[16:45] <Laibsch> hggdh: I'm the maintainer, reporter of the bug all in one
[16:45] <Laibsch> I know what is going on in that bug
[16:45] <hggdh> heh
[16:45] <Laibsch> and it is fixed ;-)
[16:46] <hggdh> sorry
[16:46] <Laibsch> I just don't understand why it's still on my radar
[16:46] <Laibsch> well, of course because the Debian task is still open
[16:46] <hggdh> OK. Actually, the LP bug should not have been closed
[16:46] <Laibsch> And LP seems to have tripped over itself here.  Trying to understand why..
[16:46] <Laibsch> why not?
[16:47] <Laibsch> It's fixed in Jaunty version
[16:47] <Laibsch> -> LP bug can be closed
[16:47] <hggdh> it is already fixed? the last comment states it was still going to be installed
[16:47] <Laibsch> Or should it have been closed by some automagic when 0.11 hit Jaunty?
[16:48] <hggdh> if the changelog for Ubuntu states (LP: xxxxx) then LP automagically closes it
[16:48] <Laibsch> yes, it was fixed in 0.11 which is in Jaunty
[16:48] <Laibsch> I think the Debian changelog has only the Debian bug number
[16:48] <hggdh> then OK. Sorry. What put me off is the last comment statings "when it reaches Jaunty)
[16:48] <Laibsch> Still does not explain why LP can't track Debian BTS here
[16:48] <hggdh> ah. It was probably merged, then
[16:49] <Laibsch> Yes, I think I closed it later without putting in another comment
[16:49] <Laibsch> It was synced
[16:49] <Laibsch> no Ubuntu changes (of course, none are necessary, I'd put them in the Debian package)
[16:49] <hggdh> the upstream task in LP should have been marked closed by LP as soon as LP re-read the bug comments
[16:50] <hggdh> this seems to have been a failure from LP to notice it
[16:50] <Laibsch> yes
[16:50] <Laibsch> I wonder why
[16:50] <hggdh> hum
[16:50] <Laibsch> Let's see if the guys in #launchpad know anything about it
[16:50] <hggdh> Laibsch, I think the best is to open a LP/Malone bug on this, and ask them why the upstream was not closed
[16:50] <hggdh> this is wrong
[16:51] <Laibsch> yeah, eventually, I will
[16:51] <Laibsch> Let's see if the lp guys have a quick answer
[16:51] <hggdh> on #launchpad?
[17:09] <seb128> thekorn: hey, what would you recommend to use nowadays to do simple things as "what is the title for bug number nnn"?
[17:11] <Laibsch> What's the commonality for bugs listed in https://bugs.launchpad.net/ubuntu/jaunty/ ?
[17:11] <Laibsch> I nominated bug 327386 for Jaunty, for example, yet it does not show up in that list.
[17:12] <seb128> nominations need to be accepted
[17:12] <charlie-tca> Laibsch: thanks for the launchpad thing. It explains what is happening to my xfce bugs too
[17:12] <seb128> you don't have the power to do direct nominations
[17:12] <Laibsch> seb128: IOW, those are the accepted nominations?
[17:13] <seb128> yes
[17:13] <Laibsch> charlie-tca: You mean upstream tasks being left open?
[17:13] <Laibsch> seb128: OK, thanks
[17:14] <thekorn> seb128, you mean in a script? - definitely launchpadlib
[17:14] <Laibsch> I guess that still leaves looking for a sane way to collect and group hardy bugs
[17:14] <Laibsch> leaves me looking
[17:14] <Laibsch> jaunty bugs
[17:14] <thekorn> it's fast and easy once you found a way to handle the credentials
[17:15] <seb128> thekorn: do you have a small example somewhere? is there an easy way to deal with the credential thing?
[17:15] <Laibsch> seb128: Is there a way to list jaunty nominations irrespective of acceptance status?
[17:16] <Laibsch> get a long list of bugs
[17:16] <Laibsch> LP search functions really suck
[17:16] <charlie-tca> Laibsch: yes.
[17:16] <Laibsch> and have sucked ever since LP was created
[17:17] <seb128> Laibsch: https://bugs.edge.launchpad.net/ubuntu/jaunty/+nominations
[17:17] <BUGabundo> Laibsch: I have a bug opened that should be a dupe of that one of fonts
[17:17] <Laibsch> seb, great. thanks
[17:17] <seb128> 362 bugs listed there utch
[17:17] <thekorn> seb128, lp:~thekorn/+junk/launchpad-shell is a ipython like shell which tries to help you with credentials etc
[17:17] <BUGabundo> Laibsch: if lp search fail, use google
[17:18] <Laibsch> well, not looking for a particular bug
[17:18] <thekorn> seb128, and also in ubuntu-dev-tools there is a script to create such credentials
[17:18] <seb128> thekorn: thanks
[17:18] <Laibsch> BUGabundo: I'm more after a task list
[17:18] <thekorn> it is called manage-credentials
[17:19] <james_w> seb128: http://paste.ubuntu.com/121952/
[17:19] <Laibsch> BUGabundo: I think https://bugs.edge.launchpad.net/ubuntu/jaunty/+nominations from seb128 might be workable
[17:19] <Laibsch> I can even search inside that group
[17:21] <Laibsch> BUGabundo: It is a very visible and often reported bug.
[17:21] <Laibsch> But yours is not listed in http://tinyurl.com/ajs8ed :P
[17:21] <seb128> james_w, thekorn: thanks
[17:22] <BUGabundo> Laibsch: the techical notes *asks* for it to be reported
[17:22] <BUGabundo> so that it can be fixed
[17:22] <thekorn> james_w, ubuntutools is this lib which is part of ubuntu-dev-tools, right
[17:22] <BUGabundo> mine was closed by the bug triager
[17:22] <BUGabundo> and then I had to open it again
[17:23]  * thekorn always gets confused by the naming and different places of all these libs
[17:23] <james_w> thekorn: yep
[17:25] <BUGabundo> seb128: on bug 333366
[17:25] <BUGabundo> sure its reproducible
[17:25] <thekorn> one day we should create a wiki page (maybe on help.lp.net) to show all this tips&tricks around launchpadlib
[17:25] <BUGabundo> every single time I use the menu or from a cli
[17:26] <seb128> BUGabundo: I still fail to see what nautilus has to do with notifications
[17:26] <BUGabundo> humm
[17:26] <BUGabundo> its the other way around
[17:26] <BUGabundo> I fail to get the link from the wiki
[17:27] <BUGabundo> but some where it says that some apps will now open in the background
[17:27] <BUGabundo> and nautilus is doing just that
[17:27] <BUGabundo> while it should be on foreground
[17:27] <seb128> ?
[17:27] <seb128> BUGabundo: nautilus is a file manager
[17:27] <seb128> ie it browse directories
[17:27] <BUGabundo> yes
[17:27] <BUGabundo> that's what I'm talking about
[17:28] <seb128> it's not doing anything to something else
[17:28] <BUGabundo> grrr
[17:28] <seb128> not doing notifications
[17:28] <BUGabundo> we are not seeing eye to eye
[17:28] <seb128> not handling focus
[17:28] <BUGabundo> seb128: when you open an app, you expect it to be foreground
[17:28] <BUGabundo> correct?
[17:28] <seb128> yes
[17:29] <BUGabundo1> _I thought_ it may have to do with the changes to set some apps as *unfocus*
[17:29] <BUGabundo1> like UM now does and a few others
[17:30] <BUGabundo1> doesn't anyone else here on jaunty see this?
[17:30] <seb128> BUGabundo1: ok, I get it now, when people don't know they should not try to guess but describe their issue otherwise  that just confuses things
[17:30] <seb128> that's a compiz issue
[17:30] <seb128> nothing to do with nautilus nor notifications
[17:31] <BUGabundo1> I'm not using compiz
[17:31] <BUGabundo1> I'm on metacity
[17:31] <BUGabundo1> but have composite enabled
[17:34] <BUGabundo1> have to go
[17:34] <seb128> composite is not revelant there
[17:34] <savvas> seb128: any chance that we'll have bug #208750 for jaunty? the patch for it was released upstream
[17:34] <BUGabundo1> I'll follow the bug
[17:34] <seb128> I got the issue until opening a mount and now that works again
[17:34] <seb128> weird bug
[17:34] <seb128> savvas: upstream will roll new tarballs next week and we will do the update
[17:35] <savvas> ah great, thanks :)
[18:20] <james_w> chrisccoulson: hey
[18:21] <chrisccoulson> hi james_w
[18:21] <james_w> chrisccoulson: I think I remember a bug you triaged where the policykit gnome authorisations tool in the System->Administration menu basically didn't work any more
[18:21] <james_w> I can't find it now, am I imaging things?
[18:22] <chrisccoulson> it's assigned to gtk+2.0 at the moment, although it might be assigned back in a few minutes. I'm just about to test a fedora patch
[18:22] <chrisccoulson> bug 328921
[18:22] <james_w> chrisccoulson: heh, you found the patch
[18:22] <james_w> thanks
[18:22] <james_w> the patch works
[18:23] <chrisccoulson> ah, you tested already. thanks!
[18:23] <james_w> I just found it from a different direction, and just requested sponsorship
[18:23] <chrisccoulson> thanks
[18:23] <james_w> and remembered the bug and so tested, and it fixes that one as well
[18:23] <james_w> so I wanted to clean it up
[18:24] <chrisccoulson> cool. i just reassigned the bug back again
[18:26] <james_w> thanks for working on it
[18:26] <james_w> it seems there was a gtk+ component as well
[18:27] <chrisccoulson> yeah, it seems that a change in gtk broke it. I tested it with the old 2.14.x version of gtk, and it worked ok
[18:28] <chrisccoulson> thanks for sorting out the patch anyway - that's one less thing for me to do this evening :)
[20:09] <maxb> If a bug is regression-potential, and it's an important regression, should it be "Nominated for release"-ed for Jaunty?
[20:18] <asomething> maxb: what bug? my understanding is that at this point, only blocker should be targeted at jaunty
[20:18] <maxb> How about bug 319825? I'd say all Acer Aspire One's deciding they can't connect to wifi using networkmanager is fairly blocking
[20:22] <asomething> maxb: sounds fair to me, especially since it's well triaged. I'd say go ahead an nominate, the worst that can happen is that someone from ubuntu-release declines it
[20:25] <hggdh> asomething, would you be willing to package Evo 2.24.4 for Intrepid?
[20:26] <asomething> hggdh: sure, but probably not until Wed
[20:26] <hggdh> oh, no prob. We just had an unhappy user on the evo ML...
[20:27] <hggdh> asomething, thank you
[20:28] <asomething> hggdh: no problem
[20:47]  * bcurtiswx waves to room
[22:12] <bdmurray> maco: If I found bugs with alsa-info output would that help you with the AlsaInfoOutput wiki page you started?
[22:13] <maco> bdmurray: i think dtchen wants jaunty ones, but if yes
[22:13] <maco> bdmurray: he says theyre all broken, so he needs these to get a listing of cards in existence and go through fixing 'em all. im not sure quite how literal "all" is
[22:13] <bdmurray> maco: isn't codec and ssid not kernel specific?
[22:14] <maco> some codecs arent supported in older kernels so they wont have output
[22:14] <BUGabundo> maco: is this a Request for Logs?
[22:14] <BUGabundo> I can send mine
[22:15] <maco> bdmurray: he told me before that codec output changes based on what quirk is in use
[22:15] <maco> since it shows how the nids are connected up
[22:16] <maco> so its possible for it to change across kernels if a quirk is added between kernels. then again, he wanted to see what was in a gentoo codec dump before dismissing it as "I've already got that one" so it probably wouldn't hurt to have older ones
[22:16] <maco> i just know he asked people to take jaunty daily cds to their nearest computer store and start recording :P
[22:18] <seb128> BUGabundo: would be nice if you could describe bugs
[22:18] <maco> i think he's gonna be here soon-ish.  he just asked if he could come borrow my internet...something about a 2.6.29-rc5 bug wiping out his entire lvm...
[22:19] <seb128> BUGabundo: a non debug glib stracktace with no description is of no use
[22:19] <BUGabundo> seb128: yeai lack that... I tend to just paste crash logs
[22:19] <BUGabundo> seb128: give me 5 mins to install gbd for it
[22:19] <BUGabundo> I just have to wait for my 3G modem to know its 3,5G and not 2G
[22:19] <seb128> BUGabundo: no gdb but valgrind, and what do you do to get the crash?
[22:20] <BUGabundo> seb128: eheh just opened gedit and closed
[22:20] <bdmurray> maco: okay, let me know because I could help find reports like bug 329741 which is Jaunty and has alsa-info in it
[22:20] <BUGabundo> akgraner just confirmed it to me on a clean install of jaunty
[22:20] <seb128> BUGabundo: do you use the seahorse plugin?
[22:20] <BUGabundo> maybe
[22:20] <BUGabundo> have to check
[22:20] <bcurtiswx> bdmurray: i would be happy to help look too
[22:21] <seb128> BUGabundo: bug #327252
[22:21] <maco> bdmurray: hahah oh that log flood...can we mark dtchen as "this bug affects me"?
[22:21] <BUGabundo> seb128: I don't see seahorse on the list of gedit plugins
[22:21] <maco> BUGabundo: encryption
[22:21] <BUGabundo> seb128: http://bugzilla.gnome.org/show_bug.cgi?id=535241
[22:22] <seb128> BUGabundo: different issue yours is a memory corruption or double free or similar
[22:22] <BUGabundo> maco: seb128 again, I don't see any encryption plugin on my gedit list
[22:22] <BUGabundo> oh ok
[22:22] <maco> i can open gedit with a file specified on the command line in jaunty
[22:22] <seb128> BUGabundo: you don't get a segfault but a glibc incorrect memory usage
[22:23] <BUGabundo> a user on +1 thought it was the same
[22:23] <charlie-tca> BUGabundo: you should look at that report again. How does "right click a file" "open with text editor" open on a command line?
[22:23] <seb128> BUGabundo: do you have seahorse-plugins installed?
[22:23] <maco> i have document stats, insert date/time, modelines, spel checker, and text encryption plugins enabled. so what do you have enabled that i dont?
[22:23] <BUGabundo> $ apt-cache policy seahorse-plugins  Installed: 2.25.90-0ubuntu1
[22:24] <BUGabundo> ahh maco now I see it there
[22:24]  * BUGabundo scrashs eyes
[22:24] <BUGabundo> its "text encription"
[22:25] <BUGabundo> and it would seem its ON by default
[22:25] <BUGabundo> cause akgraner has the same crash log
[22:25] <maco> wait does it crash on load or on exit?
[22:25] <BUGabundo> I can't disable the plugin maco seb128
[22:25] <BUGabundo> gedit just crashs
[22:25] <BUGabundo> it used to crash on exit
[22:25] <maco> because i just clicked the X and yeah...core dump
[22:26] <BUGabundo> same or new bug?
[22:26] <maco> hmm?
[22:27] <seb128> BUGabundo: gconftool --set /apps/gedit-2/plugins/seahorse-pgp --type bool false?
[22:27] <BUGabundo> diff backtrace
[22:27] <seb128> BUGabundo: that should disable it
[22:27] <maco> seb128: still crashes
[22:27] <seb128> ok no clue then
[22:27] <maco> oh wait
[22:27] <BUGabundo> still on
[22:27] <maco> that didnt disable it
[22:27] <BUGabundo> and still crasing
[22:28] <seb128> uninstall seahorse-plugins? ;-)
[22:29] <BUGabundo> and there I went
[22:29]  * maco tries
[22:29] <BUGabundo> missed something?
[22:29] <maco> no
[22:29] <BUGabundo> ok
[22:30] <maco> no crash
[22:30] <maco> (after removing seahorse-plugins)
[22:30] <maco> holy crap seahorse-plugins is a buggy package
[22:30] <bcurtiswx> what isn't it default for bug reports to have the version of ubuntu effected.  Is there a reason why its not asked for in a drop down menu when people fill out bug reports?
[22:30] <bcurtiswx> why* not what..
[22:31] <maco> i think to be simple
[22:31] <maco> but then it does say under (why not above?) the text box to include that stuff
[22:31] <maco> in small text
[22:31] <charlie-tca> also because the bug can be in all versions
[22:31] <nhandler> Could someone take a look at https://bugs.edge.launchpad.net/ubuntu/+source/lyricue/+bug/277889/comments/14 ? I have no clue what the user is requesting
[22:31] <bcurtiswx> but i think it would help to know which version the bugs being reported under
[22:32] <maco> ok how about checkboxes? this bug affects __ 6.06 __ 7.10 ___ 8.04 __ 8.10 ___ 9.04
[22:32] <bcurtiswx> that would be great
[22:32] <bugabundo> ubuok
[22:32] <bcurtiswx> like searching now.. if im interested in bugs that effect alsa and jaunty
[22:32] <maco> what?
[22:32] <bugabundo> back now from empathy
[22:32] <bugabundo> pidgin doesnt work on 2G networks
[22:32] <maco> weird
[22:33] <bcurtiswx> i can search alsa.. but not even in advanced search is there a jaunty specific search
[22:33] <maco> but the rest of the net does?
[22:33] <bugabundo> maco it will crash
[22:33] <bugabundo> got pleanty of gbd logs for it
[22:33] <maco> bcurtiswx: bugabundo you could switch off of pidgin for irc while on 2g...
[22:33] <bugabundo> http://paste.ubuntu.com/118890/
[22:33] <snap-l> PIdgin has been pretty flaky lately
[22:34] <bugabundo> snap-l: no.... really ? /sarcams
[22:34] <maco> oh wait..i forgot...i cant get pidgin to launch
[22:34] <snap-l> Not crash crash, but more not hooking up to Google Talk and showing me people I want to talk to
[22:34] <bugabundo> bugs with NM, PA, etc
[22:34] <bugabundo> maco: that was what was happening with akgraner
[22:34] <snap-l> Seeng similar behavior with empathy as well
[22:34] <bugabundo> when i confirmed the gedit bug
[22:35] <bugabundo> snap-l: so far empathy is up and running
[22:35] <bugabundo> but back to bug one: what is the current status of this gedit crash?
[22:35] <maco> so much of my chatting is in irssi i barely notice the lack of pidgin. i can only think of 1 person i talk to in pidgin that's not on this server, so... draw your own conclusions. i think it means i dont have any ungeeky friends
[22:36] <snap-l> Maybe I'm not waiting long enough
[22:36] <bcurtiswx> im sorry i missed the steps.. what are we doing to get it to crash again?
[22:36] <bugabundo> snap-l: i spoke to soon.... apport just fired agaisnt empathy butterfly
[22:36] <maco> bcurtiswx: gedit afile.txt
[22:36] <maco> bcurtiswx: when you hit the X, it crashes
[22:36] <bcurtiswx> intrepid? jaunty?
[22:36] <maco> jaunty
[22:36] <bcurtiswx> k, lemme fire up the VM
[22:36] <bugabundo> jaunty
[22:36]  * bugabundo empathy UI sucks
[22:37] <maco> meanwhile pidgin crashes from pulseaudio stuff and 2G networks apparently, and just hangs on start for some of us
[22:37] <bugabundo> ahh 3G is back....
[22:37] <bcurtiswx> bugabundo: agreed
[22:37] <maco> ugh yeah
[22:37] <bugabundo> installing gdb for gedit and glibc
[22:37] <maco> empathy's ui is like kopete
[22:37] <bugabundo> to help seb128
[22:37] <maco> forced alphabetization
[22:37] <bcurtiswx> i havent updated my vm in a bit.. im gonna test that gedit problem before and after an upgrade
[22:37] <bugabundo> 14MiBs.... xeee
[22:39] <bcurtiswx> i gedit from gui load and terminal.. clicking the X doesn't bring apport or anything suspicious up (before an update)
[22:40] <maco> bcurtiswx: did you load it from terminal with a file?
[22:40] <bugabundo> bcurtiswx: seb128 uploading gdb trace to bug
[22:41] <bugabundo> https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/333558
[22:41] <bcurtiswx> maco: i type "gedit afile.txt" then x'd it out, no problems
[22:42] <bugabundo> 121MB for valgrind? wtf
[22:43] <bcurtiswx> let me update and  i will test out those actions again
[22:44] <maco> bcurtiswx: note what version you currently have
[22:44]  * bugabundo 2G suck > 4487B/s 2h 19min 13s
[22:44] <maco> apt-cache policy gedit
[22:44] <maco> and apt-cache policy seahorse-plugins
[22:44] <bcurtiswx> 2.25.7-0ubuntu1
[22:45] <bcurtiswx> that was gedit
[22:45] <bugabundo> umm i need to post that to the bug too
[22:45] <bcurtiswx> 2.25.90-0ubuntu1 for seahorse
[22:47] <maco> seahorse or seahorse-plugins?
[22:47] <bugabundo> $ apt-cache policy seahorse  Installed: 2.25.91-0ubuntu1
[22:47] <bcurtiswx> seahorse-plugins
[22:47] <bugabundo> $ apt-cache policy seahorse-plugins  Installed: 2.25.90-0ubuntu1
[22:47] <bugabundo> $ apt-cache policy gedit  Installed: 2.25.7-0ubuntu1
[22:48] <bcurtiswx> bugabundo: i have the same versions before a software update
[22:48] <bugabundo> see the bug
[22:48] <bugabundo> i have it all there
[22:48] <bcurtiswx> i am reading it yes
[22:49] <bugabundo> but me and maco have text enc ON
[22:49] <bugabundo> and cat disable it
[22:49] <bugabundo> *cant
[22:49] <bcurtiswx> hmm, lemme try that out, idk if its set that way in mine or not yet
[22:51] <bugabundo> seb128_: is that bt good?
[22:51] <seb128_> bugabundo: which one?
[22:51] <bugabundo> valg is still donwloading
[22:51] <bugabundo> maco can u try it?
[22:51] <maco> try what?
[22:51] <bugabundo> seb128_: the new one i added from dbgsym
[22:51] <maco> valgrind on gedit?
[22:51] <bcurtiswx> bugabundo: i am able to reproduce your bug now
[22:52] <bugabundo> maco val
[22:52] <maco> bcurtiswx: what was updated?
[22:52] <bcurtiswx> maco: nothing
[22:52] <maco> oh you had the plugin disabled
[22:52] <bugabundo> i bet it rurned on text enc
[22:52] <bcurtiswx> maco: yes
[22:53] <maco> 5mb of memory leak...nice
[22:53]  * bugabundo has now a new debug toy heheh
[22:53] <bcurtiswx> bugabundo: same problem trying to disable plugin too
[22:53] <bugabundo> lol
[22:53] <maco> seb128_: so what are we looking for in valgrind?
[22:53] <bugabundo> add that to the bug
[22:53] <bugabundo> so other users find it
[22:54] <bugabundo> i cant open LP right now
[22:54] <maco> um....am i supposed to have gedit-dbgsym?
[22:54] <bugabundo> i have it
[22:54] <seb128_> maco: yes, that's usually what is useful for double free issues
[22:54] <bugabundo> if i add enough free disk, i would have it for all packageds
[22:57] <bcurtiswx> set to confirmed, for everyones information
[22:59] <bugabundo> thanks
[22:59] <bugabundo> i would like to update the bug, but its 404 for me
[22:59] <bugabundo> :(
[23:00] <maco_> valgrind and irssi are on my other workstation, and my kbd is dead in X :(
[23:00] <bcurtiswx> bugabundo: its fine for me, no 404
[23:02] <bugabundo> 94% [1 valgrind 39961640/42.2MB 94%]  woot
[23:02] <bugabundo> bcurtiswx: its not LP prob... its my 3G mode
[23:02] <bugabundo> its stuck on 2G mode :(
[23:03] <bcurtiswx> aww, what comp u using?
[23:03] <bugabundo> NM 7.1
[23:03] <bugabundo> seb128_: should the upstream bug link be removed from this bug?
[23:03] <seb128_> bugabundo: the new stacktrace is good
[23:04] <seb128_> bugabundo: well, I would tend to think that the bug is a duplicate of the seahorse one
[23:04] <seb128_> but yeah the watch is wrong
[23:04] <bugabundo> let me try and remove it
[23:04]  * bugabundo bad bruce
[23:05] <bugabundo> done
[23:06] <bugabundo> running  valgrind now
[23:09] <bugabundo> seb128_: bcurtiswx how do i read valgrind log?
[23:09] <seb128_> read or get?
[23:09] <bugabundo> interpet it
[23:10] <seb128_> you search for invalid read or write errors which are not ld or python ones
[23:10] <seb128_> those tend to be valgrind noise rather than errors
[23:10] <bugabundo> uploading log to bug
[23:11] <bugabundo> done
[23:11] <bugabundo> u guys can now see it there
[23:12] <bcurtiswx> bugabundo: yes
[23:13] <bugabundo> OT question if wanna run gwibber (python app) on valgrind, how would i do it?
[23:13] <bcurtiswx> bugabundo: i don't beleive the title reflects what the bug is about anymore..
[23:14] <bcurtiswx> but then again.. we're still determining the root cause... so nvm
[23:14] <bugabundo> feel free to edit it
[23:14] <bugabundo> i'm on 2G
[23:14] <bugabundo> so any access to websites is painfully slow
[23:14] <bugabundo> took me a while to upload that log
[23:14] <bcurtiswx> i was just about to, but im going to wait until the root cause comes out, since you're busy woking on some debud
[23:15] <bcurtiswx> eek
[23:15] <bcurtiswx> debug*
[23:15] <bugabundo> already did
[23:15] <bugabundo> until u or seb128_ask for anything else
[23:15] <bugabundo> that bug is done for me
[23:16] <bcurtiswx> bugabundo: i just assisted by testing out the bug to see if its reproducable.  i am not all that great with debugging
[23:17] <bugabundo> ok refraising: until seb or any desktop dev pings on that bug
[23:17] <bugabundo> lol
[23:18] <seb128_> the log confirms that's a seahorse issue
[23:18] <seb128_> would be nice to get a new one with seahorse-plugins-dbgsym installed
[23:18] <bcurtiswx> bugabundo: edited title to reflect bug best IMO.
[23:19] <bugabundo> seb128_: installing
[23:19] <bugabundo> seb128_: val or  gdb ?
[23:20] <seb128_> valgrind
[23:20] <bugabundo> running now
[23:22] <bugabundo> seb128_: uploading now
[23:23] <bugabundo> seb128_: http://launchpadlibrarian.net/23022329/valgrind_gedit2.log
[23:23] <seb128_> bugabundo: thanks
[23:23] <seb128_> it has the required details now
[23:23] <seb128_> you can look to the
[23:24] <seb128_> ==6915== Invalid free() / delete / delete[]
[23:24] <seb128_> snippet in the log
[23:24] <seb128_> it has the codepath for the incorrect free call
[23:24] <bugabundo> seb128_: what i lack on descriptions, i make up on debug eheh
[23:24] <seb128_> ;-)
[23:24] <bcurtiswx> lol
[23:24] <seb128_> still would be useful to write in the bug that you get the crash on closing
[23:25] <bcurtiswx> seb128_: i edited the title to reflect that i beleive
[23:26] <seb128_> bcurtiswx: ok, I didn't reopen the bug I just looked to the valgrind, thanks
[23:26] <bcurtiswx> seb128_: no prob
[23:27] <bugabundo> should this bug also affect seahorse or seahorse-plugin ?
[23:27] <bugabundo> hi maco
[23:27] <bugabundo> what happened?
[23:27] <bcurtiswx> wb maco
[23:28] <maco> i switched workspaces then X decided i had no keyboard
[23:28] <maco> had to reboot
[23:29] <maco> also, mysterious horizontal scrolling
[23:29] <bugabundo> seb128_: can u please take a look at http://paste.ubuntu.com/122094/ ?
[23:29] <bugabundo> its a pidgin valgrind log
[23:29] <bugabundo> i still need learn how to read it better
[23:30] <bugabundo> funny gedit will not open it.... just kate
[23:30] <seb128_> nothing useful there
[23:30] <seb128_> seems too short to be a real log
[23:30] <seb128_> are you sure you didn't have an already running piding instance in which case it didn't start it under valgrind since it was running
[23:30] <bugabundo> nop
[23:30] <bugabundo> pidgin just kiled it self
[23:31] <bugabundo> again...
[23:31] <bugabundo> can i run valgrind and gdb at the same time?
[23:31] <bcurtiswx> is there still any though of replacing pidgin with empathy?
[23:31] <bcurtiswx> thought*
[23:31] <bugabundo> bcurtiswx: postponed to koala i think
[23:31] <bugabundo> cant find the blueprint to be sure
[23:32] <bcurtiswx> bugabundo: yeah i think theres been a forums topic on this forever
[23:32] <bugabundo> if only "some" pidgin dev were nicer!
[23:32] <bugabundo> they are so rude...
[23:32] <bugabundo> they beat them self up.... its crazy reading their ML
[23:33] <bcurtiswx> sounds like my community.. scientists... can never agree with each other
[23:33]  * bugabundo tries to get pidgin running
[23:34] <bugabundo> while i'm on 2G pidgin will not start :(
[23:35] <bugabundo> $ gdb --args valgrind pidgin -n --debug
[23:35] <bugabundo> aint any good
[23:35] <bcurtiswx> well, i need to put some food in this belly of mine.  i will be back later all
[23:38] <maco> ah! wait pidgin IS running!
[23:38] <maco> i can see notifications from it
[23:38] <maco> it just doesnt have any open windows ???
[23:39] <BUGabundo1> maco it started to be minimized
[23:39] <BUGabundo1> a while a ago
[23:39] <maco> it doesnt show up in alt+tab
[23:39] <BUGabundo1> $ valgrindB kmail
[23:39] <BUGabundo1> <unknown program name>(22347)/: Communication problem with  "kmail" , it probably crashed.
[23:40] <BUGabundo1> lol
[23:41]  * d-b notes people who have added responses "stock / as per wiki" to closed bugs.
[23:41] <d-b> on own bug.
[23:41] <d-b> which was closed.
[23:41] <maco> and if i add a task manager to see the window list..no, there's definitely no open pidgin window
[23:41] <maco> d-b: wait they closed their own bugs for not answering themselves?
[23:41] <d-b> no i had a bug. and some guy goes and adds useless info to it
[23:42] <BUGabundo1> ehehe
[23:42] <d-b> https://bugs.edge.launchpad.net/launchpad-registry/+bug/288966
[23:42] <d-b> it was complete ... meh. not important
[23:42] <BUGabundo1> new bug triagers (from events like GBJ) commit lots of mistakes
[23:42] <BUGabundo1> I had to fix a few of them this weekend
[23:43] <d-b> BUGabundo1: in that case i hope some one checks the ones i commented on- >i tried to be as helpful as possible.
[23:43] <BUGabundo1> "they" have to learn from their mistakes
[23:44] <BUGabundo1> we have been here way longer then them
[23:44] <d-b> BUGabundo1: not me. i'm new
[23:44] <BUGabundo1> I've been fileing bugs and learning since 2005
[23:44] <BUGabundo1> and still learn new stuff every day
[23:44]  * BUGabundo1 checks LP profile
[23:45] <d-b> BUGabundo1: ah ?
[23:45] <BUGabundo1> Member since:       2006-06-10
[23:51] <maco> bdmurray: dtchen says yes the kernel matters
[23:52] <bdmurray> maco: otay
[23:52] <maco> because the codec dump varies by driver
[23:53] <maco> (like, as the driver changes, so will that)