=== kmously-afk is now known as kmously [05:11] -queuebot:#ubuntu-release- New binary: libsignal-protocol-c [ppc64el] (bionic-proposed/none) [2.3.1+git20171007-2] (no packageset) [05:12] -queuebot:#ubuntu-release- New binary: libsignal-protocol-c [arm64] (bionic-proposed/none) [2.3.1+git20171007-2] (no packageset) [05:12] -queuebot:#ubuntu-release- New binary: libsignal-protocol-c [s390x] (bionic-proposed/none) [2.3.1+git20171007-2] (no packageset) [05:13] -queuebot:#ubuntu-release- New binary: seqtools [ppc64el] (bionic-proposed/none) [4.44.1+dfsg-1] (no packageset) [05:13] -queuebot:#ubuntu-release- New binary: seqtools [s390x] (bionic-proposed/none) [4.44.1+dfsg-1] (no packageset) [05:13] -queuebot:#ubuntu-release- New binary: libsignal-protocol-c [armhf] (bionic-proposed/none) [2.3.1+git20171007-2] (no packageset) [05:15] -queuebot:#ubuntu-release- New binary: seqtools [arm64] (bionic-proposed/none) [4.44.1+dfsg-1] (no packageset) [05:16] -queuebot:#ubuntu-release- New binary: libsignal-protocol-c [amd64] (bionic-proposed/none) [2.3.1+git20171007-2] (no packageset) [05:17] -queuebot:#ubuntu-release- New binary: libsignal-protocol-c [i386] (bionic-proposed/none) [2.3.1+git20171007-2] (no packageset) [05:18] -queuebot:#ubuntu-release- New binary: libterm-choose-perl [amd64] (bionic-proposed/none) [1.507-1] (no packageset) [05:18] -queuebot:#ubuntu-release- New binary: ruby-guard-shell [amd64] (bionic-proposed/none) [0.7.1-1] (no packageset) [05:18] -queuebot:#ubuntu-release- New binary: nipy [s390x] (bionic-proposed/none) [0.4.1-2] (no packageset) [05:18] -queuebot:#ubuntu-release- New binary: r-cran-recipes [amd64] (bionic-proposed/none) [0.1.0-1] (no packageset) [05:20] -queuebot:#ubuntu-release- New binary: nipy [ppc64el] (bionic-proposed/none) [0.4.1-2] (no packageset) [05:21] -queuebot:#ubuntu-release- New binary: seqtools [armhf] (bionic-proposed/none) [4.44.1+dfsg-1] (no packageset) [05:22] -queuebot:#ubuntu-release- New binary: seqtools [amd64] (bionic-proposed/none) [4.44.1+dfsg-1] (no packageset) [05:22] -queuebot:#ubuntu-release- New binary: seqtools [i386] (bionic-proposed/none) [4.44.1+dfsg-1] (no packageset) [05:32] -queuebot:#ubuntu-release- New binary: nipy [i386] (bionic-proposed/none) [0.4.1-2] (no packageset) [05:38] -queuebot:#ubuntu-release- New binary: nipy [amd64] (bionic-proposed/none) [0.4.1-2] (no packageset) [05:46] -queuebot:#ubuntu-release- New binary: nipy [arm64] (bionic-proposed/none) [0.4.1-2] (no packageset) [09:13] -queuebot:#ubuntu-release- Unapproved: strongswan (artful-proposed/main) [5.5.1-4ubuntu2.1 => 5.5.1-4ubuntu2.2] (ubuntu-server) [09:14] -queuebot:#ubuntu-release- Unapproved: strongswan (zesty-proposed/main) [5.5.1-1ubuntu3.2 => 5.5.1-1ubuntu3.3] (ubuntu-server) [09:14] -queuebot:#ubuntu-release- Unapproved: strongswan (xenial-proposed/main) [5.3.5-1ubuntu3.4 => 5.3.5-1ubuntu3.5] (ubuntu-server) [10:08] -queuebot:#ubuntu-release- New sync: haskell-unliftio-core (bionic-proposed/primary) [0.1.0.0-1] [10:10] -queuebot:#ubuntu-release- New sync: haskell-fgl-arbitrary (bionic-proposed/primary) [0.2.0.3-1] [10:10] -queuebot:#ubuntu-release- New sync: haskell-unliftio (bionic-proposed/primary) [0.1.1.0-1] [10:10] -queuebot:#ubuntu-release- New sync: haskell-storable-record (bionic-proposed/primary) [0.0.3.1-1] [10:23] -queuebot:#ubuntu-release- Unapproved: ntp (artful-proposed/main) [1:4.2.8p10+dfsg-5ubuntu3 => 1:4.2.8p10+dfsg-5ubuntu3.1] (ubuntu-server) [10:29] -queuebot:#ubuntu-release- New: accepted libsignal-protocol-c [amd64] (bionic-proposed) [2.3.1+git20171007-2] [10:29] -queuebot:#ubuntu-release- New: accepted libsignal-protocol-c [armhf] (bionic-proposed) [2.3.1+git20171007-2] [10:29] -queuebot:#ubuntu-release- New: accepted libsignal-protocol-c [ppc64el] (bionic-proposed) [2.3.1+git20171007-2] [10:29] -queuebot:#ubuntu-release- New: accepted libterm-choose-perl [amd64] (bionic-proposed) [1.507-1] [10:29] -queuebot:#ubuntu-release- New: accepted ruby-guard-shell [amd64] (bionic-proposed) [0.7.1-1] [10:29] -queuebot:#ubuntu-release- New: accepted seqtools [arm64] (bionic-proposed) [4.44.1+dfsg-1] [10:29] -queuebot:#ubuntu-release- New: accepted seqtools [i386] (bionic-proposed) [4.44.1+dfsg-1] [10:29] -queuebot:#ubuntu-release- New: accepted libsignal-protocol-c [arm64] (bionic-proposed) [2.3.1+git20171007-2] [10:29] -queuebot:#ubuntu-release- New: accepted libsignal-protocol-c [s390x] (bionic-proposed) [2.3.1+git20171007-2] [10:29] -queuebot:#ubuntu-release- New: accepted seqtools [amd64] (bionic-proposed) [4.44.1+dfsg-1] [10:29] -queuebot:#ubuntu-release- New: accepted seqtools [s390x] (bionic-proposed) [4.44.1+dfsg-1] [10:29] -queuebot:#ubuntu-release- New: accepted libsignal-protocol-c [i386] (bionic-proposed) [2.3.1+git20171007-2] [10:29] -queuebot:#ubuntu-release- New: accepted seqtools [armhf] (bionic-proposed) [4.44.1+dfsg-1] [10:29] -queuebot:#ubuntu-release- New: accepted r-cran-recipes [amd64] (bionic-proposed) [0.1.0-1] [10:29] -queuebot:#ubuntu-release- New: accepted seqtools [ppc64el] (bionic-proposed) [4.44.1+dfsg-1] [10:45] -queuebot:#ubuntu-release- New sync: haskell-unliftio-core (bionic-proposed/primary) [0.1.0.0-1] [10:50] in the interests of clearing some backlog pre-christmas - please can ceph in artful-proposed under bug 1728576 be released to updates? [10:50] bug 1728576 in ceph (Ubuntu Artful) "[SRU] ceph 12.2.1" [High,Fix committed] https://launchpad.net/bugs/1728576 [11:10] -queuebot:#ubuntu-release- New binary: tesseract [s390x] (bionic-proposed/universe) [4.00~git2174-3b62badd-5] (kubuntu) [11:13] -queuebot:#ubuntu-release- New binary: tesseract [ppc64el] (bionic-proposed/universe) [4.00~git2174-3b62badd-5] (kubuntu) [11:14] -queuebot:#ubuntu-release- New binary: mumps [s390x] (bionic-proposed/universe) [5.1.2-2] (no packageset) [11:18] -queuebot:#ubuntu-release- New binary: mumps [ppc64el] (bionic-proposed/universe) [5.1.2-2] (no packageset) [11:19] -queuebot:#ubuntu-release- New binary: mumps [i386] (bionic-proposed/universe) [5.1.2-2] (no packageset) [11:19] -queuebot:#ubuntu-release- New binary: tesseract [amd64] (bionic-proposed/universe) [4.00~git2174-3b62badd-5] (kubuntu) [11:23] -queuebot:#ubuntu-release- New binary: tesseract [i386] (bionic-proposed/universe) [4.00~git2174-3b62badd-5] (kubuntu) [11:24] -queuebot:#ubuntu-release- New binary: tesseract [arm64] (bionic-proposed/universe) [4.00~git2174-3b62badd-5] (kubuntu) [11:26] -queuebot:#ubuntu-release- New binary: tesseract [armhf] (bionic-proposed/universe) [4.00~git2174-3b62badd-5] (kubuntu) [11:27] -queuebot:#ubuntu-release- New binary: tesseract-lang [amd64] (bionic-proposed/none) [4.00~git15-45ed289-3] (no packageset) [11:29] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (artful-proposed/main) [4.13.0-21.24] (core, kernel) [11:29] -queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (xenial-proposed/universe) [4.13.0-1012.13] (kernel) [11:29] -queuebot:#ubuntu-release- New binary: mumps [amd64] (bionic-proposed/universe) [5.1.2-2] (no packageset) [11:30] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [amd64] (xenial-proposed/main) [4.13.0-21.24~16.04.1] (kernel) [11:31] -queuebot:#ubuntu-release- New binary: mumps [arm64] (bionic-proposed/universe) [5.1.2-2] (no packageset) [11:40] -queuebot:#ubuntu-release- New binary: mumps [armhf] (bionic-proposed/universe) [5.1.2-2] (no packageset) [12:02] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [amd64] (xenial-proposed) [4.13.0-21.24~16.04.1] [12:02] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (xenial-proposed) [4.13.0-1012.13] [12:34] cjwatson, please re-enable haskell autosync, I don't foresee any ghc 8.2 in the near future [12:35] (we should probably try to get 8.2 in 18.04 anyway) [12:35] LocutusOfBorg: done [12:35] ta [12:35] people are putting pressure to have 8.2 in unstable, but stackage is not tracking it [12:36] damn, stackage just published it [12:36] :/ [15:46] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (artful-proposed) [4.13.0-21.24] [16:12] -queuebot:#ubuntu-release- Unapproved: libmbim (xenial-proposed/main) [1.12.2-2ubuntu1 => 1.14.0-1ubuntu0.16.04.1] (kubuntu, ubuntu-desktop) [16:12] -queuebot:#ubuntu-release- Unapproved: libqmi (xenial-proposed/main) [1.12.6-1 => 1.16.2-1ubuntu0.16.04.1] (kubuntu, ubuntu-desktop) [16:13] -queuebot:#ubuntu-release- Unapproved: modemmanager (xenial-proposed/main) [1.4.12-1ubuntu1 => 1.6.4-1ubuntu0.16.04.1] (kubuntu, ubuntu-desktop) [16:16] -queuebot:#ubuntu-release- New sync: linux-kvm (bionic-proposed/primary) [4.4.0-1013.18] [16:17] -queuebot:#ubuntu-release- New sync: linux-meta-kvm (bionic-proposed/primary) [4.4.0.1013.13] [18:16] -queuebot:#ubuntu-release- Unapproved: debian-installer (xenial-proposed/main) [20101020ubuntu451.17 => 20101020ubuntu451.18] (core) [18:56] RAOF: hey! Could you release ubuntu-image into -updates for artful, zesty and xenial? Thanks! [19:02] Hi, could pintery test against qtbase-opensource-src on arm64 perhaps be ignored? [19:02] for https://autopkgtest.ubuntu.com/packages/pinentry/bionic/arm64 [19:03] it seems to be failing the same in all but one random case, and not related to new Qt at all [19:06] doko: fwiw we don't expose 'error' state in update_excuses.yaml, we only list results as regression vs. alwaysfail. So we don't have a good way to automatically retry only those tests that errored out and which are relevant to migration [19:08] jibel: hi, I understand from powersj that ~canonical-platform-qa-jenkins is the team that has access to trigger jenkins jobs for the image smoketests. Could ubuntu-release be added as part of that team? Or should it be some canonical-only subset? (AIUI the jenkins is firewalled, so maybe it doesn't have to be subsetted) [19:12] apw: are you doing SRU work right now? Could you release ubuntu-image while you're at it? ;) [19:15] slangasek, hi, I added ubuntu-release. [19:15] jibel: cheers [19:16] slangasek, good day I did all the verification-done-$RELEASE for "ca-certificates-java", there is no autopkgtest failures in pending SRU and it will reach its 7 days (minimum aging period in -proposed) this Friday. Do you think there is a chance we can release it in -updates on friday ? or you would prefer to release it early Jan 2018 ? [19:16] slashd: well I'm not going to be here Friday to release it [19:17] slashd: we could release it early, if the SRUer of the day agrees [19:18] slangasek, sound good I'll ping ask sil2100 on Thursday, it'll give the pkg an extra 48 hours in -proposed [19:18] slangasek, thanks and enjoy your time off [19:18] slashd: a) why would you wait instead of doing it now? [19:18] slashd: b) pinging sil2100 won't do any good, he's already off [19:20] slangasek, ack for sil2100, because today the SRU vanguard is already EOD, and I wanted to give the package as much time as possible in -proposed. [19:21] slangasek, but if someone from the SRU team is okay to release it now, I'm totally fine with it [19:25] slashd: giving it more time in -proposed means giving us less time to respond to any regressions detected in -updates before it becomes a holiday emergency. if we're going to release it early we should do so asap [19:26] slashd: and RAOF shouldn't be EOD yet, he should be just coming online shortly [19:26] slangasek, make sense to me to have some day left to react in case of.... will ping RAOF then, tks again [19:28] o/ RAOF, based on the above discussion with slangasek ^ can you please look at "ca-certificates-java" in -proposed for Xenial and Zesty, and see if it could be eligible for an early release ? [19:31] slashd, what I meant by RAOF EOD is that he is the Tuesday vanguard, but when he will be online it's going to be Wednesday for him, so it'll be someone else duty, but if RAOF doesn't do it. I'll ping the Wednesday vanguard when I start my day tomorrow. [19:31] slangasek, ^ [19:32] slashd: my understanding is that RAOF celebrates western-hemisphere-Tuesday for these purposes ;) [19:32] slangasek, ok ;) We are all good then [19:38] jibel: ah... does being added to that team need to be confirmed by ubuntu-release, or something? I don't see ubuntu-release added, and I don't see anything pending for me to accept [20:14] Laney: did you happen to see my follow-up question on https://bugs.launchpad.net/auto-package-testing/+bug/1733839 ? seems like a small enough change and I'm happy to follow this through, but I don't understand the rationale for part of it here [20:14] Launchpad bug 1733839 in Auto Package Testing "Sometimes we use upstream cloud images without harmful packages removed" [Undecided,New] [20:40] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.14.0-13.15] (core, kernel) [21:17] -queuebot:#ubuntu-release- New: accepted linux-kvm [sync] (bionic-proposed) [4.4.0-1013.18] [21:17] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.14.0-13.15] [21:17] -queuebot:#ubuntu-release- New: accepted linux-meta-kvm [sync] (bionic-proposed) [4.4.0.1013.13] [21:17] does anybody understand why updating libjs-jquery-colorpicker doesn't trigger autopkgtesting of cacti? [21:18] cacti needs a rebuild for libjs-jquery-colorpicker 1.2.14-1 to not break it (due to the use of dh_linktree) [21:19] see Debian bug 884756 and 884804 [21:19] Debian bug 884756 in cacti "cacti can not install missing dependency" [Grave,Open] http://bugs.debian.org/884756 [21:19] Debian bug 884804 in release.debian.org "nmu: cacti_1.1.28+ds1-2" [Normal,Open] http://bugs.debian.org/884804 [21:39] -queuebot:#ubuntu-release- New: accepted mumps [amd64] (bionic-proposed) [5.1.2-2] [21:39] -queuebot:#ubuntu-release- New: accepted mumps [armhf] (bionic-proposed) [5.1.2-2] [21:39] -queuebot:#ubuntu-release- New: accepted mumps [arm64] (bionic-proposed) [5.1.2-2] [21:39] -queuebot:#ubuntu-release- New: accepted tesseract-lang [amd64] (bionic-proposed) [4.00~git15-45ed289-3] [21:40] -queuebot:#ubuntu-release- New: accepted tesseract [armhf] (bionic-proposed) [4.00~git2174-3b62badd-5] [21:41] -queuebot:#ubuntu-release- New: accepted tesseract [amd64] (bionic-proposed) [4.00~git2174-3b62badd-5] [21:41] -queuebot:#ubuntu-release- New: accepted tesseract [i386] (bionic-proposed) [4.00~git2174-3b62badd-5] [21:41] -queuebot:#ubuntu-release- New: accepted tesseract [arm64] (bionic-proposed) [4.00~git2174-3b62badd-5] [21:41] -queuebot:#ubuntu-release- New: accepted mumps [i386] (bionic-proposed) [5.1.2-2] [21:41] -queuebot:#ubuntu-release- New: accepted mumps [s390x] (bionic-proposed) [5.1.2-2] [21:41] -queuebot:#ubuntu-release- New: accepted nipy [arm64] (bionic-proposed) [0.4.1-2] [21:41] -queuebot:#ubuntu-release- New: accepted nipy [ppc64el] (bionic-proposed) [0.4.1-2] [21:41] -queuebot:#ubuntu-release- New: accepted tesseract [ppc64el] (bionic-proposed) [4.00~git2174-3b62badd-5] [21:41] -queuebot:#ubuntu-release- New: accepted mumps [ppc64el] (bionic-proposed) [5.1.2-2] [21:41] -queuebot:#ubuntu-release- New: accepted nipy [i386] (bionic-proposed) [0.4.1-2] [21:41] -queuebot:#ubuntu-release- New: accepted tesseract [s390x] (bionic-proposed) [4.00~git2174-3b62badd-5] [21:41] -queuebot:#ubuntu-release- New: accepted nipy [amd64] (bionic-proposed) [0.4.1-2] [21:41] -queuebot:#ubuntu-release- New: accepted nipy [s390x] (bionic-proposed) [0.4.1-2] === Ukikie is now known as OldManWinter [22:39] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (artful-proposed/main) [0.98ubuntu1 => 0.98ubuntu1.1] (desktop-core, ubuntu-server) === hggdh is now known as desole [22:51] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (zesty-proposed/main) [0.93.1ubuntu2.3 => 0.93.1ubuntu2.4] (desktop-core, ubuntu-server) [22:52] slangasek: Please update your pinentry hint so that it covers arm64 as well, it seems to be a container problem. [22:52] tsimonq2: arm64 tests don't run in containers [22:53] slangasek: er, my terminology's off, but regardless, this seems runner-related: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/p/pinentry/20171219_184830_03711@/log.gz [22:53] It also fails on all other arches except for armhf, which is *weird*. [22:54] ah; so what's exceptional there is that it *did* ever succeed on arm64 [22:54] it's not runner-related, it's what-the-hell-is-wrong-with-your-test,-pinentry-related [22:54] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (xenial-proposed/main) [0.90ubuntu0.8 => 0.90ubuntu0.9] (desktop-core, ubuntu-server) [22:54] I run it against itself, so we have a record that it was regressed in release [22:54] slangasek, bad test is bad, and even worse when completely unreliable [22:54] (see the comment above the existing hint in my hint file) [22:54] tsimonq2, what about pinging upstream? [22:55] * LocutusOfBorg pointed tsimonq2 to you just because of your comment :p [22:55] it hadn't been necessary to hint it for other archs because they were always-failed. I just don't know why it managed to pass on arm64 one time [22:55] LocutusOfBorg: I could do that, but it's irrelevant to the fact that qtbase migration is blocked because of it [22:55] tsimonq2, for the future I mean [22:55] hint updated [22:55] <3 [22:55] Thanks slangasek! [22:56] The last failure, which I'm working on right now... wh- why... [22:56] Actual (noImplicitSmb.path()) : "//path1/path2" [22:56] Expected (QString("/path1/path2")): "/path1/path2" [22:56] tsimonq2, the interesting fact is that against itself it passes [22:56] so the new qt is adding a new slash? [22:56] LocutusOfBorg: I doubt it's related to the new Qt, to be honest. [22:56] speaking of running tests against themselves, LocutusOfBorg you may be interested in my MP to facilitate batching such things: https://code.launchpad.net/~vorlon/ubuntu-archive-tools/fancier-autopkgtest-retries/+merge/335413 [22:57] oh... tsimonq2 samba might be the clue [22:58] slangasek: YES <3 [22:58] LocutusOfBorg: Oh? [22:58] (please use responsibly) [22:58] slangasek, <3 [22:58] btw, somebody sent you an email wrt freetype :) [22:59] tsimonq2, I remember a new samba landing in Ubuntu last weeks [22:59] LocutusOfBorg: Oh, I didn't catch that. [23:00] That could possibly explain it. [23:00] "KUrlTest::testSmb" [23:00] Right... [23:00] I would expect smb to mean samba, but there is nothing in -proposed related to samba, and the test is not installing it [23:00] sooo maybe this is completely unrelated [23:01] In any case, an extra erraneous slash... shouldn't be an issue... [23:01] I'm tempted to just XFAIL it. [23:01] LocutusOfBorg: freetype> hmm indeed [23:03] I'm tempted to close the RFS, but in case somebody else sponsor it... they might do some big damage [23:03] tsimonq2, better fix it :p [23:04] LocutusOfBorg: If I can reproduce it locally, then meh, why not :P [23:04] (sometimes I deal with autopkgtest failures that consistently happen on the autopkgtesters but can't reproduce locally... those are the *fun* ones) [23:06] slashd: Ok, that looks like a sensible thing to release early. [23:08] tsimonq2, it might be a qt regression, better not xfail it [23:08] you can send the issue upstream, maybe they have a fix [23:09] I know an extra slash isn't hurting, but this is a library, so maybe applications might misbehave with shared samba folders [23:10] LocutusOfBorg: Let me steal slangasek's MP for --no-proposed and try it out real quick, maybe it's just a kde4libs(or whatever the freaking thing's called) regression [23:11] tsimonq2, it doesn't fail against itself [23:11] I did a no change rebuild already [23:11] it fails against proposed, yeah [23:11] and proposed means qt mostly [23:11] so, unless you want to meld the two logs, and see which versions differs, I doubt a new rebuilds will have a different outcome [23:12] * LocutusOfBorg goes to sleep, mumps rebuilds issued, haskell is ongoing, and retry for failed qt tests issued to [23:12] *too [23:14] Cool cool. [23:25] thanks RAOF [23:41] fossfreedom: hi there [23:41] slangasek, hi [23:41] fossfreedom: so, flavor respins. I think we should do them, yes [23:42] I need to work out the mechanics of how we will even do them [23:42] thanks for the confirmation. We are just putting a notice on our website as well just to let everyone know - with a link to the bug report. I hope that's ok to-do that. [23:42] but their release will be dependent on having folks to test etc [23:42] are you guys talking about the lenovo bios issue? [23:43] fossfreedom: yes, I think that's appropriate. We've done the same today for the ubuntu.com download page and I've updated the release notes [23:43] wxl: yes [23:43] oh my [23:43] ^^ @tsimonq2 incoming respins of 17.10 due to BIOS issue on Lenovo laptops (will fix our UEFI issue, too) [23:43] s/will/should/ [23:43] hah, so I guess you'll be +1 on it [23:43] :) [23:44] that's a fair assumption [23:44] NB I don't know that I'll be able to get the respin started until next week [23:44] ^^ @valorie heads up to you, too, about potential 17.10 respins coming soon [23:45] wxl, slangasek: So it takes a machine-bricking issue to get a respin of all flavors but when you can't install Lubuntu in the first place on those machines to begin with, we don't get a respin? :P [23:45] nice [23:45] Huh. [23:45] (lol, in all reality, I'm glad this is getting dealt with) [23:45] @tsimonq2: it takes world breaking, yes. not ridiculous [23:45] i must say lenovo's response to the whole thing is just sad [23:46] wxl: How so? [23:46] fwiw I wouldn't assume that the responses users are getting so far from support is Lenovo's final word on the subject [23:47] slangasek: I wouldn't be surprised if it would be far off from "you broke our warranty by installing an unofficial operating system, we can't help you" to be honest. [23:53] -queuebot:#ubuntu-release- Unapproved: rejected rtl8812au [source] (xenial-proposed) [4.3.8.12175.20140902+dfsg-0ubuntu2.1]