[13:43] <balloons> Oi knome?
[13:47] <knome> just wanted to brag about the new features at http://tracker.xubuntu.org/#tab-details
[13:49] <balloons> I see hehe. You did that with what again?
[13:49] <knome> just php, js and jquery
[13:50] <knome> no external jquery libs
[14:14] <knome> flocculant, now you can also filter by multiple assignees/blueprints
[15:41] <flocculant> oh boo
[15:42] <flocculant> was expecting something about autotests with a ping in here :p
[15:43] <sak> Does ubuntu-unity use the lightdm display manager which is know as the login greeter?
[15:48] <flocculant> http://cdimage.ubuntu.com/daily-live/20150915/wily-desktop-amd64.manifest
[15:49] <sak> flocculant are you responding to me?
[15:49] <flocculant> yea - check the manifest for ubuntu
[15:52] <sak> Yup, it is
[16:25] <balloons> ping DalekSec
[16:25] <balloons> bah, sorry..
[16:25] <balloons> ping DanChapman
[16:30] <knome> hahah.
[17:19] <DanChapman> balloons: pong
[17:21] <sak> Most of the bugs that I have submitted on launchpad have not been looked at yet. These bugs go back to 15.04. I changed their status to incomplete. Yet, how do I know I am submitting bugs correctly if no one comments on them?
[17:22] <balloons> you changed there status to incomplete?
[17:22] <flocculant> hard to know the answer to that
[17:22] <flocculant> why did you change status?
[17:22] <balloons> if it's set to incomplete it's not going to be looked at; that incdicates something for the reporter to do
[17:22] <flocculant> ninja'd ... should learn to touchtype ...
[17:23]  * balloons keeps on with modified hunt and peck
[17:25] <flocculant> sak: well - second one I looked at - talks about a testcase, but is reported against shotwell
[17:26] <flocculant> so - is it a bug with shotwell or testcase?
[17:26] <flocculant> if it's testcase then the affects needs to change
[17:28] <flocculant> That's quite common - people report against testcase when it should be package foo and vice versa :)
[17:29] <flocculant> The only way to get further with New bugs is at least get someone to try and confirm it
[17:30] <flocculant> and finally - however much any of us would like all bugs to be looked at - it's not likely if only 1 person ever sees it
[17:31] <flocculant> sak: also by marking them as incomplete - if nothing happens within 60 days they'll expire :)
[17:34] <balloons> right.. marking them anything but new means it's been looked at
[17:34] <balloons> so really as the bug submitter, you shouldn't be setting status unless you are also working it
[17:39] <sak> I changed their status because they are old and not sure if they constitute as bugs
[17:40] <sak> flocculant, that bug is with the testcase
[17:43] <sak> understood ballons. If I am clear on this, a bug must be filed against the right package, more than one person must be experiencing the effect, and someone else has to take a look at it. Am I right so far
[17:45] <flocculant> it helps
[17:45] <flocculant> with testcases - report them with https://bugs.launchpad.net/ubuntu-manual-tests/+filebug
[17:46] <sak> Can I change what package the bug effects?
[17:46] <flocculant> you can
[17:46] <flocculant> though you can't with the shotwell one now - I've done that one :)
[17:47] <flocculant> if you go to bug 1493908
[17:47] <flocculant> just under the Affects is a solid arrow - click that :)
[17:48] <flocculant> I changed that from shotwell package to manual tests project
[17:48] <sak> Now, on my lp account, there are a list of bugs that have been submitted, half by me, but I don't see the new bugs pertaining to testcases that were submitted. Who sees that?
[17:49] <flocculant> I only see 1 you've reported lately
[17:49] <flocculant> the one I changed
[17:53] <sak> ok, yes I see the changes
[17:55] <flocculant> https://bugs.launchpad.net/~saqman2060/+reportedbugs
[17:55] <flocculant> that's bugs you reported - not many testcase ones :)
[17:57] <sak> ok, I see it now, and learned how to navigate lp much better.
[17:57] <flocculant> :)
[17:57] <sak> You guys are very responsive :-)
[17:57] <flocculant> people try :)
[17:58] <flocculant> vivid bugs are unlikely to get looked at unless they're present still and important
[17:58] <flocculant> security for example
[17:59] <flocculant> that's why I try and get things reported during a dev cycle - much more chance - though LTS is a bit different
[18:00] <sak> why is LTS different?
[18:02] <sak> that's what the number grade means. "6" means very low doesn't it?
[18:03] <knome> all new bugs start low
[18:06] <sak> will be back
[18:07] <flocculant> at 6 even :)
[18:12] <brendand> https://bugs.launchpad.net/+help-bugs/bug-heat.html
[18:13] <brendand> 6 because all bugs have to have at least 1 affected user (4 points) and 1 subscriber (2 points)