[00:00] ack [00:00] cyphermox: Unless you really feel like documenting every bug fixed since wily. [00:00] not especially [00:00] ;) [00:00] I want to be able to use my computer to test tomorrow [00:00] cyphermox, jderose Doing an OEM install. Ubiquity doesn't prompt to join WiFi networks. So proceeds without a connection. [00:00] and you might want LP to not decide I'm evil and never respond to me ever again [00:00] flexiondotorg: hmm, that was working just a week or so ago [00:00] flexiondotorg: you should see nm-applet [00:01] * infinity crashes. [00:01] The applet is there. [00:01] And works. [00:01] However, Ubiquity itself no longer prompts for join a wireless network. [00:02] When wifi is available. [00:04] d'oh [00:05] I should unxz that image before I write it shouldn't I? :) [00:05] flexiondotorg: I don't know that oem-config ever did [00:07] cyphermox, Yeah, it did. Both during the initial install and also in after it had been prepared. [00:08] VirtualBox has a regression. [00:09] cyphermox: it definitely used to prompt you to join the wifi network, although it was broken in 15.10. but it was working in 16.04 not that long ago (it was at most 2 weeks ago when i last tested) [00:09] Had this in 14.10 where the graphics are screwed in the guest and you have to switch tty and back to correct the corruption. [00:09] ok well then oem-config has been broken this way since before wily, not critical enough to scramble to fix and respin the images [00:10] jderose: weird [00:10] I tried looking into this, since at some point the applet was missing too [00:10] but all indicates it *should* work [00:10] cyphermox: yeah, i think you had it 100% fixed. but sounds like something might have changed [00:10] oem-config wifi worked in wily and in xenial, as jderose said, just a couple of weeks back. [00:10] maybe I have some weird ordering issue in the panels for OEM that I didn't notice [00:11] jderose: I didn't change anything relevant for the network prompts there. [00:11] The new a11y indicator has been introduced since. [00:13] flexiondotorg: well, I distinctly recall you guys mentioning that wifi prompts didn't work when we were preparing wily. [00:14] flexiondotorg: grub-install fails with nvme drives in BIOS mode on 14.04.4 also... so longstanding bug, not a regression [00:14] if things started working again, and then started not working again, it sounds like it wasn't my conscious doing :) [00:15] jderose: possible we didn't add nvme in grub-installer until after the .4 release [00:15] well [00:15] in fact either way it would not work since it doesn't work in xenial [00:20] slangasek: armhf+raspi2 looks good. [00:21] cyphermox, wifi prompts do not work in any install mode right now :-( [00:22] cyphermox, What jderose and I reported in Wily was that there was no network indicator in oem-config after the prepare had been done. [00:22] oh, nmcli dev must report all your wifis are wireds? [00:23] Maybe. How can I confirm that? [00:23] run 'nmcli dev' [00:26] OK, preparing next test machine. Will do that. [00:27] So those last minute VirtualBox changes are busted. [00:30] nmcli dev is correctly reporting wifi devices. [00:30] Like I say, the network indicator works. I can manually join a wifi network. The issue is that Ubiquity is no longer prompting to do so. [00:34] cyphermox, ^^^ [00:35] yeah, I see [00:37] jderose, ack the nvme testing. Thanks. [00:43] jderose https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1572793 [00:43] Launchpad bug 1572793 in ubiquity (Ubuntu) "Ubiquity no longer prompts to join available WiFi networks" [Undecided,New] [00:50] ugh [00:53] flexiondotorg: I fail. [00:53] not sure why it's doing that, I'll have a look. [00:53] can you file a bug? [00:53] Oh, OK. I thought you were saying you couldn't reproduce for a moment :-) [00:57] lost the ability to fully shutdown or reboot in virtualbox. [00:58] (from the lubuntu64 livemedia) [00:59] flexiondotorg: nah, something is clearly broken [01:11] OK, I've done what testing I can. Tracker updated. Night. Or morning ;-) [01:39] cyphermox: you guys need anything else that I can help with? [01:39] cyphermox: for release tomorroe [01:39] cyphermox: *tomorrow [01:39] test any image you'd like. [01:40] report findings on iso.qa.ubuntu.com, as usual :) [01:40] (and open bugs when you see some) [01:43] alright [01:43] that's all? [01:44] yeah [01:47] cool :) [02:27] can someone approve that ^, so I can re-spin [02:34] slangasek: ^ if you're still around [03:01] darkxst, cyphermox: looking [03:03] darkxst: why such a late seed change? and doesn't this imply you'll have an extra session type now on the image that needs validated for release? [03:04] (package accepted into -proposed for building, but not unblocking into xenial yet to give you time to reconsider / demand I comply :) [03:05] slangasek, the fallback to X11 is broken on some systems, and yes a "wayland" session will show up [03:07] "fallback to X11" - without this package, aren't you currently using X11 on all systems? [03:07] we will still call the "wayland" session experimental though [03:07] gdm tries to start on wayland first [03:07] when that fails it should use X11 [03:07] so "experimental" but used by default? :) [03:08] the user (login) session is experimental [03:09] that would need to be manually selected when logging in [03:10] alright, well, it doesn't sound to me like a change that is going to improve users' experience overall, but it's certainly your call - unblock hint added as well [03:10] gdm running on wayland is well supported, but I could also force that off in the config [03:10] so feel free to respin when it lands in xenial [03:12] well landing at a blank screen at boot is not a great experience [03:29] well, I'll certainly jump on that, darkxst, I've been meaning to try wayland on as many bare metal boxes as I can, and that seems like a good opportunity [03:38] hm go 1.6.2... [03:38] nothing very urgent looking though, could just sru after release [04:04] hmm actually I might revert that and just patch gdm conf instead [04:08] slangasek, are you able to reject the -meta upload? [04:10] darkxst: it's already accepted so can't be rejected, but can be removed [04:10] assuming it hasn't already published to xenial, let me see [04:11] darkxst: ah yeah, it's already published to xenial. Sorry, was expediting to not hold up your respins [04:13] darkxst: so, if you want to revert you need another meta upload [04:36] darkxst: ^^ is there also an ubuntu-gnome-meta revert coming? [04:36] slangasek, yes uploading now [04:37] ok [04:39] darkxst: both accepted and unblocked [04:39] slangasek, thanks [05:01] moar coffeee [05:33] ogra_: looks like the arm64 build doesn't want to pull from multiverse [05:52] cyphermox: failed xubuntu test case; am I doing something wrong with my setup? https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1572842 [05:52] Launchpad bug 1572842 in ubiquity (Ubuntu) "xubuntu 16.04 image does not give auto-resize option on 8GB disk" [Undecided,New] [05:59] isn't 8gb slightly too small? [06:00] come to think of it, for xubuntu it should be fine I think [06:00] well, that's what I don't knowv [06:00] I looked at actual usage, and it seemed it should have been enough space [06:01] you may be able to tell from running ubiquity --debug; at some point you'll see ubiquity SUBST the free_space templates, and you'd have the size there [06:01] it does seem like it should be plenty though [06:01] mmm [06:02] I'll just make the disk a bit bigger and retry [06:02] I also can boot up a xubuntu vm with the same conditions and try it [06:03] need to zsync that image first [06:05] ENOTENOUGHPOWEROUTLETSHERE [06:10] cyphermox, bigger battery required ... [06:10] yeah, battery replacements for old spare laptops [06:10] well, old testing laptops I guess [06:14] cyphermox: same problem reproduced with 10G disk [06:14] ok [06:14] wow, this release is terrible for the installer [06:22] I'm starting the ppc64el netboot test, and finishing the others I have been running, and then logging off [06:27] cyphermox: ok I had resized the disk to 10GB but realize that there was still a swap partition in the middle of that. Blew that away, resized the original partition up to fill the disk, and now I have the auto-resize option [06:31] ah? [06:32] why would it matter that it's a swap? [06:32] oh wait, we do explicitly swapon them now.. [06:32] no, that wouldn't matter either [06:33] slangasek: please leave the bug open, I wonder if it's not that we don't deal with the swap correctly for resizing [06:34] cyphermox: well, I expect it makes a difference because it means it can't make space for the new OS just by carving up the existing install partition === agateau_ is now known as agateau [06:34] right [06:35] cyphermox: also, just dropped another comment on the bug - spectacular failures [06:35] so I'm going to consider this a failure and move on [06:35] yeah [06:36] slangasek: is it too late to save the exact crash message? === TiGR is now known as Guest58880 [06:39] cyphermox: yes. the crash message was self-explanatory to me, it was an "out of space" error, and the partition table confirmed this [06:40] trusty -> xenial upgrade for Ubuntu GNOME seems to have dpkg diverts in place still [06:40] diverted by libgbm1-lts-wily to: /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0 [06:41] darkxst: please file a bug against xorg-lts-transitional tjaalton ^^ [06:41] slangasek: right, but you said crash, so I'm curious where it crashed exactly, but I can just find out after rest. [06:41] ok [06:47] I don't see where that divert comes from.. === Guest58880 is now known as polosatus [06:47] ah [06:47] now I do [06:50] Good morning [06:51] iso testing time! :-) [06:51] tjaalton: yeah, so the new package in xenial will need to un-divert :/ [06:51] sure [06:52] pitti: good morning [06:52] there is also the gbm drm driver diverted [06:52] bug 1572855 [06:52] bug 1572855 in xorg-lts-transitional (Ubuntu) "libgbm.so.1: cannot open shared object file" [Undecided,New] https://launchpad.net/bugs/1572855 [06:52] yep [06:53] I guess this has been carried over to newer lts stacks for no reason [06:53] anyway [06:53] xnox: your mainframes netbooting ok? [06:59] slangasek: was the ppc netboot test you? [06:59] cyphermox: no [07:00] cyphermox: tracker says user 'sqldatapoo' [07:00] yeah, I just hadn't look far enough [07:00] no idea if the described system is one that this is expected to work on [07:01] I find it a bit confusing that we still have these "ubuntu core" tarballs; seems this got overloaded quite a lot by now [07:08] slangasek: if we really care lots I'll try to boot my G5 again in the morning [07:09] cyphermox: surely that's a matter for the powerpc community to care about... sooner than the day before release [07:09] of course [07:09] but I wouldn't mind upgrading that system anyway [07:40] * cyphermox -> sleep; back in ~4-5 hours [07:48] ^ tested [07:50] tjaalton: the postinst->postinst.in logic /should/ be done in the build target, not in the clean target; it's valid to call build on the unpacked source without first running clean. But LP builds call clean so this is ok. But the maintscript logic worries me a bit; why do you have to do the dpkg-divert query, is it not guaranteed that the package which owns the divert is the same one currently [07:50] running? [07:51] slangasek: copied it from a similar case when it removed xrandr diverts [07:51] that it was copied doesn't make me feel better about it ;) [07:51] hear that [07:52] maybe for scriptability [07:55] tjaalton: so if this were me, this would be the entirety of the postinst.in: http://paste.ubuntu.com/15960926/ [07:55] WTF [07:55] ubuntu desktop/i386 with OEM still seems broken [07:56] tjaalton: this way, each package only removes its own divert [07:56] slangasek: ok I can do that [07:56] tjaalton: cool; I'll reject the previous one, please test the above [07:56] crap, need another victim machine :) [07:56] heh [07:57] or I'll just add manual diverts of course [07:58] pitti: but on the bright side, there are no i386 OEMs? [07:58] heh, yes [07:58] well, we might still respin that one, there aren't too many test cases yse [07:58] yet [07:58] or we ignore this indeed [07:59] pitti: is it broken in a way that's fixable without source uploads that touch every image? [07:59] slangasek: yes, this looks like the mirror desync again [07:59] ok [07:59] live system has ubiquity 2.21.63, pool/ still has 2.21.59 [07:59] i. e. prodding that mirror and rebuilding just that iso should fix it [07:59] infinity, cjwatson ^ [08:00] updated bug 1572436 [08:00] bug 1572436 in Ubuntu CD Images ""Prepare for OEM install" icon and oem-config-prepare missing on Ubuntu desktop i386" [High,Confirmed] https://launchpad.net/bugs/1572436 [08:01] and pool/ being out of date for ubiquity probably also means out-of-date-ness for other debs [08:01] and we are shipping a binary which we don't ship a source for [08:01] mmm, would this impact all i386 images? [08:01] let's hope not [08:02] I don't think it's arch specific [08:02] yesterday we had that on the amd64 image, and the current one is good [08:02] file-roller xenial-desktop-i386.iso and checkign the version in pool/main/u/ubiquity/ is a quick test that doesn't even need installation [08:03] or checking the .list files [08:03] indeed [08:03] hm, hang on [08:04] .disk/info says 20160419 [08:04] I just downloaded this an hour ago.. [08:04] from the wrong url? [08:04] http://cdimage.ubuntu.com/cdimage/daily-live/current/ [08:04] well, who knows, rsyncing again [08:05] (oh the joys of mirror rotation :) ) [08:05] pitti, I'm retriggering the job that makes the copy. [08:05] jibel: how do you mean? [08:05] pitti, the copy between pending and current didn't happen [08:05] the node crashed during the nighrt [08:05] oh [08:06] http://cdimage.ubuntu.com/cdimage/daily-live/current/ looks okay [08:06] so maybe that actually updated in the last hour after I downloaded, or it's only one mirror that is affected? [08:06] or it's a problem that affected only your rsync endpoint, not the http endpoint? [08:06] pitti, it should be now, I did it 5 minutes ago [08:06] ah, heh [08:06] aah [08:07] ok, .disk/info is current now, and so is pool/, sorry for the noise [08:07] retest o'clock [08:11] slangasek: ^ there you go. btw, debuild -S runs clean, so the package itself comes with the .postinst's so there should be no way to not have them :) [08:12] tjaalton: except the postinst is supposed to be different on each arch - anyway, that's not a blocker [08:12] oh indeed, hehe [08:12] hi [08:14] pitti, How did that i386 issue manifest? Ubuntu MATE i386 images were some of the last made, I tested them last night. No issues with oem mode. [08:15] flexiondotorg: yes, you'd notice because OEM mode is broken [08:15] pitti, Thanks. [08:15] that was an issue on a lot of images yesterday, and was supposed to be fixed; so I just fell into that "old image" trap [08:16] pitti: WTF? I did a hard ftpsync before building anything. [08:17] infinity: yes, it wasn't the internal mirror after all, just a cdimage mirror being out of date (see above, jibel fixed it) [08:17] Oh, you were looking at current, not the dated dirs [08:17] yes, my daily rsync scripts do that [08:18] all good on the current image [08:22] tjaalton: Did you see the llvm-3.8/i386 FTBFS? [08:23] Laney: yes, and uploaded a new version [08:24] tjaalton: Ahhhhh, in the queue. [08:24] Um [08:24] infinity: does it make sense to manually test ubuntu core? (on some less common arches like arm64 or ppc64el), or do we have some automagic for that? [08:25] Can't you just disable the relevant tests? [08:25] Or are they the only ones? [08:25] pitti: I do a quick run across all arches, it's a 2 minute affair. [08:25] infinity: yeah, I thought the same, nice thing to do while watching ubiquity install :) ok, I'll leave this to you then [08:25] * pitti would need more like 3 minutes per arch, not 2 minutes for everything [08:31] pitti: *phew* [08:31] cjwatson: *phew*² indeed [08:32] I was testing last night. Not sure if you guys have seen the backlog. [08:32] infinity: We could do the cloudfront uploads now, right? [08:33] The VirtualBox updates that were included yesterday are a bit busted. Has a regression that reintroduces video corruption. [08:33] Requires switching ttys to restore a usable display. [08:34] cjwatson: Yup. I was just going to run officeward, but if you want to relay the info to IS while I walk, yay. [08:34] infinity: Will do. Presumably just the pre-published ones? [08:34] cjwatson: No, they want everything, I believe. [08:34] flexiondotorg: That should be fixable in SRU, I guess. [08:34] Ubiquity no longer prompts to join wifi networks - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1572793 [08:34] Launchpad bug 1572793 in ubiquity (Ubuntu) "Ubiquity no longer prompts to join available WiFi networks" [Undecided,Confirmed] [08:35] cjwatson, Yes, except installs right now on VirtualBox appear broken. [08:35] flexiondotorg: Right, sure, but the virtualisation host is usually easily updatable to SRUs. [08:35] The install is fine, but on first boot video is completely screwed. [08:35] (once they exist) [08:35] they ask me if you could accept a last-minute sync of virtualbox, changing nothing from the current version in debian but the version (maintainer uploaded both in debian and ubuntu for fear of hitting dinstall last night and not having the upload done to ubuntu) [08:35] pitti, I confirm the swap issue is totally fixed :-D [08:36] virtualbox isn't seeded, if someone had a magic fix, I'd take it. Otherwise, meh. [08:36] The "not seeded" part also means that an SRU with magically fix it. [08:36] infinity, Kernel modules. [08:36] flexiondotorg: The kernel modules builtin to the Ubuntu kernel didn't change. [08:37] flexiondotorg: Only the dkms packages did. [08:37] "an SRU with magically fix it" s/with/will/ ? [08:37] flexiondotorg: So, if your image was fine N days ago and broke recently, it's all the unseeded packages being pulled in later. [08:37] flexiondotorg: yay [08:37] mapreri: Will, yes. [08:37] infinity: do you mean an SRU will magically be accepted? [08:37] infinity, Something changed. Has worked fine throughout 16.04 cycle until image built yesterday. [08:37] if so, guess I'll tell him "just wait tomorrow" [08:37] mapreri: No, I mean an SRU that fixes it would DTRT, since the images aren't broken, it's packages pulled during install. [08:38] flexiondotorg: Again, it's not the *image*, though, it's the archive. [08:38] flexiondotorg: It's the drivers being installed from the archive at install. [08:38] flexiondotorg: Installing without network probably wouldn't reproduce the bug. [08:38] ok. i'll forward the NACK. To me it seems crazy anyway bugging for only a version change :) ta. [08:38] flexiondotorg: And, thus, an SRU post-release would also fix it. [08:39] infinity, So I install from the current image, without network connected, and the video is corrupt in VirtualBox. [08:39] infinity: I'm assuming the MySQL 5.7 upstream update will need to be a 0-day at this stage? In which case, probably the security pocket? [08:40] flexiondotorg: Then that can't be virtualbox's (the package) fault, since it's not anywhere near your ISO. [08:40] rbasak: Coordinate with the security team, yes. [08:40] OK [08:41] infinity, I see linux-firmware-nonfree is no longer in the xenial archive. [08:41] Is that intentional? [08:42] https://bugs.launchpad.net/ubuntu/+source/linux-firmware-nonfree/+bug/1513589 Yes. [08:42] Launchpad bug 1513589 in linux-firmware-nonfree (Ubuntu Xenial) "linux-firmware-nonfree should be removed from Xenial" [Undecided,Fix released] [08:44] infinity, Thanks. I'll need to request an update to Ubuntu MATE Welcome. [08:51] cyphermox: you about? [08:51] infinity: wizard is missing the connect to wifi page [08:52] davmor2: Reported a few times over the last day. [08:53] infinity: I'm wondering if it is the update to 1.93 changes that broke it [08:53] flexiondotorg: Respinning for MATE welcome alone is probably not reasonable at this stage, unless it's completely busted. [08:53] flexiondotorg: As for your vbox woes, what's the host machine? Is that also up to date xenial? I can see it perhaps having broken on the host side. [08:54] infinity: network-manager that is :) [08:54] slangasek, infinity http://paste.ubuntu.com/15961377/ does that look sane ? [08:54] oh god an ogra_ diff [08:54] lol [08:54] infinity, Not to respin the image. Just a package upload. Is that OK? [08:55] flexiondotorg: Only as an SRU. [08:55] flexiondotorg: Images should match the release pocket. [08:56] ogra_: Probably not. [08:56] infinity, So I should not file an package update in the usual way? [08:57] infinity, well, how else do i get multiverse into a dedicated chroot then ? [08:57] flexiondotorg: Do an SRU in the usual way [08:57] Laney, Never done one before. [08:57] Then reading https://wiki.ubuntu.com/StableReleaseUpdates#Procedure is in your future. :) [08:57] * ogra_ grumbles about last minute landing that make everything explode [08:57] *landings [08:58] pot, kettle, ... :-) [08:58] ogra_: That didn't "make everything explode", you were building from a PPA before. :P [08:58] infinity, well, i''m naggibng the kernel team since 6 weeks about the rpi kernel that was stuck in proposed [08:58] * flexiondotorg is already reading about SRU [08:59] especially to avoid shuch crap [08:59] ogra_: http://paste.ubuntu.com/15961413/ [08:59] ogra_: That's probably what you want. [08:59] infinity, that wont work [08:59] Because? [08:59] because there is adedicated chroot freshly debootstrapped [09:00] will a plain debootstrap call pick up COMPONENTS= ? [09:00] ogra_: Which you use the previous sources.list for. [09:00] ogra_: cp -a chroot/etc/apt/* chroot-device/etc/apt/ [09:00] oh, wait ... i think i'm copying /etc/apt [09:00] ogra_: So, yes, it'll work. [09:00] yeah :) [09:00] thanks ! [09:00] ogra_: If it didn't work, you wouldn't have a kernel either (since debootstrap only uses main, and your kernel is universe) [09:01] indeed [09:04] anyone know if the wifi page has been removed from ubiquity on purpose? [09:04] cyphermox, ^ [09:04] cf bug 1572793 [09:04] bug 1572793 in ubiquity (Ubuntu) "Ubiquity no longer prompts to join available WiFi networks" [Undecided,Confirmed] https://launchpad.net/bugs/1572793 [09:05] nevermind, I scrolled up [09:05] cjwatson, i assume i can land your livecd-rootfs change alongside ? [09:06] ogra_: yes [09:06] that was "I never want to see that particular mistake again" [09:07] heh [09:09] o_O what happened to 2.407? [09:10] dch -i ... seemingly ... [09:10] * ogra_ sighs [09:11] :) [09:11] should i re-upload ? [09:11] ok [09:11] And rename that tag. :P [09:12] Well, delete that tag. [09:12] Tag the taggy tag [09:13] * ogra_ notes he cant win ... i spent nightshifts the last weeks making sure everything is fine and snappy builds rock solid ... to avoid exactly these last minute hacks ... :(((((( [09:18] sigh [09:18] ssh: Could not resolve hostname bazaar.launchpad.net: Name or service not known [09:20] I swear we haven't decommissioned it [09:20] haha [09:25] infinity, jibel: so the wifi page doesn't show in standard setup or in the End User setup in oem mode so I assume we need a fix for this right? [09:26] pitti: on a good news side of things No swap space error dialogue \o/ [09:26] davmor2: Not a fix in the sense of an ISO respin. AFAIK, the nm-applet still works, so you can configure there instead. [09:27] Sounds like a release note + SRU [09:27] i. e. fix for 16.04.1? [09:27] sucks a bit, but meh [09:27] Sucks less than delaying the release for a day for it. [09:28] (a day or more, since no one's quite sure what the bug is yet) [09:29] Laney, Can an SRU be a point release "upgrade" or should it just be a patch to the existing version? [09:30] flexiondotorg: I'm not sure I understand that question. [09:31] ubuntu-mate-welcome is currently 16.04.9. I've pushed and change and built it in a PPA as 16.04.10 [09:31] Can the SRU introduce the newer version? [09:32] Yes [09:34] Laney, ty [09:36] yofel: can nepomuk-widgets be removed? it seems to have a bunch of uninstallables [09:36] cjwatson: kill it [09:37] yofel: awesome, thanks. is it superseded by something I can log in the removal message? [09:37] nepomuk itself was obsoleted by baloo, so nothing should be using nepomuk-* anymore [09:37] ok [09:37] yofel: how about declarative-plasmoids? [09:37] infinity: might be a secondary issue with wifi on oem mode just reinstalling to check on it [09:38] cjwatson: "Depends: kdeworkspace-bin", that's kde4 and can go too [09:39] * cjwatson nukes [09:40] yofel: startactive too? I think that's the last of the KDE-specific all-arch uninstallables [09:41] cjwatson: yes, can go too [09:42] done [09:48] Laney, infinity Does this look like what you'd expect? https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-welcome/+bug/1572931 [09:48] Launchpad bug 1572931 in ubuntu-mate-welcome (Ubuntu) "SRU: ubuntu-mate-welcome 16.04.10 bug fix [dsc attached]" [Undecided,New] [09:51] flexiondotorg: Sure, although I think you should apply some imagination to the regression potential section :) [09:51] Laney, it's accurate :-) [09:51] Yeah right [09:51] So, I should also subscribe the sru verification team? [09:52] No [09:52] Nominate to xenial, then upload or subscribe sponsors [09:52] Sponsors subscribed. [09:53] Laney, Do I nominate xenial using tags? [09:56] No, there's a link for it below the list of bug tasks [09:56] But if you can't see it then don't bother [09:57] Laney, I don't see bug tasks :-( [09:59] k [09:59] I don't remember what permissions it needed [10:02] yofel: oh, one more, how about sentinella? [10:02] cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797942 [10:02] Debian bug 797942 in src:sentinella "sentinella: build-depends on obsolete kdebase-workspace-dev" [Serious,Open] [10:02] maybe I should demote that one to -proposed since there seems at least some chance that it might be fixed at some point, and it's synced from Debian [10:03] yeah, I've argued myself into that, done [10:04] infinity, jibel: yeap confirmed second oem install and I have no wifi for the end user http://people.canonical.com/~davmor2/desktop-screenshots/wifi-broken.png [10:04] I need to reboot the end user session to get working wifi [10:05] infinity, Using different 16.04 host, which is fully updated. Installing a VirtualBox guest I have no video corruption :-) [10:05] davmor2, "reboot the user session" means logout/in again ? [10:06] infinity, Looks like you're right about host/guest mismatch. [10:06]