[00:14] <braiam> oh... thats explain it.
[00:24] <yofel> penguin42: what's the error? (The bug is private)
[00:25] <penguin42> yofel: I get the 'Lost something?' page
[00:25] <yofel> sounds like a bug in launchpad... It should give a Permission denied page
[00:26]  * yofel goes bothering #launchpad
[00:27] <penguin42> yofel: Well except braiam just said 'oh...thats explain it' I assume the same thing ;-)
[00:27] <yofel> right, just got the same when logging out
[00:28] <braiam> but I receive the link in a email, that my bug is a dup of it
[00:30] <yofel> right, apport auto-duped it. That the master bug is private doesn't  change it. And remembering your issue the duping was right
[00:31] <yofel> let's see if someone answers in #launchpad. If not I'll mark the bug public in a few minutes.
[00:31] <penguin42>  #launchpad isn't known for the speed of its responses :-)
[00:31] <yofel> I know I'm challenging the laziness of the devs, maybe I'm lucky :P
[00:32] <yofel> that it's weekend doesn't help -.-
[00:32] <yofel> penguin42: wait, aren't you in BC?
[00:33] <penguin42> BC?
[00:33] <yofel> bug control
[00:33] <penguin42> no, just bug squad
[00:33] <yofel> :O, thought you were by now ^^
[00:33]  * penguin42 doesn't spend enough time on it
[00:35] <yofel> heh, my triaging count has gone down too since I'm spending most of my time with the kubuntu team now... (we need more packagers)
[00:40] <lifeless> yofel: its an apport bug
[00:40] <lifeless> yofel: and don't mark it public unless you've audited the attachments
[00:41] <lifeless> yofel: for private data
[00:41] <yofel> well, that much I know. And that's what I was going to do now
[00:41] <yofel> the old behaviour was better though IMO
[00:41] <braiam> lifeless: I had the same bug and is a trivial one
[00:41] <lifeless> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/764414
[00:41] <ubot4> Launchpad bug 764414 in apport (Ubuntu) "private master bugs are confusing and lead to more duplicate filings (affects: 3) (heat: 74)" [Wishlist,Triaged]
[00:42] <braiam> https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/795813
[00:42] <lifeless> yofel: the old behaviour was complex to maintain and lead to at least one vector for data leaks
[00:42] <yofel> braiam: I'm already looking at it
[00:43] <yofel> lifeless: k, thanks anyway for the explenation
[00:46] <yofel> braiam: you can see it now
[00:47] <braiam> ok
[00:53]  * penguin42 has been asked to retest a bug I reported at the beginning of 2008 - all I have to do is remember how to use the package I reported the bug in
[01:00] <penguin42> right, bed
[03:19] <braiam> yofel: nice response in #launchpad
[04:26] <RedSingularity> micahg: any command to go about getting a stacktrace for a given program?
[04:29] <CarlFK> RedSingularity: gdb?
[04:30] <braiam> RedSingularity: installing package-dbg?
[04:32] <RedSingularity> CarlFK: gdb may do the trick.  braiam: I am thinking of something that comes default with the system, that way an end user doesn't have to install it.
[04:32]  * RedSingularity looking at gdb man
[04:34] <CarlFK> if running "foo -bar" crashes, run "gdb -arg foo -bar", you will get a gdb prompt: run, crash, gdb prompt: bt full
[04:34] <braiam> RedSingularity: I think that you're going for a full retrace :P
[04:39] <RedSingularity> CarlFK: that does the job.
[04:39] <RedSingularity> hmmm no apport tools?
[04:40] <RedSingularity> to add to an existing report I mean.
[04:43] <CarlFK> apport-cli        -u report-number, --update-report report-number              Run apport information collection on an already existing problem              report. The  affected  package  is  taken  from  the  report  by               default...
[04:59] <micahg> RedSingularity: you can use apport to create the crash report and then use apport-retrace to retrace locally
[05:00] <RedSingularity> micahg: Yeah I was trying apport-retrace but it was not working....i was missing the 'a' in 'retrace' :/  Thanks.
=== luciano_ is now known as virusuy
=== luciano_ is now known as virusuy
=== JanC is now known as Guest4037
[09:26] <njin> hello, can someone tell me which kernel is actually running maverick ?
[09:28] <micahg> njin: 2.6.35
[09:30] <njin> micahg: thanks 2.6.35-...,seems that the 3.0rc2 is having great problems, better don't suggest to install it
[09:32] <njin> micahg: NP, I suggest 2.6.35-5
[09:32] <njin> thanks again
[09:33] <micahg> njin: we don't support 3.0 on maverick
[09:34] <njin> micahg, no i've suggested in natty
[09:35] <micahg> njin: natty has 2.6.38
[09:35] <njin> micahg, now i want ihe to downgrade to maverick's kernel
[09:35] <njin> that's working for him
=== maxb_ is now known as maxb
=== lifeless_ is now known as lifeless
=== matti_ is now known as matti
=== matti_ is now known as matti
=== pleia2_ is now known as pleia2
=== abhinav_ is now known as abhianv-
=== abhianv- is now known as abhinav-
=== luciano_ is now known as virusuy
[20:17] <j1mc> hi there - i had a quick question about this bug:
[20:17] <j1mc> https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/794426
[20:17] <ubot4> Launchpad bug 794426 in gnome-user-docs (Ubuntu) (and 1 other project) "Can't open help because of XML error in user-guide.xml (affects: 1) (heat: 6)" [Undecided,Confirmed]
[20:18] <j1mc> is there a translations group that i can assign this to?
[20:18] <charlie-tca> What about https://wiki.ubuntu.com/Backtrace
[20:18] <j1mc> hm, nm
[20:18] <j1mc> charlie-tca: howdy
[20:18] <charlie-tca> nm
[20:18] <charlie-tca> Hello, j1mc
[20:18] <j1mc> o/
[20:19]  * charlie-tca late again and forgot to scroll the logs all the way
[20:20] <charlie-tca> j1mc: what about subscribing the translations team, so the head guy sees it
[20:20] <j1mc> charlie-tca: thanks... i'll give that a try
[20:21] <charlie-tca> You are welcome
=== yofel_ is now known as yofel
=== Guest4037 is now known as JanC
=== Adri2000 is now known as Guest26577
=== elopio_ is now known as elopio