[00:22] <trinikrono> hey does anyone know where the default time for inactive monitor times in gnome power manager are set, in ubuntu or upstream i have this bug 371195 that i would like to get triaged
[00:22] <ubot2> Launchpad bug 371195 in gnome-power-manager (Ubuntu) "Blacklight stays lit (affects: 1) (heat: 10)" [Wishlist,Confirmed] https://launchpad.net/bugs/371195
[02:19] <trinikrono> hey guys
[02:19] <trinikrono> if i have a bug filed a against a package
[02:20] <trinikrono> and it says that is crashed on resuming from hibernation, should i file it against linux also?
[02:23] <hggdh> trinikrono: what crashed? The application, or Linux?
[02:24] <trinikrono> hey hggdh, the application , in this case it was checkgmail
[02:24] <trinikrono> i meant if to file it against the kernel also (linux package)
[02:25] <hggdh> trinikrono: right now I see no reason to open a task for linux
[02:25] <trinikrono> okie
[02:25] <trinikrono> was jut curious here
[02:26] <hggdh> what might have happened is (something like) checkgmail tried to use the network just after resuming, it was not yet there, and the appl crashed
[02:27] <hggdh> until something can be tied to kernel resume, this is still only an application issue
[02:27] <trinikrono> hggdh: next one bug 151226, i believe this bug can be closed now
[02:27] <ubot2> Launchpad bug 151226 in checkgmail (Ubuntu) "Synaptic recommends libsexymm2, which is useless (missing Perl bindings) (dups: 1) (heat: 18)" [Undecided,Incomplete] https://launchpad.net/bugs/151226
[02:28] <trinikrono> the question is weither it is invalid or fix released
[02:28] <trinikrono> since it works fine now
[02:28] <trinikrono> it is a pretty old bug they filed
[02:31] <hggdh> trinikrono: state it is working on <release>; the bug was opened against Hardy, it seems. Hardy desktop is still supported
[02:33] <hggdh> trinikrono: it is not invalid, anyways, this is a real bug. It can go to either wontfix or fix released
[02:33] <hggdh> from where it is now
[02:33] <hggdh> but I would still keep it open
[02:33] <trinikrono> okie
[02:33] <trinikrono> i was thinking fix released
[02:35] <trinikrono> we dont have a response for fix released?
[02:54] <hggdh> trinikrono: sorry, got busy
[02:54] <trinikrono> well i found a nice one on the responses page
[02:54] <trinikrono> i am sending out gentle reminders on bugs now
[02:54] <hggdh> trinikrono: usually, when (say) a Lucid bug gets fixed on the Maverick version, we willclode the bug fix released
[02:55] <hggdh> but, in this case, this was opened on Hardy, and lagged unresolved until Lucid
[02:55] <trinikrono> well its okie now
[02:55] <hggdh> so... yes, you can close fix released. BUT -- make sure you write down the workaround in the bug description
[02:56] <trinikrono> no workaround now
[02:56] <trinikrono> it just works now :D
[02:56] <trinikrono> before they where complaining about dependcies when installing the package
[02:56] <trinikrono> but now it works fine
[02:56] <micahg> hggdh: hi :) are you familiar with a lack of context menu on indicators?
[03:08] <hggdh> hi micahg. I guess you mean the lack of left-click actions?
[03:10] <micahg> hggdh: right click :)
[03:10] <hggdh> micahg: sorry, the usual confusion on left-handed people ;-)
[03:11] <hggdh> micahg: IIRC, this is proposital -- there should not be any need of conext menus on indicators
[03:12] <hggdh> (which, I agree, is a major change in paradigm)
[03:12] <micahg> hggdh: right, I was wondering if you could pen a canned response quoting that lack of need, I see bugs frequently reporting the issue
[03:13] <hggdh> micahg: oh. K. I will research the official explanations, and try something
[03:13] <micahg> hggdh: thank you, feel free to hand off to someone else that might know more :)
[03:13] <hggdh> micahg: easy, everybody knows more than I do :-)
[03:14] <micahg> hggdh: you know that's not what I meant ;)
[03:14] <hggdh> :-)
[03:23] <trinikrono> excuse me guys
[03:24] <trinikrono> isnt firefox 3.6 in lucid?
[03:24] <micahg> trinikrono: yes
[03:25] <trinikrono> lol? bug 597691
[03:25] <ubot2> Launchpad bug 597691 in ubuntu (and 1 other project) "Please push to latest FF (3.6.*) (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/597691
[03:25]  * micahg wishes people would stop filing those
[03:25] <trinikrono> what is the issue here?
[03:25] <trinikrono> clearly i am confused lol
[03:25] <micahg> trinikrono: actually, I think the user just wants the latest zeitgeist
[03:26] <trinikrono> so its a package request for zeitgeist?
[03:26] <micahg> trinikrono: not really sure
[03:28] <micahg> trinikrono: you could ask the user to clarify the request
[03:28] <trinikrono> for real
[03:28] <trinikrono> ima gonna use the !vague thing
[03:29] <trinikrono> also can i assign it to firefox?
[03:29] <micahg> trinikrono: k
[03:29] <trinikrono> or just make sure what he is doing first
[03:29] <micahg> trinikrono: please no unless it's a firefox request
[03:29] <trinikrono> okie
[03:29] <micahg> trinikrono: thanks
[03:30] <drew212> micahg: do you have time to tell me what should be in a proper bug report?
[03:30] <micahg> drew212: bug or crash report?
[03:30] <drew212> crash
[03:31] <micahg> drew212: k, so, a proper crash report will contain a coredump that can be retraced by the retracer
[03:31] <micahg> drew212: what
[03:31] <micahg> drew212: what's uploaded is a .crash file by apport
[03:32] <micahg> drew212: the problem is not everyone's machine can generate these
[03:32] <micahg> drew212: the alternative is a  local gdb backtrace
[03:32] <micahg> drew212: questions?
[03:32] <drew212> aren't there times where apport fails?
[03:32] <micahg> drew212: yes
[03:33] <drew212> so how can we tell whats a good one and whats a bad one?
[03:33] <micahg> drew212: well, the retracer will tell you if it can't do the job (i.e. *-retrace-failed tags)
[03:34] <micahg> drew212: otherwise, you might see some of the files from a .crash attached to a bug w/out the coredump and stacktraces
[03:34] <drew212> so how do we get a local gdb backtrace if it fails?
[03:34] <micahg> !backtrace | drew212
[03:34] <ubot2> drew212: To get a backtrace of a failing application please read: https://wiki.ubuntu.com/Backtrace
[03:36] <drew212> are there times when apport gets a successful backtrace but it doesnt contain the information needed?
[03:36] <micahg> drew212: yes, flash can be a good example
[03:37] <drew212> is there anything in the files i should look for? (an example would probably be beneficial)
[03:38] <micahg> drew212: well, it takes practice to read a backtrace
[03:38] <micahg> drew212: the stacktrace and threadedstacktrace files should be what to look at
[03:39] <drew212> alright
[03:41] <drew212> micahg: ill hit you up if i have any questions later, thanks! ;-)
[03:41] <micahg> drew212: k, np
[03:41] <micahg> drew212: it took me quite a while to be able to read the stacktraces usefully
[03:49] <trinikrono> micahg: what should i do if users complain about a memory leak in a application in a bug
[03:49] <trinikrono> what i mean is what to ask for
[03:49] <micahg> trinikrono: which bug?
[03:50] <trinikrono> bug 382267
[03:50] <ubot2> Launchpad bug 382267 in checkgmail (Debian) (and 1 other project) "memory leak (affects: 5) (heat: 37)" [Undecided,New] https://launchpad.net/bugs/382267
[03:50] <micahg> trinikrono: https://wiki.ubuntu.com/Valgrind
[03:51] <micahg> trinikrono: there should be a response for it too
[03:51] <trinikrono> yes vlagrind  i was wondering what that was lol
[03:53] <micahg> hggdh: still around?
[03:57] <trinikrono> and providing i get the op to get a valgrind log
[03:57] <trinikrono> what will we do with it micahg
[03:57] <micahg> trinikrono: that I don't know :)
[03:58] <trinikrono> i must say it looks like quiet alot of work to do
[04:02] <micahg> trinikrono: memory leaks aren't easy things to fix
[04:02] <trinikrono> should i look for a upstream bug now?
[04:08] <trinikrono> micahg: it appears to be upstream also, so i will go and put the link to the upstream bugtracker
[04:09] <micahg> trinikrono: great
[04:38] <ddecator> looks like micahg does a good job of taking my place ;)
[04:38] <micahg> ddecator: ?
[04:39] <trinikrono> lol
[04:39] <trinikrono> i was writing so much my pen died
[04:39] <ddecator> micahg: you're doing a good job of answering the questions of both of my students, haha
[04:39] <micahg> ddecator: ah, wanna take my 2?
[04:39]  * micahg hasn't contacted them yet
[04:39] <trinikrono> i am one
[04:39] <ddecator> micahg: oh, didn't know you had two
[04:40] <micahg> ddecator: yeah, and I can't handle any right now, all I can do is answer quick Qs
[04:40] <ddecator> sounds like the admins are doing a good job
[04:40] <ddecator> micahg: well i appreciate you helping them out :)
[04:41] <micahg> ddecator: np, we help each other :)
[04:41] <trinikrono> ddecator: you know i am now reading about the launchpad email interface, its good right?
[04:41] <ddecator> trinikrono: i've never actually used the email interface, but i've seen comments submitted that way
[04:42] <trinikrono> ddecator: maybe because your inbox is beyond repair lol?
[04:43] <ddecator> trinikrono: haha, only at the moment. i keep meaning to tackle all of my bugmail, but other things keep coming up
[04:43] <trinikrono> ddecator: you ever had to track a memory leak?
[04:44] <ddecator> trinikrono: can't say i have..
[04:44] <ddecator> trinikrono: other than watching top to see if memory usage skyrockets
[04:44] <trinikrono> i found one in checkgmail bug 382267
[04:44] <ubot2> Launchpad bug 382267 in checkgmail (Debian) (and 2 other projects) "memory leak (affects: 5) (heat: 38)" [Undecided,New] https://launchpad.net/bugs/382267
[04:44] <trinikrono> so far all i did was add a bug tracker and put !valgrind
[04:47] <ddecator> trinikrono: looks good so far :)
[04:52] <trinikrono> i wanted to try out the email interface, but it says i need to sign messages =\
[04:52] <trinikrono> i use gmail
[04:53] <ddecator> sign like with a pgp key?
[04:53] <trinikrono> yes, i regeistered the one in launchpad
[04:56] <micahg> trinikrono: you can use gmail w/Thunderbird for signing
[04:57] <trinikrono> what about evolution?
[05:01] <micahg> trinikrono: idk, probably
[05:01] <ddecator> seems like there would be a way
[05:01]  * micahg is on the Mozilla Team, not GNOME :)
[05:01] <trinikrono> lol you guys dont use the email interface much?
[05:01]  * ddecator uses gmail in prism :)
[05:21] <trinikrono> shucks
[05:21] <trinikrono> looks like im with you guys on the thunderbird bandwagon
[05:23] <ddecator> i can't get used to tb until it has conversation style threading
[05:23] <micahg> ddecator: well, you get message based threading
[05:24] <ddecator> micahg: yah, i enabled that, but i didn't like it as much
[05:43] <nigelb> micahg: how do I change default template for thunderbird mails?
[05:43] <nigelb> file-> save as -> templates doesn't work :/
[05:43] <micahg> nigelb: probably in preferences
[05:53] <trinikrono> hey is it hugday today?
[05:54] <nigelb> if its thursday in your tz, yes
[05:55] <ddecator> so yes :)
[05:55] <ddecator> idk if i ever got an email saying what the focus is..
[05:57]  * micahg got the emails but forgot
[05:57] <micahg> fontconfig :)
[05:58] <ddecator> huh...i wonder if my filter accidentally caught it
[06:00] <ddecator> huh, the one from two bugdays ago did, but i never got one for today's :(
[06:22] <trinikrono> apparently you can just reply to the bug email address and it comes up in launchpad with pgp keys or anything
[06:22] <trinikrono> i mean none
[06:27] <ddecator> yah, it shows up as a comment
[07:37] <trinikrono> so how do we triage font bugs lol?
[08:14] <trinikrono> i saw something in QA wiki that said i should assign myself to a bug until a bug triaged, does that stand?
[08:33] <kermiac> trinikrono: only assign yourself to a bug report if you intend to fix the bug
[08:34] <trinikrono> :D, thats what i thought must be a old wiki
[08:34] <kermiac> trinikrono: have you got a link to that wiki page?
[08:35] <trinikrono> https://wiki.ubuntu.com/QATeam/TriageAtOpenWeek
[08:35] <trinikrono> apparently thats how they used to do it
[08:36] <kermiac> ok, thanks trinikrono
=== ogra_ is now known as ogra
[09:28] <trinikrono> is there any triagers online
[09:34] <kermiac> trinikrono | !ask
[09:34] <kermiac> haha fail
[09:34] <kermiac> !ask
[09:34] <ubot2> Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-)
[09:35] <trinikrono> :D does dpkg reconfigure fontconfig-config work for you in lucid?
[09:35] <trinikrono> doesnt work for me in jaunty
[09:35] <trinikrono> or look at bug 349663
[09:35] <ubot2> Launchpad bug 349663 in fontconfig (Ubuntu) "debconf options still present but not working (affects: 12) (dups: 3) (heat: 50)" [Low,Confirmed] https://launchpad.net/bugs/349663
[09:39] <kermiac> trinikrono: that command doesn't appear to do anything for me on Lucid either.
[09:40] <kermiac> trinikrono: I experienced the same behaviour as the last comment in that bug report
[09:43] <trinikrono> nice
[09:44] <trinikrono> so just to find a upstream bug then we can triage it?
[09:50] <kermiac> trinikrono: yup, that seems like the right way to go (although I'm def. not an expert in that package). FWIW asac set that bug to triaged over a year ago & somone (wrongly) changed it to confirmed
[09:52] <trinikrono> so you will put it back to triaged and  i will close it?
[09:55] <trinikrono> ouch and they say to use it on a wikipage
[09:55] <trinikrono> https://wiki.ubuntu.com/Fonts#Enabling%20Bitmapped%20Fonts
[10:07] <kermiac> trinikrono: "sudo dpkg-reconfigure fontconfig" (from the wiki page) worked for me
[10:08] <trinikrono> well apparently they pulled the -configure
[10:20] <trinikrono> kermiac: you still there, bug 539008 i think can wishlist
[10:20] <ubot2> Launchpad bug 539008 in fontconfig (Ubuntu) "Microsoft Sans Serif maps to Thai font even on european setups (affects: 2) (heat: 38)" [Undecided,New] https://launchpad.net/bugs/539008
[10:21] <trinikrono> or ask that they test in maverick
=== schmidtm_ is now known as schmidtm
=== BlackZ_ is now known as BlackZ
[10:57] <vish> xteejx: you had me confused for a sec there ;)
[10:57] <vish> xteejx: i usually close 3-4 bugs together :)
[10:58] <xteejx> vish: Ohhh right didn't realise thought you'd missed 1 :)
[11:31] <chilicuil> hi there, I've seen here: https://wiki.ubuntu.com/UbuntuBugDay/Planning that today is gonna be a hug day, I wonder what time is gonna be the meeting if any, what I need to do to help?, this will be my first first time
=== om26er_ is now known as om26er
=== BUGabundo is now known as BUGabundo_fewd
[13:20] <smallfoot-> why i get sata errors on my disk if my cd drive is plugged in?
=== yofel_ is now known as yofel
[14:13] <seb128> pedro_, hey
[14:13] <pedro_> bonjour seb128
[14:13] <seb128> pedro_, how are you?
[14:13] <seb128> pedro_, busy today? ;-)
[14:14] <seb128> pedro_, I've a mission for bugsquad ;-)
[14:14] <pedro_> seb128, like always ;-)
[14:14] <pedro_> seb128, sure, what's the mission? ;-)
[14:14]  * pedro_ listen
[14:14] <pedro_> reading works too
[14:15] <pedro_> morning kamusin
[14:15] <seb128> pedro_, so gst0.10-python has some 139 bugs registered
[14:15] <seb128> I noticed that yesterday and wait "no way so many people use that"
[14:15] <seb128> pedro_, so it seems checkbox files all the "sound is not working correctly" bug there for some reason
[14:16] <seb128> pedro_, could somebody try to figure what would be the right component for those bugs, it's not gst0.10-python in any case
[14:16] <seb128> pedro_, and maybe reassing all the current bugs to that component or something
[14:16] <seb128> pedro_, and make sure checkbox got updated to stop doing that?
[14:17] <pedro_> seb128, yeap I'll coordinate something to move those bugs from there and ping cr3 about the checkbox part
[14:17]  * pedro_ kicks cr3
[14:17] <seb128> thanks
[14:17] <kamusin> hey pedro_ :)
[14:17] <pedro_> thanks seb128
[14:19] <pedro_> kamusin, ready to squash some bugs on the bug day?
[14:23] <kamusin> always ready haha (go go go #chi)
[14:36] <genux> hi all, if someone going throught a bug from start to finish today ?
[14:36] <genux> so that I can follow what you are doing ?
=== BUGabundo_fewd is now known as BUGabundo
[15:49] <vish> pedro_: did the bugsquad/BC mailing list get the mail about the mentorship student pruning mail i sent a few hrs ago?
[15:49]  * vish seems to be having problem with mail
[15:50] <pedro_> vish, yes! thanks for the update ;-)
[15:50] <vish> pedro_: cool ,thanks..  files a bug in rt :)
[15:50] <vish> * /me
[15:51] <vish> i dont seem to be getting copies of the mails i send :/
[15:52] <pedro_> is your alias linked to a gmail address?
[15:52] <pedro_> i don't get any copy i send trough my gmail account
[15:52] <pedro_> seems its designed to be that way...
[15:52] <vish> pedro_: yeah , gmail.
[15:53] <pedro_> well could be the same
[15:53] <vish> hmm.. so not a bug
[15:53] <pedro_> yeah
[15:54] <pedro_> vish, there's maybe something to check/uncheck in the web preferences though
[15:55] <vish> pedro_: i checked that in the mailman mailing list prefs but still it doesnt work , and the mails to the lp mailing list [BC] should have worked.. seems gmail is doing something ;)
[15:56]  * vish checks gmail prefs , probably something hiding there
[15:56] <vish> pedro_: thanks for the confirmation, about gmail thingee..
[15:56] <pedro_> vish, if you find it  please let me know ;-)
[15:57] <vish> pedro_: sure thing
[15:57]  * vish  had asked nigelb and he scared me .. 
[15:57] <vish> nigelb: pff
=== BUGabundo is now known as BUGabundo_writin
=== BUGabundo_writin is now known as BUGabundoWriting
[16:11] <Pici> jpds: *poke*, got a question about old-releases.u.c
[16:13] <jpds> Hello.
[16:15] <Pici> jpds: Is it worth filing a but/rt ticket about old-releases' intrepid backports/proposed missing packages for i386 arch?
[16:15] <jpds> Pici: ŧ
[16:15] <jpds> Pici: Which packages is it missing for example?
[16:16] <Pici> jpds: All of them? There simply isn't a binary-i386 folder in (for example) http://old-releases.ubuntu.com/ubuntu/dists/intrepid-backports/universe/
[16:18] <jpds> Pici: Ports is there, the [now un-]supported intrepid archive is yet to be moved over.
[16:18] <Pici> jpds: Ah. Okay.
[16:35] <jpds> Pici: Can you try again? We've moved the x86 stuff across.
[16:36] <Pici> jpds: You didn't need to do it now... but it looks good at-a-glance to me.
[16:37] <jpds> Pici: Sooner is better than later™.
[16:37] <Pici> jpds: Thanks
[16:37] <jpds> [Though intrepid will sit on archive.u.c for a little longer]
=== deryck is now known as deryck[lunch]
[18:24] <psusi> bugs are not the place for help requests right?  so if someone has managed to mess up their system but otherwise does not really have a bug to report, should they be sent to the ubuntu forums for help and the bug report closed?
[18:24] <dutchie> perhaps there should be a bug against whatever allowed them to mess up their system ;)
[18:28] <psusi> I mean like if say, they filed a bug report against nethack because they were playing that when their system crashed, and now they can't boot or access the filesystem and are asking for help repairing the system to boot or at least recovering their data... that doesn't really belong in a bug report does it?
[18:30] <ddecator> psusi: if it's a support question, there is a "Covert to Question" link that can turn the report into a question on LP Answers
[18:31] <psusi> hrm.. maybe you could take a look at bug #598086 and see what I mean...
[18:31] <ubot2> Launchpad bug 598086 in dmraid (Ubuntu) "system stops booting after message JDB: barrier-based sync failed on md1-8 - disabling barriers ... wrong # of devices in RAID (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/598086
[18:32] <psusi> this doesn't actually have anything to do with the dmraid package...
[18:32] <EricJ> similar to a problem of mine, tho.
[18:35] <psusi> so you think I should convert it to a question?  but what is the question and what package?  since it doesn't really have anything to do with dmraid...
=== deryck[lunch] is now known as deryck
[19:23] <psusi> hrm... the help page on lp says that after 2 weeks of being in needs information state, questions are supposed to automatically expire, but that does not seem to be happening...
[19:24] <elopio> pedro_: are you available now?
[19:24] <pedro_> elopio, hey, yes ;-)
=== cyphermox_ is now known as cyphermox
=== BUGabundoWriting is now known as BUGabundo_Legend
=== BUGabundo_Legend is now known as BUGa_LegendSeker
[21:27] <htorque> hello, a "New" bug was fixed with an update - should i mark it "Fix Released" or "Invalid"?
[21:28] <BUGa_LegendSeker> you don't
[21:28] <BUGa_LegendSeker> LP should do it
[21:28] <BUGa_LegendSeker> if the package states the bug
[21:29] <htorque> no it doesn't, the bug is "New"/"Unconfirmed"
[21:30] <psusi> if it was fixed intentionally it will automatically be marked fix released.. if the user just finds that the problem does not occur with a new version, that is different
[21:33] <htorque> i _assume_ it was fixed due to an intentionally fixed other bug (a race condition - the bug(s) i'm talking about are SIGSEGVs)
[21:34] <BUGa_LegendSeker> https://bugs.edge.launchpad.net/ubuntu/+source/pavucontrol/+bug/598260
[21:34] <ubot2> Launchpad bug 598260 in pavucontrol (Ubuntu) "pavu control lost icon (affects: 1) (heat: 6)" [Undecided,New]
[21:34] <BUGa_LegendSeker> can anyone please confirm? thanks in advance
[21:56] <xteejx> Evening all