=== shuduo-afk is now known as shuduo
flocculantballoons: ping18:35
balloonsflocculant, yes?18:35
flocculantlumme - that was quick  - do you know where we stand with getting defect reports back?18:36
balloonsahh, defect reporting18:47
balloonsno one is working on it, so no, I've no idea18:47
balloonsIf it's enough of an issue, we do have the option of rolling back the changes18:47
balloonsflocculant, do you feel it's big enough to warrant that?18:51
flocculantballoons: well - we're just about to start looking at b118:52
balloonsmaybe it's an easy fix -- not sure. I just know folks are currently busy atm, so no one is actively working it18:53
balloonsso like I said, we're not completely without options18:53
flocculantso - 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 dupes18:53
flocculanton the other hand18:54
flocculantthere'll be no preconceptions for the b1 images18:54
flocculantnot sure I'd want to be going backwards with the changes we've got :)18:54
flocculantyea - that's where I am :)19:04
balloonsI probably shouldn't mention it, but it is likely possible to only back out the change that affected that page19:05
flocculantnot sure what other changes it affects19:08
flocculantif it's the losing stuff that's *old* then perhaps we should do so19:08
balloonsI was going to say, let me see.. But actually, this is a good option for you.19:09
balloonsGo find the commit that changed that page and back out that change. Then submit that as an MP to trunk.19:10
balloonsthink you can do that?19:10
flocculantnot in any sort of hurry - got bunch of stuff to deal with this evening19:10
flocculantcan look tomorrow19:11
balloonsjust thought I'd see if you might want to try as a learning exercise19:12
balloonsno rush till beta19:12
balloonsbut backing it out might be the way to do it, if a fix doesn't come19:13
flocculantyep - happy enough to be learning :D19:13
flocculantballoons: well - had a quick look - can't even work out how to see which commit in that list did the deal :D19:55
balloonsflocculant, yea, same on me mostly to not leave better commit messages19:55
balloonsbut still, find your bug report that changed the page, it has the linked MP, which tells you which commit19:55
flocculantdidn't think about that :p19:57
flocculantnope - not finding it that way - only bug halfway close is bug 1366581 and https://code.launchpad.net/~hjarrell555/ubuntu-qa-website/bug_1366581/+merge/28133420:15
ubot5bug 1366581 in Ubuntu QA Website "Testcase Report page enhancements" [Undecided,Fix released] https://launchpad.net/bugs/136658120:15
flocculantwhich is right at the beginning afair20:15
=== uaa is now known as Guest61494
=== Guest61494 is now known as damascene
balloonsso that mp then?20:24
flocculantI'm not sure20:25
flocculantballoons: it's the only one I can find with anything about a bug table in it20:28
balloonsthats what i was thinking it was20:29
balloonsits the only one touching that page20:29
balloonsbut we'll test it anyway20:29
wxlanyone seen bug 1547518?20:48
ubot5bug 1547518 in ubiquity (Ubuntu) "ubiquity crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.InvalidArgs: No such interface '/org/freedesktop/UPower'" [Medium,Confirmed] https://launchpad.net/bugs/154751820:48
flocculantwxl: I've seen report - but I've not seen it myself20:58
wxlflocculant: 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
flocculantcould be20:59
flocculantI check our images on hardware - but don't install reguarly21:00
flocculantthough this install needs clearing out - it's been limping along since October :D21:01
PaulW2Uwxl: just tested on my laptop - I can only install with the battery removed otherwise ubiquity crashes21:01
wxlPaulW2U: i386 or amd64?21:02
flocculantPaulW2U: thanks for that :)21:02
wxlPaulW2U: and is that with Ubuntu proper? (probably doesn't matter, but worth asking)21:02
PaulW2UNo, Xubuntu21:02
wxlwell it's not lubuntu so there's that XD21:03
wxlcould you confirm the bug and perhaps comment on it? would be appreciated21:03
PaulW2UOff to LP right now..21:03
wxlthank you PaulW2U :)21:03
flocculantseems like someone is assigned to that already21:07
=== damascene is now known as ahmed_sabir
=== ahmed_sabir is now known as damascene
flocculantwxl: have you noticed the 'terminal' in the install window not populating anymore?21:21
wxlhm i hadn't actually21:21
wxlusually i walk away and/or do something else flocculant :)21:21
* wxl doesn't have a current image to test :/21:22
wxlcan someone tell me where exactly the problem occurs? does it happen when selecting install within the live session? flocculant PaulW2U ?21:22
flocculantwxl:  yea I know what you mean - I just happened to notice today21:22
flocculantwxl: 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
PaulW2Uwxl: if you install from icon on desktop then ubiquity doesn't start as it crashes immediately21:23
PaulW2Uif you chose install from menu then you go to desktop with a crash error message21:24
wxlthx PaulW2U21:26
flocculantyep - thanks PaulW2U :)21:26
wxlbug 1547518 severely cleaned up thanks to everyone's help21:37
ubot5bug 1547518 in ubiquity (Ubuntu) "ubiquity crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.InvalidArgs: No such interface '/org/freedesktop/UPower'" [Critical,Confirmed] https://launchpad.net/bugs/154751821:37

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!