[18:35] <flocculant> balloons: ping
[18:35] <balloons> flocculant, yes?
[18:36] <flocculant> lumme - that was quick  - do you know where we stand with getting defect reports back?
[18:47] <balloons> ahh, defect reporting
[18:47] <balloons> no one is working on it, so no, I've no idea
[18:47] <balloons> If it's enough of an issue, we do have the option of rolling back the changes
[18:51] <balloons> flocculant, do you feel it's big enough to warrant that?
[18:52] <flocculant> balloons: well - we're just about to start looking at b1
[18:53] <balloons> maybe it's an easy fix -- not sure. I just know folks are currently busy atm, so no one is actively working it
[18:53] <flocculant> yea
[18:53] <balloons> so like I said, we're not completely without options
[18:53] <flocculant> so - if the test pages showed more than just reported for that milestone - example the live session page showed bugs seen on all xenial live sessions there's some hope of seeing dupes
[18:54] <flocculant> on the other hand
[18:54] <flocculant> there'll be no preconceptions for the b1 images
[18:54] <flocculant> not sure I'd want to be going backwards with the changes we've got :)
[19:02] <balloons> mmm
[19:04] <flocculant> yea - that's where I am :)
[19:05] <balloons> I probably shouldn't mention it, but it is likely possible to only back out the change that affected that page
[19:07] <flocculant> mmm
[19:08] <flocculant> not sure what other changes it affects
[19:08] <flocculant> if it's the losing stuff that's *old* then perhaps we should do so
[19:09] <balloons> I was going to say, let me see.. But actually, this is a good option for you.
[19:10] <balloons> Go find the commit that changed that page and back out that change. Then submit that as an MP to trunk.
[19:10] <balloons> think you can do that?
[19:10] <flocculant> not in any sort of hurry - got bunch of stuff to deal with this evening
[19:11] <flocculant> can look tomorrow
[19:12] <balloons> right
[19:12] <balloons> just thought I'd see if you might want to try as a learning exercise
[19:12] <balloons> no rush till beta
[19:13] <balloons> but backing it out might be the way to do it, if a fix doesn't come
[19:13] <flocculant> yep - happy enough to be learning :D
[19:55] <flocculant> balloons: well - had a quick look - can't even work out how to see which commit in that list did the deal :D
[19:55] <balloons> flocculant, yea, same on me mostly to not leave better commit messages
[19:55] <balloons> but still, find your bug report that changed the page, it has the linked MP, which tells you which commit
[19:57] <flocculant> didn't think about that :p
[20:15] <flocculant> nope - not finding it that way - only bug halfway close is bug 1366581 and https://code.launchpad.net/~hjarrell555/ubuntu-qa-website/bug_1366581/+merge/281334
[20:15] <flocculant> which is right at the beginning afair
[20:24] <balloons> so that mp then?
[20:25] <flocculant> I'm not sure
[20:28] <flocculant> balloons: it's the only one I can find with anything about a bug table in it
[20:29] <balloons> thats what i was thinking it was
[20:29] <balloons> its the only one touching that page
[20:29] <balloons> but we'll test it anyway
[20:48] <wxl> anyone seen bug 1547518?
[20:58] <flocculant> wxl: I've seen report - but I've not seen it myself
[20:59] <wxl> flocculant: my guess is that it's only affecting real hardware and real hardware with batteries. i'm trying to get that confirmed as we speak, but be aware. always glad SOMEONE is doing hardware testing.
[20:59] <flocculant> could be
[21:00] <flocculant> I check our images on hardware - but don't install reguarly
[21:01] <wxl> right
[21:01] <flocculant> though this install needs clearing out - it's been limping along since October :D
[21:01] <PaulW2U> wxl: just tested on my laptop - I can only install with the battery removed otherwise ubiquity crashes
[21:02] <wxl> PaulW2U: i386 or amd64?
[21:02] <flocculant> PaulW2U: thanks for that :)
[21:02] <PaulW2U> amd64
[21:02] <wxl> PaulW2U: and is that with Ubuntu proper? (probably doesn't matter, but worth asking)
[21:02] <PaulW2U> No, Xubuntu
[21:03] <wxl> k
[21:03] <wxl> well it's not lubuntu so there's that XD
[21:03] <wxl> could you confirm the bug and perhaps comment on it? would be appreciated
[21:03] <PaulW2U> Off to LP right now..
[21:03] <wxl> thank you PaulW2U :)
[21:07] <flocculant> seems like someone is assigned to that already
[21:21] <flocculant> wxl: have you noticed the 'terminal' in the install window not populating anymore?
[21:21] <wxl> hm i hadn't actually
[21:21] <wxl> usually i walk away and/or do something else flocculant :)
[21:22]  * wxl doesn't have a current image to test :/
[21:22] <wxl> can someone tell me where exactly the problem occurs? does it happen when selecting install within the live session? flocculant PaulW2U ?
[21:22] <flocculant> wxl:  yea I know what you mean - I just happened to notice today
[21:23] <flocculant> wxl: not doing hardware today - definitely won't be doing so with anything with a battery - but I CAN confirm it's not affecting vbox ;)
[21:23] <PaulW2U> wxl: if you install from icon on desktop then ubiquity doesn't start as it crashes immediately
[21:24] <PaulW2U> if you chose install from menu then you go to desktop with a crash error message
[21:26] <wxl> thx PaulW2U
[21:26] <flocculant> yep - thanks PaulW2U :)
[21:37] <wxl> bug 1547518 severely cleaned up thanks to everyone's help