[01:07] <Moc> Latest installer not loading maybe because of my nvidia video card..
[09:41] <ginggs> nvidia visual profiler doesn't work with the default jre (LP: #1766948) - does depending on openjdk-8-jre and running nvvp from a wrapper setting JAVA_HOME and PATH  sound like a reasonable workaround?
[10:04] <ginggs> doko: ^ any suggestion please?
[10:07] <doko> and it needs root privs?
[10:07] <doko> is there an upstream issue open for this?
[10:11] <ginggs> doko: hmm, i didn't receive that message about root privs - they haven't been needed before - will check that
[10:11] <ginggs> doko: I don't know of an upstream issue for not working with latest java, anbe wasn't even aware of it
[10:15] <doko> well, preference would be to get it working with openjdk-10, if not we can have a temporary work around. but I don't like the suggestion with the alternatives ...
[10:20] <ginggs> doko: yeah, I'd rather work around with a wrapper than have everyone update-alternatives, I'll update that bug once we have a better solution.  What does getting it working with openjdk-10 entail?  I have no idea where to start
[10:21] <ginggs> doko: and it doesn't work with openjdk-9 either
[11:35] <rbasak> cpaelzer: on bug 1764668
[11:35] <rbasak> cpaelzer: is it possible that some users have guests that fail to shut down in production? In that case, what will happen to them after this SRU?
[11:36] <rbasak> eg. will the host now not shut down, or they'll have to wait for a timeout and then it will?
[11:37] <cpaelzer> rbasak: hiho
[11:39] <cpaelzer> rbasak: this is a two stage thing
[11:40] <cpaelzer> rbasak: let me explain ...
[11:41] <cpaelzer> before 1.3.1-1ubuntu10.21 there were cases where it could hang on shutdown
[11:41] <cpaelzer> this was fixed and good in that regard, but the fix introduced another issue which was missed
[11:41] <cpaelzer> so the new case is that all guests get a shutdown signal now, but it immediately detects them as shut down and goes on with the systems shutdown
[11:42] <cpaelzer> the latter is fixed by the current SRU
[11:42] <cpaelzer> so currently people might have guests that shut down but too fast go on and shut down the full system
[11:42] <cpaelzer> with the fix it will wait up to timeout (as defined in the config)
[11:43] <cpaelzer> it will not exceed that timeout and hang (as before the last SRU)
[11:43] <cpaelzer> but it will also not go on too fast
[11:43] <cpaelzer> rbasak: did the above eplxain what you wanted to know?
[11:43] <rbasak> Yes, thanks. The case I had in mind can't happen because of the timeout.
[11:44] <cpaelzer> I have tested and examples with timeouts in the bug
[11:46] <rbasak> cpaelzer: would it be fair to consider this bug regression-updates?
[11:47] <cpaelzer> rbasak: yes I think this would be correct in this case
[11:47] <rbasak> OK thanks
[12:04] <rbasak> Looks like libvirt 1.3.1-1ubuntu10.18 in Xenial introduced a spurious empty directory called debian/patches/debian/patches
[12:05] <ogra_`> the redundant redundancy of redundance :)
[12:08]  * rbasak adds debian/patches/debian/patches/ogra_`
[12:08] <ogra_`> haha
[12:08] <rbasak> Or should that be ogra_`_`? :-P
[12:09] <ogra_`> lol
[12:09] <ogra_> np backticks ... backticks are evil :)
[12:09] <ogra_> *no
[12:23] <cpaelzer> rbasak: I can commit a removal of that dir to git
[12:23] <cpaelzer> rbasak: so on next update it will be removed
[12:23] <cpaelzer> (no extra SRU for that
[12:23] <cpaelzer> )
[12:24] <rbasak> cpaelzer: I was pondering suggesting that.
[12:24] <rbasak> But OTOH SRUs are supposed to be minimal and it causes no harm there.
[12:24] <rbasak> So I guess I'm on the fence, and will accept either way.
[12:25] <cpaelzer> I added it to be in next submission
[12:25] <rbasak> OK, thanks
[12:25] <cpaelzer> not worth to reroll anythinf ongoing
[12:25] <rbasak> Agreed
[13:19] <rbasak> coreycb: looking at the SRU queue for bug 1763179 and bug 1760918. I don't follow the user impact of either of those bugs. Please could you expand the SRU information?
[13:24] <coreycb> rbasak: sure np. 1763179 fixes a regression in the fix for 1760918. 1760918 causes an exception but the specific exception is not listed in the bug.
[13:24] <coreycb> rbasak: will get the bug updated
[13:24] <rbasak> Thanks
[14:53] <seyeongkim> hey coreycb rbasak hello, I couldn't touch this but I re-tested this few days ago and xenial and mitaka only got error ( I mean can't create cinder volume ). 1763179's desc only need to be changed? or both of them?
[14:54] <coreycb> seyeongkim: would you mind just clearing up the impact section to make it clear as to what the user impact is?
[14:56] <seyeongkim> ok will do
[15:06] <Moc> loru: going to take more than 1 hours... there is no new daily build yet
[15:14] <seyeongkim> changed it, not sure clear enough coreycb
[15:26] <coreycb> seyeongkim: thanks lgtm. rbasak: impact sections are updated
[15:28] <rbasak> Thanks
[15:28] <rbasak> I'm a bit tied up right now. I'll look when I can
[16:06] <JHOSMAN> How long time is it until the ISO's release of 18.04?
[16:06] <nacc> JHOSMAN: when they do, don't pester
 You could join the #ubuntu-release-party
[18:55] <Moc> wee 20180426 daily build is out ! Downloading it now to see if the installer bug was fixed !
[23:13] <Laney> 🆕
[23:17] <Unit193> sil2100: Missed a spot. ;)
[23:17] <Unit193> 'support and discussion of Trusty-Artful'
[23:18] <Laney> Unit193: be the change
[23:19] <Laney> 👏
[23:20] <krytarik> That's not quite correct either though..
[23:21] <Unit193> krytarik: Gives upper and lower bounds, which is the goal.
[23:21] <krytarik> I think one could very well do without it too.
[23:22] <krytarik> It always gets overlooked anyway!
[23:38] <tsimonq2> Final Freeze? o_O
[23:41] <sarnold> isn't there usually a day or two of "please bugfixes only" kind of upload activity?
[23:45] <dpb1> long live Ubuntu CC?