[13:15] <svij> balloons: irqbalance keeps crashing in the vm inside the cloud instance when I try to run the tests, even on utopic
[13:16] <balloons> that's no good
[13:16] <svij> that might be the issue because I'm booting the iso with qemu without kvm inside a xen/kvm instance, tested on ec2 and digitalocean, no idea why it worked before
[13:16] <balloons> so we may be back to square one on this heh
[13:17] <svij> so having proper hardware *might* be the better solution
[13:17] <svij> maybe DanChapman knows something, atleast he said also said something regarding the irqbalance crash
[13:17] <balloons> right, I remmeber
[13:17] <balloons> and you tried on DO and ec2?
[13:17] <svij> yep
[13:18] <svij> maybe I could try a VM with higher specs…
[13:18] <svij> but i doubt that would help, that were already dual-cores with 4gb ram
[13:21] <balloons> right. Seems clear this is pointing back to wanting real hw again
[13:21] <balloons> odd
[13:47] <gQuigs> did I mess something up in my testdrive or does the latest (20150811) ubuntu desktop image push you to a lock screen
[13:57] <balloons> a lock screen? what do you mean?
[13:57] <balloons> the greeter?
[13:57] <balloons> wxl, you about?
[14:17] <gQuigs> balloons: yup, the greeter comes up and I can't login (live cd test)
[14:45] <balloons> ahh.. heh, so the session crashes on load
[14:46] <balloons> if you can, nab some logs. We've had similar bugs in the past
[15:34] <gQuigs> hmm. I can't find any relevant logs
[15:40] <flocculant> balloons: well I am pleased that Ubuntu is now getting that boot to login on the livesession - yesterday it seemed to be just xubuntu
[15:44] <balloons> flocculant, I know you have experience with this, lol
[15:44] <balloons> any existing bug to point at?
[15:44]  * balloons didn't look
[15:54] <flocculant> couldn't find one
[15:55] <flocculant> obviously I looked back a while
[15:56] <balloons> flocculant, do you remember what logs where relevant last time?
[15:56] <balloons> perhaps Xorg.log?
[15:57] <flocculant> I did look in lightdm log last night - but we were waiting on an upload, so I stopped looking in order to wait
[15:59] <flocculant> will go back over xubuntu bug blueprint first
[15:59] <flocculant> or second, tea first
[16:16] <flocculant> balloons: not finding anything, nothing jumping out at me from logs either
[16:18] <balloons> hmm..
[16:19] <balloons> We should file a bug regardless if there isn't one. Did you file something gQuigs?
[16:19] <flocculant> tried to find in tracker defects
[16:19] <balloons> we can add logs later if needed
[16:23] <flocculant> balloons: bug 1445206 appears close
[16:27] <flocculant> balloons: yesterday one of my testers found it on hardware, so at least it's not just vm
[16:28] <balloons> knome, ping
[16:28] <balloons> flocculant, ahh.. so it's not just a vbox thing. that's good to confirm
[16:28] <flocculant> indeed :)
[16:29] <knome> balloons, pong
[16:30] <balloons> knome, so I see http://tracker.xubuntu.org exists now.
[16:30] <knome> yes
[16:30] <balloons> did you get everything you needed for that?
[16:30] <knome> in what sense?
[16:31] <balloons> knome, I wondered if you got all the data you need, etc. I was going to ask before if you planned on hosting it or not, but I see it's on xubuntu now
[16:31] <knome> aha
[16:32] <knome> well, it's still in development
[16:32] <knome> no data is pulled from the QA trackers (yet)
[16:38] <wxl> balloons: am now
[16:38] <balloons> wxl, o/. I was curious about the pending merges on ubuntu-manual-tests project
[16:39] <wxl> balloons: hey. yeah, i saw the email but haven't got back to it. yes, all that stuff should still be valid.
[16:39] <balloons> wxl, ok. Guess we had a busy spring and didn't get those updated in time for vivid. We can get them all merged now. I was curious if you still wanted to drag everything under LXDE that was related
[16:40] <wxl> balloons: yeah i kind of copied how xubuntu was doing things. i also think it's nice because it helps visually prioritize package testing.
[16:42] <gQuigs> balloons: I haven't filed anything yet..
[16:42] <gQuigs> flocculant: did that user report a bug?
[16:46] <flocculant> gQuigs: no - as I said we were waiting to make sure it wasn't just an issue with upload we needed
[17:40] <flocculant> gQuigs: cyphermox is having a look - maybe hangfire on reporting bug till we know more about what to report against
[17:44] <cyphermox> what kind of graphics card?
[17:44] <flocculant> not sure about *my* other tester, but was hardware, for me it'd be whatever vbox uses, not sure about gQuigs
[17:46] <flocculant> if you need - I can do a usb and boot here to hardware, that'll be nvidia
[17:46] <cyphermox> it's not important just yet
[17:47] <cyphermox> just making sure because one log mentions dri
[17:47] <gQuigs> cyphermox: I was using TestDrive
[17:47] <gQuigs> with KVM
[17:47] <cyphermox> ok
[17:47]  * cyphermox is zsync'ing the images
[18:08] <flocculant> cyphermox: those logs all came from my machine via vbox
[18:27] <cyphermox> ah, I think I see
[18:27] <cyphermox> could we have just started to build images with systemd as a user session manager thingy?
[18:32] <cyphermox> nah, it's probably not that
[19:01] <cyphermox> flocculant: this is lightdm, I'm looking into a fix
[19:03] <cyphermox> yep, got it, I think
[19:20] <flocculant> cyphermox: I did think it was probably lightdm
[19:21] <cyphermox> lightdm now expects an actual meaningful value instead of what we're handing it for autologin-session=
[19:21] <cyphermox> I'll "fix" that in a second