[03:58] <snap-l> Anyone know why I can't seem to get rhythmbox to crash properly?
[03:58] <snap-l> bug 235651
[03:58] <snap-l> I've enabled apport, but I'm not sure where I should be looking for the crash files
[04:14] <virtuald> /var/crash
[04:35] <snap-l> Nothing in there
[04:35] <snap-l> I think I have a known problem with apport from a gutsy to hardy upgrade.
[04:35] <snap-l> bug 122688
[04:36] <snap-l> Except I'm not getting the empties
[04:36] <snap-l> Just an empty /var/crash
[04:40] <Gralco_> hey guys
[05:06] <ruiboon> Hi. Can i get the to triage a bluetooth bug? Using a particular bluetooth dongle,2 applications that uses pybluez gives some error. however other bluetooth applications are fine. User tries another dongle, and all application works. Dmesg output does not seems to suggest anything. What should i do next?
[05:44] <Gralco> ruiboon you mean report and triage it?
[06:08] <ruiboon> Gralco: sorry that i wasnt clear. the bug was already reported and i was trying to triage it
[06:08] <Gralco> well then why not do it?
[06:19] <ruiboon> Gralco: i have ask for the rev info as stated in the wiki, but it does not seems to be useful
[06:20] <ruiboon> Gralco: and i am also not really sure on which package do i assign it to
[06:27] <Gralco> ruiboon are you in the ubuntu bug control team?
[06:28] <ruiboon> Gralco: nope
[06:28] <Gralco> I'm not, yet, unfortunately I don't have enough triaging experience yet
[06:29] <Gralco> ruiboon just triage as many bugs as you can for now and once you get a hang of it apply for ubuntu bug control team
[06:29] <ruiboon> Gralco: maybe you would like to look at the bug itself? bug 234015
[06:29] <Gralco> are you in bugsquad?
[06:29] <ruiboon> Gralco: yes
[06:30] <Gralco> you need to figure out what team to assign it too after you have confirm the bug
[06:31] <Gralco> you wont be able to change the importance until you are accepted to the team
[06:31] <Gralco> ruiboon, well i have to go to bed
[06:31] <ruiboon> Gralco: i am not sure if i can call it as confirmed as i dont think that the relevant info is present. however, i am also not sure what other info is needed
[06:31] <Gralco> night all
[06:31] <ruiboon> Gralco: thanks for your input and good nigh
[06:31] <ruiboon> Gralco: good night*
[06:32] <Gralco> if you think it should be confirmed then you should do that
[06:33] <Gralco> other wise tell the the blueprosimity maintainer to decide
[06:33] <Gralco> later...
[06:34] <ruiboon> gralco: thanks, i will try that idea
[08:23] <|DuReX|> https://bugs.launchpad.net/ubuntu/+bug/235889 plz look @ it :x
[09:37] <gnomefreak> bdmurray: there seems to be something wrong with Ubuntu-bugs mailing list. Its sending out mail to everyone stating that you joined and was made admin of the mailing list, this is something only the admins should get AFAIK
[09:45] <Hobbsee> gnomefreak: are you subscribed to the bugcontrol list, in the same place?
[09:45] <gnomefreak> i think so
[09:47] <Hobbsee> gnomefreak: they were the admins.
[09:47] <gnomefreak> oh
[09:47] <gnomefreak> thanks i didnt think to look since AFAIK a team shouldnt be an admin for another team
[09:57] <persia> gnomefreak: There are cases where that makes sense, but bugcontrol is an odd admin team.
[10:19] <jdenhaer> anyone knows how to use dazuko module on 2.6.24-17-generic kernels?
[10:19] <jdenhaer> I'm searching too long now, can't make it work
[12:06] <|DuReX|> https://bugs.launchpad.net/ubuntu/+bug/235889 plz look @ it :'(
[12:08] <persia> ﻿﻿|DuReX|: You may find https://wiki.ubuntu.com/KernelTeamBugPolicies useful in ensuring there is enough information for the kernel developers.
[12:11] <asac> err
[12:12] <asac> anyone can reproduce bug 231116 with adblock plus package installed?
[13:00] <Hobbsee> bug 231116
[13:00] <Hobbsee> bah
[13:08] <Hobbsee> asac: i can't reproduce that at all.
[13:40]  * thekorn also can't reproduce bug 231116
[15:08] <Susana> hello, i would like to speak to the person who is responsable for the triage guide
[15:08] <persia> Susana: It's a collaborative document.  Why do you ask?
[15:09] <Susana> am i allowed to object to some of its content
[15:09] <Susana> ?
[15:09] <persia> Susana: Sure.  What specifically?
[15:10] <Susana> the part about invalidating translation bugs
[15:10] <Susana> they may not be important to you, but theu are important to the translation teams
[15:10] <persia> Susana: Typically the translations can't be fixed in the packages directly (although there are a few exceptions).
[15:10] <Susana> you are marking them invalid and sending people to rosetta
[15:11] <persia> It's generally better to get them into Rosetta or Debian (or upstream).
[15:11] <Susana> rosetta only allows people to make suggestions
[15:11] <Susana> and the translation teams don't get warned about it
[15:11] <Susana> so bugs that are *real* go unnoticed
[15:11] <persia> Susana: Ah.  I understand.  Do you think the translation teams would rather be subscribed to those bugs, and process them directly?
[15:12] <Hobbsee> or assign them.
[15:12] <Susana> it is much better to subscribe the team yes
[15:12] <Susana> personally, i subscribe all the packages that are reallated to translations
[15:12] <Susana> but not every team does that
[15:13] <persia> Susana: I think the invalidation is a leftover from when there weren't enough translators to handle that.  I'd recommend sending a proposal for the change to ubuntu-bugsquad@lists.ubuntu.com for discussion (and maybe copying any relevant translation coordination list).
[15:13] <Susana> so warning translators about the bugs is only way you can make sure the bug will be fixed
[15:13] <persia> it's a fairly big change to make without discussion, but if the translation teams are up to chasing and closing them all, it would certainly be better to take advantage of the user input.
[15:14] <Susana> everytime i see a translation issue i subscribe its team and i can tell you that translators are usually very fast at fixing things once they know about the problem
[15:16] <Susana> i will send an email, thanks
[15:16] <persia> Susana: Thanks for raising this.  If there is a good mechanism to handle the translation bugs it will be better for both users and triagers to take advantage of it.
[15:28] <Gasten> Hello squad! I got this bug caused by a faulty power supply. What do you think I should do with it? #214707
[15:30] <Gasten> om/mailman/listinfo/ubuntu-bugsquad | File bugs at  https://launchpad.net/ubuntu/+filebuB[B[B[B[B
[15:30] <Gasten> sorry
[15:30] <Gasten> https://bugs.launchpad.net/bugs/214707
[15:34] <persia> Gasten: I'd call that Invalid, and leave a comment saying that it appears to have been a hardware fault, rather than a bug in the software.
[15:35] <persia> I'm guessing that the problem was that the DVD drive wasn't spinning at a reliable speed or something.
[15:37] <persia> brasero might do well to have a nice error for the user "Your hardware doesn't seem to work", but it's likely a rare enough case that the note that there was an error, and encouragement to look at the log is sufficient.
[15:38] <persia> If upstream has a good bugtracker, it might be worth forwarding there as wishlist, but I'm guessing there are more pressing demands for developer time than writing an exception handler for this.
[15:46] <Gasten> persia: yeah, that's what I was thinking. could you mark the bug as triaged?
[15:46] <persia> Gasten: You're sending it upstream?
[15:46] <Gasten> yeah
[15:47] <persia> Gasten: OK.  I've marked it Triaged/Wishlist.  Please add a comment detailing the problem just in case someone doesn't feel like reading through the entire brasero error log.
[15:48] <Gasten> yep
[15:48] <persia> Thanks.
[16:13] <ruiboon> Hi. Could i get some help in triaging this bluetooth bug? I am not sure if i can called it as invalid or leave it as incomplete. https://launchpad.net/bugs/234015
[16:14] <ruiboon> basically, 2 applications that uses pyblue does not work in scanning for bluetooth devices. however other application works. when user try other bluetooth dongle, all applications work
[16:15] <techno_freak> ruiboon, only the 3rd party apps do not work and everything that comes as a part of ubuntu works?
[16:16] <ruiboon> techno_freak: those that uses pybluez doesnt, others like sending files via obex works
[16:17] <techno_freak> ruiboon, ask him to check with something within ubuntu repos which uses pyblue, if they work then it's not our bug, if not then the bug might be valid on pyblue
[16:18] <techno_freak> ruiboon, may be even poking those two sourceforge projects might help him
[16:20] <ruiboon> techno_freak: blueproximity is in ubuntu repos, the other one is not.
[16:20] <ruiboon> techno_freak: to poke sf.net seems like a good idea. i will redirect him over there
[16:21] <ruiboon> techno_freak: thanks for your help
[16:21] <techno_freak> ruiboon, :) also check blueproximity bugs for something
[16:24] <ruiboon> techno_freak: i will do that. Thanks again (:
[16:25] <techno_freak> welcome :)
[16:38] <Prognatus> Hello everybody!  I'm new here and willing to help.  At the moment I'm reading how-to's for bug reporting, triaging and so forth, so I have much to learn about this system and Launchpad.
[16:39] <Prognatus> Else... I'm from Norway, and have coding experience - about 20 years in total, 5 of those with C and C++.
[16:39] <Iulian> Prognatus: Excellent, welcome!
[16:40] <Prognatus> Thank you, Iulian!  :)
[16:40] <Iulian> Prognatus: If you have any questions about anything feel free to ask here.
[16:41] <Prognatus> Thanks.  Many questions, but I'll spread them out one at a time when they come to me.
[16:42] <Iulian> Sure
[16:42] <Prognatus> One thing I've wondered about though, is what happens to bugs in Ubuntu versions that expires on support?  Like when Dapper soon will be retired.
[16:44] <Prognatus> If they're not confirmed in newer releases, will they just be forgotten/deleted?
[16:49] <Iulian> Prognatus: Well, some of them are fixed in newer Ubuntu versions. If they are not confirmed in newer releases I think they remain untouched.
[16:49] <Iulian> Prognatus: That's a good question. I have never thought about it.
[16:49] <Prognatus> Ok
[16:50] <Iulian> Prognatus: They remain untouched until someone knows how to fix the bug.
[16:52] <Iulian> Prognatus: It depends. If the reporter doesn't provide enough information in the bug report the status will be changed to Invalid after 30 days IIRC.
[16:52] <Prognatus> Ok.  I guess it's important then to triage them before they disappear from Launchpad lists.  Warty, Hoary and Breezy all lists with zero bugs now ...
[16:52] <Prognatus>  https://bugs.launchpad.net/ubuntu/breezy/+bugs
[16:52] <Prognatus> https://bugs.launchpad.net/ubuntu/hoary/+bugs
[16:53] <Prognatus> https://bugs.launchpad.net/ubuntu/warty/+bugs
[16:54] <Iulian> Prognatus: There are no open bugs in breezy, hoary and warty.
[16:58] <Prognatus> Ok.
[17:05] <persia> Prognatus: You might look at edgy, which recently lost support.  Dapper is still supported for a couple more years.
[17:05] <persia> feisty will be the next release to lose support.
[17:07] <persia> Anyway, I think those lists only track bugs that have a release task.  There are still bugs open from hoary that were never nominated for a release.  This might be true for warty, but I don't know of any (and this is more complicated because of the bugzilla->malone transition)
[17:25] <Prognatus> persia: Ok.  I found the support dates here: https://wiki.ubuntu.com/#head-9906e7f587421bb42c7095527b5e91d60890eaaa
[20:27] <mohbana> hi
[20:28] <mohbana> has anyone noticed recently that some images in firefox come out a bit blurry
[20:47] <mohbana> no ?
[21:30] <LimCore> hello
[21:30] <LimCore> krecordmydesktops fails to work on 8.04
[21:30] <LimCore> what can I do to  1) have it working for me     2) help others
[21:31] <LimCore> https://bugs.launchpad.net/ubuntu/+source/krecordmydesktop/+bug/235376
[21:31] <ubot3> Malone bug 235376 in krecordmydesktop "doesn't work - problems/hang while saving even after encode on the fly" [Undecided,New]
[22:28] <afflux> hi there
[22:50] <emgent> heya
[22:51] <dejv_ntb> hey