[04:14] <colonelqubit> Is it poor form for me to triage my own bugs?
[04:14] <colonelqubit> I've had hibernation problems for a while and had an open bug for a month (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/366264)
[04:14] <ubot4> Launchpad bug 366264 in linux "[Dell XPS m1530] Resume fails after hibernate/suspend" [Undecided,New]
[04:14] <micahg> colonelqubit: triage no, confirm yes
[04:15] <colonelqubit> What about marking importance?
[04:16] <colonelqubit> jtholmes was nice enough to tag the bug "hibernation", but there's no Importance level specified yet.
[04:17] <lifeless> colonelqubit: importance is project-wide, not individual wide
[04:18] <micahg> colonelqubit: I don't work with the kernel package, so I can't be of much help
[04:18] <colonelqubit> lifeless: yes. That's why I was wondering if I should be the one marking importance, seeing as how I kind of have a personal bias on this one bug... :-)
[04:18] <colonelqubit> micahg: Should I ask people in #ubuntu-kernel ?
[04:19] <micahg> colonelqubit: probably worth a shot
[04:19] <colonelqubit> micahg: thanks
[06:38] <YoBoY> hi
[06:38] <micahg> hi
[15:29] <skroon> looking for kubuntu package: clicking on logout in the KDE menu causes my machine to _shut down_ (default behaviour after upgrades - no configuration done)
[15:30] <skroon> any suggestions for a workaround also appreciated
[15:33] <skroon> any suggestions which package to report the bug under?
[15:59] <bddebian> Boo
[16:25] <hggdh> bdmurray, ping
[16:26] <bdmurray> hggdh: howdy
[16:29] <hggdh> bdmurray, morning, can you please renew my bugs-control membership?
[16:29] <bdmurray> hggdh: your lp id is hggdh2 correct?
[16:29] <hggdh> bdmurray, correct
[16:31] <plars> bdmurray: while you're at it... could I get an extension on my by a few weeks?  I've got that list I showed you down to <200 bugs, but it will take me longer than the 40 hours or so I have left
[16:31] <plars> s/my/mine
[16:33] <micahg> how often does membership expire?
[16:33] <hggdh> micahg, yearly
[16:34] <micahg> ok
[16:46] <G__81> hi hggdh
[16:48] <hggdh> hi G__81
[16:48] <G__81> hggdh, i did some triaging of bugs and then i couldnt come online so can i apply for the membership now ?
[16:50] <hggdh> G__81, it all depends on experience -- how many you triaged, how correct was your triaging, etc
[16:50] <hggdh> G__81, if I remember correctly, you were inactive for a long time, and got back a few weeks ago
[16:50] <G__81> https://bugs.launchpad.net/~balajig81
[16:50] <hggdh> looking
[16:50] <G__81> inactive for long time ?
[16:51] <hggdh> G__81, when I looked you up, you had pretty much no karma. Although I do not consider karma a precise indicator, having a *very* small karma shows one has been inactive
[16:52] <G__81> no karma >
[16:52] <G__81> :) i ve 43 :D
[16:57] <sectech> heh then I am screwed...
[16:57] <hggdh> heh. Well, yes, that's a pretty small karma... even I, not touching that many bugs/questions/etc in the last few months have a bit more than that...
[16:57]  * micahg knows karma :)
[16:57] <hggdh> again -- karma is *not* an indicator of being good on something, but it *is* an indicator of activity
[16:57] <sectech> If I can ever kick this warcraft addiction maybe I can do something productive.
[16:58] <hggdh> :-)
[16:59] <sectech> Insufficient funds should do the trick...
[17:02] <hggdh> G__81, I can see only two bugs with actions from you in 2009...
[17:02] <sectech> hggdh,  If I end up expiring and eventually want to come back it wouldn't be a problem would it? Pending I actually start triaging more bugs?
[17:02] <sectech> Not sure when I expire...
[17:03] <hggdh> sectech, er, are you planning your death? ;-)
[17:03] <hggdh> and, ah, reincarnation?
[17:03] <sectech> hggdh,  lol no.... but I seem to have lost motivation for IT work at the moment...  I imagine it will come back in time.
[17:04] <hggdh> sectech, you would be reinstated, provided you show new work (as everybody else)
[17:04] <sectech> okay.
[17:05] <G__81> hggdh, only 2 bugs ? no it cannot be on the other day i had done nearly 5-6 bugs
[17:05] <G__81> i still remember that
[17:08] <hggdh> G__81, please give me an URL with all your bugs (and yes, I could get it myself, but please look at it as a check you know where to find it)
[17:09] <hggdh> and -- sectech -- I would also be in the same boat if I leave for a while
[17:10] <sectech> fair is fair...
[17:24] <micahg> hggdh: I'm been triaging over a month, so I can go back over my Incompletes now and poke people :)
[17:29] <hggdh> micahg, yes... :-)
[17:31] <G__81> hggdh, there are actually 3 bugs in total so what i would do is triage more bugs and then think about the next step
[17:32] <G__81> and what happened to your application ?
[17:36] <hggdh> G__81, yes, this is the issue: not enough bugs to show to the -control members you know what you are doing...
[17:36] <hggdh> G__81, I guess Brian already took care of my renewal
[17:36] <G__81> you became an ubuntu member ?
[17:37] <hggdh> yes, I did... I finally came out of the closet ;-)
[17:38] <G__81> oh great congrats
[17:39] <hggdh> thanks
[17:48] <G__81> hggdh, 5 a day should be fine right ?
[17:48] <G__81> :)
[18:00] <hggdh> G__81, yes, it should... keep in mind that it is not only the number of bugs you triage, but *how* you do it
[18:00] <G__81> yes
[18:00] <G__81> i understand
[18:01] <G__81> i am more focused on bug fixing
[18:01] <G__81> :)
[18:02] <hggdh> :-)
[18:06] <kklimonda> hggdh: bug 382391 is wishlist... confirmed?
[18:06] <ubot4> Launchpad bug 382391 in bash-completion "completion support for "ubuntu-bug"" [Undecided,New] https://launchpad.net/bugs/382391
[18:07] <bencrisford> !info gcomrpis
[18:07] <ubot4> bencrisford: Package gcomrpis does not exist in jaunty
[18:07] <bencrisford> !info gcompris
[18:07] <ubot4> bencrisford: gcompris (source: gcompris): Educational games for small children. In component main, is optional. Version 8.4.4-1.1ubuntu4 (jaunty), package size 523 kB, installed size 1740 kB
[18:54] <hggdh> kklimonda, still need me?
[18:55] <hggdh> kklimonda, I think it is worth it... a wishlist?
[18:55] <kklimonda> ya
[18:56] <hggdh> kklimonda, I set it to wishlist, but left it otherwise as it was
[18:57] <kklimonda> ok, thanks
[20:03] <askand> Hi, since upgrading to Jaunty I hade a lot of crashes, someone over at #nautilus said, when I shoed him the trace of nautilus chrashed, that it looked like it was because of a pango or a cairo crash. Since these libraries are widely used in gnome this could indeed  explain that I had a lot of crashing. Is this a plausible theory?
[20:12] <hggdh> askand, yes, it is
[20:16] <askand> hggdh: How can I find out?
[20:17] <hggdh> askand, looking at the stacktrace...
[20:17] <hggdh> which functions, from which packages, are crashing
[20:23] <askand> hggdh: I'm not sure where to look really, here is the trace from nautilus http://pastebin.com/m50704da6 and another from gimp http://pastebin.com/m6a85888d
[20:36] <hggdh> askand, looking at it
[20:37] <hggdh> askand, first pastebin, frame #2 is cairo
[20:37] <bcurtiswx> hi all/hggdh
[20:38] <hggdh> hi bcurtiswx
[20:38] <hggdh> askand, it seems pango called cairo, and cairo barfed on a free()
[20:40] <askand> hggdh: okey
[20:40] <hggdh> askand, same thing with the second BT
[20:40] <askand> hggdh: great
[20:41] <hggdh> askand, one thing you can try if to search for a dupe on b.g.o
[20:41] <askand> What is b.g.o?
[20:41] <hggdh> copy & paste one of the BTs here: http://bugzilla.gnome.org/dupfinder/simple-dup-finder.cgi
[20:42] <hggdh> b.g.o is bugzilla.gnome.org
[20:42] <hggdh> the bug tracking system (BTS) for gnome
[20:42] <askand> ah :)
[20:47] <askand> hggdh: I get "     A stack trace was found in the bug description you specified.  It appears     that the first few relevant function calls in the stacktrace are" and some function calls and then "The following bug reports  contain all 5     function calls and likely match the bug description you gave" but it shows no bugs
[20:47] <askand> But I'll ask in #cairo too :)
[20:48] <hggdh> askand, so there is no hit for the first BT
[20:48] <hggdh> askand, now try the second BT. If it gets the same result, then it seems it is a new thing
[20:49] <askand> I will try, it's like firefox feels I'm on to sometthing, it crashes more than ever
[20:53] <hggdh> askand, this is on FF? Or across the board?
[20:53] <askand> hggdh: across the board
[20:53] <hggdh> weird. Jaunty, up-to-date, no non-ubuntu packages?
[20:55] <askand> hggdh: yes, memcheck is fine to, there was no dupes on the other trace either
[21:03] <hggdh> askand, sounds like something common (but, then, if all BTs show cairo on top, cairo is the commonality)
[21:03] <hggdh> are you running low on available memory?
[21:12] <askand> hggdh: nope
[21:12] <askand> hggdh: I am told that "crash in malloc means heap corruption means run valgrind"
[21:13] <hggdh> askand, yes, this is quite possible
[21:14] <hggdh> so... valgrind the beast. Take a deep breath, and get something to do while valgrind runs
[21:14] <persia> Note that it's worth checking the values being passed to malloc().  Sometimes the problem is actually that someone tries to allocate several petabytes by accident.
[21:14] <hggdh> heh
[21:15] <persia> One example might be failing to deference a pointer in a rarely used code path.  There are others.
[21:16] <hggdh> looking at the BT, in this case it seems it was a call to malloc 404 bytes
[21:17] <hggdh> askand, one command line for valgrind: G_SLICE=always-malloc G_DEBUG=gc-friendly  valgrind -v --tool=memcheck --track-origins=yes --show-reachable=yes --leak-check=full --num-callers=40 --log-file=valgrind.log <command>
[21:17] <hggdh> where <command> is whatever you are trying to run
[21:23] <persia> yeah, 404 bytes indicates something else is wrong.
[21:26] <hggdh> and it seems to happen on many different applications... X?
[21:32] <persia> What's a bug number for this set of issues?
[21:34] <hggdh> askand, ^^
[21:36] <askand> persia: bug 382504 is one
[21:36] <ubot4> askand: Bug 382504 on http://launchpad.net/bugs/382504 is private
[21:36] <persia> askand, Could you subscribe me?  That's extra private.
[21:38] <askand> persia: done
[21:43] <persia> askand, That looks deep indeed.  You say you're getting lots of crashes in different applications  with these symptoms?  Have you tried a memcheck run?
[21:57] <askand> persia: yes, a memcheck sucessfully ran for >24 h without errors
[22:05] <askand> persia: hggdh: now I have obtained a valgrind log from a gimpcrash
[22:06] <hggdh> askand, good. Do you have a bug opened for the crash?
[22:07] <askand> hggdh: no I will file one
[22:08] <askand> hggdh: here is the log in the mantime, a long one http://pastebin.com/m6f348f57
[22:08] <askand> meantime*
[22:12] <askand> hggdh: bug 382563
[22:12] <ubot4> Launchpad bug 382563 in ubuntu "Gimp crashed" [Undecided,New] https://launchpad.net/bugs/382563
[22:16] <askand> Hm, firefox, on which I run another valgrind froze now, dont know if I should kill it or wait..
[22:16] <hggdh> heh. Wait a bit
[22:19] <hggdh> even more confusing, valgrind shows a segv in gtk (http://pastebin.ca/1444068)
[22:21] <hggdh> now I *am* confused, askand. How did you get the valgrind and backtrace?
[22:21] <askand> hggdh: hm I got the backtrace running gdb on a crashfile
[22:21] <askand> and I got the valgrind log with the command you mentioned above
[22:21] <hggdh> same run?
[22:21] <hggdh> or from a different crash?
[22:22] <askand> from a different crahs
[22:22] <hggdh> ah
[22:24] <hggdh> askand, do me a favour, and please run, on  a terminal, "apport-collect -p gimp 382563"
[22:29] <askand> hggdh: it wasn't a lot that was uploaded
[22:32] <hggdh> that's OK, the important part is the dependencies file
[22:33] <askand> ok
[22:33] <hggdh> hum. You are using nvidia. Which nvidia is this?
[22:33] <askand> hggdh: the one from thre repos
[22:33] <askand> not sure what version it is
[22:33] <BUGabundo> ora boas noites
[22:37] <hggdh> ora, ora, BUGabundo
[22:37] <hggdh> askand, do you run compiz?
[22:38] <askand> hggdh: I do usually yes
[22:38] <BUGabundo> Hellow: hggdh
[22:38] <hggdh> hello BUGabundo :-)
[22:38] <hggdh> askand, can you try disabling compiz?
[22:38] <Hellow> wait, what?
[22:38] <Hellow> lol
[22:38] <hggdh> heh
[22:39] <BUGabundo> LOLOLOLOL Hellow.... sorry for the higilght
[22:39] <BUGabundo> ROFL
[22:39] <Hellow> ROFLOL
[22:39] <askand> hggdh: sure
[22:41] <askand> hggdh: are you suspecting compiz? :)
[22:43] <hggdh> askand, since this happens across the board, I am suspecting either compiz or X
[22:44] <askand> hggdh: I had gnome-terminal crashed with SIGSEGV in _XSend if that might be related
[22:47] <hggdh> it might, but it is still too early to say anything
[22:49] <askand> Ok, I got a trace for that too in bug 382143 , but I have disabled compiz now, I'll be back if things continues to crash
[22:49] <ubot4> askand: Bug 382143 on http://launchpad.net/bugs/382143 is private
[22:49] <askand> oh it was private too
[22:49] <hggdh> heh
[22:50] <askand> now its public
[22:51] <hggdh> askand, I subcribed myself, and put it back as private -- the coredump is still there
[22:53] <hggdh> let's wait for apport to retrace it, and delete the coredump, then... back to public
[22:54] <askand> hggdh: what's in the coredump that should be private?
[22:56] <kklimonda> askand: depends on program - passwords, emails etc. ;)
[22:56] <askand> kklimonda: ohh, yeah that can remain private indeed
[22:57] <kklimonda> askand: basically a lot of private data
[22:57] <BUGabundo> hey kklimonda
[22:58] <kklimonda> hey :)
[22:58] <BUGabundo> did you enjoy the album I gave you ?
[22:58] <hggdh> askand, it can have anything that was loaded in the memory address space -- for example, encryption keys
[22:58] <kklimonda> BUGabundo: it's nice
[22:58] <BUGabundo> humm really?
[22:59] <BUGabundo> I though you were a METAL dude
[22:59] <kklimonda> BUGabundo: nah, I listen to all kind of music.
[23:12] <kklimonda> how to get list of patches applied on ubuntu kernel?
[23:14] <hggdh> changelog?
[23:40] <dtchen> kklimonda: there is no easily-parsed list, unfortunately. the kernel team uses git (just as most distros tracking upstream do).
[23:40] <dtchen> kklimonda: on the other hand, it is fairly readable; see kernel.ubuntu.com/git
[23:42] <kklimonda> dtchen: thanks