/srv/irclogs.ubuntu.com/2015/02/20/#ubuntu-release.txt

infinitybdmurray: You still around?00:23
infinitybdmurray: If so, can you bump 14.04.1 to 14.04.2 in metarelease?00:23
wxlinfinity: i'm about to head out in 30 mins or so. any chance of being done by then?00:58
infinitywxl: Just fiddling with the website, but should be releasing very shortly.00:58
elfyohhh01:00
elfysorry infinity - though the shout went out ... bad elfy :(01:00
bdmurrayinfinity: still need that metarelease change?01:00
infinitybdmurray: Yeah, unless I have access and don't know it.01:01
infinitybdmurray: But someone would need to point me at the branch to mangle.01:01
bdmurrayinfinity: I can do it01:01
infinityelfy: Eh, from an infra POV, it's all out, except for the ubuntu.com website and my announce email.01:01
infinityelfy: Nothing stopping flavours from announcing if they want to.01:02
elfyright - saw so much words - I just read the few I wanted to :)01:02
elfyyea - but I do like to wait for the nod - only polite :)01:02
bdmurrayinfinity: all done01:09
=== infinity changed the topic of #ubuntu-release to: Released: Trusty 14.04.2, Utopic 14.10, Vivid Alpha 2 | Archive: open | Vivid Release Coordination. Please don't upload things during freezes where you shouldn't, or be prepared to apologise to the release team | We accept payment in cash, check or beer | melior malum quod cognoscis
rsalvetistgraber: seems the system-image importer is commented out in nusakan01:51
rsalvetistgraber: was that on purpose?01:52
stgraberrsalveti: I don't know01:54
stgraberyou should ask whoever commented it :)01:54
rsalvetistgraber: how to know that?01:55
rsalvetiwe 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 out01:55
stgraberyou can't really, just guess. ogra_ is usually a pretty safe bet :)01:55
stgraberor maybe slangasek knows01:56
rsalvetistgraber: right, guess will just run it now manually and see if we can import at least the current rtm image01:57
ScottKinfinity: Now isn't it time for the "Hey - feature freeze" email?02:19
* bluesabre managed to get everything xubuntu pushed before the email02:21
infinityScottK: It is, I just haven't sent it.02:25
ScottKK.02:25
infinityScottK: If you want to do the honors, be my guest, I'm eating dinner. ;)02:25
ScottKWouldn't want you to get to comfortable and relaxed.02:25
infinityHeh.02:25
ScottKLet me see what I can whip up before a spouse or child appears.02:26
ScottKIt's vivid vervet, right?02:27
infinityScottK: Last I checked.02:27
ScottKSent.02:30
=== ScottK changed the topic of #ubuntu-release to: Released: Trusty 14.04.2, Utopic 14.10, Vivid Alpha 2 | Archive: Feature Freeze | Vivid Release Coordination. Please don't upload things during freezes where you shouldn't, or be prepared to apologise to the release team | We accept payment in cash, check or beer | melior malum quod cognoscis
ScottKinfinity: It needs to be moderated.02:34
infinityScottK: Done.02:45
ScottKThanks.02:45
infinityScottK: Those looked suspiciously like my words. :)02:46
infinityScottK: Or I'm rubbing off on you.02:46
ScottKThe similarity was non-random.02:46
rbasakI hope you used a Sender: header? :-)02:46
slangasekstgraber, 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 it02:47
slangasekre-enabled now02:48
infinityDoes anyone else ever get an uncontrollable urge to watch the Tunak Tunak Tun music video?02:51
infinityNo?  Just me?02:51
slangaseknever heard of it02:51
infinityslangasek: Really?  Did you not have the Internet in 1998?02:52
slangasekI did, but perhaps not the Canadian Internet02:52
rsalvetiholy, that's old03:10
rsalvetithat was everywhere03:11
rsalvetislangasek: thanks03:11
rsalvetistill good though :-)03:12
slangasekI guess this was filmed on the set of DOOM II03:15
ogra_rsalveti, stgraber, i always notify this channel if i turn the importer off or on07:53
cjwatsonauto-sync belatedly switched to dry-run10:18
=== beisner- is now known as beisner
=== peterm-ubuntu is now known as peter-lunch
=== pgraner-afk is now known as pgraner
flexiondotorgWould is be possible to try a build for Ubuntu MATE?14:02
flexiondotorgcyphermox, Has helped get the backend stuff integrated.14:02
flexiondotorgI'd like to see how far along it gets so I can fix things if required.14:02
Mirvwould 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 builds14:56
=== Guest35307 is now known as rcj
=== rcj is now known as Guest81339
caribouDoes the PlusOne maintenance team still exist ?15:12
=== ubuntu is now known as Guest76382
=== teward- is now known as teward
cyphermoxcjwatson: in case you're still around, could you kick off a mate build?16:35
cyphermoxflexiondotorg: ^16:36
cjwatsoncyphermox: done16:37
cjwatsonfailed immediately :)16:37
cyphermoxawesome, thanks :)16:38
cjwatsonah, I know what we need, there's a production config branch16:38
cjwatsonlet me fix16:38
cyphermoxcould 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
cjwatsonshould be building now16:39
cyphermoxok16:39
cjwatsonwell you can't see the branch without access to nusakan16:39
cyphermoxoh ok16:39
cjwatsonit has private data and such16:39
cjwatsonit's mentioned in https://wiki.ubuntu.com/ReleaseTeam/CDImageSetup16:39
bdmurrayCould somebody run the -proposed cleanup on the pending-sru report?16:40
cjwatsonbdmurray: running16:40
bdmurraycjwatson: thanks, is there anything wrong with two factor auth and staging.launchpad?16:40
cjwatsonbdmurray: what are you seeing?16:41
cjwatsonyou have to use a different 2fa setup for staging sso remember16:41
bdmurrayoh, its been awhile since I've used staging16:42
cjwatsonbdmurray: https://help.ubuntu.com/community/SSO/FAQs/2FA#Why_doesn.27t_my_2F_login_work_on_staging.3F16:42
bdmurraycjwatson: thanks16:44
elfyinfinity: 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 menu17:29
elfyif nothing else it would be good to have an idea of who we could actually talk to about it :)17:29
bdmurrayslangasek: sru-remove tool mp at https://code.launchpad.net/~brian-murray/ubuntu-archive-tools/sru-remove/+merge/25049217:50
infinityelfy: Point me at the bugs, maybe I can at least sort out who's responsible. :P17:53
elfybug 142316117:54
ubot93bug 1423161 in ubiquity (Ubuntu) "No try/install dialogue displayed" [High,Confirmed] https://launchpad.net/bugs/142316117:54
elfyinfinity: I did try with kvm :)17:54
elfythanks though :)17:54
infinityelfy: Seems pretty unlikely to be a ubiquity bug if it only happens on one type of "hardware".17:58
elfyoh - I did report it syslinux too - hard to know what to report it against18:00
elfybug 142326718:00
ubot93bug 1423267 in syslinux (Ubuntu) " No try/install dialogue displayed " [Undecided,New] https://launchpad.net/bugs/142326718:00
infinityelfy: That seems even less likely, assuming you're talking about an X desktop. :)18:01
elfyhttp://iso.qa.ubuntu.com/qatracker18:01
elfythose bug reporting instructions are what we get :)18:02
elfyhard to know what to do18:02
* infinity wonders what the "Xubuntu Core" product on the tracker is meant to be.18:02
cyphermoxI wonder if that could be related to that "being unable to select OEM install" on some images bug that I've been looking at18:03
infinitycyphermox: Oh, if he's actually referring to gfxboot?  Maybe.18:04
cyphermoxyes18:04
infinityelfy: Do you have a screenshot from a working system of the screen you think you're meant to be seeing? :P18:04
infinitycyphermox: See, I'm assuming it's the dialog in X that has try/install.18:04
cyphermoxelfy: or a screenshot of the screen you're seeing when things are stuck18:04
cyphermoxinfinity: yeah18:04
cyphermoxbut ubiquity is *meant* to wait for you to click Try or Install when you've gone through the gfxboot timeout, AFAIK18:05
infinitycyphermox: Right, but it's also meant to display a pretty dialog explaining that.18:05
infinityWhich it might not be.18:05
cyphermoxyes18:05
cyphermoxcould be18:05
infinityBut that would still not be a ubiquity bug if it's hardware-specific.18:05
infinityMore likely X has partially exploded.18:06
cyphermoxunity18:06
infinityAnd the window is there, but not so much with the visible.18:06
cyphermoxoh wait18:06
infinityXFCE, no Unity.18:06
cyphermoxyes, I realized that18:06
LaneyThere's no unity at that point in ubiquity anyhow18:06
infinityBut 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
cyphermoxLaney: well, ubiquity-dm might be trying to start something in setting up the session and failing to do so18:07
infinityLaney: Oh, is that dialog pre-window-manager?  You're probably right.18:07
cyphermoxwe'll know exactly, or much better, with a screenshot18:07
elfyhttp://i.imgur.com/rDCyE0O.png18:07
elfy64bit on the left :)18:08
cyphermoxah, ubiquity-dm perhaps.18:08
infinityOkay, that's the dialog I assumed you were talking about.18:08
infinitySo, some very verbose printf-debugging of ubiquity-dm might show up what's happened.18:08
cyphermoxI'm not sure exactly what starts when you go through that dialog18:08
infinitycyphermox: I'll leave that one with you. :)18:08
elfythanks for looking :)18:09
cyphermoxelfy: are we still talking trusty?18:09
infinitycyphermox: Given the full desktop is otherwise loaded, I'm skeptical about blaming X/drivers, so ubiquity itself might be having a sad.18:09
elfyno - this is vivid - those are both today's daily18:09
infinitycyphermox: This is vivid/i38618:10
infinitycyphermox: xubuntu.18:10
cyphermoxgood, I had hoped so18:10
elfyI do understand that vbox can be a pita18:10
infinityelfy: Stupid question, but I assume those yellow dots are part of the wallpaper, not rendering artifacts from the window shooting itself in the head? :P18:11
elfyyea - that wallpaper is how it should look :)18:11
infinityKay.18:11
infinityWallpaper that looks a lot like video tearing is kinda entertaining.18:11
cyphermoxelfy: is there a ubiquity process?18:11
cyphermoxit already set up the panel and wallpaper so it at least got through some piece of setting up the session18:12
elfycyphermox: appears to be http://i.imgur.com/T2YgMde.png18:13
cyphermoxthanks18:14
infinityNeat.18:14
infinitycyphermox: 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
cyphermoxyeah18:15
cyphermoxwill probably need .xsession-errors at this point, and/or syslog18:15
elfywhat is interesting is that yesterday 64bit gave the same result18:16
cyphermoxI did install vbox here so I'll spin it real quick to see if I get the same thing18:16
elfyok - I'm floating about - grub time in UK - and ravenous teenager18:17
cyphermoxphablet_demo: hi Will!18:22
cyphermoxhow does one not get just garbage graphics in virtualbox again?18:24
elfyhostF1 then hostF218:25
elfyusually right ctrl18:25
cyphermoxI still get a screen of green lines and a mouse the size of my head18:25
cyphermoxok18:25
cyphermoxahh!18:27
cyphermoxgot the dialog though18:27
cyphermoxelfy: was the vm set to 64bit and you ran the 32 bit image?18:27
=== pgraner is now known as pganer-afk
cyphermoxah, got it, no dialog18:29
elfycyphermox: nope and good :)18:35
cyphermoxbut also no useful logs18:35
cyphermoxthings look fine, nothing weird in ubiquity's logs18:35
cyphermoxit says it's trying to use DISPLAY=:0 which is also right18:36
elfyI know last cycle there was one thing after another with vbox18:36
cyphermoxelfy: I only got this when I used a 64-bit vm to run the 32-bit image though18:37
elfyinfinity: and xubuntu core is a stripped down racing version of xubuntu installed from mini.iso18:37
cyphermoxso I could try to start the same image on real hardware and see if it does something similar18:37
elfycyphermox: I'll double check and build a new vm - but I don't think that's the issue18:38
elfycyphermox: it does boot on hardware fine18:38
cyphermoxeep, 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 pointer18:38
infinityelfy: Okay.  Just seems weird to list it as an ISO product, but as long as that doesn't break publishing scripts, whatever.18:39
cyphermoxinfinity: adding xubuntu core?18:40
elfyinfinity: it's not new - was there last cycle18:40
infinityelfy: Really?  I guess I have a short memory.18:41
infinityelfy: Although, I don't see it on the Utopic Final milestone.18:41
elfyseemed the only way to get it on the tracker was like that - we just wanted it to chug along cycle18:41
elfyinfinity: no - it just shows up on dailies18:41
infinityelfy: Check.18:42
elfyif that's wrong blame balloons :D18:42
infinityelfy: Nah, don't care, if it's working for everyone, I'll just ignore it.18:42
elfyit's something we're actively looking at - but it's a bit of a corner case18:42
cyphermoxelfy: 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 this18:43
infinitycyphermox: Confirmed your 32-on-32 works, 32-on-64 doesn't findings.18:43
cyphermoxinfinity: yay18:43
infinitycyphermox: 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:43
elfycyphermox: ummm, I'll do that if you can give me a bigger clue :)18:44
cyphermoxthis 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 anyway18:44
elfyor do you mean at grub?18:44
elfycyphermox: I just built a new vm - double checked it was 32bit - same issue18:44
cyphermoxelfy: 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 line18:44
cyphermoxelfy: ok18:45
cyphermoxelfy: then it's even more worth your time trying this out18:45
cyphermoxhmm.. I may have just gotten the same result18:45
cyphermoxinfinity: guess it's some race, 32-on-32 failed for me too18:45
infinitycyphermox: Well, that's actually more comfortin from a WTF perspective, but it does mean the bug is probably ours, not Oracle's. :P18:46
cyphermoxheh18:47
cyphermoxmaybe I see something a little unusual here18:47
cyphermoxelfy: you do have to switch VTs to not get garbage on screen, right?18:47
elfysometimes - not always18:48
elfyunless I boot an Ubuntu vm - then always18:48
cyphermoxright18:50
cyphermoxah, this definitely needs more testing. If I can get another case where the window does show\18:51
cyphermoxinfinity: did you flush your vm yet?18:51
cyphermoxif you could DISPLAY=:0 xwininfo -name ubiquity that would be cool if you still have your vm running18:51
cyphermoxah, the window is definitely there, just off-screen18:53
cyphermoxif only I could remember the key combo to move windows from the keyboard18:53
elfycyphermox: added both to bug 142316118:54
ubot93bug 1423161 in ubiquity (Ubuntu) "No try/install dialogue displayed" [High,Confirmed] https://launchpad.net/bugs/142316118:54
elfyback shortly18:54
cyphermoxelfy: thanks18:54
cyphermoxheh, if you just press up or down a bit it pops back up18:56
infinitycyphermox: 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:58
cyphermoxno, not a positioning issue18:59
cyphermoxI just got the window to display from boot and the resulting xwininfo is the same18:59
elfyoh ...18:59
cyphermoxso looks like it someone is hidden18:59
cyphermoxit'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 again19:00
elfyhah so changing where the cursor is - language and it shows up19:00
cyphermoxyup19:00
cyphermoxI'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 happening19:02
cyphermoxnope, it's there on my "successful" run too19:03
cyphermoxbrb, I need to secure beverage, apparently we still need to boil water here19:05
=== pganer-afk is now known as pgraner
cyphermoxelfy: 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 case19:52
cyphermoxbut 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:52
cyphermoxlooks like it works but I don't always hit the bug anyway19:54
infinitycyphermox: I can't think of when we'd not want it to be visible in the frontends, at least.19:57
infinitycyphermox: Is this code GTK-specific?19:57
infinitycyphermox: If so, I'm pretty confident no one wants an invisible GTK ubiquity.19:57
cyphermoxI'm putting it in the gtk_ui frontend only19:57
cyphermoxyeah, 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 it19:58
cyphermoxespecially when I'm further complicating things by breaking the boot to edit files before ubiquity has a chance to start19:59
infinitycyphermox: 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
infinitycyphermox: Then break and edit, and see if you can't.20:00
cyphermoxI did20:00
elfythanks for this :)20:00
cyphermoxthat's what I've been doing, so far haven't hit one case where I edited the file and the dialog didn't show20:00
infinitycyphermox: 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:01
cyphermoxhehe yeah ;)20:02
cyphermoxflexiondotorg: 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:05
cyphermoxflexiondotorg: really it could be anything though -- https://launchpadlibrarian.net/198284153/buildlog_ubuntu_vivid_amd64_ubuntu-mate_BUILDING.txt.gz20:06
cyphermoxinfinity: 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:34
cyphermoxactually, fairly critical packages for these, but still :)21:35
infinitycyphermox: 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.22:05
robruinfinity: 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-ofono23:03
robruis already in vivid. also cicopy.log doesn't show any error.23:03
infinityrobru: No idea, copy it again?23:06
robruinfinity: oh, hm, the packagelist is invalid....23:07
robrusigh23:08
robruok23:08
bdmurrayinfinity: is there something missing here? http://cdimage.ubuntu.com/ubuntu/releases/14.04.2/release/23:16
infinitybdmurray: I don't know, is there?23:18
bdmurrayI only see amd64+mac not amd64 for 14.04.223:19
infinitybdmurray: Are you maybe looking for http://releases.ubuntu.com/14.04.2/ ?23:19
bdmurrayyeah, maybe23:20

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