[00:01] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Bionic Final] has been updated (20180425.1)
[00:04] <tsimonq2> slangasek: Knock yourself out.
[00:05] <tsimonq2> And did you spot the bug or not? ;)
[00:07] <sil2100> What bug?
[00:09] <slangasek> tsimonq2: I mean, I've spotted the bug but I don't have a good fix for it.  The issue is that SUPPORTED_SEEDS = ["all"] which encompasses everything and trumps the NON_LTS_SEEDS
[00:18] <slangasek> tsimonq2: I think I might try reordering the list and special-casing 'all'
[00:18] <tsimonq2> slangasek: Thanks.
[00:19] <tsimonq2> (just got home and I'm packing for my flight tomorrow)
[00:41] <slangasek> tsimonq2: https://code.launchpad.net/~vorlon/ubuntu-archive-publishing/lubuntu-next-support-fixup/+merge/344358 untested
[00:46] <sil2100> mwhudson: hey! Can you help with testing the bionic subiquity images?
[00:46] <mwhudson> sil2100: sure, although in some sense i'm a very bad person to test them
[00:47] <mwhudson> sil2100: http://iso.qa.ubuntu.com/qatracker/milestones/389/builds/171072/testcases ?
[00:47] <mwhudson> uh http://iso.qa.ubuntu.com/qatracker/milestones/389/builds/171072/downloads has the wrong link
[00:48] <sil2100> Oh
[00:48] <sil2100> Let me try fixing that
[00:48] <mwhudson> bionic-live-amd64.iso.zsync
[00:48] <mwhudson> s/live/live-server/ i think
[00:49]  * sil2100 fixes that
[00:50] <slangasek> infinity: https://code.launchpad.net/~vorlon/ubuntu-archive-publishing/lubuntu-next-support-fixup/+merge/344358 is an untested stab at the lubuntu support metadata.  I don't see a trivial way to test this
[00:52] <sil2100> mwhudson: should be fixed
[00:53] <mwhudson> sil2100: looks better thanks
[01:09] <sil2100> Ok, I go take a few hours or sleep, but I'll start off earlier to help out with testing
[01:09] <sil2100> o/
[01:25] <mwhudson> oh phew the installed system boot was just a bit slow for some reason in this test
[02:05] <bashfulrobot> Tick tick tick. (Exciting)
[02:08] <sforshee> slangasek: no it's tjaalton you want for linux-oem
[03:35] -queuebot:#ubuntu-release- Unapproved: java-atk-wrapper (bionic-proposed/main) [0.33.3-20 => 0.33.3-20ubuntu0.1] (core)
[03:36] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Bionic Final] has been updated (20180426)
[03:36] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Bionic Final] has been updated (20180426)
[03:41] <jbicha> ^ um, the iso cronjob isn't still on, is it?
[03:46] <jbicha> slangasek: ping ^ since you might still be around
[03:46] <slangasek> it was turned off well before; just checked and it's off. someone must have manually requested that rebuild
[03:46] <slangasek> despite it being a no-op
[03:47] <slangasek> handsome_feng: ^^ was that you?
[03:47] <jbicha> yeah, I diffed the manifest's and they were the same
[03:47] <slangasek> were there test results already reported from the previous build?  I can axe it from the iso tracker
[03:48] <handsome_feng> slangasek: You mean rebuild the iso?
[03:49] <slangasek> handsome_feng: yes
[03:50] <handsome_feng> slangasek: It's zhangchao in our team, we found some thing wrong in the iso, so we rebuild it
[03:50] <jbicha> handsome_feng: could you be more specific about what you think was wrong?
[03:51] <slangasek> handsome_feng: ok but you rebuilt it against an archive that has not changed
[03:53] <jbicha> sorry to change the topic but I'm going to bed…
[03:53] <handsome_feng> We found that there are some permissions related errors in the x86_64 live system, we thought it maybe someting wrong when build the iso
[03:54] <slangasek> handsome_feng: what permissions where?  let us help you debug this, please
[03:54] <jbicha> handsome_feng: I think there are some concerns about Ubuntu Kylin's request to offer 5 years of support for this LTS so please discuss that here too
[03:55] <jbicha> good night all
[03:56] <handsome_feng> jbicha: good night
[04:09] <handsome_feng> slangasek: https://paste.ubuntu.com/p/x9cwtjBGGh/
[04:15] <slangasek> handsome_feng: when these dconf errors happen, can you please show the uid of the at-spi-bus-launcher process (e.g.: 'ps awxu | grep 3948') and the permissions on /run/user/999/ and /run/user/999/dconf (if it exists)?
[04:16] <doko> crossbuild-essential-amd64/amd64 unsatisfiable Depends: gcc-x86-64-linux-gnu (>= 7.3)
[04:16] <slangasek> handsome_feng: also: what is the effect of these permission failures?
[04:16] <doko> is this only checked on amd64? I mean, this was true before for arm64 and ppc64el on these archs as well
[04:17] <slangasek> doko: that package only exists on !amd64
[04:18] <slangasek> so do you intend for the amd64 package to pull in a foreign-arch foo-to-x86 compiler?
[04:18] <handsome_feng> slangasek: the effect is that the peony, ukui-panel, ukui-menu launch failed
[04:18] <slangasek> doko: or, it's an arch: all package; do you intend this only to be installed on !amd64?
[04:19] <doko> no. but as I said, that was already the case with crossbuild-essential-arm64/arm64
[04:19] <doko> yes, the latter
[04:19] <slangasek> doko: right - so it's possible the dependencies of arch: all packages are only enforced on amd64 (this is somewhat configurable in britney, I don't remember if that's the current value).  We can consider overriding this
[04:20] <slangasek> handsome_feng: when did this last work?
[04:20] <doko> ahh, ok. so maybe no need to make it Arch:any
[04:21] <handsome_feng> slangasek: the daily 0421
[04:24] <handsome_feng> we tested it in daily 0421. And it's ok.
[04:27] <handsome_feng> slangasek: https://paste.ubuntu.com/p/3JNzF5m4V8/
[04:29] <handsome_feng> slangasek: and this error only happend in x86_64, the i386 works fine in live system.
[04:29] <slangasek> handsome_feng: ok.  can you also test the 20180425 image to see if it happens there?  that will help us better bisect the delta between the images
[04:30] <slangasek> 109 packages changed between 20180421 and 20180426 so that will take some time to dig through
[04:32] <slangasek> handsome_feng: ok, so something has pre-created the /sur/user/999/dconf/user file as root.  not good..
[04:33] <handsome_feng> slangasek: OK, we will test it ASAP, but it will take some time to download the iso
[04:34] <slangasek> handsome_feng: yes, understood.  I will keep digging into the changesets in the meantime.  Also, the squashfs from the 20180424 build is still available from launchpad; if 20180425 is broken we should try to download that and manually add it to an ISO for testing
[04:34] <slangasek> handsome_feng: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/bionic/ubuntukylin/+build/130378
[04:35] <handsome_feng> slangasek: Thanks
[04:41] <tjaalton> slangasek: dunno what's the criteria to unblock (never done that before) but the tests that had been run looked green so it's unblocked now
[04:44] <slangasek> tjaalton: ok, and un-frozen as well now
[04:59] <tjaalton> great
[05:11] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Bionic Final] has been marked as ready
[05:11] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Bionic Final] has been marked as ready
[05:22] <handsome_feng> slangasek: 20180425 has the same problem
[05:22] <slangasek> ok, at least that tells us which side the problem is on
[05:23] <slangasek> handsome_feng: how do I reproduce this locally?  with the 'try' or 'install' option?
[05:23] <handsome_feng> slangasek: with try
[05:25] <handsome_feng> This only occurs in live system, if we install the system directly, all goes fine.
[05:26] <slangasek> handsome_feng: ok.  I went to 'try' with 20180426 and I didn't see the problem in /run/user/999/dconf
[05:26] <slangasek> this is with 20180426 amd64
[05:26] <handsome_feng> slangasek: OK , we will try that now
[05:30] <doko> please accept gcc-snapshot
[05:31] <slangasek> doko: I might leave it there for a little bit if that's ok, so I have something to trigger archive regeneration for the lubuntu cleanup I'm working on
[05:33] <doko> ok
[05:49] <handsome_feng> slangasek: we test the 20180426, and it also has the same problem..
[05:50] <slangasek> handsome_feng: ok.  I am also testing 20180425.1 now to see if I can reproduce the problem here
[06:00] <slangasek> infinity1, tsimonq2: alright, I've wrapped my head around this code now and have good output now - 62 packages having their support term lowered.  Pushing.
[06:01] <slangasek> handsome_feng: I cannot reproduce the problem on 20180425.1.  Can you give me any more guidance on steps to reproduce this?
[06:05] <tsimonq2> slangasek: ack, thabks.
[06:05] <tsimonq2> *thanks
[06:09] <sil2100> handsome_feng: did you fill in a bug for it already?
[06:10] <slangasek> sil2100: good morning
[06:12] <handsome_feng> slangasek: We've burn the 20180426 iso again. The bug disappears.
[06:12] <slangasek> hmm
[06:13] <slangasek> handsome_feng: do you think the previous burn didn't get done correctly?  or do you think that we have a race condition in the boot?
[06:14] <handsome_feng> Maybe the previous burn was wrong. We will test 20180425.1 again to confirm the problem.
[06:15] <slangasek> handsome_feng: I would suggest also trying 20180426 several times to be sure the problem is really gone
[06:15] <handsome_feng> slangasek: OK, We will do it
[06:17] <sil2100> slangasek: morning o/
[06:17] <sil2100> phew
[06:19] <sil2100> slangasek: any blockers reported in the meantime?
[06:20] <handsome_feng> sil2100:Good morning! and we didn't fill a bug for it, we just found this problem when we test the iso this morning
[06:22] <slangasek> sil2100: none that I know of
[06:22] -queuebot:#ubuntu-release- Unapproved: python-pip (bionic-proposed/universe) [9.0.1-2 => 9.0.1-2.1] (no packageset)
[06:23] -queuebot:#ubuntu-release- Unapproved: accepted python-pip [source] (bionic-proposed) [9.0.1-2.1]
[06:36] <sil2100> infinity1: ubuntu-studio looks ok for both amd64 and i386
[06:37] -queuebot:#ubuntu-release- Unapproved: yapf (bionic-proposed/universe) [0.20.1-1 => 0.20.1-1ubuntu1] (no packageset)
[06:38] -queuebot:#ubuntu-release- Unapproved: accepted yapf [source] (bionic-proposed) [0.20.1-1ubuntu1]
[06:39] -queuebot:#ubuntu-release- Unapproved: pywinrm (bionic-proposed/universe) [0.0.3-1 => 0.3.0-1ubuntu1] (no packageset)
[06:40] -queuebot:#ubuntu-release- Unapproved: accepted pywinrm [source] (bionic-proposed) [0.3.0-1ubuntu1]
[06:43] <sil2100> mwhudson: I'll give subiquity a quick spin as well, so that you don't have to feel that your bias affected the test results ;)
[06:44] <sil2100> slangasek: do you know if it's still ok to process package removals?
[06:45] <slangasek> sil2100: sure
[06:45] <slangasek> sil2100: I mean, if you remove the package and somebody disagrees, there will be sadness because there's no time for it to be readded
[06:45] -queuebot:#ubuntu-release- Unapproved: pyroma (bionic-proposed/universe) [2.0.2-1 => 2.0.2-1ubuntu1] (no packageset)
[06:46] -queuebot:#ubuntu-release- Unapproved: accepted pyroma [source] (bionic-proposed) [2.0.2-1ubuntu1]
[06:48] -queuebot:#ubuntu-release- New sync: python-requests-ntlm (bionic-proposed/primary) [1.1.0-1]
[06:50] <sil2100> xnox: the fallback casper message on exit is nice, but I must say I find it sometimes confusing
[06:52] <sil2100> xnox: maybe 'confusing' being the wrong term, but since I see it everytime before plymouth kicks in, it's confusing as at one time the user is told to just reboot and then suddenly "nope, just press enter to do that"
[06:57] -queuebot:#ubuntu-release- Unapproved: woo (bionic-proposed/universe) [1.0+dfsg1-2 => 1.0+dfsg1-2ubuntu1] (no packageset)
[06:58] -queuebot:#ubuntu-release- Unapproved: accepted woo [source] (bionic-proposed) [1.0+dfsg1-2ubuntu1]
[06:59] <Mirv> it seems no-one updated slideshow translations, can someone find out what needs to be fixed/documented where for the process? https://code.launchpad.net/~ubiquity-slideshow/ubiquity-slideshow-ubuntu/html
[07:01] <Mirv> I've tested Finnish and French, the second (snap) and last slides are untranslated due to string changes during the cycle
[07:02] <Mirv> (the middle string on the last slide is translated though)
[07:03] -queuebot:#ubuntu-release- New: accepted python-requests-ntlm [sync] (bionic-proposed) [1.1.0-1]
[07:03] <Mirv> it's documented here https://wiki.ubuntu.com/NonLanguagePackTranslationDeadline but maybe some process document needs to be updated as well
[07:05] -queuebot:#ubuntu-release- Unapproved: capstone (bionic-proposed/universe) [3.0.4-3 => 3.0.4-5] (no packageset) (sync)
[07:05] -queuebot:#ubuntu-release- Unapproved: accepted capstone [sync] (bionic-proposed) [3.0.4-5]
[07:09] <fossfreedom> anybody got quick access to an ISO to boot? - clicking quit from ubiquity doesnt launch into the live session - appears to hang (standard bios boot)
[07:11] -queuebot:#ubuntu-release- New binary: python-ntlm-auth [amd64] (bionic-proposed/none) [1.1.0-1] (no packageset)
[07:12] -queuebot:#ubuntu-release- New: accepted python-ntlm-auth [amd64] (bionic-proposed) [1.1.0-1]
[07:12] <Mirv> filed bug #1767048
[07:12] <ubot5`> bug 1767048 in ubiquity-slideshow-ubuntu (Ubuntu) "Slideshow translations were not updated for 18.04 LTS" [Undecided,New] https://launchpad.net/bugs/1767048
[07:12] <acheronuk> fossfreedom: xubuntu? or all?
[07:12] <jibel> fossfreedom, where do you press "quit" and which flavour?
[07:15] <Mirv> fossfreedom: correct, clicking Quit from the keyboard selection menu does not seem to do anything
[07:15] <Mirv> (Ubuntu main flavor for me)
[07:15] <Mirv> it just hangs and becomes unresponsive
[07:16] <sil2100> Mirv: hm, so we had an upload of the slideshow before release, but it didn't seem to include new translations
[07:16] <sil2100> I guess that's what hid the issue
[07:16] <Mirv> sil2100: right, it may have confused someone following the process that "oh, that was uploaded"
[07:18] <sil2100> That might have been my responsibility, ouch
[07:18] <fossfreedom> acheronuk, I'm on Ubuntu Budgie - thanks for the confirmation Mirv
[07:19] <Mirv> sil2100: well it's not the first time, and can be fixed for .1, but it's good to get the process bullet proof for updating the nonlangpack translations for release
[07:19] <acheronuk> I dunno if KDE front end even has that option there. certainly never noticed
[07:31] <sil2100> Ok, switching to the office for a short while
[07:32] <sil2100> brb
[07:36] <doko> are python3-networkx or python-networkx on any image?
[07:40] <fossfreedom> Thoughts on this - three times this morning I've tried to boot into a live session on UB and I'm getting this https://imgur.com/a/NwCJRt6
[07:42] <jibel> that's the same error handsome_feng mentioned earlier
[07:43]  * fossfreedom scrolling back
[07:43] -queuebot:#ubuntu-release- Unapproved: python-networkx (bionic-proposed/main) [1.11-1ubuntu1 => 1.11-1ubuntu2] (ubuntu-server)
[07:43] <jibel> fossfreedom, https://paste.ubuntu.com/p/x9cwtjBGGh/
[07:44] <fossfreedom> yep -same issue
[07:45] <jibel> Laney, ^^ any thoughts? same error on 2 different flavours
[07:45] <jibel> fossfreedom, which build of which flavour ?
[07:45] <fossfreedom> 64bit Ubuntu Budgie
[07:45] <doko> Laney: s390x autopkg testers unhappy (unknown versions everywhere)
[07:47] <jibel> fossfreedom, what is the build number?
[07:47] <jibel> 201804??
[07:48] <sil2100> jibel, fossfreedom: which bug is this about?
[07:51] <jibel> sil2100, "unable to create file '/run/user/999/dconf/user': Permission denied.  dconf will not work properly" when at-spi-dbus-bus is activated
[07:51] <jibel> I don't think any bug has been filed
[07:51] <jibel> I didn't see any in the backscroll
[07:54] <doko> is it already possible to upload to -proposed?
[07:57] <infinity1> Was it ever not?
[07:58] <doko> can't remember
[07:59] <sil2100> jibel: what are the steps to reproduce that?
[07:59] <sil2100> I guess I'm missing some backscroll
[07:59] <apw> doko, we always upload to -proposed all cycle, via the redirect for 'bionic' to -proposed
[08:00] <doko> apw: well, my question is, if I already can queue up -proposed uploads
[08:01] <apw> doko, as long as things are prepped as SRUs i believe they are fine to upload
[08:02] <apw> doko, though i would not think we want anything major in there in case we have to rebuild anything
[08:02] <doko> ok
[08:02] <apw> infinity, ^ that make sense ?
[08:03] <jibel> sil2100, I don't know. I didn't reproduce it myself but 2 testers on 2 different flavours reported it?.
[08:03] <jibel> -?
[08:05] <jibel> fossfreedom, can you report a bug please and attach the journal?
[08:06] <jibel> also describe the steps to reproduce  the problem if you can do it reliably
[08:14] <acheronuk> if this the no free space thing again, or something else?
[08:18] <handsome_feng> slangasek: I found this problem also occurs in Ubuntu, see https://paste.ubuntu.com/p/sZykyz5BVg/
[08:19] <jibel> handsome_feng, how do you reproduce it?
[08:19] <jibel> can you reproduce it in a VM or only hardware?
[08:19] <handsome_feng> jibel: Just burner the iso and then go into live system
[08:20] <handsome_feng> jibel: I found that is only occurred in Dell computer.
[08:20] <handsome_feng> And in the vm, all works fine
[08:21] <jibel> yeah but fossfreedom did it in vbox apparently
[08:21] <sil2100> hmmmmm
[08:21] <handsome_feng> jibel: emmm, It's wired..
[08:22] <jibel> handsome_feng, can you report a bug in LP please?
[08:23] <jibel> it'll be easier to track the status than on IRC
[08:23] <handsome_feng> jibel, OK, I will do it now
[08:23] <jibel> thanks
[08:28] <acheronuk> In latest ubuntu iso in virtualbox, I click 'try' and punts me to gdm login screen instead of straight into live session? is the intended?
[08:29] <jibel> no it means that the shell failed to start
[08:30] <jibel> you'll find more info in the journal
[08:30] <handsome_feng> jibel: LP: #1767067
[08:30] <ubot5`> Launchpad bug 1767067 in Ubuntu "[Live]Wrong Permission in live mode." [Undecided,New] https://launchpad.net/bugs/1767067
[08:30] <acheronuk> and if I click live session user, the 1st time seems to crash and push me back to gdm. 2nd try logs me in to live user
[08:31] <handsome_feng> And feel free to edit it
[08:32] <acheronuk> jibel: https://i.imgur.com/Hx7YJGI.png
[08:33] <jibel> acheronuk, yeah same bug than handsome_feng
[08:35] <fossfreedom_> sil2100: sorry - dropped out of IRC - on mobile at the moment - this bug is about trying to launch into a live session.  When I tried earlier it was failing 50% of the time.  Basically left at the login screen.  Cannot launch into the session
[08:37] <fossfreedom_> It is intermittent. sometimes the live session launches - sometimes it doesn't.  Nothing obvious as to why
[08:37] <jibel> okay, I reproduced it
[08:37] <fossfreedom_> Never seen this before until last nights respin
[08:40] <willcooke> I saw it during the day yesterday
[08:40] <willcooke> (but thought it was just me)
[08:46] <jibel> handsome_feng, when did you first see this problem? with which build?
[08:46] <jibel> willcooke, did you ever see it before?
[08:47] <willcooke> jibel, Not sure if we're talking about the same thing.  I saw the live image booting to a login screen instead of a logged in session during the day yesterday, and I /think/ Tuesday evening
[08:47] <handsome_feng> jibel: We test 20180421, and it works fine
[08:49] <seb128> handsome_feng, did you get any imagine in between those days? like on monday 23 or 24?
[08:49] <jibel> willcooke, that would be the symptom but without the log it cannot be confirmed.
[08:49]  * willcooke checks his trash
[08:50] <handsome_feng> seb128: no...I just got the 20180425
[08:50] <handsome_feng> I found if I manually select "try but not install" , all goes fine!
[08:51] <seb128> handsome_feng, jibel, in what mode is the issue happening exactly?
[08:51] <sil2100> jibel: were you able to reproduce it finally? Is this random?
[08:51] <handsome_feng> live mode
[08:52] <seb128> handsome_feng, but you just said that if you select "try" it goes fine?
[08:52] <handsome_feng> I can reproduce, If  I manually select "try but not install" , all goes fine, and if I wait until the windows shows, the problem occurs
[08:52] <seb128> isn't try = live session?
[08:53] <jibel> seb128, just boot, then in ubiquity-dm select 'try ubuntu'
[08:53] <seb128> jibel, it happens only through that codepath? picking the live session from syslinux works?
[08:53] <jibel> seb128, yes
[08:54] <seb128> jibel, what flavor(s) are we talking about?
[08:54] <jibel> seb128, ubuntu, budgie and kylin
[08:54] <seb128> oh, ubuntu as well?
[08:54] <jibel> yes
[08:54] <handsome_feng> wait until the windows show and then chose try
[08:54] <seb128> *fun*
[08:54] <seb128> jibel, do you know on what iso it started?
[08:54] <seb128> we had ubuntu isos in between monday and today
[08:54] <jibel> no, I've 24 here, I'll try it
[08:54] <seb128> thx
[08:55] <seb128> that sucks, looks like a release blocker issue?
[08:56] <LocutusOfBorg> question: can I sru virtualbox or sync it? I guess the former, right?
[08:56] <acheronuk> FFS I just tried again to video capture what it does, and it didn't happen
[08:56] <seb128> Laney, are you guys in London poking at it?
[08:56] <jibel> seb128, and you see the bug only on BIOS machine because on UEFI you don't start ubiqutiy-dm
[08:58] <handsome_feng> 1. when start, hit the arrow keys, choose "try Ubuntu but not install" -> works fine.   2. Wait until the windows show and then choose the "try ubuntu" -> failed.
[08:58] <sil2100> jibel, handsome_feng: I was testing kylin i386 on my VM and it worked correctly
[08:58] <sil2100> jibel, handsome_feng: just now re-tested with clicking 'try ubuntu' and everything works
[08:58] <handsome_feng> sil2100: Yeah, I also test it in vm, and works fine
[09:00] <jibel> I have the bug in a VM and fossfreedom too
[09:00] <acheronuk> urgh. randomly hard to reproduce! fun
[09:00] <seb128> jibel, I'm testing
[09:00] <sil2100> jibel: are you able to reproduce it on a VM? Or you're on the real hardware?
[09:00] <jibel> sounds racy
[09:00] <jibel> sil2100, yes in qemu
[09:00] <jibel> other in vbox
[09:00] <sil2100> Or maybe it's because I'm testing the i386 image
[09:01] <jibel> the platform is unrelated
[09:01] <jibel> the flavour too
[09:02] <seb128> I just tried on an amd64 iso, didn't get the issue
[09:03] <sil2100> I wonder when this started
[09:04] <seb128> if I had to guess I would say this week when we started fixing ubiquity use of gsettings, that uncovered issue with code that never worked properly
[09:04] <Laney> seb128: a bit, but please do too
[09:05] <seb128> Laney, do you have any clue so far? I didn't manage to reproduce yet :/
[09:05] <Laney> no didn't make it happen
[09:05] <seb128> I guess something in ubiquity-dm triggers a gsettings write with the worng user/env
[09:05] <seb128> but I've not idea what
[09:11] -queuebot:#ubuntu-release- Unapproved: python-redis (bionic-proposed/main) [2.10.6-2 => 2.10.6-2ubuntu1] (ubuntu-server)
[09:19] <willcooke> Just to update the channel.... I consider this a release blocker.  Release team in London are trying to reproduce it right now
[09:20] <willcooke> I've let JamieBennett know that this is a problem
[09:20] <seb128> willcooke, thx for the update, difficult to follow for those who are not in London
[09:20] <willcooke> I'll relay messages
[09:20] <seb128> thx
[09:21]  * didrocks doesn't succeed in reproducing :/
[09:21] <didrocks> and looking at the code, I don't see anymore obvious guilty path
[09:21]  * seb128 neither
[09:22] <jibel> seb128, no failure with 24 and 50% of the boot are failing with 25.1
[09:23] <didrocks> yeah, that was the day we fixed the a11y… correct?
[09:23] <seb128> jibel, can you boot to -maybe, go to a tty and look at the permission of the /run ... file which is listed in the error?
[09:23] <jibel> willcooke, to reproduce just boot 25.1 in qemu and select "try ubuntu", retry until it fails
[09:23] <seb128> didrocks, that's the day we fixed the session reboot
[09:23] <seb128> jibel, are we talking about the "login fails, you get gdm" or about the dconf errors?
[09:24] <jibel> willcooke, I kept a VM running with the problem if they need more data in london
[09:24] <willcooke> just reconfigured my test laptop in to legacy mode, L_aney is writing a USB stick
[09:24] <willcooke> #livetweet
[09:24] <jibel> willcooke, you can relay the message ;)
[09:24] <didrocks> seb128: hum, are you sure? we fixed the a11y issue on the 24, so 25.1 contains the a11y fix, not the one from 24
[09:25] <willcooke> jibel, shall we get you on a HO?
[09:25] <seb128> willcooke, great that you are here, at least we have some update of what is going on in London
[09:25] <seb128> otherwise it feels like complet disconnect
[09:25] <doko> infinity, Laney: are you aware of<EMAIL_ADDRESS>?
[09:25] <JamieBennett> willcooke: a HO seems sensible
[09:25] <jibel> sure, give me a minute
[09:25] <seb128> which is a bit sad
[09:25] <Laney> doko: yes
[09:25] <Laney> seb128: :/
[09:25] <Laney> we're trying to reproduce it
[09:26] <Laney> but please try as well
[09:26] <seb128> Laney, sorry, feels like we have pretty much being blocked or informed with hours delays of anything happening since tuesday, it's a bit the suck :/
[09:26] <seb128> yeah, i'm trying
[09:26] <seb128> but I'm a bit confused now
[09:26] <Laney> what delays?
[09:26] <doko> Laney: looks like a quoting error?
[09:26] <Laney> doko: no, the apt update failed
[09:26] <seb128> are we investigating the dconf permission errors?
[09:26] <doko> ahh
[09:26] <Laney> yes
[09:26] <seb128> or the "get login screen"
[09:26] <Laney> what has the release sprint delayed in that though?
[09:27] <seb128> Laney, if you guys were not at the same place there would be IRC discussions about the issues being considered/worked on and others would be in the loop of what's going on/what are the issues/what is the status
[09:28] <Laney> this is a bug that was raised on IRC?
[09:28] <seb128> yes
[09:28] <seb128> 1h30 ago
[09:28] <Laney> that's the first we knew
[09:28] <jibel> seb128, I think the "get loing screen" is the same problem
[09:28] <seb128> anyway that's not an important discussion to have now
[09:28] <seb128> jibel, I don't understand, does it happen in live or not?
[09:29] <jibel> seb128, yes in a live session
[09:29] <jibel> 4213 [  306.097343] ubuntu gnome-session-binary[4872]: dconf-CRITICAL: unable to create file '/run/user/999/dconf/user': Permission denied.  dconf will not work properly.
[09:29] <seb128> jibel, do you have the buggy session atm?
[09:29] <jibel> seb128, you boot to a live session, and get a login screen
[09:29] <jibel> tes
[09:29] <jibel> yes
[09:30] <seb128> do you need to go through ubiquity-maybe?
[09:30] <seb128> or does it happen also in direct live from syslinux?
[09:30] <willcooke> HO: https://hangouts.google.com/hangouts/_/canonical.com/will?authuser=0
[09:30] <jibel> seb128, yes, I didn't reproduce it when booting straight to the live sesion from syslinux
[09:31] <seb128> k, good
[09:31] <seb128> jibel, can you "ps axu | grep dconf" on the buggy system?
[09:31] <willcooke> jibel, link ^
[09:31] <willcooke> for HO
[09:31] <willcooke> cc seb128, didrocks
[09:31] <jibel> yup 1s, the sound indicator disappeared
[09:32] <didrocks> joining once my other vm trial booted
[09:32] <didrocks> (don't want to artifically slowing it down and see what happens)
[09:32] <LocutusOfBorg> distro_info.DistroDataOutdated: Distribution data outdated. Please check for an update for distro-info-data. See /usr/share/doc/distro-info-data/README.Debian for details.
[09:32] <LocutusOfBorg> sigh
[09:33] <LocutusOfBorg> backprotpackage broken
[09:34] <seb128> willcooke, same as didrocks, my laptop is already struggling with vms boots etc atm, might join in a bit
[09:35] <philroche> Canonical CPC team checking in. I am CPC vanguard so if you know of any packages server/cloud related that will possibly cause a respin please ping. We're currently getting dailies uploaded to public clouds but will hold off on promotion until we get the OK from you guys.
[09:36] <seb128> jibel, did you see my question about the ps?
[09:37]  * didrocks does another testboot closing thunderbird this time…
[09:38] <seb128> I'm not getting the issue in virtualbox
[09:38] <didrocks> I'm using kvm/qemu through gnome-boxes
[09:38] <didrocks> as it's clearly a race depending on who writes first, hard to reproduce :/
[09:39] <jibel> Laney, https://bugs.launchpad.net/ubuntukylin/+bug/1767067
[09:39] <ubot5`> Ubuntu bug 1767067 in ubiquity (Ubuntu) "Booting to live session fails with: at-spi-bus-launcher: unable to create file '/run/user/999/dconf/user': Permission denied." [Critical,New]
[09:39] <seb128> sounds like we lost jibel, probably under pings from r-t and others
[09:40] <seb128> willcooke, jibel, I can't reproduce and can't help if IRC get ignored so I'm stepping out of that for a bit and going to look at launchpad recent reports & co, let me know if I can help/if someone wants to look at what I asked a bit earlier
[09:43] <Laney> :/
[09:43] <Laney> we're just trying hard to debug it, it's not a deliberate ignoring of you
[09:44] <seb128> I was trying to help
[09:44] <jibel> seb128, sorry, I missed your messsage
[09:45] <willcooke> seb128, join the HO
[09:45] <seb128> Laney, it's fine, it's just that it seems impossible from people not with you to get enough interaction bandwith to be useful, which is fair enough
[09:46] <jibel> seb128, gdm       5318  0.0  0.2 280736  5736 tty1     Sl   08:37   0:00 /usr/lib/ibus/ibus-dconf
[09:46] <jibel> ubuntu    5685  0.0  0.0  21536  1068 tty3     S+   09:45   0:00 grep --color=auto dconf
[09:46] <ubot5`> Ubuntu bug 5685 in searchandrescue (Ubuntu) "searchandrescue: merge new debian version" [Medium,Fix released] https://launchpad.net/bugs/5685
[09:46] <seb128> willcooke, I can't, my machine is already swapping from the vm and GNOME session eating 1.5G ram
[09:46] <seb128> jibel, you don't have dconf-service process(es)?
[09:46] <seb128> weird :/
[09:46] <jibel> no
[09:46] <didrocks> same here, it's either vm or HO :/
[09:46] <JamieBennett> seb128: how about joining the HO via phone?
[09:47] <willcooke> update for IRC:  xnox thinks he can see the race
[09:47] <seb128> JamieBennett, I guess I can try, I just don't have my canonical account on my phone
[09:47] <seb128> willcooke, ah, nice
[09:47] <willcooke> atspi starting before dconf
[09:47] <willcooke> and sometimes it doesnt
[09:47] <didrocks> which basically matches the first report on atspi
[09:48] <didrocks> I guess needing its env vars to see what's up
[09:48] <seb128> who is owner the dconf/user file?
[09:49] <seb128> it doesn't make sense to me
[09:49] <seb128> at-spi-bus-laun[4081]: unable to create file '/run/user/999/dconf/user': Permission denied. dconf will not work properly.
[09:49] <seb128> suggests that's it's not at-spi starting before dconf
[09:49] <jibel> seb128, it doesn't exist
[09:49] <willcooke> we think it;s that the file doesn't exist, rather than perms
[09:49] <seb128> while permission denied then?
[09:49] <didrocks> we had the same issue in ubiquity
[09:49] <seb128> no
[09:50] <didrocks> it was printing "Permission denied"
[09:50] <seb128> ubiquity had the file owned by root
[09:50] <didrocks> remember the second one
[09:50] <seb128> because a dconf-server was spawned by root
[09:50] <jibel> and 999 is owned by ubutnu
[09:50] <didrocks> the one while you left for lunch :)
[09:50] <didrocks> yeah, that was the first issue
[09:50] <didrocks> the second was missing XDG_RUNTIME_DIR
[09:50] <seb128> with XDG env was uncorrect
[09:50] <seb128> right, be the result was a file root owned there
[09:50] <didrocks> which was printing '/run/user/999/dconf/user': Permission denied
[09:50] <didrocks> there was no file
[09:52] <willcooke> HO closed for now
[09:53] <willcooke> xnox has a plan
[09:53] <seb128> good
[09:54] <didrocks> just in case the issue is the same the second fix we got the other day: check XDG_RUNTIME_DIR in that process and if setting it works
[09:54] <didrocks> ftr
[09:56] <willcooke> xnox, ^
[09:58] <seb128> would be useful to have the env of at-spi if the process doesn't exit due to the error
[09:58] <seb128> but it's weird, the a11y stack has its own bus iirc, it's not using the standard session one
[09:59] -queuebot:#ubuntu-release- Unapproved: val-and-rick (bionic-proposed/universe) [0.1a.dfsg1-5build1 => 0.1a.dfsg1-6~build1] (no packageset)
[10:00] -queuebot:#ubuntu-release- Unapproved: accepted val-and-rick [source] (bionic-proposed) [0.1a.dfsg1-6~build1]
[10:07] <Laney> I made it happen
[10:07] <Laney> this is weird
[10:08] <didrocks> anything interesting in env/file permission/confirming file doesn't exist?
[10:10] <Laney> https://paste.ubuntu.com/p/VYh4qqJFpf/ that's the install debug log
[10:10] <Laney> first bad line is (ubiquity:1430): IBUS-WARNING **: 09:47:25.837: The owner of /home/ubuntu/.config/ibus/bus is not root!
[10:12] <cjwatson> I was suggesting here trying to get an strace -f of both ubiquity-dm and the running dbus-daemon (the latter by pid)
[10:12] <cjwatson> and then assuming you hit the bug, search down for that directory name and then work backwards
[10:13] <cjwatson> big hammer but it might be quickest, assuming it doesn't perturb the bug out of existence
[10:20] <seb128> Laney, did you find a way to trigger it or just go it after n tries?
[10:21] -queuebot:#ubuntu-release- New binary: python-requests-ntlm [amd64] (bionic-proposed/universe) [1.1.0-1] (no packageset)
[10:21] <infinity> seb128: The latter.
[10:21] <seb128> k :/
[10:23] <enyc> "intermittent race-condition heisenbug" =)
[10:25] <seb128> bug #1767048 :/ (not rc but annoying if that's the case)
[10:25] <ubot5`> bug 1767048 in ubiquity-slideshow-ubuntu (Ubuntu) "Slideshow translations were not updated for 18.04 LTS" [Undecided,New] https://launchpad.net/bugs/1767048
[10:25] -queuebot:#ubuntu-release- New: accepted python-requests-ntlm [amd64] (bionic-proposed) [1.1.0-1]
[10:26] <infinity> seb128: Yeah, if we find ourselves having to delay, that's a valid candidate.
[10:35] <jibel> seb128, are this strings in a langpack or with the package? when I look earlier today, the untranslated string in French is translated in LP since 2016
[10:36] <cjwatson> in the package
[10:36] <cjwatson> that's true of the installer in general - it can't rely on langpacks
[10:36] <Mirv> jibel: part of the nonlangpack translations: https://wiki.ubuntu.com/NonLanguagePackTranslationDeadline
[10:37] <jibel> right, that's what I supposed but everything is translated in French.
[10:37] <Mirv> I think the template in LP is correct, but the translations just weren't exported and included in an upload
[10:37] <cjwatson> last translation update in the package seems to have been 2017-10-17
[10:38] <willcooke> seb128, jibel - everyone here as now reproduced the issue.  Adding more cpus to a VM seems to "help".  Trying to figure out what's going on now in parallel
[10:38] <Mirv> jibel: the link changed a bit: https://bazaar.launchpad.net/~ubiquity-slideshow/ubiquity-slideshow-ubuntu/html/revision/810#slideshows/ubuntu/slides/gethelp.html
[10:38] <Mirv> so that's why the two strings on the last page got affected
[10:38] <cjwatson> I'll see if I can get a translation update going
[10:40] <willcooke> seb128, jibel - "help" = help reproduce
[10:43] <Laney> we found another gsettings call too https://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/view/head:/bin/ubiquity-dm#L526
[10:44] <Laney> without all the sudo shizzle
[10:47] -queuebot:#ubuntu-release- Unapproved: python-josepy (bionic-proposed/universe) [1.0.1-1 => 1.1.0-1] (no packageset) (sync)
[10:48] <seb128> cjwatson, thx
[10:48] -queuebot:#ubuntu-release- Unapproved: accepted python-josepy [sync] (bionic-proposed) [1.1.0-1]
[10:48] <seb128> willcooke, k, let me try that
[10:49] <seb128> Laney, ah, that sounds boggus
[10:53] <Wimpress> willcooke Laney jibel Ubuntu MATE are experiencing the dconf issues.
[10:53] <Wimpress> It seems 100% reproducible in the 25.1 i386 image for Ubuntu MATE if that helps.
[10:53] <Wimpress> I got word of this last night while travelling to UbuCon
[10:54] <Wimpress> Sat in the hotel now, happy to assist.
[10:54] <willcooke> Wimpress, if you have old images, could you see if you can work out when it broke?
[10:56] <Wimpress> Was also broken in 25
[10:56] <jibel> I couldn't reproduce with 24
[10:57] <willcooke> does that tie in with the permissons fixes
[10:57] <willcooke> it must do
[10:57] <Wimpress> The oldest image I have is 24. So going to test it.
[10:58] <seb128> willcooke, thanks for the cpu hint, I got the pb on first try after changing vbox ncpu from 1 to 2
[10:58] <seb128> while I didn't get it on like 15 tries before
[10:58] <willcooke> thanks apw :)
[10:59] <seb128> on that session I've a dconf/user though
[10:59] <seb128> but it's root:root owned
[10:59] <willcooke> seb128, did you go direct in to the live session?
[10:59] <seb128> no
[10:59] <seb128> ubiquity-maybe (the screen with the Ui and the 2 choices)
[10:59] <seb128> and clicked on "try"
[11:00] <Laney> that's weird, we don't see those files
[11:00] <seb128> let me retry a new boot
[11:00] <Laney> because there's no user session and the xdg runtime user gets deleted
[11:00] <Laney> so you can't see the root:root state, not here
[11:01] <seb128> the user session is in "closing" state for me (c1)
[11:01] <seb128> still active due to ibus which didn't exit
[11:02] <seb128> ibus-daemon and ibus-dconf
[11:03] -queuebot:#ubuntu-release- Unapproved: accepted cloud-utils [source] (xenial-proposed) [0.27-0ubuntu25.1]
[11:04] -queuebot:#ubuntu-release- Unapproved: accepted cloud-utils [source] (artful-proposed) [0.30-0ubuntu2.1]
[11:05] <Laney> interesting
[11:05] -queuebot:#ubuntu-release- Unapproved: python-pyvmomi (xenial-proposed/main) [5.5.0-2014.1.1-3 => <IP_ADDRESS>7.5-0ubuntu1~16.04.1] (ubuntu-server)
[11:07] <Wimpress> Laney seb128 Ubuntu MATE doesn't use ibus.
[11:07] <seb128> I don't think ibus is the issue
[11:08] <seb128> Laney, I think fixing those gsettings calls in -dm done without the wrapper is worth trying
[11:08] <seb128> Laney, I killed ibus, session closed, dconf dir had been wipped out
[11:09] <seb128> but the file was there and root owned in my case
[11:09] <seb128> didrocks, ^
[11:09] <didrocks> yeah, I think the gsettings call fix worth a shot (ensuring it has correct DBUS address and XDG_RUNTIME_DIR)
[11:10] <Laney> trying to see where the bad permissions actually come in
[11:17] -queuebot:#ubuntu-release- Unapproved: ubiquity-slideshow-ubuntu (bionic-proposed/main) [137 => 138] (kubuntu, ubuntu-desktop)
[11:20] <Mirv> thanks cjwatson
[11:22] <cjwatson> seb128,didrocks,Laney: I think that would be https://paste.ubuntu.com/p/RSqyqmz6s2/
[11:23] <cjwatson> naive untested conversion
[11:23] <cjwatson> (the logfile stuff is probably unnecessary, but is just in case)
[11:23] <cjwatson> can somebody try editing that in place?
[11:24]  * didrocks still can't reproduce it… a quick diff look sounds good to try out with the wrapper we fixed
[11:25]  * cjwatson is too rusty on all this and also doesn't have a reproducer case to hand
[11:29] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (xenial-proposed) [1:2.5+dfsg-5ubuntu10.26]
[11:32] <silWeb> cjwatson: reviewing the slideshow upload o/
[11:33] <cjwatson> thanks
[11:34] <cjwatson> I mean it's 123000 lines of unreviewable diff, but go nuts
[11:36] <Mirv> fwiw I checked all the fi.po in the diff and it seemed to do what it's supposed, for all flavors
[11:37] <silWeb> Reviewing as much as possible, sanity checking
[11:37] <silWeb> But looks like the translations aren't bogus
[11:38] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity-slideshow-ubuntu [source] (bionic-proposed) [138]
[11:42] <cjwatson> Laney can still reproduce #1767067 with my patch
[11:55] <seb128> :(
[12:00] <cjwatson> we're hitting it with more debugging
[12:01] <cjwatson> https://people.canonical.com/~cjwatson/tmp/ubiquity-gsettings.patch is the current thing in progress
[12:02] <seb128> cjwatson, thanks for the status updates on IRC!
[12:12] <xnox> Laney, infinity, cjwatson - "fix" the permissions, before quiting (meaning inside on_click handler of Try Ubuntu button) http://paste.ubuntu.com/p/gz6ddmPSF4/
[12:12] <xnox> trying this now
[12:16] <seb128> xnox, cjwatson, Laney, I guess you already saw that, but booting to ubiquity-maybe, going to a tty I've dconf/user root owned
[12:17] <seb128> so it's clearly from ubiquity-dm and not during the session start later
[12:19] -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (xenial-proposed) [1.3.1-1ubuntu10.22]
[12:19] -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (artful-proposed) [3.6.0-1ubuntu6.6]
[12:20] <Laney> yeah
[12:20] <willcooke> seb128, hard deadline for a decision abot a release today is 4pm UK time.  Current options are, AIUI, revert the a11y fixes and respin -or- release as is -or- fix the bug
[12:20] <willcooke> seb128, could you look at how we could save some time if we do revert so that we've got a headstart if that is the final decision?
[12:21] <willcooke> like maybe make a start on reverting?
[12:21] <willcooke> JamieBennett, fyi ^
[12:21] <seb128> willcooke, are we confident a revert would fix it?
[12:21] <silWeb> Did we bisect it to started after this weeks a11y fixes?
[12:22] <silWeb> jibel: you tried earlier images, right?
[12:23] <jibel> silWeb, I tried 24
[12:23] <willcooke> yeah jibel tried earlier images, and Wimpress did too
[12:24] <jibel> i'm trying a revert of a a11y patch
[12:24] <seb128> willcooke, on what image did it start?
[12:25] <seb128> did it start with ubiquity .11 or .12?
[12:25] <willcooke> 25 I think
[12:25] <seb128> or .10?
[12:26] <silWeb> On the 24th the a11y fixes landed
[12:27] <seb128> which one
[12:27] <seb128> we had several iterations
[12:28] <silWeb> The keypress one, and it was in the 25 image
[12:28] <silWeb> https://launchpad.net/ubuntu/+source/ubiquity/18.04.11
[12:29] <silWeb> jibel: so you could reproduce with 24 as well or not?
[12:29] -queuebot:#ubuntu-release- Unapproved: virtualbox (bionic-proposed/multiverse) [5.2.10-dfsg-5 => 5.2.10-dfsg-5ubuntu1] (ubuntu-cloud)
[12:30] <LocutusOfBorg> can we have virtualbox processed please???^^^ I can sync from Debian, but I think this is too late, so I would like to do an sru
[12:30] <LocutusOfBorg> (in case, accept when convenient
[12:31] <silWeb> LocutusOfBorg: I'll look at it once the fires are extinguished
[12:31] <jibel> silWeb, I didn't reproduce with 24
[12:43] <acheronuk> the bug just changed to "Fix Released"?
[12:48] -queuebot:#ubuntu-release- Unapproved: nvidia-cuda-toolkit (bionic-proposed/multiverse) [9.1.85-3 => 9.1.85-3ubuntu1] (no packageset)
[12:48] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (bionic-proposed/multiverse) [5.2.10-dfsg-5ubuntu18.04.1 => 5.2.10-dfsg-5ubuntu18.04.2] (no packageset)
[12:48] <cjwatson> seb128: my analysis of the debug output so far is that dconf/user is being created as root by ubiquity rather than by ubiquity-dm
[12:48] <cjwatson> at least in the cases we've looked at
[12:49] <seb128> cjwatson, is "maybe-ubiquity" using ubiquity or -dm?
[12:49] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-cuda-toolkit [source] (bionic-proposed) [9.1.85-3ubuntu1]
[12:49] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-hwe [source] (bionic-proposed) [5.2.10-dfsg-5ubuntu18.04.2]
[12:49] <cjwatson> acheronuk: that's interfering users for you
[12:49] <seb128> sorry I'm not that familiar with how ubiquity works
[12:49] <seb128> I though the standalone mode was -dm
[12:49] <seb128> and ubiquity the UI used in the live session
[12:49] <cjwatson> maybe-ubiquity goes through ubiquity-dm
[12:50] <cjwatson> which starts ubiquity as a subprocess within X etc.
[12:50] <seb128> I see
[12:51] <seb128> well at least by the time the 2 choices screen is displayed I've a dconf/user root owned
[12:51] <cjwatson> xnox: I mean ... I guess.  perhaps.  pretty awful though
[12:51] <seb128> I did a gsettings wrapper that logs uid/$@/env and call the real binnary
[12:51] <seb128> the /usr/bin/gsettings command is never called as root
[12:52] <seb128> but I guess that was not a likely case, anyway that seems ruled out
[12:52] <Wimpress> There is a useful bug in Ubuntu MATE that might be interesting to you
[12:52] <cjwatson> it was definitely possible though I'd mostly ruled it out here, but thanks for the confirmation
[12:52] <Wimpress> crtl + alt + t works in Ubiquity
[12:53] <seb128> is that still true?
[12:53] <seb128> sounds like one of the possible side effect of the gsettings misuse we fixed recently
[12:54] <seb128> in any case switch to a tty works now in ubiquity so it's easy to get a debug command line
[12:54] <Wimpress> Not on HPI ;-)
[12:54] <Wimpress> And the ctrl + alt +t thing has been around for a good while.
[12:55] -queuebot:#ubuntu-release- Unapproved: ruby-delayed-job-active-record (bionic-proposed/universe) [4.1.2-1 => 4.1.2-2] (no packageset)
[12:55] <ahasenack> LocutusOfBorg: I got that "distribution data outdated" error too in a script a jenkins job is using: /usr/bin/download-latest-test-iso. Do you know where that script comes from by any chance? https://pastebin.ubuntu.com/p/wZgVs2n7ym/
[12:55] <cjwatson> distro-info
[12:55] -queuebot:#ubuntu-release- Unapproved: accepted ruby-delayed-job-active-record [source] (bionic-proposed) [4.1.2-2]
[12:55] <cjwatson> happens on release day every six months
[12:55] <LocutusOfBorg> ahasenack, sudo vi /usr/share/distro-info/ubuntu.csv
[12:56] <LocutusOfBorg> set the bionic date to tomorrow
[12:56] <LocutusOfBorg> 18.04 LTS,Bionic Beaver,bionic,2017-10-19,2018-04-27,2023-04-26
[12:56] <ahasenack> I don't have shell access on that box
[12:56] <LocutusOfBorg> and postpone the issue for 24h :)
[12:56] <seb128> Wimpress, well, we fixed that gsettings bug this week, could have made that hack stop working
[12:56] <LocutusOfBorg> so, ask to SRU the fix, you need to add a new entry with CC and some tentative schedule I would guess
[12:57] <ahasenack> this is the ci job that gates the live-server iso image from pending to current
[12:57] <ahasenack> need to find someone who can hack it
[12:57] <ahasenack> josh is on pto
[12:57] <cjwatson> ahasenack: please could you debug this elsewhere?
[12:57] <cjwatson> we have enough fires here
[12:57] <rbalint> Laney: can we expect bionc/s390x autopkgtest runners to be fixed before the release or hints may be the way to go?
[12:58] <jibel> ahasenack, i'll have a look
[12:59] <Laney> rbalint: IS is looking
[13:00] <rbalint> Laney: thanks!
[13:05] <cjwatson> seb128: I'm wondering if Gio.Settings.new in gtk_ui might create the dconf/user file with the privileges of the current process
[13:06] <cjwatson> or something in those bindings
[13:06] <cjwatson> it looks to me as though dconf-service creates that even if reading
[13:07] <jibel> I reverted this http://paste.ubuntu.com/p/p7xdxWqwNN/ (r6627) and cannot reproduce the bug
[13:07] <seb128> cjwatson, the way gsettings work dconf is only used for writes and dconf-service shouldn't start on reads
[13:07] <seb128> or until you issue a write
[13:07] <cjwatson> what else would be creating dconf/user though?
[13:07] <seb128> nothing that I know of
[13:08] <seb128> I would expect that some root code is issue a dbus call that tells dconf to write something
[13:09] <cjwatson> I think we should go ahead with this revert now (reversioned to 18.04.13 rather than 18.04.12ubuntu1, but otherwise jibel's patch LGTM)
[13:09] <cjwatson> does anyone object?  we should definitely continue to try to find the root cause but we're pretty nearly out of time
[13:10] <jibel> could someone else test the revert?
[13:11] <cjwatson> I think apw is doing so
[13:11] <apw> sil2100, ^ apw@brain:~/vms$
[13:11] <apw> sil2100, ^ are you doing that ?
[13:12] <seb128> cjwatson, if we think it's fine to release without screen reading in the installer that makes sense
[13:15] <cjwatson> I mean it's not *fine* but it may be least-bad
[13:15] <cjwatson> and fix properly for .1
[13:16] <sil2100> I'm testing it
[13:18] <Mirv> if there's the respin, will you unblock http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ubiquity-slideshow-ubuntu before that?
[13:18] <infinity> Mirv: Yes.
[13:18] <Mirv> ok
[13:19] <jbicha> jibel: the screen reader was broken for 17.10 too, right?
[13:19] <cjwatson> xnox has an alternative hack that chowns dconf/user to 999:999 in the try_ubuntu entry point
[13:19] <cjwatson> I think personally I'm more comfortable with the revert - fewer unknowns
[13:19] <cjwatson> but that's just me
[13:19] <cyphermox> jibel: looking at the code, wouldn't it have made the screen reader only work in the only-ubiquity session?
[13:20] <cyphermox> oh, duh
[13:20] <acheronuk> a revert will re-break ubiquity reboot for flavours?
[13:21] <jibel> cyphermox, yes, but without it there is not way for someone blind to boot to the live session or install the distro
[13:21] <cjwatson> only a revert of the screen reader stuff
[13:21] <cjwatson> I don't think the reboot fix needs to be involved
[13:21] <cyphermox> jibel: yeah, I clued in... also in a normal session you can start it yourself..
[13:21] <seb128> cjwatson, I tried to do the Gio.Settings.new/connect/etc from a root python interpreter, that doesn't lead to a dconf/user file created
[13:21] <cjwatson> maybe it depends on the signal being received?
[13:22] <seb128> well I went to another tty and did a write on the key
[13:22] <jibel> cyphermox, right but if your blind you cannot go to the live session
[13:22] <seb128> but maybe I tested something not right
[13:22] <jibel> you are*
[13:23] <seb128> the callback didn't seem to get called
[13:23] <cjwatson> it's clear that reverting a screen reader fix would be bad for blind people, and I don't *like* that
[13:24] <cyphermox> jibel: maybe-ubiquity gives you the option. that's what you'd get normally if you just wait at the bootspash in legacy mode
[13:24] <cyphermox> if you're booting UEFI you'd fall right in the live session if I'm not mistaken
[13:24] <jibel> cyphermox, how do you know which button to click and that you're on the right button if you do not *see* it
[13:25] <cjwatson> xnox's alternative hack wouldn't have that downside; I'm less comfortable with that I think basically because I feel that there are too many paths to check
[13:25] <xnox> willcooke, cjwatson, Laney, infinity, jibel, apw - here is my bodge/hack, possibly will not be taken, but this appears to fix it for me
[13:25] <xnox> https://code.launchpad.net/~xnox/ubiquity/fixup-owner-dconf/+merge/344474
[13:25] <xnox> if interested
[13:25] <cyphermox> jibel: people know to hit left or right and then enter.
[13:25] <cyphermox> (or at least, some do)
[13:25] <jibel> how? just turn off your screen and try
[13:26] <cjwatson> jibel: I understand that you're arguing really hard that reverting a screen reader fix is bad.  What's your positive alternative suggestion?
[13:26] <jibel> https://code.launchpad.net/~jibel/ubiquity/lp1767067_revert_r6627_a11y if we go the revert way
[13:26] <cjwatson> jibel: Do you prefer xnox's patch?
[13:27] <cjwatson> xnox: needs to be chown uid:uid rather than just uid I think
[13:27] <cjwatson> mode 600. I *guess*.
[13:28] <seb128> cjwatson, xnox, I would just rm the file
[13:28] <jibel> cjwatson, I don't have an alternative, I was replying to "in a normal session you can start it yourself" which is not true for disabled users
[13:28] <seb128> that file is not useful, it's just the way dconf has to tell client code to reload the db after it changes
[13:29] <seb128> dconf-service is going to rewrite the file if it's not there
[13:29] <cjwatson> reasonable point
[13:29] <xnox> seb128, true, if dconf is restarted and if that file is not locked / not in use....
[13:30] <xnox> seb128, let me try
[13:30] <cjwatson> I mean after try-ubuntu it surely ought not to be :)
[13:32] <xnox> sil2100,  https://code.launchpad.net/~xnox/ubiquity/fixup-owner-dconf/+merge/344474
[13:34] <cyphermox> xnox: ubi-language seems late to be doing this?
[13:34] <cjwatson> it's the try-ubuntu entry point
[13:34] <cjwatson> so it's effectively where we're about to exit ubiquity
[13:35] <cyphermox> heh
[13:35] <cjwatson> xnox: also, needs a great big comment explaining WTF is going on
[13:35] <cjwatson> and to be moved above the "Spinning cursor" comment
[13:35] <cjwatson> a hack like this with zero inline commentary isn't acceptable
[13:37] <sil2100> I'm prepping an iso with xnox
[13:37] <sil2100> 's branch as well
[13:41] <didrocks> yeah, removing the file sounds the best path to me for now
[13:45] <xnox> seb128, cjwatson - removing file, works good. Pushing branch.
[13:46] <seb128> :)
[13:49] <didrocks> phew :)
[13:56] <sil2100> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767067
[13:56] <ubot5`> Ubuntu bug 1767067 in ubiquity (Ubuntu Bionic) "Booting to live session fails with: at-spi-bus-launcher: unable to create file '/run/user/999/dconf/user': Permission denied." [Critical,Confirmed]
[14:01] <willcooke> update: new patch being pushed now, then an image, then we need to test
[14:01] <didrocks> great!
[14:02] <seb128> good
[14:03] <Wimpress> willcooke: Is one sample test image being created?
[14:03] <Wimpress> If so, I've found somewhere with WiFi. Can download and test.
[14:03] <xnox> apw, https://code.launchpad.net/~xnox/ubiquity/fixup-owner-with-remove/+merge/344477
[14:03] <xnox> here
[14:03] <xnox> here
[14:08] <seb128> cjwatson, looking at the timestamp of the dconf/user root owned and the journal log with millisec precision the file is modified really close from the Gio.Settings.new use and I can't find anything else in the patch/code that could explain the problem so you might be right
[14:10] -queuebot:#ubuntu-release- Unapproved: ubiquity (bionic-proposed/main) [18.04.12 => 18.04.13] (core)
[14:14] <Laney> seb128: think I know the real fix, can we talk about it?
[14:14] <seb128> oh, waouh
[14:14] <seb128> sure!
[14:14] <Laney> ok
[14:15] <Laney> so the code ended up in run() instead of __init__() which is where I was putting it
[14:15] <Laney> problem is that run() runs as root and __init__ as the user
[14:15] <Laney> so the dconf call is happening as the root user
[14:15] <cjwatson> (this seems promising and I'm happy with it replacing the 18.04.13 above)
[14:16] <Laney> what I don't understand is why it was a race
[14:16] <Laney> presumably the callback racing with a regain_privileges() elsewhere or something
[14:18] <seb128> ah
[14:18] <seb128> that's a bit weird
[14:18] <seb128> I also don't understand what "dconf call" is happening
[14:18] <Laney> whatever Gio.Settings.new is doing
[14:18] <Laney> or the read maybe
[14:19] <seb128> but it shouldn't do one
[14:19] <seb128> and dconf shouldn't start until there is a writte
[14:19] <seb128> that's one of the things desrt was always pointing, on a normal session login dconf shouldn't be activated
[14:19] <seb128> the reads go through direct mmaping of the db
[14:20] <seb128> well, if moving to __ini__ fixes the issue that great and I think it's a better way out
[14:20] <seb128> but I still don't fuilly understand it either
[14:21] <seb128> neither why it's a race nor why there is a write at all
[14:21] <cjwatson> I'm thinking maybe it socket-activates something as root that then later creates dconf/user due to a gsettings set?
[14:21] <seb128> could be I guess
[14:22] <seb128> Laney, you/anyone is trying to move the Gio blob to __init__ now?
[14:22] <Laney> yes
[14:22] <seb128> great
[14:22] <Laney> I'll do a merge proposal in a second
[14:22] <seb128> thx, let me know and I give it a try as well
[14:25] <ginggs> can nvidia-cuda-toolkit be unblocked please?
[14:27] -queuebot:#ubuntu-release- Unapproved: synapse (bionic-proposed/universe) [<IP_ADDRESS>-1 => <IP_ADDRESS>-1] (no packageset) (sync)
[14:27] -queuebot:#ubuntu-release- Unapproved: accepted synapse [sync] (bionic-proposed) [<IP_ADDRESS>-1]
[14:30] -queuebot:#ubuntu-release- Unapproved: sugar-read-activity (bionic-proposed/universe) [119-1 => 120-1] (sugar) (sync)
[14:32] -queuebot:#ubuntu-release- Unapproved: sugar-browse-activity (bionic-proposed/universe) [201.3-1 => 202-1] (no packageset) (sync)
[14:32] -queuebot:#ubuntu-release- Unapproved: accepted sugar-browse-activity [sync] (bionic-proposed) [202-1]
[14:33] -queuebot:#ubuntu-release- Unapproved: sugar (bionic-proposed/universe) [0.112-2 => 0.112-4] (no packageset) (sync)
[14:33] -queuebot:#ubuntu-release- Unapproved: accepted sugar [sync] (bionic-proposed) [0.112-4]
[14:39] <Laney> xnox: apw cjwatson seb128 https://code.launchpad.net/~laney/ubiquity/lp1767067/+merge/344482
[14:42] <seb128> Laney, thx, testing that
[14:43] <Laney> accidentally pushed it to trunk again ://///
[14:45] <cjwatson> have retroreviewed
[14:50] -queuebot:#ubuntu-release- Unapproved: rejected ubiquity [source] (bionic-proposed) [18.04.13]
[14:51] -queuebot:#ubuntu-release- Unapproved: ubiquity (bionic-proposed/main) [18.04.12 => 18.04.14] (core)
[14:57] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (bionic-proposed) [18.04.14]
[14:57] <Laney> http://people.canonical.com/~laney/ubiquity-gsettings.patch
[14:57] <Laney> that's the same thing as a .patch
[14:58] <Laney> You can apply it in break=bottom or whatever
[15:07] <Laney> that ubiquity is going to be unblocked and then we'll respin
[15:11] -queuebot:#ubuntu-release- Unapproved: accepted sugar-read-activity [sync] (bionic-proposed) [120-1]
[15:11] <doko> any update on the s390x autopkg runners?
[15:11] <xnox> doko, no, and not work on in this channel.
[15:12] <xnox> (as in it is tracked / debugged on internal channel)
[15:13] <doko> xnox: must be so internal that I cannot follow it :-/
[15:14] <doko> are desktop images the only images for the respin?
[15:14] <infinity> doko: No.
[15:15] <jbicha> infinity: I tried pinging handsome_feng twice about the 5 year support for Kylin issue but I didn't really get a reaction
[15:16] <handsome_feng> jbicha, infinity:Hi, I'm here
[15:17] <jbicha> handsome_feng: I'm not a member of the Tech Board or Release Team
[15:18] <jbicha> but I think there are concerns about whether Kylin can support its packages for 5 years now that it is no longer based on the main Ubuntu flavor supported by Canonical
[15:18] <jbicha> and Ubuntu MATE is only offering 3 years of support
[15:19]  * acheronuk assumed that 5 years was a typo?
[15:19] -queuebot:#ubuntu-release- Unapproved: freeipa (bionic-proposed/universe) [4.7.0~pre1+git20180411-2ubuntu1 => 4.7.0~pre1+git20180411-2ubuntu2] (no packageset)
[15:19] <doko> infinity: please could you considering to ignore the i386 autopkg test failure for python-redis and accept that one? please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896864 for the background. we could accept the upload in unapproved too instead
[15:19] <ubot5`> Debian bug 896864 in src:python-redis "python-redis autopkg test failures on i386" [Important,Fixed]
[15:19] <jbicha> handsome_feng: is 3 years support ok for Kylin?
[15:20] -queuebot:#ubuntu-release- Unapproved: accepted freeipa [source] (bionic-proposed) [4.7.0~pre1+git20180411-2ubuntu2]
[15:22] <handsome_feng> jbicha: I'm ping my leader, so please wait a moment. :)
[15:24] -queuebot:#ubuntu-release- Unapproved: dogtag-pki (bionic-proposed/universe) [10.6.0-1ubuntu1 => 10.6.0-1ubuntu2] (no packageset)
[15:25] -queuebot:#ubuntu-release- Unapproved: accepted dogtag-pki [source] (bionic-proposed) [10.6.0-1ubuntu2]
[15:26] -queuebot:#ubuntu-release- Unapproved: accepted java-atk-wrapper [source] (bionic-proposed) [0.33.3-20ubuntu0.1]
[15:26] -queuebot:#ubuntu-release- Unapproved: accepted python-redis [source] (bionic-proposed) [2.10.6-2ubuntu1]
[15:26] -queuebot:#ubuntu-release- Unapproved: accepted xdg-desktop-portal [sync] (bionic-proposed) [0.11-1]
[15:26] -queuebot:#ubuntu-release- Unapproved: accepted python-networkx [source] (bionic-proposed) [1.11-1ubuntu2]
[15:26] -queuebot:#ubuntu-release- Unapproved: bind-dyndb-ldap (bionic-proposed/universe) [11.1-3 => 11.1-3ubuntu1] (no packageset)
[15:26] -queuebot:#ubuntu-release- Unapproved: accepted xdg-desktop-portal-gtk [sync] (bionic-proposed) [0.11-1]
[15:27] -queuebot:#ubuntu-release- Unapproved: accepted bind-dyndb-ldap [source] (bionic-proposed) [11.1-3ubuntu1]
[15:29] <Guest85065> !isitout
[15:29] <ubot5`> Not yet!
[15:29] <doko> ok, uploading tdaitx's fix for ceph as well
[15:34] -queuebot:#ubuntu-release- Unapproved: ceph (bionic-proposed/main) [12.2.4-0ubuntu1 => 12.2.4-0ubuntu2] (desktop-core, ubuntu-server)
[15:35] <Wimpress> jbicha: Give Kylin is base on MATE and Ubuntu MATE is 3 years I don't see how Kylin can offer 5.
[15:35] <Wimpress> handsome_feng: See above ^
[15:36] <seb128> cjwatson, Laney, willcooke, I tested a few reboot with what is currently in lp:ubiquity (patching the code in rescue.target) and I didn't hit the error, looks good so far to me
[15:37] <didrocks> I couldn't reproduce the issue, but I didn't get any regression with the same inline patching method
[15:37] <seb128> thx didrocks
[15:41] <Laney> thx
[15:41] <Laney> we tried lots of times here too
[15:41] <handsome_feng> Wimpress, jbicha, infinity: After dissussing with the other members of ubuntu kylin, we agree with the desision that offering 3 years support for kylin
[15:41] <doko> infinity: please review the ceph upload
[15:42] <handsome_feng> Wimpress: Thanks! :)
[15:43] <jbicha> handsome_feng: could you reply to your reply on the ubuntu-release mailing list then? thank you
[15:43] <handsome_feng> jbicha: Fine, I will do it now
[15:47] <jbicha> slangasek: sorry about the lateness but would you approve of me uploading gnucash 3.0 with the build tests ignored? LP: #1758740
[15:47] <ubot5`> Launchpad bug 1758740 in gnucash (Ubuntu) "FFe: Sync gnucash 1:3.0-1 (universe) from Debian experimental (main)" [Wishlist,Incomplete] https://launchpad.net/bugs/1758740
[15:49] <slangasek> jbicha: you want to sync a package with a failing test whose impact you don't know, in order to be able to remove webkitgtk?
[15:49] <slangasek> jbicha: reverse-depends also suggests this is not the only remaining blocker for webkitgtk
[15:50] <rbasak> Could I have an ack from a release team member on https://code.launchpad.net/~racb/ubuntu-seeds/demote-nagios3/+merge/344490 please?
[15:50] <rbasak> In particular are there any implications that I'm missing?
[15:51] <jbicha> slangasek: yes. 🙁 Those other rdepends are kinda unimportant
[15:52] <slangasek> rbasak: no impact on metapackages/images; ok to make that change if you're sure
[15:52] <rbasak> slangasek: thanks. Also is it syntactically OK to drop the Monitoring section in the seed file?
[15:53] <slangasek> rbasak: sure, those are just human-readable labels
[15:53] <rbasak> Yeah that's what I thought. Thanks. I'll push.
[15:54] <abdelraouf> hello guys, when'll 18.04 LTS be available for download
[15:54] <dpb1> it will be announced when it's ready
[15:54] <doko> rbasak: remove from artful?
[15:54] <abdelraouf> there is too much work left ?
[15:55] <rbasak> doko: not remove, just demote.
[15:55] <rbasak> I've pushed the branch.
[15:55] <doko> rbasak: really from artful?
[15:55] <rbasak> I guess someone will need to move it after that takes effect?
[15:55] <tjaalton> doko: so I have the patch for tomcat jre8 support ready and test suite passes, so either push that or revert to build with jdk8. opinions? I'll send the patch upstream soon
[15:55] <rbasak> doko: no, bionic
[15:55] <doko> ahh, ok
[15:56] <doko> tjaalton: I would prefer the former
[15:56] <tjaalton> doko: ok, I'll upload that
[16:03] -queuebot:#ubuntu-release- Unapproved: tomcat8 (bionic-proposed/universe) [8.5.30-1ubuntu1 => 8.5.30-1ubuntu2] (kubuntu)
[16:04] <jbicha> slangasek: oh never mind. Eclipse depends indirectly on webkitgtk and I never got around to seeing how badly Eclipse would break if that dep were removed
[16:04] <slangasek> jbicha: ok.  in any case, I'm not ok with this as a last-minute untested change
[16:04] <infinity> jbicha: Thanks for clearing that up for us (re: kylin support length)
[16:05] <infinity> doko: Too late for ceph, it's on some images.  It'll need to be an SRU.
[16:05] <doko> ok
[16:05] <jbicha> infinity: np. I thought it was strange when Kylin proposed 5 years this time but it wasn't my job so I didn't say anything…
[16:05] <seb128> cjwatson, Laney, didrocks, k, I confirmed with http://people.canonical.com/~seb128/startorca.py started with sudo -E -H that it leads to a root owned dconf/user
[16:06] <JHOSMAN> How long is it until the ISO's release of 18.04?
[16:06] <rbasak> infinity: so to be clear I'm expecting a component mismatch to appear somewhere. So you're aware.
[16:06] <cjwatson> JHOSMAN: we won't be giving expected times here; please don't ask
[16:06] <didrocks> seb128: thx for testing, so reading a key lead to this… weird :/
[16:08] <slangasek> rbasak, infinity: I'm going ahead with the nagios demotions now
[16:08] <dpb1> JHOSMAN: sign up here, and you wont have to poll https://lists.ubuntu.com/mailman/listinfo/ubuntu-announce
[16:09] <JHOSMAN> thanks dpb1
[16:12] <rbasak> Thanks
[16:41] <doko> infinity, slangasek: please unblock ruby-delayed-job as well
[16:41] <infinity> doko: Refresh the page?
[16:41] <infinity> doko: Oh, NVM, I had the longer named one.
[16:44] <doko> infinity, slangasek: slangasek mentioned a possibility to ignore the "crossbuild-essential-amd64/amd64 unsatisfiable Depends: gcc-x86-64-linux-gnu" for build-essential. is this possible?
[16:45] <flocculant> infinity: hi - just got in from work - are we respinning?
[16:45] <infinity> doko: Not for release, build-essential is on media, and we're respinning in a matter of minutes.
[16:45] <Wimpress> flocculant: Yes.
[16:46] <flocculant> Wimpress: okey doke - thanks
[16:47] <Mirv> duty calls, but thank you everyone in advance for your hard work
[16:49] <teward> is everything still on track for release today?
[16:56] <slangasek> xnox, Laney: should ntp block the network-online target?  Should the autopkgtest runner setup scripts key on time-sync.target?
[16:56] <slangasek> teward: we're having to respin desktop images at the very last minute, but still on target for some value of "today"
[16:57] <teward> slangasek: cool.  I'm more concerned about the Server images here, but I thought I'd ask.  :)
[16:57] <slangasek> those images have no known blockers; but the release happens across all flavors at once
[17:02] <teward> indeed.  glad to know it's "in the works" either way :)
[17:03] <xnox> slangasek, time-sync.target only starts ntp daemon; but does not block until ntp sync is finished. we do start and reach time-sync.target; there is a new wait-time-sync.target with a wait-time-sync binary that blocks sysinit.target until NTP is *synced*
[17:03] <xnox> but that's only in v238 which we do not have yet.
[17:04] <slangasek> k
[17:04] <slangasek> so "yes in principle but doesn't help us today"
[17:04] <xnox> that
[17:04] <slangasek> anyway, I bumped the RT
[17:04] <xnox> thanks
[17:05] <xnox> slangasek, "local" time on machines appear to be in EDT timezone, and wrong time.
[17:06] <LocutusOfBorg> accepting vbox will make me so happy :)
[17:06] -queuebot:#ubuntu-release- Unapproved: virtualbox (bionic-proposed/multiverse) [5.2.10-dfsg-5 => 5.2.10-dfsg-6] (ubuntu-cloud) (sync)
[17:06] <LocutusOfBorg> also people upgrading and finding their saved snapshots working and not completely broken
[17:09] <slangasek> xnox: and did this just recently change on the machines, or did something change in the apt/archive behavior?
[17:13] -queuebot:#ubuntu-release- Unapproved: rejected virtualbox [source] (bionic-proposed) [5.2.10-dfsg-5ubuntu1]
[17:13] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox [sync] (bionic-proposed) [5.2.10-dfsg-6]
[17:23] <dpb1> slangasek: https://bugs.launchpad.net/subiquity/+bug/1766980 - comments 11 and particularly 12
[17:23] <ubot5`> Ubuntu bug 1766980 in subiquity "Failed to import ssh key" [High,Triaged]
[17:24] <doko> tjaalton: I assume tomcat8 will need a SRU. is in the kubuntu seed
[17:24] <xnox> slangasek, it has finally drifted far enough for apt to stop considering them as good enough drift
[17:24] <xnox> slangasek, apt was updated a while back; but this issue is reproducible on xenial guests too.
[17:24] <xnox> slangasek, so i'm suspecting HMC->lpar->nova->qemu side of things, rather than guest.
[17:25] <xnox> guest should be made more resilient against buggy hosts, and block on ntp sync. but both things should be fixed.
[17:29] <dpb1> ahasenack: at least we should add a release note for the ssh-import-id problem.  I think until we have a definitive error condition more than that, it's not worth escalating.
[17:29] <ahasenack> ok
[17:30] <dpb1> ahasenack: I suspect it doesn't happen on vms due to races, and wasn't caught there?
[17:30] <ahasenack> dpb1: oh, we were talking about two things then
[17:30] <ahasenack> a) this ssh key one for subiquity
[17:30] <ahasenack> b) the desktop bug people here have been rallying about
[17:30] <dpb1> ahasenack: no, I'm just talking subiquity
[17:31] <slangasek> xnox: indeed
[17:31] <slangasek> dpb1: thanks, reading
[17:32] <doko> slangasek: http://people.canonical.com/~ubuntu-archive/component-mismatches.txt is this already addressed?
[17:32] <slangasek> doko: yes, *twice*, I went to process it and found somebody else had already demoted them despite me commenting here
[17:33] <doko> I didn't
[17:40] <infinity> I did it ages ago.
[17:48] <infinity> slangasek: Oh, erk.  Did you do those demotions again after I did?
[17:48] <slangasek> infinity: possibly, considering I replied here 2 minutes after rbasak's comment saying I would take care of it
[17:49] <infinity> slangasek: I was probably already alt-tabbed and doing it.
[17:49] <infinity> slangasek: I'll copy them all back in after I've started image builds to undo double-override bain damage.
[17:49] <infinity> s/bain/brain/
[17:49] <slangasek> ok
[17:54] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (bionic-proposed/multiverse) [5.2.10-dfsg-5ubuntu18.04.2 => 5.2.10-dfsg-6ubuntu18.04.1] (no packageset)
[17:55] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-hwe [source] (bionic-proposed) [5.2.10-dfsg-6ubuntu18.04.1]
[17:59] <tjaalton> doko: hah, ok
[18:02] <stgraber> hmm, we're getting reports that dist-upgrading a clean Ubuntu 16.04 server to 18.04 leads to apparmor being removed, will try to reproduce now
[18:02] <stgraber> second such report in two days (heard of it because LXD isn't very happy when the apparmor tools are missing and apparmor isn't disabled by the user)
[18:03] <infinity> stgraber: That's a neat trick.
[18:03] <infinity> stgraber: Although, to be fair, almost nothing depends on it.
[18:04] <infinity> stgraber: And without using do-release-upgrade, I don't see why we'd expect ubuntu-standard to always stick aorund.
[18:04] <stgraber> sorry, wasn't clear, that was with do-release-upgrade
[18:04] <infinity> Oh, that's more sketchy.
[18:04] <stgraber> which is why I'm looking into it at all :)
[18:05] <stgraber> deploying clean 16.04 server on MAAS, will try to do-release-upgrade that and see if I still have apparmor, if not, that may be a bit of a problem
[18:15] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Bionic Final] has been updated (20180426)
[18:15] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Bionic Final] has been updated (20180426)
[18:15] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Bionic Final] has been updated (20180426)
[18:15] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Bionic Final] has been updated (20180426)
[18:15] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Bionic Final] has been updated (20180426)
[18:15] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Bionic Final] has been updated (20180426)
[18:18] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Bionic Final] has been marked as ready
[18:18] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Bionic Final] has been marked as ready
[18:21] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Bionic Final] has been updated (20180425.1)
[18:21] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Bionic Final] has been updated (20180425.1)
[18:22] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate amd64 [Bionic Final] has been updated (20180426)
[18:22] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate i386 [Bionic Final] has been updated (20180426)
[18:23] <dpb1> oooh
[18:23] <krosonp> wow it's really fun to watch this :)
[18:26] <acheronuk> Kubuntu marked ready in error. whoops :P
[18:26]  * acheronuk watches the world re-spin
[18:27] <acheronuk> so what QA do we do on these respins? sanity check on ubiquity and slideshows?
[18:28] <infinity> acheronuk: boot-install-reboot smoketest, make sure the slideshow kinda slideshows, and for gtkish flavours, check screen reader works.
[18:29] <acheronuk> right thanks
[18:32] <slangasek> infinity: is that only subiquity that's being rebuilt?  (looking at email about failed rebuild)  what's the trigger for that?
[18:32] <infinity> slangasek: oem-config is on literally every image.
[18:32] <infinity> How it failed, I don't know.
[18:34] <slangasek> infinity: squint
[18:36] <popey> stgraber: fwiw I just upgraded a clean 16.04.4 to 18.04 and apparmor is still there
[18:36] <dpb1> pshew
[18:36] <popey> stgraber: i have seen oddities (not this specifically) where people install from an older point release.
[18:36] <stgraber> popey: yeah, same with clean 16.04 server here, trying with one using the version of LXD our bug reporter used
[18:36] <popey> kk
[18:36] <stgraber> popey: so far, apt doesn't show me any weird removal so I expect that to work too
[18:37] <stgraber> which is good, that means we won't find ourselves with a good chunk of our server users running without apparmor
[18:37] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Bionic Final] has been updated (20180426)
[18:37] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Bionic Final] has been updated (20180426)
[18:37] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Bionic Final] has been updated (20180426)
[18:37] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Bionic Final] has been updated (20180426)
[18:38] <willcooke> dpb1, ^
[18:39] <ahasenack> does this mean the pending/ subdirectory contains these now?
[18:39] <infinity> ahasenack: http://cdimage.ubuntu.com/ubuntu-server/daily/20180426/
[18:39] <ahasenack> the timestamp there is odd, it's from yesterday still, albeit close to midnight
[18:39] <dpb1> ah
[18:40] <ahasenack> mh, daily, that's not subiquity, is it?
[18:42] <dpb1> daily-live is
[18:42] <stgraber> popey: yeah, install with LXD 2.21 works fine too, apparmor is still there
[18:42] <popey> odd, does something conflict with apparmor maybe?
[18:44] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Bionic Final] has been updated (20180426)
[18:44] <ogra_> yeah, perhaps something they installed on 16.04
[18:44] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Bionic Final] has been updated (20180426)
[18:44] <stgraber> possibly, apparmor is a recommends of ubuntu-standard, so I can see how it may be removed to satisfy the upgrade, but I'd need to know more about what that user might have done differently first...
[18:44] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Bionic Final] has been updated (20180426)
[18:44] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Bionic Final] has been updated (20180426)
[18:46] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Bionic Final] has been updated (20180426)
[18:46] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop i386 [Bionic Final] has been updated (20180426)
[18:46] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Bionic Final] has been updated (20180426)
[18:46] <willcooke> pizza has arrived
[18:46] <popey> \o/
[18:47] <bdmurray> wait where?
[18:47] <apw> in my hand ?
[18:48] <xnox> bdmurray, it is good
[18:51] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Bionic Final] has been updated (20180426.1)
[18:51] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Bionic Final] has been updated (20180426.1)
[18:54] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Bionic Final] has been updated (20180426)
[18:54] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Bionic Final] has been updated (20180426)
[18:54] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Bionic Final] has been updated (20180426)
[18:54] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Bionic Final] has been updated (20180426)
[18:58] <valorie> there we are
[18:58] <willcooke> \m/
[18:58] <Laney> SHIP. IT.
[18:59] <krosonp> !press the button!
[18:59] <ubot5`> krosonp: I am only a bot, please don't think I'm intelligent :)
[19:00] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Bionic Final] has been updated (20180426)
[19:00] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD i386 [Bionic Final] has been updated (20180426)
[19:00] <valorie> zsyncing....
[19:00] <doko> mehh, woo build on arm64 restarted?
[19:01] <slangasek> "woo build"?
[19:01] <Laney> https://launchpad.net/ubuntu/+source/woo/1.0+dfsg1-2ubuntu1/+build/14797731 ?
[19:04] <popey> BIOS boot 20180426 ubuntu image, chose f4 screen reader, try ubuntu. I get no voices.  Audio works - I get drums on launching ubiquity
[19:04] <popey> Is there some additional key-combo to make it speak to me?
[19:04] <jdstrand> stgraber, infinity: fyi, I've tested this myself and can't reproduce. note that apparmor did introduce a Breaks: media-hub, mediascanner2.0, messaging-app, webbrowser-app
[19:05] <jdstrand> none of that would be on server though
[19:05] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi2 [Bionic Final] has been updated (20180426)
[19:06]  * flocculant waits for popey's answer
[19:06]  * sil2100 tests studio
[19:07] <willcooke> popey, alt + super + s
[19:07] <popey> ok, that poked it
[19:07] <willcooke> phew
[19:08] <flocculant> willcooke: which does nothing on xubuntu
[19:08] <flocculant> not sure we've ever tested it
[19:10] <Laney> that specific code path
[19:10] <Laney> is for gnome
[19:10] <Laney> not sure what xfce uses, maybe something different
[19:11] <flocculant> Laney: oh right - I just read the testcase - will have to investigate that at some point and deal with the testcase
[19:13] <ogra_> jdstrand, heh, you have high confidence in server users :)
[19:14] <ogra_> .oO( oh. that media-hub thing could be helpful for my streaming server )
[19:22] <popey> hm, can't get my thinkpad to boot this usb in uefi mode. black screen. maybe pilot error.
[19:22] <willcooke> Use cases all passed on what was the crashy hardware here
[19:23] <popey> i keep getting grub
[19:23] <willcooke> with the options of try install etc?
[19:23] <popey> ya
[19:23] <willcooke> thats normal.  It should boot to live from there if you leave it, or select try
[19:24] <popey> We don't show the super menu thing in uefi mode?
[19:24] <willcooke> no because UEFI
[19:24] <jibel> translations of the slideshow are correct in French.
[19:24] <popey> ok, screen reader works here in both uefi and bios mode
[19:24] <Laney> fantastique!
[19:27] <jdstrand> stgraber, infinity: fyi, I tried a server install with media-hub installed (one of the Breaks from apparmor): apt-get upgrade has apparmor correctly held, apt-get dist-upgrade has it upgrade with media-hub removal, do-release-upgrade -d has it upgrade with media-hub removal
[19:27] <jdstrand> I think we need to put this in the 'needs info' column
[19:28] <stgraber> jdstrand: yeah, definitely. If we get more such reports we'll try to track down what they have in common
[19:28] <flocculant> Wimpress: running 64bit install for you screen reader working
[19:29] <popey> https://usercontent.irccloud-cdn.com/file/sorZj2gJ/IMG_20180426_202857.jpg
[19:29] <popey> That's annoying.
[19:31] <jibel> popey, do you have an existing operating system on this machine?
[19:31] <popey> yes
[19:31] <popey> windows 10 on another ssd
[19:32] <sil2100> popey: ok, that's ugh, a known bug sadly
[19:32] <jibel> popey, likely bug 1766945
[19:32] <ubot5`> bug 1766945 in ubiquity (Ubuntu) "(EFI on top of legacy install) choosing "replace" or "resize" options in partitioning may lead to an install failure" [Undecided,New] https://launchpad.net/bugs/1766945
[19:33] <sil2100> Partially caused by my removal of the partman-efi force_uefi warning
[19:34] <sil2100> Since that's this case I didn't taste
[19:35] <sil2100> s/taste/test
[19:35] <popey> ok
[19:35] <abdelraouf> popey: can you disable UEFI support
[19:35] <abdelraouf> from bios?
[19:35] <popey> i jhave already tested with uefi off
[19:36] <popey> now I'm testing with it on, but can't.
[19:36] <popey> but we know that's a known bug now. thanks seb128 jibel
[19:38] <jibel> I did a bunch of smoke tests with 26: dm -> live session -> install, dm -> install, syslinux -> live -> install, syslinux -> install. Tried with and without orca and also a series of dm -> live boots. nothing to report, ubuntu desktop looks fine.
[19:38] <Laney> ♥
[19:38] <willcooke> thanks jibel
[19:38] <willcooke> jibel, could you comment on the bug to that effect?
[19:39] <jibel> yes
[19:39] <Laney> 🆒
[19:39] <popey> testing MATE i386 and amd64
[19:40] <flocculant> Wimpress: did 64 bit screen reader for you
[19:40] <flocculant> wxl tsimonq2 - doing 64 bit lubuntu
[19:41] <popey> flocculant: yes, amd64 mate screen reader worked here
[19:41] <flocculant> popey: and here
[19:41] <willcooke> thanks ahasenack
[19:42] <flocculant> no idea how to screen reader in lubuntu - just testing it installs
[19:44] <popey> flocculant: does it not trigger from the menu at boot?
[19:44] <flocculant> seemingly not
[19:44] <flocculant> did the F5 choose screen reader - like I did for us (xubuntu)
[19:45] <flocculant> same result - silence
[19:46] <sil2100> Studio looks good (on a kvm)
[19:46] <popey> flocculant: which iso did you grab?
[19:46] <flocculant> wxl tsimonq2 - lubuntu slideshow, browse the web slide - might be useful to update that pic from 16.10 ;)
[19:46] <popey> i only see alternate isos
[19:47] <flocculant> http://iso.qa.ubuntu.com/qatracker/milestones/389/builds/171117/testcases
[19:47] <flocculant> definitely on the tracker
[19:47] <popey> ah got it
[19:47] <popey> daily-live - duh
[19:47] <flocculant> oh really? I see it on Bionic Final page here
[19:49] <popey> ok, mate i386 and amd64 are good here.
[19:50]  * flocculant is doing things he can zsync quickly
[19:50] <sil2100> Trying budgie now
[19:50] <jibel> budgie and kylin, anyone ?
[19:50] <sil2100> i386
[19:51] <flocculant> sil2100: I'm on the way to having budgie 64bit
[19:51] <jibel> k, syncing kylin
[19:51] <ahasenack> I don't know how to test the screen reader, I have never used it before
[19:51] <flocculant> at 835.2 kBps :|
[19:51] <ahasenack> in legacy boot, I see "f5", used that, selected screen reader, and then hit "try ubuntu" in the menu
[19:51] <ahasenack> but nothing is different
[19:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Bionic Final] has been updated (20180426)
[19:52] <valorie> ooooo, it rebooted ok!
[19:52] <valorie> \o/
[19:53] <popey> jibel: need me to do one?
[19:53] <acheronuk> valorie: oem?
[19:53] <sil2100> flocculant: excellent! I'm testing i386 in the meantime, thanks!
[19:54] <sparkiegeek> ahasenack: if you hit Alt + Super + S it enables the screen reader
[19:54] <jibel> popey, kylin i386would be nice
[19:54] <flocculant> sil2100: no problem
[19:54] <popey> jibel: on it
[19:55] <jibel> downloading is slow
[19:55] <valorie> oem now
[19:55] <flocculant> jibel: indeed it is - got worse here in the last 30 minutes
[19:55] <valorie> I missed the grub bit so went ahead and did two others
[19:55] <popey> yeah, getting 1-2MB/s now
[19:56] <flocculant> yea - jumped - at 93% for budgie 64 bit
[19:57] <Wimpress> UbuCon ninjas are on it like a bonnet
[19:58] <ahasenack> sparkiegeek: indeed it does, thanks
[20:00] -queuebot:#ubuntu-release- Unapproved: mozjs24 (xenial-proposed/universe) [24.2.0-3ubuntu2 => 24.2.0-3ubuntu2.1] (ubuntugnome)
[20:00] <flocculant> budgie screen reader works
[20:01] <JamieBennett> Anyone tested in VMWare?
[20:01] <popey> Not what you asked, but I test in VirtualBox
[20:01] <flocculant> though I've turned it off - screen reader and Ozric Tentacles is a bad combo
[20:01] <flocculant> and I'm doing these in kvm
[20:02] <jibel> JamieBennett, I did
[20:02] <jibel> in vmplayer
[20:02] <JamieBennett> VMWare Fusion 8.x -> "Try Ubuntu" -> Screen Reader on -> black screen for 5 mins
[20:03] <jibel> JamieBennett, how much memory did you allocate to your vm ?
[20:03] <JamieBennett> (testing on Mac)
[20:03] <JamieBennett> 1GB
[20:03] <jibel> JamieBennett, be a bit more generous
[20:03] <popey> Hah. is it 2012?
[20:03] <jibel> JamieBennett, 1.5 is the minimum
[20:03] <JamieBennett> Sorry, 1GB RAM
[20:03] <Wimpress> You'd get away with 1GB with Ubuntu MATE ;-)
[20:03] <Kamilion> i can't even get most of the flavors to boot with 1GB of ram
[20:03] <JamieBennett> 20GB disk
[20:03] <flocculant> lol
[20:04] <Kamilion> i have to crank up to 2048MB in vmware for every new VM I create, hehe
[20:04]  * JamieBennett tries again
[20:04] <flocculant> Kamilion: I wondered sometime ago why xubuntu iso was like treacle - I had been testing something, and it was set at 768Mb
[20:04] <flocculant> it 'worked'
[20:05]  * popey gets out his Thinkpad 380XD with 32MB RAM for ISO testing..
[20:05]  * flocculant doesn't work for Canonical :p
[20:05] <Kamilion> I said most of the flavors
[20:05] <Kamilion> xubuntu and lubuntu are the ones that generally work for 1GB or less
[20:06] <Kamilion> ubuntu-studio has always been annoying in it's thirst for RAM form e :D
[20:06] <ogra_> popey, ubuntu-core FTW !
[20:06] <flocculant> sil2100: budgie 64bit done
[20:06] <JamieBennett> jibel: problem is that VMWare defaults to 1GB
[20:06] <ogra_> ah, damn, we dont have isos
[20:06] <popey> ogra_: yeah, was about to mention, lack of installer...
[20:06] <JamieBennett> ogra_: we have UC16 images
[20:06] <popey> No. "dd" is not an installer.
[20:06] <ogra_> yeah, ... that will come :)
[20:06] <jibel> JamieBennett, so do virt-manager
[20:07] <sil2100> i386 almost done
[20:07] <ogra_> popey, as a frontend to dd ;)
[20:08] <JamieBennett> ogra_: etcher.io is just a frontend to dd but it does look pretty
[20:08] <jdstrand> stgraber, infinity: for completeness on a 16.04 desktop install with media-hub, mediascanner2.0, webbrowser-app and messaging-app (ie, all the new Breaks in bionic), apt-get upgrade correctly holds apparmor, apt-get dist-upgrade upgrades apparmor and removes those packages, and update-manager -d upgrades apparmor and removes those packages
[20:08]  * popey guess which of the various chinese glyphs in the installer enable screen reader
[20:08] <ogra_> JamieBennett, yeah, we can have the same for code one day :)
[20:09] <jdstrand> stgraber, infinity: again, needs info. doesn't seem to be related to the added breaks, whatever it is
[20:09] <flocculant> anything else need doing?
[20:09] <ogra_> jdstrand, stgraber, perhaps some broken PPA package the user added ?
[20:09] <flocculant> other than Chinese ...
[20:09] <sil2100> i386 is good
[20:09] <sil2100> fossfreedom: thanks for testing as well!
[20:09] <jdstrand> ogra_: yeah, that is what I was thinking
[20:09] <popey> Uh, screen reader didnt start on kylin i386
[20:10] <popey> dunno how to poke it.
[20:10] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Bionic Final] has been marked as ready
[20:10] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Bionic Final] has been marked as ready
[20:10] <tsimonq2> I'm about to leave for Milwaukee then will be on a plane to Seattle. Once Lubuntu is ready, don't wait on me to mark things as ready please.
[20:11] <flocculant> tsimonq2: looks like you've got tests on all types 32/64/alternate/desktop
[20:12] <JamieBennett> jibel: OK, 2GB did it, no blank screen now
[20:13] <stgraber> jdstrand, ogra_: current suspicion is that the "clean" install from that user came from hetzner.de and that they messed something up... they had apparmor installed for sure but maybe hetzner didn't have ubuntu-standard on there for some reason.
[20:13] <stgraber> the next LXD SRU will add a recommends on apparmor, that may help with such weird systems
[20:13] <jdstrand> stgraber: nice
[20:15] <ogra_> given how important apparmor got now it should probably be moved up a little from recommends
[20:15] <JamieBennett> Anyone got the installer showcase to disappear during install in a live session
[20:15] <popey> which iso you using JamieBennett ?
[20:15] <JamieBennett> plain Ubuntu 18.04 as linked above
[20:16] <JamieBennett> ah
[20:16]  * sil2100 is testing kylin amd64 now
[20:16] <JamieBennett> "System program problem detected"
[20:16] <popey> "Insufficient RAM" :)
[20:16] <jibel> JamieBennett, bug 1751252
[20:16] <ubot5`> bug 1751252 in ubiquity (Ubuntu Bionic) "ubiquity crashed with signal 5 in _XEventsQueued()" [High,Triaged] https://launchpad.net/bugs/1751252
[20:16] <JamieBennett> waiting for the report to be generated
[20:16] <jibel> compare the stack traces once it's retraced
[20:17] <JamieBennett> jibel: looks like that one, yes
[20:19] <JamieBennett> jibel: old bug?
[20:20] <jibel> not old, it started in bionic
[20:20] <jibel> willcooke, ^^ something to investigate
[20:20] <JamieBennett> jibel: old as in weeks not today
[20:21] <jibel> JamieBennett, yes, early 2018
[20:21] <JamieBennett> it looks like it hung trying to report the bug :(
[20:21] <JamieBennett> or it is very ssssslllllllllllooooooooooooooooooowwwwwwwwww
[20:21] <Kamilion> Does *ANYONE* test if TORAM=Yes works, or is that considered to be 'if it works it works, if it breaks, you get to keep both pieces' ?
[20:22] <Kamilion> I'm not saying it's broken, I'm just querying if I'm the only one who actually uses/tests with it
[20:24] <jibel> ubuntukylin amd64 is ok. First slide of the slideshow is not fully translated though
[20:25] <JamieBennett> jibel: probably completely unrelated but did you turn screen reader off half way through install in your testing?
[20:26] <jibel> JamieBennett, I didn't
[20:27] <JamieBennett> jibel: OK
[20:27] <popey> jibel: how did you trigger screen reader in kylin?
[20:27]  * JamieBennett tries that again
[20:27] <JamieBennett> alt, super, s?
[20:27] <popey> didnt work on the i386 image
[20:27] <jibel> popey, I didn't try the screen reader, they use their own and don't know how to activate it. But they hit the bug without it
[20:28] <popey> oh ok
[20:32] <Wimpress> Has anyone tried an OEM install?
[20:32] <willcooke> Wimpress, I have on ubuntu desktop
[20:32] <willcooke> doing free software now
[20:33] <jibel> Wimpress, i did
[20:36] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate amd64 [Bionic Final] has been marked as ready
[20:36] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Bionic Final] has been marked as ready
[20:36] <sil2100> Testing subiqity now
[20:36] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Bionic Final] has been marked as ready
[20:36] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate i386 [Bionic Final] has been marked as ready
[20:36] <sil2100> jibel: you testing kylin i386 now?
[20:36] <sil2100> Since I saw you also did kylin
[20:36] <jibel> sil2100, I did 64bit
[20:36] <popey> i did kylin i386
[20:38] <sil2100> popey: <3
[20:38] <sil2100> jibel: <3
[20:39] <willcooke> jibel, do you have a vm you can test "reuse home" on?
[20:40] <jibel> willcooke, yes
[20:40] <jibel> just did
[20:41] <willcooke> <3
[20:42] <flocculant> I assume I can go rest a bit now then :p
[20:42] <cjwatson> doko: woo was an accidental manual cancellation (the canceller mistakenly thought it had hung)
[20:42] <willcooke> jibel, looks like we can mark ubuntu desktop ready
[20:43] <willcooke> Laney, you want the honour? ^
[20:43] <jibel> Done
[20:44] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Bionic Final] has been marked as ready
[20:44] <jibel> \o/
[20:44] <Laney> ⛔
[20:44] <popey> I also tested the oem install, worked fine.
[20:45] <sil2100> fossfreedom: is budgie ready?
[20:45] <sil2100> fossfreedom: can you trigger it on the isotracker?
[20:46] <fossfreedom> will do - one last test 64bit, partitioning, no network - just a few minutes sil2100
[20:46] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Bionic Final] has been marked as ready
[20:46] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Bionic Final] has been marked as ready
[20:47] <sil2100> fossfreedom: thanks!
[20:50] <willcooke> valorie, you need any help with kubuntu 386?
[20:50] <valorie> oh it would be great if someone did one
[20:50] <willcooke> testers.... away
[20:50]  * willcooke downloads
[20:50]  * valorie is a little shaken up and need to catch my breath for a sec
[20:51] <popey> any others need doing?
[20:51] <acheronuk> I'm doing Kubuntu i386 oem, but can only do a VM test with that
[20:52] <popey> acheronuk: what do you need me to do?
[20:54] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Bionic Final] has been marked as ready
[20:54] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop i386 [Bionic Final] has been marked as ready
[20:54] <willcooke> looks like kylin need some i386 tests doing too
[20:55] <acheronuk> popey: probably nothing, unless you feel like doing a belt and braces re-test of i386 oem on real hardware. thanks :)
[20:55] <jibel> willcooke, popey did it
[20:55] <sil2100> Subiquity looks good
[20:55] <sil2100> mwilson-e: ^
[20:55] <popey> willcooke: TRUE
[20:55] <popey> acheronuk:
[20:55] <sil2100> mwilson-e: (nvm)
[20:55] <jibel> popey, can you update the tracker?
[20:55] <sil2100> mwilson-e: pinged wrong person! Sorry!
[20:55] <sil2100> mwhudson: ^
[20:56] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate amd64 [Bionic Final] has been updated (20180426)
[20:56] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Bionic Final] has been updated (20180426)
[20:56] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Bionic Final] has been updated (20180426)
[20:56] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate i386 [Bionic Final] has been updated (20180426)
[20:57] <sil2100> mwhudson: will you mind if we mark subiquity as ready?
[20:57] <popey> jibel: done
[20:57] <jibel> thx
[20:57] <mwhudson> sil2100: ask slangasek!
[20:57] <sil2100> !
[20:58] <sil2100> slangasek: can we mark subiquity as good? I tested amd64 on bios and uefi on kvm (so, well, limited testing)
[20:58] <sil2100> But seeing the delta for these images, I'd think that's enough
[20:59] <flocculant> doing a quick manual test for lubuntu
[21:00] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Bionic Final] has been marked as ready
[21:00] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Bionic Final] has been marked as ready
[21:00] <mwhudson> sil2100: the point being there might be a new subiquity image coming
[21:01] <sil2100> mwhudson: wha?
[21:01] <sil2100> mwhudson: why? Is  there something we do not know and should?
[21:01] <sil2100> mwhudson: is there a regression in the newly respun image?
[21:01] <mwhudson> sil2100: https://bugs.launchpad.net/subiquity/+bug/1766980
[21:01] <ubot5`> Ubuntu bug 1766980 in subiquity "Failed to import ssh key" [High,Triaged]
[21:02] <mwhudson> sil2100: at least subiquity is a snap...
[21:02] <sil2100> Isn't it a bit too late for a subiquity image by now? We're already late with everything
[21:03] <sil2100> We didn't know about this one before it seems
[21:03] <slangasek> sil2100, mwhudson: ! don't ask me either, ask the server team! :)
[21:03] <sil2100> Was it linked in the isotracker?
[21:04] <mwhudson> sil2100: it was but i think it's priority was misdiagnosed at the time
[21:04] <mwhudson> slangasek: heh
[21:05]  * slangasek tags in dpb1
[21:05] <infinity> mwhudson: Ugh.
[21:05] <sil2100> eh
[21:05] <sil2100> mwhudson: ok, since subiquity is a snap I guess we could live through that, but it would have to land ASAP
[21:05] <sil2100> Like, 2 hours ago at best
[21:05] <slangasek> infinity, sil2100, mwhudson: it's release-noted and we're not holding you up for it
[21:05] <dpb1> slangasek: +1, post-release is fine
[21:06] <mwhudson> oh
[21:06] <dpb1> slangasek: we have updated the release-notes page already
[21:06]  * mwhudson dials down the panic slightly
[21:07] <sil2100> phew, thank you
[21:07] <marathone> !isitout
[21:07] <ubot5`> Not yet!
[21:07] <slangasek> mwhudson: apologies; I thought it was important to work through characterizing the bug and come up with a plan for fixing but I didn't ever think it was realistic to have it fixed in GA and should have said
[21:08] <mwhudson> slangasek: that'll learn me for being too optimistic
[21:08] <flocculant> sil2100: you want to know release note place for xubuntu - it's different from beta one now we're releasing -  https://xubuntu.org/news/xubuntu-18-04-release/
[21:08] <flocculant> infinity: or you ^^
[21:08] <infinity> flocculant: The main release notes should link to it.
[21:09] <flocculant> infinity: aah yes - it does
[21:11] <flocculant> been talking to tsimonq2 - he's ok for it to be marked ready, so I did for him
[21:11] <sil2100> \o/
[21:12] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate amd64 [Bionic Final] has been marked as ready
[21:12] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Bionic Final] has been marked as ready
[21:12] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Bionic Final] has been marked as ready
[21:12] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate i386 [Bionic Final] has been marked as ready
[21:13] <flocculant> well thanks eveyone for the fun ride this week - but I'm off up the wooden hill
[21:13] <sil2100> mwhudson, slangasek: soo, with all that, should we mark subiquity as ready?
[21:13] <slangasek> sil2100: you're still talking to !server team ;)
[21:13] <flocculant> I've marked mine too obviously
[21:13] <slangasek> sil2100: dpb1 is the authority on this
[21:14] <sil2100> bluesabre: ping!
[21:14] <sil2100> dpb1: ^ ;)
[21:14] <flocculant> sil2100: what do you need bluesabre for?
[21:15]  * dpb1 reads
[21:15] <flocculant> sil2100: if it's anything Xubuntuish - I've done what needs doing afaik
[21:15]  * flocculant hangs about a bit longer
[21:15] <sil2100> Ah, it's marked, sorry
[21:15] <sil2100> bluesabre: unping
[21:15] <flocculant> :)
[21:16] <flocculant> sil2100: you know I'm in the Xubuntu release team?
[21:16] <flocculant> if you didn't you do now lol
[21:16] <rpcruz> !isitout
[21:16] <ubot5`> Not yet!
[21:16] <Kamilion> i ran into that ssh key bug myself, failed to import my keys from launchpad/kamilion and github/kamilion.
[21:17] <dpb1> slangasek: the jenkins jobs are all green
[21:17] <slangasek> dpb1: so you're happy to release the amd64 subiquity image?
[21:17] <slangasek> dpb1: the alternate server images have some un-finished tests also; should we be blocking on these?
[21:18] <sil2100> ErichEickmeyer: ping! Are you around by any chance?
[21:18] <valorie> Kubuntu is https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes/Kubuntu
[21:18] <popey> acheronuk: confirmed oem install of 386 kubuntu worked fine :)
[21:18] <sil2100> ErichEickmeyer: we did some sanity-testing of studio bionic on both arches, do you think we can proceed with marking those as ready?
[21:19] <acheronuk> popey: fantastic. thanks
[21:20] <flocculant> sil2100: ovenwerks (studio guy) was trying to raise erich at 21:53 - no reply in their dev channel yet
[21:20] <sil2100> flocculant: thanks for the info
[21:20] <flocculant> np
[21:21] <flocculant> from that channel I would suspect they'd be happy to mark it *shrug*
[21:22]  * flocculant really goes now - thanks to you all - happy release :)
[21:22]  * Kamilion starts grabbing .torrent files to seed
[21:22] <sil2100> dpb1: we good to mark subiquity as ready?
[21:23] <dpb1> sil2100: we are good on subiquity
[21:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Bionic Final] has been marked as ready
[21:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Bionic Final] has been marked as ready
[21:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Bionic Final] has been marked as ready
[21:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Bionic Final] has been marked as ready
[21:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Bionic Final] has been marked as ready
[21:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Bionic Final] has been marked as ready
[21:24] <Skotsj> Woo
[21:24] <sil2100> dpb1: <3
[21:24] <valorie> release team: <3
[21:25] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Bionic Final] has been marked as ready
[21:25] <krosonp> thank you guys for the hard work!
[21:26] <willcooke> any kylin devs online in this channel/
[21:26] <slangasek> xnox: are you available to talk s390x?
[21:26] <willcooke> ?
[21:26] <xnox> slangasek, yes.
[21:26] <xnox> slangasek, online installs are all good.
[21:26] <sil2100> acheronuk: are you around by any chance?
[21:26] <slangasek> xnox: none of the tests are marked off on the iso tracker
[21:26] <xnox> slangasek, and the offline one should be working fine, but i appear to be failing to point it to the offline export of the .iso to complete offline install
[21:27] <xnox> (it is failing to find the kernel.... but it looks like i'm exporting the iso badly)
[21:27] <acheronuk> sil2100: yep
[21:27] <xnox> slangasek, i cannot mark things "ready"
[21:27] <slangasek> xnox: and what are the tests you actually run, since I expect the default ones for ubuntu server don't map correctly to the s390x install paths?
[21:27] <slangasek> xnox: but you can report test results and there are none reported against this image
[21:28] <jibel> willcooke, it's a bit early for kylin
[21:29] <sil2100> acheronuk: ah, actually, I found what I needed, nvm! Sorry to bother
[21:29] <willcooke> jibel, yeah figures.  I think we can mark them ready.
[21:29] <slangasek> dpb1: ^^ seems we don't yet have a confirmed good run of the s390x iso
[21:29] <willcooke> jibel, sil2100 - doing one more 64bit test on Kylin
[21:33] <jibel> willcooke, they didn't report any critical bug apparently but it's hard to tell everything they reported is untriaged
[21:33] <dpb1> slangasek: then if we can't release the others, we need to wait for that testing.
[21:34] <jibel> willcooke, I'd rather wait until they wake up.
[21:34] <willcooke> jibel, we're testing and are going to call it good I think
[21:35] -queuebot:#ubuntu-release- Builds: Netboot amd64 [Bionic Final] has been marked as ready
[21:35] -queuebot:#ubuntu-release- Builds: Netboot i386 [Bionic Final] has been marked as ready
[21:35] -queuebot:#ubuntu-release- Builds: Netboot s390x [Bionic Final] has been marked as ready
[21:35] <willcooke> loving that animated shutdownb scren
[21:35] <jibel> willcooke, for example bug 1766499
[21:35] <ubot5`> bug 1766499 in Ubuntu Kylin "Unable to find http://archive.ubuntukylin.com:10006/ubuntukylin bionic Release" [Undecided,New] https://launchpad.net/bugs/1766499
[21:36] <sil2100> Marking studio, looks sane enough to me (and no contact with the release manager)
[21:36] <sil2100> ErichEickmeyer: ^ hope you don't mind
[21:36] <jibel> willcooke, they say it is not fixed and the bug suggests they cant update the system
[21:37] <willcooke> jibel, that won't be affected by anything that has changed today
[21:37] <slangasek> xnox: is the "failing to point to iso export" a hard failure?
[21:37] <SlidingHorn> sil2100: last I saw someone report in -devel, it was working
[21:37] <jibel> willcooke, which does not mean the image is good
[21:37] <SlidingHorn> I'm not authorized to give a green light though
[21:37] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Bionic Final] has been marked as ready
[21:37] <sil2100> SlidingHorn: I guess it's enough for us (being this late)
[21:37] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD i386 [Bionic Final] has been marked as ready
[21:39] <willcooke> jibel, not iso testing though
[21:39] <JamieBennett> willcooke: are you happy to release?
[21:39] <willcooke> JamieBennett, yeah, Ubuntu Desktop is marked ready
[21:39]  * mwhudson gets on a bus for a bit
[21:40] <willcooke> JamieBennett, I think 5 more mins are everything will be marked ready
[21:40] <JamieBennett> OK, we can fix any issues afterwards in .1 or even before, lets give the world Ubuntu 18.04
[21:41] <jibel> willcooke, I just verified and the kylin apt source on the iso is wrong. Not sure they'll want to release with this kind of issue.
[21:41] <Laney> They fix it by fixing their archive
[21:41]  * JamieBennett nods
[21:45] <xnox> slangasek, so, cause the time was wrong, and d-i seems to not have did ntp sync.... but with the right clock offline install works too, so s390x server is awesome.
[21:47] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Bionic Final] has been marked as ready
[21:47] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Bionic Final] has been marked as ready
[21:48] <slangasek> xnox: thanks. you'll post this result to the iso tracker?
[21:48] <xnox> slangasek, yes, offline test case pass.
[21:50] <dpb1> OK
[21:50] <dpb1> slangasek: we are a go on all required server testing
[21:51] <willcooke> \m/
[21:51] <slangasek> dpb1: marked ready for release
[21:51] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Bionic Final] has been marked as ready
[21:51] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Bionic Final] has been marked as ready
[21:51] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi2 [Bionic Final] has been marked as ready
[21:51] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Bionic Final] has been marked as ready
[21:51] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Bionic Final] has been marked as ready
[21:52]  * JamieBennett has a sigh of relief
[21:52] <JamieBennett> Super proud of everyone involved, well done!
[21:52] <Odd_Bloke> slangasek: infinity: Are we good to start pushing out cloud images?
[21:54] <infinity> Odd_Bloke: Official release will be right around midnight London time, but if you need some lead time pushing, push away.
[21:54] <willcooke> popey, Wimpress - thanks for your testing skillz
[21:54] <popey> no problemo
[21:54] <Odd_Bloke> infinity: Ack.
[21:54] <Wimpress> Something something Cuba Libre
[21:55] <Wimpress> #isitoutyet
[22:00] <ogra_> ot yet!
[22:00] <ogra_> +N
[22:00] <ogra_> (bah)
[22:07] <LocutusOfBorg> infinity, please unblock virtualbox and virtualbox-hwe whenever possible?
[22:12] <infinity> LocutusOfBorg: Done.
[22:33] <sil2100> Wimpress: you'll be updating https://ubuntu-mate.org/download/ to include bionic soonish, right?
[22:35] <popey> it is updated
[22:35] <popey> i clicked 64-bit and got a page offering bionic
[22:37] <ogra_> http://i.imgur.com/YsbKHg1.gifv
[22:38] <popey> free wifi in a car park of a pub apparently
[22:44] <sil2100> wow, magic indeed
[22:44]  * sil2100 probably had some old cache
[23:02] <willcooke> thanks everyone
[23:03] <davidcalle> Bravo
[23:04] <sil2100> \o/
[23:04] <freehUgsz> CONGRATS
[23:05] <popey> woot
[23:05] <pietroalbini> \o/
[23:05] <kyrofa> Congratulations everyone, thanks for all the hard work
[23:10] <valorie> yay!!!!!!!!!!!!!!!
[23:11] <valorie> thank you to all of you super people who make this happen
[23:11] <sparkiegeek> \o/
[23:11] <Laney> 🍑
[23:14] -queuebot:#ubuntu-release- Builds: 35 entries have been added, updated or disabled
[23:17] <teward> yay for release!  thank you everyone for your efforts :D
[23:18] <dpb1> nice work guys
[23:18] <dpb1> <clapping emoji>
[23:19] <dpb1> 👏 👏 👏
[23:19] <dpb1> there we go
[23:19] <willcooke> 👏
[23:19] <willcooke> bah
[23:19] <willcooke> you beat me
[23:19] <dpb1> willcooke: I had emoj installed (snap) !
[23:19] <knome> oh gosh emoji, i must part ;)
[23:19] <willcooke> harsh
[23:20] <mwhudson> haha
[23:20] <Laney> 👋
[23:20] <dpb1> an actual emoji-ragequit.  i love it.
[23:20] <sarnold> ~fifteen years ago I helped organize IRC "conferences" on a predominately spanish-speaking educational irc network ..
[23:20] <sarnold> after every presentation there were *hundreds* of lines of
[23:20] <sarnold> plas plas plas plas plas plas plas plas plas plas
[23:20] <sarnold> in glorious colours
[23:21] <sarnold> a few emojies feels a bit restrained :D
[23:21] <popey> 💃
[23:22] <Laney> congratulations to all the ubuntu developers on a great 18.04 LTS!!!!!!!
[23:22] <sil2100> WOW
[23:22] <Laney> 😠
[23:23] <sil2100> infinity doesn't appreciate cute...
[23:23] <sil2100> Ok, I think I go EOD to bed
[23:23] <sil2100> o/
[23:23] <sarnold> Laney: *thats* the stuff!
[23:26] <willcooke> g'night all
[23:27] <DalekSec> Laney: Haha!  Nice job.
[23:27] <Laney> :D
[23:27] <Laney> sarnold: That's a script I never get to use
[23:27] <Laney> like the kenny one
[23:27] <Laney> mfmppfppfmpmpppmffmfmmfpfmp!
[23:28] <sarnold> lol
[23:34] <tsimonq2> hahahaha
[23:34] <valorie> are you in the airport, tsimonq2?
[23:35] <tsimonq2> Boarding.
[23:35] <tsimonq2> I barely made it!
[23:36] <acheronuk> thank you everyone. :)
[23:36] <tsimonq2> Ditto.
[23:36] <tsimonq2> Nice job y'all.
[23:36] <tsimonq2> 😃😃😃😁😁😁😁😁😁😁
[23:37] <tsimonq2> Now we wait for the Calculating Camel to be announced... 😁
[23:43] <valorie> carrot
[23:43] <valorie> gonna be carrot, I just know
[23:44] <valorie> although Chthonic Cthulhu is the best I've heard so far
[23:49] <infinity> valorie: I read that as Catholic Cthulhu, which would also be alright.
[23:50] <valorie> lol
[23:50] <valorie> + + +
[23:52]  * infinity closes bionic in Launchpad.
[23:54] <teward> to be honest, y'all just made me laugh with your last few messages, and I thank you for that since today's been a chaotic day that hasn't had me smile or laugh.  :)
[23:57] <slangasek> teward: then I'm sure you must be looking forward to Chaotic Chinchilla
[23:58] <teward> heh
[23:59] <acheronuk> usually the meta on changelogs.ubuntu.com gets updated after half a day or so? was wondering when, given the lateness now?