[08:50] <DanChapman> good morning
[08:50] <SaberX01> very early good morning 2:00am here :-)
[08:52] <DanChapman> SaberX01, Wow thats early! :-) I couldn't manage being up at that time
[08:55] <SaberX01> Holidays, .. this time of day si the only time it's quiet around here :-)
[15:28] <elfy> PaulW2U: when you do testcases - it's better for you not to worry about numbering them - we do that when we add them to the tracker system - that's where the numbers actually originatr
[15:29] <elfy> there is already a 1628 ;)
[15:30] <elfy> mmm - not in the branch though ...
[15:33] <elfy> there is now
[15:34] <elfy> PaulW2U: anyway - installing kubuntu to a vm - will deal with those testcases you've got mp for over the next day or so
[16:00] <PaulW2U> elfy: yeah, sorry about that. I missed that until I read the instructions a second time. it was my first attempt though :)
[16:01] <elfy> yep - you should have been about for my first attempt(s) poor old balloons and DanChapman :)
[16:01] <DanChapman> :-)
[16:01] <elfy> of course I blamed bzr for it all
[16:03] <PaulW2U> to a non-programmer it is a little confusing. more kde testcases to come once I know the three that I've done are ok
[16:03] <elfy> PaulW2U: I TOTALLY know where you coming from :)
[16:03] <phillw> I will probably get told off again, but there is a non-pae version of lubuntu 13.10 http://phillw.net/isos/non-pae/
[16:04] <elfy> just ask balloons or DanChapman about talking about autopilot to me ...
[16:05]  * DanChapman has always been impressed with elfy's attempts to 'try' and understand :-)
[16:05] <elfy> PaulW2U: only thing I would be thinking about now - while you can build these testcases and someone will merge them into the tracker - it'll be up to kubuntu qa to sort out the package tracker - at present there's not anywhere for the kubuntu ones to live
[16:06]  * elfy is always impressed at DanChapman's attempts to explain it :)
[16:06] <PaulW2U> elfy: oh, i see. am I wasting my time or do I need to contact someone?
[16:07] <elfy> well I don't know - I've not any idea what the kubuntu plans are - even if they want to do it - I'd ask before doing more
[16:08] <PaulW2U> ok, i just saw all the kde todo's and thought it would be a good place to start
[16:08] <elfy> yea
[16:10] <elfy> PaulW2U: chilcuil did a whole load of bugs and tagged them - I'd find out if kubuntu are going to do anything with them - and if not maybe mark the bugs as invalid or something
[16:11] <elfy> I'll hold off on merging them as well until you let me know there's a need for them - does that sound sensible?
[16:11] <PaulW2U> looking at packages.qa.ubuntu.com now - i see what you mean, no kubuntu, thanks for the heads up
[16:11] <PaulW2U> elfy: yes, thanks
[16:11] <elfy> that's ok - I thought I'd mention it :)
[20:13] <sergio-br2> hi, anyone?
[20:15] <Noskcaj> sergio-br2, always someone
[20:15] <sergio-br2> Noskcaj, how are you
[20:15] <Noskcaj> Pretty good. you?
[20:15] <sergio-br2> fine!
[20:16] <sergio-br2> i have some hardwares issues in trusty, and there is no testcase in laptop.qa
[20:17] <Noskcaj> You don't need a testcase to report a bug
[20:17] <sergio-br2> hum, yeah
[20:18] <sergio-br2> so... there is no need of testcases in laptop.qa?
[20:29] <Noskcaj> I think that got partly removed. And either way, file a bug first
[20:30] <sergio-br2> one problem is this: Bug #1263351
[20:32] <Noskcaj> Maybe try and get it fixed upstream?
[20:32] <sergio-br2> i think it is problem with the kernel, because there is a firmware problem. But i don't know how to assign it to upstream
[20:34] <TheLordOfTime> what do you mean "assign" it to upstream.
[20:35] <sergio-br2> hum, "subscribe" or link it with upstream, i don't know the correct word for it
[20:39] <TheLordOfTime> sergio-br2: okay, because "assign" means assigning someone to the bug, which isn't what you want to do, if you file an upstream bug and Ubuntu knows about the upstream tracker, it can link the two, if not, just post a link to the upstream bug as a comment, referencing that you've filed it upstream
[20:40] <TheLordOfTime> i think there's special kernel triage guidelines though, lemme double check that
[20:40] <TheLordOfTime> (this is why I don't touch kernel bugs)
[20:41] <TheLordOfTime> i was right, the kernel team has special triage procedures https://wiki.ubuntu.com/Kernel/BugTriage
[20:41] <TheLordOfTime> ultimately though if it's not working with a proprietary driver, then the proprietary driver providers are probably the ones fixing it
[20:42] <TheLordOfTime> (not to intrude on your thunder, Noskcaj, just my observations is all)
[20:42] <sergio-br2> hey, thanks
[20:43] <Noskcaj> TheLordOfTime, no problem. I'd looked away after saying "file a bug"
[20:43] <TheLordOfTime> Noskcaj: hehe
[20:44] <TheLordOfTime> i'm assuming since you've filed against linux, sergio-br2, that its a kernel / firmware / driver issue, so that's about all I can do to help ya, I make it a mission to avoid touching any bugs that have special triage guidelines :P
[20:45] <TheLordOfTime> ('tis why i work primarily in the server packages with my triage, they don't have super special guidelines in most cases)