[00:23] <infinity> bdmurray: You still around?
[00:23] <infinity> bdmurray: If so, can you bump 14.04.1 to 14.04.2 in metarelease?
[00:58] <wxl> infinity: i'm about to head out in 30 mins or so. any chance of being done by then?
[00:58] <infinity> wxl: Just fiddling with the website, but should be releasing very shortly.
[01:00] <elfy> ohhh
[01:00] <elfy> sorry infinity - though the shout went out ... bad elfy :(
[01:00] <bdmurray> infinity: still need that metarelease change?
[01:01] <infinity> bdmurray: Yeah, unless I have access and don't know it.
[01:01] <infinity> bdmurray: But someone would need to point me at the branch to mangle.
[01:01] <bdmurray> infinity: I can do it
[01:01] <infinity> elfy: Eh, from an infra POV, it's all out, except for the ubuntu.com website and my announce email.
[01:02] <infinity> elfy: Nothing stopping flavours from announcing if they want to.
[01:02] <elfy> right - saw so much words - I just read the few I wanted to :)
[01:02] <elfy> yea - but I do like to wait for the nod - only polite :)
[01:09] <bdmurray> infinity: all done
[01:51] <rsalveti> stgraber: seems the system-image importer is commented out in nusakan
[01:52] <rsalveti> stgraber: was that on purpose?
[01:54] <stgraber> rsalveti: I don't know
[01:54] <stgraber> you should ask whoever commented it :)
[01:55] <rsalveti> stgraber: how to know that?
[01:55] <rsalveti> we got our possibly rtm image for ota out, but didn't show up in system-image yet (to be validate by QA), and just noticed it was commented out
[01:55] <stgraber> you can't really, just guess. ogra_ is usually a pretty safe bet :)
[01:56] <stgraber> or maybe slangasek knows
[01:57] <rsalveti> stgraber: right, guess will just run it now manually and see if we can import at least the current rtm image
[02:19] <ScottK> infinity: Now isn't it time for the "Hey - feature freeze" email?
[02:21]  * bluesabre managed to get everything xubuntu pushed before the email
[02:25] <infinity> ScottK: It is, I just haven't sent it.
[02:25] <ScottK> K.
[02:25] <infinity> ScottK: If you want to do the honors, be my guest, I'm eating dinner. ;)
[02:25] <ScottK> Wouldn't want you to get to comfortable and relaxed.
[02:25] <infinity> Heh.
[02:26] <ScottK> Let me see what I can whip up before a spouse or child appears.
[02:27] <ScottK> It's vivid vervet, right?
[02:27] <infinity> ScottK: Last I checked.
[02:30] <ScottK> Sent.
[02:34] <ScottK> infinity: It needs to be moderated.
[02:45] <infinity> ScottK: Done.
[02:45] <ScottK> Thanks.
[02:46] <infinity> ScottK: Those looked suspiciously like my words. :)
[02:46] <infinity> ScottK: Or I'm rubbing off on you.
[02:46] <ScottK> The similarity was non-random.
[02:46] <rbasak> I hope you used a Sender: header? :-)
[02:47] <slangasek> stgraber, rsalveti: sorry, that was my doing, there was some ubuntu-core s-i damage that I needed to fix and I forgot to re-enable it
[02:48] <slangasek> re-enabled now
[02:51] <infinity> Does anyone else ever get an uncontrollable urge to watch the Tunak Tunak Tun music video?
[02:51] <infinity> No?  Just me?
[02:51] <slangasek> never heard of it
[02:52] <infinity> slangasek: Really?  Did you not have the Internet in 1998?
[02:52] <slangasek> I did, but perhaps not the Canadian Internet
[03:10] <rsalveti> holy, that's old
[03:11] <rsalveti> that was everywhere
[03:11] <rsalveti> slangasek: thanks
[03:12] <rsalveti> still good though :-)
[03:15] <slangasek> I guess this was filmed on the set of DOOM II
[07:53] <ogra_> rsalveti, stgraber, i always notify this channel if i turn the importer off or on
[10:18] <cjwatson> auto-sync belatedly switched to dry-run
[14:02] <flexiondotorg> Would is be possible to try a build for Ubuntu MATE?
[14:02] <flexiondotorg> cyphermox, Has helped get the backend stuff integrated.
[14:02] <flexiondotorg> I'd like to see how far along it gets so I can fix things if required.
[14:56] <Mirv> would someone friendly accept the binnew simgear packages from the queue? I believe I'd have all openscenegraph 3.2.1 bits uploaded but simgear is needed to unlock the rest of the builds
[15:12] <caribou> Does the PlusOne maintenance team still exist ?
[16:35] <cyphermox> cjwatson: in case you're still around, could you kick off a mate build?
[16:36] <cyphermox> flexiondotorg: ^
[16:37] <cjwatson> cyphermox: done
[16:37] <cjwatson> failed immediately :)
[16:38] <cyphermox> awesome, thanks :)
[16:38] <cjwatson> ah, I know what we need, there's a production config branch
[16:38] <cjwatson> let me fix
[16:39] <cyphermox> could you tell me more? to share the wealth of knowledge and all of that even though I'm not on the release team ;)
[16:39] <cjwatson> should be building now
[16:39] <cyphermox> ok
[16:39] <cjwatson> well you can't see the branch without access to nusakan
[16:39] <cyphermox> oh ok
[16:39] <cjwatson> it has private data and such
[16:39] <cjwatson> it's mentioned in https://wiki.ubuntu.com/ReleaseTeam/CDImageSetup
[16:40] <bdmurray> Could somebody run the -proposed cleanup on the pending-sru report?
[16:40] <cjwatson> bdmurray: running
[16:40] <bdmurray> cjwatson: thanks, is there anything wrong with two factor auth and staging.launchpad?
[16:41] <cjwatson> bdmurray: what are you seeing?
[16:41] <cjwatson> you have to use a different 2fa setup for staging sso remember
[16:42] <bdmurray> oh, its been awhile since I've used staging
[16:42] <cjwatson> bdmurray: https://help.ubuntu.com/community/SSO/FAQs/2FA#Why_doesn.27t_my_2F_login_work_on_staging.3F
[16:44] <bdmurray> cjwatson: thanks
[17:29] <elfy> infinity: so ... our 32 bit images still get the fail in vbox, running it from kvm - it only passes because it just sits there waiting for *you* to choose between try or install at the first boot menu
[17:29] <elfy> if nothing else it would be good to have an idea of who we could actually talk to about it :)
[17:50] <bdmurray> slangasek: sru-remove tool mp at https://code.launchpad.net/~brian-murray/ubuntu-archive-tools/sru-remove/+merge/250492
[17:53] <infinity> elfy: Point me at the bugs, maybe I can at least sort out who's responsible. :P
[17:54] <elfy> bug 1423161
[17:54] <elfy> infinity: I did try with kvm :)
[17:54] <elfy> thanks though :)
[17:58] <infinity> elfy: Seems pretty unlikely to be a ubiquity bug if it only happens on one type of "hardware".
[18:00] <elfy> oh - I did report it syslinux too - hard to know what to report it against
[18:00] <elfy> bug 1423267
[18:01] <infinity> elfy: That seems even less likely, assuming you're talking about an X desktop. :)
[18:01] <elfy> http://iso.qa.ubuntu.com/qatracker
[18:02] <elfy> those bug reporting instructions are what we get :)
[18:02] <elfy> hard to know what to do
[18:02]  * infinity wonders what the "Xubuntu Core" product on the tracker is meant to be.
[18:03] <cyphermox> I wonder if that could be related to that "being unable to select OEM install" on some images bug that I've been looking at
[18:04] <infinity> cyphermox: Oh, if he's actually referring to gfxboot?  Maybe.
[18:04] <cyphermox> yes
[18:04] <infinity> elfy: Do you have a screenshot from a working system of the screen you think you're meant to be seeing? :P
[18:04] <infinity> cyphermox: See, I'm assuming it's the dialog in X that has try/install.
[18:04] <cyphermox> elfy: or a screenshot of the screen you're seeing when things are stuck
[18:04] <cyphermox> infinity: yeah
[18:05] <cyphermox> but ubiquity is *meant* to wait for you to click Try or Install when you've gone through the gfxboot timeout, AFAIK
[18:05] <infinity> cyphermox: Right, but it's also meant to display a pretty dialog explaining that.
[18:05] <infinity> Which it might not be.
[18:05] <cyphermox> yes
[18:05] <cyphermox> could be
[18:05] <infinity> But that would still not be a ubiquity bug if it's hardware-specific.
[18:06] <infinity> More likely X has partially exploded.
[18:06] <cyphermox> unity
[18:06] <infinity> And the window is there, but not so much with the visible.
[18:06] <cyphermox> oh wait
[18:06] <infinity> XFCE, no Unity.
[18:06] <cyphermox> yes, I realized that
[18:06] <Laney> There's no unity at that point in ubiquity anyhow
[18:07] <infinity> But xfce also does hardware compositing by default (just much, much, much less hardware taxing), so it could be an accelerated driver thing with the vbox drivers, or lack thereof, on the CD?
[18:07] <cyphermox> Laney: well, ubiquity-dm might be trying to start something in setting up the session and failing to do so
[18:07] <infinity> Laney: Oh, is that dialog pre-window-manager?  You're probably right.
[18:07] <cyphermox> we'll know exactly, or much better, with a screenshot
[18:07] <elfy> http://i.imgur.com/rDCyE0O.png
[18:08] <elfy> 64bit on the left :)
[18:08] <cyphermox> ah, ubiquity-dm perhaps.
[18:08] <infinity> Okay, that's the dialog I assumed you were talking about.
[18:08] <infinity> So, some very verbose printf-debugging of ubiquity-dm might show up what's happened.
[18:08] <cyphermox> I'm not sure exactly what starts when you go through that dialog
[18:08] <infinity> cyphermox: I'll leave that one with you. :)
[18:09] <elfy> thanks for looking :)
[18:09] <cyphermox> elfy: are we still talking trusty?
[18:09] <infinity> cyphermox: Given the full desktop is otherwise loaded, I'm skeptical about blaming X/drivers, so ubiquity itself might be having a sad.
[18:09] <elfy> no - this is vivid - those are both today's daily
[18:10] <infinity> cyphermox: This is vivid/i386
[18:10] <infinity> cyphermox: xubuntu.
[18:10] <cyphermox> good, I had hoped so
[18:10] <elfy> I do understand that vbox can be a pita
[18:11] <infinity> elfy: Stupid question, but I assume those yellow dots are part of the wallpaper, not rendering artifacts from the window shooting itself in the head? :P
[18:11] <elfy> yea - that wallpaper is how it should look :)
[18:11] <infinity> Kay.
[18:11] <infinity> Wallpaper that looks a lot like video tearing is kinda entertaining.
[18:11] <cyphermox> elfy: is there a ubiquity process?
[18:12] <cyphermox> it already set up the panel and wallpaper so it at least got through some piece of setting up the session
[18:13] <elfy> cyphermox: appears to be http://i.imgur.com/T2YgMde.png
[18:14] <cyphermox> thanks
[18:14] <infinity> Neat.
[18:15] <infinity> cyphermox: I'm having a really hard time seeing how this could be ubiquity's fault, but I think this is one of those "have to prove it's not us, so we can reassign to the real culprit with a vengeance" type bugs.
[18:15] <cyphermox> yeah
[18:15] <cyphermox> will probably need .xsession-errors at this point, and/or syslog
[18:16] <elfy> what is interesting is that yesterday 64bit gave the same result
[18:16] <cyphermox> I did install vbox here so I'll spin it real quick to see if I get the same thing
[18:17] <elfy> ok - I'm floating about - grub time in UK - and ravenous teenager
[18:22] <cyphermox> phablet_demo: hi Will!
[18:24] <cyphermox> how does one not get just garbage graphics in virtualbox again?
[18:25] <elfy> hostF1 then hostF2
[18:25] <elfy> usually right ctrl
[18:25] <cyphermox> I still get a screen of green lines and a mouse the size of my head
[18:25] <cyphermox> ok
[18:27] <cyphermox> ahh!
[18:27] <cyphermox> got the dialog though
[18:27] <cyphermox> elfy: was the vm set to 64bit and you ran the 32 bit image?
[18:29] <cyphermox> ah, got it, no dialog
[18:35] <elfy> cyphermox: nope and good :)
[18:35] <cyphermox> but also no useful logs
[18:35] <cyphermox> things look fine, nothing weird in ubiquity's logs
[18:36] <cyphermox> it says it's trying to use DISPLAY=:0 which is also right
[18:36] <elfy> I know last cycle there was one thing after another with vbox
[18:37] <cyphermox> elfy: I only got this when I used a 64-bit vm to run the 32-bit image though
[18:37] <elfy> infinity: and xubuntu core is a stripped down racing version of xubuntu installed from mini.iso
[18:37] <cyphermox> so I could try to start the same image on real hardware and see if it does something similar
[18:38] <elfy> cyphermox: I'll double check and build a new vm - but I don't think that's the issue
[18:38] <elfy> cyphermox: it does boot on hardware fine
[18:38] <cyphermox> eep, if I kill off the ubiquity process I get thrown into a proper session, which is good, but I see there are still some graphic issues -- lots of tearing around the pointer
[18:39] <infinity> elfy: Okay.  Just seems weird to list it as an ISO product, but as long as that doesn't break publishing scripts, whatever.
[18:40] <cyphermox> infinity: adding xubuntu core?
[18:40] <elfy> infinity: it's not new - was there last cycle
[18:41] <infinity> elfy: Really?  I guess I have a short memory.
[18:41] <infinity> elfy: Although, I don't see it on the Utopic Final milestone.
[18:41] <elfy> seemed the only way to get it on the tracker was like that - we just wanted it to chug along cycle
[18:41] <elfy> infinity: no - it just shows up on dailies
[18:42] <infinity> elfy: Check.
[18:42] <elfy> if that's wrong blame balloons :D
[18:42] <infinity> elfy: Nah, don't care, if it's working for everyone, I'll just ignore it.
[18:42] <elfy> it's something we're actively looking at - but it's a bit of a corner case
[18:43] <cyphermox> elfy: if you could, start the same cd to reproduce the issue but edit the command line (ie, you don't just let things time out), to add 'maybe-ubiquity debug-ubiquity', and then put /var/log/installer/debug and /var/log/installer/dm on whatever bug report you may have open about this
[18:43] <infinity> cyphermox: Confirmed your 32-on-32 works, 32-on-64 doesn't findings.
[18:43] <cyphermox> infinity: yay
[18:43] <infinity> cyphermox: For bonus points, on a Win32 installation of vbox (it's on my gaming desktop :P), so you can rule out host kernel weirdness.
[18:44] <elfy> cyphermox: ummm, I'll do that if you can give me a bigger clue :)
[18:44] <cyphermox> this makes it sound a little less critical to me, because if that fails and it works fine on hardware, I expect people bringing up VMs to more or less use the right bitsize for the image they try to run... not that it shouldn't be fixed anyway
[18:44] <elfy> or do you mean at grub?
[18:44] <elfy> cyphermox: I just built a new vm - double checked it was 32bit - same issue
[18:44] <cyphermox> elfy: well, at grub if you get grub, or when you get the splash for the cd, press a key to get the menu, then hit F6, ESC and type that before the -- at the end of the command line
[18:45] <cyphermox> elfy: ok
[18:45] <cyphermox> elfy: then it's even more worth your time trying this out
[18:45] <cyphermox> hmm.. I may have just gotten the same result
[18:45] <cyphermox> infinity: guess it's some race, 32-on-32 failed for me too
[18:46] <infinity> cyphermox: Well, that's actually more comfortin from a WTF perspective, but it does mean the bug is probably ours, not Oracle's. :P
[18:47] <cyphermox> heh
[18:47] <cyphermox> maybe I see something a little unusual here
[18:47] <cyphermox> elfy: you do have to switch VTs to not get garbage on screen, right?
[18:48] <elfy> sometimes - not always
[18:48] <elfy> unless I boot an Ubuntu vm - then always
[18:50] <cyphermox> right
[18:51] <cyphermox> ah, this definitely needs more testing. If I can get another case where the window does show\
[18:51] <cyphermox> infinity: did you flush your vm yet?
[18:51] <cyphermox> if you could DISPLAY=:0 xwininfo -name ubiquity that would be cool if you still have your vm running
[18:53] <cyphermox> ah, the window is definitely there, just off-screen
[18:53] <cyphermox> if only I could remember the key combo to move windows from the keyboard
[18:54] <elfy> cyphermox: added both to bug 1423161
[18:54] <elfy> back shortly
[18:54] <cyphermox> elfy: thanks
[18:56] <cyphermox> heh, if you just press up or down a bit it pops back up
[18:58] <infinity> cyphermox: Oh, so just a positioning issue?  Perhaps the driver is reporting the wrong screen size at just the wrong time before the desktop settles?
[18:59] <cyphermox> no, not a positioning issue
[18:59] <cyphermox> I just got the window to display from boot and the resulting xwininfo is the same
[18:59] <elfy> oh ...
[18:59] <cyphermox> so looks like it someone is hidden
[19:00] <cyphermox> it's right there in the middle of the screen, when it's not showing you can hit up and down to switch languages and it will drawn on the screen again
[19:00] <elfy> hah so changing where the cursor is - language and it shows up
[19:00] <cyphermox> yup
[19:02] <cyphermox> I'm kind of curious if it's not ** (xfdesktop:2205): CRITICAL **: xfdesktop_grid_is_free_position: assertion 'icon_view->priv->grid_layout != NULL' failed that is a hint as to why this is happening
[19:03] <cyphermox> nope, it's there on my "successful" run too
[19:05] <cyphermox> brb, I need to secure beverage, apparently we still need to boil water here
[19:52] <cyphermox> elfy: infinity: i may have a fix but it's a little hard to be certain just like this that I'm not ignoring some critical use case
[19:52] <cyphermox> but my wild guess is that in general when we run the installer we really want it to be visible, so I'm just making that explicit as it starts.
[19:54] <cyphermox> looks like it works but I don't always hit the bug anyway
[19:57] <infinity> cyphermox: I can't think of when we'd not want it to be visible in the frontends, at least.
[19:57] <infinity> cyphermox: Is this code GTK-specific?
[19:57] <infinity> cyphermox: If so, I'm pretty confident no one wants an invisible GTK ubiquity.
[19:57] <cyphermox> I'm putting it in the gtk_ui frontend only
[19:58] <cyphermox> yeah, but I'm still figthing this trying to be very sure the bug fixes it, and that I'm not just lucky.
[19:58] <cyphermox> *code fixes it
[19:59] <cyphermox> especially when I'm further complicating things by breaking the boot to edit files before ubiquity has a chance to start
[20:00] <infinity> cyphermox: Well, be a bit sciency about it.  Break the boot and *don't* edit files, and see if you can still hit the race reliably.
[20:00] <infinity> cyphermox: Then break and edit, and see if you can't.
[20:00] <cyphermox> I did
[20:00] <elfy> thanks for this :)
[20:00] <cyphermox> that's what I've been doing, so far haven't hit one case where I edited the file and the dialog didn't show
[20:01] <infinity> cyphermox: But I vaguely recall other gtk visibility issues (or, rather, the need to forcefully tell it YES I WANT A WINDOW YOU TWIT) in the past, so you're probably on the right track, just need to make sure you call it dead last after the UI is drawn, so it doesn't blink in and out of existence, I suspect.
[20:02] <cyphermox> hehe yeah ;)
[20:05] <cyphermox> flexiondotorg: btw, livefs build failed for mate, that needs to happen before it gets much CD done, I wonder if there isn't another package that is in the seed that hasn't made it in Ubuntu yet.
[20:06] <cyphermox> flexiondotorg: really it could be anything though -- https://launchpadlibrarian.net/198284153/buildlog_ubuntu_vivid_amd64_ubuntu-mate_BUILDING.txt.gz
[21:34] <cyphermox> infinity: could you please review mate-menu and mate-tweak source packages in the new queue? they should have been landed prior to feature freeze, leaf packages for a flavor we don't yet quite build, etc. ;)
[21:35] <cyphermox> actually, fairly critical packages for these, but still :)
[22:05] <infinity> cyphermox: Yeah, I'm not going to ask for a FFe for most MATE stuff, except when they have to touch packages shared with other flavours.
[23:03] <robru> infinity: you around? can you figure out what happened to telepathy-qt5? it's in the PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-025 and in the packagelist https://ci-train.ubuntu.com/job/ubuntu-landing-025-2-publish/22/artifact/packagelist_rsync_landing-025-vivid/*view*/ but it didn't even get to proposed while telepathy-ofono
[23:03] <robru> is already in vivid. also cicopy.log doesn't show any error.
[23:06] <infinity> robru: No idea, copy it again?
[23:07] <robru> infinity: oh, hm, the packagelist is invalid....
[23:08] <robru> sigh
[23:08] <robru> ok
[23:16] <bdmurray> infinity: is there something missing here? http://cdimage.ubuntu.com/ubuntu/releases/14.04.2/release/
[23:18] <infinity> bdmurray: I don't know, is there?
[23:19] <bdmurray> I only see amd64+mac not amd64 for 14.04.2
[23:19] <infinity> bdmurray: Are you maybe looking for http://releases.ubuntu.com/14.04.2/ ?
[23:20] <bdmurray> yeah, maybe