[06:04] <snadge> #200337
[06:05] <snadge> aka ubuntu hardy cant burn dvds ;)
[06:06] <snadge> normally pretty tolerant of bugs.. except this ones long standing, unresolved, and has cost me money in the form of coasters
[06:06] <techno_freak> bug #200337
[06:07] <snadge> the only remotely useful advise in the whole thread.. is that downgrading to gutsy works fine.. also an interesting suggestion to try the use_generic_ide option
[06:08] <snadge> which one person reported didnt work for them either.. i personally havn't tried it (doesnt seem like much of a fix), and got an I/O error about 25% way through burn myself
[06:11] <snadge> i want to help resolve this issue, but i obviously dont want to waste blank dvds
[06:15] <sbeattie> snadge: are you able to successfully burn dvds from other tools?
[06:15] <sbeattie> e.g. k3b?
[06:23] <snadge> i dont know, have been reluctant to try it sine the problem (from the bugreport) seems to affect all burning programs
[06:23] <snadge> sine/since
[06:23] <snadge> i suppose i could try doing a "pretend" burn
[06:24] <snadge> installing k3b now
[06:33] <snadge> this bug probably should've got more focus
[07:06] <snadge> so far k3b test burn is taking forever
[07:07] <snadge> @ approx 3x (was set to auto)
[07:07] <snadge> looks like its having trouble keeping the buffer full
[08:45] <bliZZardz> Hi, can someone correct me w.r.t Bug #242275 ?
[11:12] <bliZZardz> ﻿/join #ubuntu-bugs-message
[13:14] <LimCore> how to tell damn dpkg to not idiotically cut columns when displaying dpkg -l ?
[13:24] <james_w> LimCore: dpkg -l | cat
[13:24] <james_w> or COLUMNS=largenumber dpkg -l
[13:26] <LimCore> thanks
[13:26] <LimCore> is this a known bug?  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/242322
[13:28] <james_w> not sure, you may want to ask -mozillateam
[16:14] <bliZZardz> hi - would be this the right forum to ask for some help w.r.t a bug. I can see the fix(or the lack of it). need some help in structuring it
[16:25] <bliZZardz> w.r.t Bug #189515 - i see that this is present in the gcalcli code. But it looks like more of an enhancement than a bug.
[16:26] <bdmurray> bliZZardz: Okay
[16:27] <bliZZardz> bdmurray : any comments?
[16:28] <bdmurray> What do you mean by you can see the fix?
[16:29] <bliZZardz> it is present in the code as a comment - line 993 : "elif (opt == "--mon"): Usage() #calMonday = True # not ready yet...)"
[16:29] <bliZZardz> the usage of 'calMonday' across the script denotes that the author are planning to introduce it - hence it doesnt look like a 'bug'
[16:30] <bliZZardz> [http://code.google.com/p/gcalcli/source/browse/trunk/gcalcli]
[16:30] <bdmurray> It'd help to add some information like that to the bug and add which specific version of the package you found this in
[16:31] <bdmurray> Okay, it might not be a bug, rather a missing feature, but that is still fine to have in Launchpad.  Do you know if upstream has a bug trackign system?
[16:31] <bliZZardz> they are using code.google.com
[16:31] <bliZZardz> (am a n00b here,, hence am just learning the policies - and hence the questions here)
[16:32] <bdmurray> Does code.google.com have a bug tracking system though?
[16:32] <bliZZardz> yes
[16:32] <bdmurray> Maybe there is an existing bug regarding that this lack of functionality then.
[16:33] <bliZZardz> there is no existing bug in upstream - checked it. How do i forward it there?
[16:35] <bdmurray> bliZZardz: In general terms you would report the bug in the upstream bug tracking system and then add a 'bug watch' in launchpad to keep an eye on the upstream bug report.  This will update the launchpad bug with status information about the upstream bug.  I'm not certain if Launchpad can watch bugs at code.google.com though.
[16:35] <sectech> bliZZardz, if you are going to ask a triager a question in a bug please remember to change the status to incomplete?
[16:38] <bliZZardz> so i can comment and change the status to 'incomplete'. and i shall mention the issue# from google in the comment.
[16:40] <sectech> bliZZardz,  Sure...  It just helps when triaging issues to know if the bug has been touched or not...
[16:40] <bdmurray> sectech: I think it can be confirmed since the functionality is not there and no other information is needed.
[16:41] <bliZZardz> bdmurray, sectech : 'confirmed' or 'incomplete' ?
[16:43] <bdmurray> bliZZardz: confirmed
[16:44] <bliZZardz> ok
[16:45] <sectech> bdmurray,  I think I was referring to one of the other bugs he touched....
[16:45] <sectech> I'll go back and find it
[16:46] <sectech> Bug #242376
[16:46] <sectech> that was the one I was referring ot
[16:46] <sectech> err to
[16:46] <sectech> I'll see if I can reproduce the reporters problem in a VM
[16:48] <bliZZardz> sectech : are you looking into Bug #242376 ?
[16:49] <sectech> I can, unless you don't want me to....
[16:49] <bliZZardz> you can :)
[16:49] <sectech> It looks like a dup of bug #134323 though...
[16:49] <sectech> that bug is quite old though
[16:49] <sectech> and is still marked new at that...
[16:50] <bliZZardz> yea...Dup :)
[16:50] <ScottK> bdmurray or heno: Are either of you around?
[16:50] <sectech> bdmurray,  Since the original wasn't dealt with, should we leave the new bug open and deal with it?
[16:50] <heno> ScottK: I am
[16:51] <ScottK> heno: Since there was so much excitement about wiki page editing before, I want to bring something to your attention ...
[16:51] <ScottK> https://wiki.ubuntu.com/Bugs/Responses#head-246b9a0b2091d7aee70afd2b0579dbbc986eb51b
[16:51] <ScottK> This response should point to SRU, not to backports.
[16:51] <sectech> bliZZardz,  might as well mark it as a dup but put a comment in the original bug that this is still occuring
[16:52] <bliZZardz> sectech : k..will do. will look into the fix tomm.
[16:52] <ScottK> heno: As one of the people that approves backports, I will won't fix a backport request that fixes an SRU worthy bug.
[16:52] <ScottK> Backports is for features not fixes.
[16:53] <ScottK> heno: Can I edit that or would you rather?
[16:53] <bliZZardz> sectech : status changed to 'Invalid' in the new one?
[16:54] <sectech> bliZZardz, no mark it as a dup of the original one
[16:54] <heno> ScottK: sounds like a reasonable clarification; go ahead
[16:54] <sectech> brb
[16:54] <ScottK> heno: Thanks.
[16:54] <bliZZardz> so the original's status changes to??
[16:57] <bdmurray> bliZZardz: The one that is a duplicate should be invalid and the one with a duplicate should be confirmed
[16:57] <bliZZardz> ok
[16:57] <bdmurray> pedro_: are there logs from a recent traiging class you have given for https://wiki.ubuntu.com/BugSquad/KnowledgeBase
[16:58] <pedro_> bdmurray: yep, i'll update the page in a bit
[16:59] <bdmurray> pedro_: great, that particular class has a bit about bug assignment that was confusing
[17:00] <bliZZardz> bdmurray : thanks for the hints.. solved some bugs today :)
[17:01] <techno_freak> bdmurray, have a doubt, should we ask people reporting bugs in gutsy or feisty to check it in hardy, or should ask them to confirm it in intrepid?
[17:01] <bdmurray> bliZZardz: No problem, thanks for helping out!
[17:02] <bdmurray> techno_freak: Ideally Intrepid but w/o an alpha image it is harder
[17:02] <techno_freak> bdmurray, so we first check it with hardy, if they can reproduce then it needs to be confirmed with intrepid as well?
[17:02] <bliZZardz> bdmurray : got a quick Q, from the wiki i read that Ubunteros are newbies in the kingdom and they go on to become Members - right?
[17:04] <bdmurray> bliZZardz: ubunteros are people who have signed the code of conduct.  Ubuntu members have made a contribution to Ubuntu.
[17:05] <bdmurray> techno_freak: recreation with hardy is enough to confirm a bug
[17:06] <bliZZardz> bdmurray : what kind of contribution you mean there?? does Triaging,QA,packaging constitute members?
[17:06] <techno_freak> bdmurray, ok, got it. thanks :)
[17:19] <ScottK> heno: Updated https://wiki.ubuntu.com/Bugs/Responses?action=show#head-246b9a0b2091d7aee70afd2b0579dbbc986eb51b
[17:20] <heno> ScottK: looks good, thanks
[17:21] <ScottK> No problem.
[17:56] <bdmurray> mvo: I seem to recall and update-manager bug re ftp is bug 160166 related to that?
[19:00] <zul> how do you get an upstream bugtracker registered in launchpad/
[19:01] <bdmurray> zul: jcastro is the man there
[19:01] <zul> bdmurray: thanks
[19:17] <mvo> bdmurray: looking
[21:02] <thekorn> bdmurray, hi, I prepared a ibtrepid.merge-branch over the weekend,
[21:02] <thekorn> https://code.edge.launchpad.net/~bughelper-dev/python-launchpad-bugs/intrepid.merge
[21:02] <thekorn> I think I commited almost all pending patches
[21:02] <thekorn> It still needs some more polishing,
[21:03] <thekorn> but if you have some time for testing,
[21:03] <thekorn> or can use it for your scripts,
[21:03] <thekorn> this would be cool
[21:04] <bdmurray> thekorn: okay, I'll poke at it this week
[21:04] <thekorn> thanks alot