=== micahg_ is now known as micahg
[03:27] <smartboyhw> Hello any bug control people here?
[03:28]  * smartboyhw wonders if TheLordOfTime is here to help
=== emma_ is now known as em
=== emma_ is now known as em
=== em is now known as emma
[09:36] <gigix> hi guys, I can't get hugday tools to work on my quantal installation. I followed the instructions on the wiki, checked out the bazaar branch, run "hugday current --remember", but "hudgay list" raises a TypeError at me
[09:36] <gigix> am  I missing something ?
[09:56] <gigix> what's the appropriate behaviour towards bugs reported on versions of Ubuntu no longer supported such as Maverick or Natty ?
=== emma is now known as em
[13:54] <om26er> hugday close give me http://paste.ubuntu.com/1650936/
[13:54] <om26er> help ?
[13:55] <penguin42> hmm I think there is a single useful line in there 'You are not allowed to edit this page. '
=== rsalveti_ is now known as rsalveti
=== Ursinha_ is now known as Ursinha
[15:19] <LantzR> Hi I'm a rookie. Can someone double check Bug #1125275. I copied the head of the dist to show what I was running. Is that clear enough?
[15:19] <ubot2> Launchpad bug 1125275 in nautilus (Ubuntu) "Dropping a file into folder does a copy instead of a move" [Undecided,New] https://launchpad.net/bugs/1125275
[15:27] <jibel> LantzR, looks good even if I cannot reproduce the issue. The version of nautilus is missing, you can get it with: apt-cache policy nautilus
[15:28] <jibel> LantzR, for next reports, it's usually easier to use ubuntu-bug e.g ubuntu-bug nautilus
[15:28] <jibel> it will collect the right information for you
[15:29] <LantzR> jibel - I tried to use ubuntu-bug but it does not seen to be included in the distribution. I could not figure out what package to install either.
[15:29] <LantzR> err seem to be
[15:31] <LantzR> Oh sorry. The version matched the only version in roaring.
[15:32] <jibel> LantzR, the package that contains ubuntu-bug is apport, it is installed by default
[15:32] <jibel> or should be
[15:33] <LantzR> Ok... I'll try again. It tried 'which ubuntu-bug' and found nothing
[15:34] <LantzR> i did not try apport because there was no crash. Isn't there something special about apport being disabled in raring
[15:35] <LantzR> something about a new crash reporter
[15:38] <LantzR> jibel  I hit Alt. Then typed: 'ububtu-bug <ProcessID of the running nautilus>' then enter. Nothing happened. Then I tried to find it in the shell
[15:41] <jibel> LantzR, <alt> shows you the HUD, it's a quick access to application's menu
[15:41] <jibel> err, he left
[15:49] <fully_human> So, I'm a little confused with bug fixing. Who is a "triager?" Am I one or is that a specific team?
[15:53] <jibel> fully_human, a triager is a person who triages bug reports. It can be anyone https://wiki.ubuntu.com/BugSquad/GettingInvolved
[15:58] <fully_human> Ah, thank you.
[15:58] <fully_human> I read the wiki, but I was still fuzzy on the understanding.
[16:00] <jibel> yw
[16:02] <fully_human> *yw?
[16:03] <jibel> fully_human, you're welcome :)
[16:07] <LantzR> I went back and double checked. I did have apport , apport-cl1 and ubuntu-bug available. I'll guess typo re missing ubuntu-bug. which apport is null, did not try which apport-cli
[16:14] <fully_human> Okay, I'm new at this so I'd like to make sure I'm doing it right: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1090291
[16:14] <ubot2> Ubuntu bug 1090291 in totem (Ubuntu) "gdk threads safe issue when playing totem" [Undecided,New]
[16:14] <fully_human> I'm the comment at the bottom.
[16:19] <penguin42> fully_human: So there are two things about that report that makes it a little unusual; 1st it's quite old so it might be worth checking if it affects a newer version, 2ndly the reporter is quite technical - he's asking about a specific set of function calls/thread interactions
[16:19] <penguin42> oh, and 3rd it's using some codecs he isn't telling us about
[16:25] <fully_human> penguin42: I have experience with multi-threading, but yeah, it does seem a bit technical.
[16:26] <fully_human> I like how he gave technical details, though.
[16:26] <fully_human> So if it smells "fishy" I should probably leave it alone?
[16:27] <penguin42> fully_human: So I'd probably use the stock answer to ask him to check it on a newer version, but I'd also advise him that if he has a specific question about Totem's source to ask the totem dev list, it's not really the right thing to ask on a bug
[16:27] <fully_human> Okay, thank you.
[16:28] <penguin42> fully_human: I'd put a bug in for something where I new there was a line of code that was wrong would be ok, but not asking a question
[16:29] <penguin42> knew
=== yofel_ is now known as yofel