[00:03] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_cantor build #102: STILL UNSTABLE in 55 min: https://kci.pangea.pub/job/bionic_stable_cantor/102/
[00:08] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_libkgapi build #65: STILL UNSTABLE in 1 hr 0 min: https://kci.pangea.pub/job/bionic_unstable_libkgapi/65/
[00:08] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #100: STILL UNSTABLE in 59 min: https://kci.pangea.pub/job/bionic_unstable_amarok/100/
[00:08] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_cantor build #95: STILL UNSTABLE in 59 min: https://kci.pangea.pub/job/bionic_unstable_cantor/95/
[00:08] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #130: STILL UNSTABLE in 1 hr 0 min: https://kci.pangea.pub/job/bionic_unstable_kstars/130/
[00:09] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_libgravatar build #79: STILL FAILING in 19 min: https://kci.pangea.pub/job/bionic_unstable_libgravatar/79/
[00:41] <valorie> dang, since restarting, falkon seems to freeze all the time
[00:41] <valorie> :(
[01:06] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kdepim-addons build #130: FAILURE in 7 min 33 sec: https://kci.pangea.pub/job/bionic_stable_kdepim-addons/130/
[02:03] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_pimcommon build #98: STILL FAILING in 20 min: https://kci.pangea.pub/job/bionic_unstable_pimcommon/98/
[02:51] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_akonadi build #146: STILL FAILING in 30 min: https://kci.pangea.pub/job/bionic_unstable_akonadi/146/
[02:59] <BionicMac> valorie: I see the iso has changed since early am. Ready for more testing yet? 
[02:59] <valorie> uh
[02:59] <valorie> let me check again
[02:59] <valorie> I didn't see the "build" report
[02:59] <BionicMac> ok I just zync'd and it was very different.
[03:00] <valorie> well, I tested what is there now
[03:00] <valorie> however, they are re-spinning now
[03:00] <valorie> just not built yet
[03:01] <BionicMac> ok just let me know please maam. hilight me nick or something on top of the usual email I may see the irc 'ding' before the email. =)
[03:02] <valorie> zsyncing was good; it will probably save you some time
[03:02] <valorie> aha, it now says (rebuilding)
[03:02] <BionicMac> valorie: my bad. I was in the wrong dir/ when I zsync'd.  
[03:02] <valorie> :-)
[03:02] <valorie> heh
[03:03] <BionicMac> Lot of upgrades today including the kernel.
[03:05] <BionicMac> Even 16.04 had a new kernel on my server(s) upgrades.
[03:06] <valorie> yeah
[03:07] <valorie> I had a problem because packagekit crashed part way through an update
[03:07] <valorie> had to use apt and dpkg to fix it
[03:07] <valorie> and go back to nvidia after trying intel with prime-select 
[03:11] <BionicMac> I kinda sorta don't miss nvidia cards. Been a many moon since 2000 or so since I ran one.
[03:11] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Bionic Final] has been updated (20180425)
[03:11] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop i386 [Bionic Final] has been updated (20180425)
 they are a bargain with the devil
 you're tempted with marginally better performance per dollar, but suffer an eternity of torment
[03:12] <BionicMac> Yup, I quaked my bum off with a killer nvidia setup nack in the day. Every time I upgrade the kernel.. argh...
[03:12] <BionicMac> haha eternity!
[03:12]  * BionicMac cracks up a bit
 Mandatory nomodeseton a live boot on hybrid laptop, would anyone consider that a bug?
 Hey, they fixed the boot menu option on 4k screens.  Text is no longer 1mm high and its fast.  Naviagation to add nomodeset used to be painfully slow...
[03:48] <valorie> oh hey, there are our new images
 yep, testing now....
[03:48] <valorie> zsyncing....
[03:48] <tsimonq2> \o/
 my zsync was really fast (less than a minute, but I was not timing).
[03:56] <valorie> yeah
[03:57] <valorie> ok, lists written to
[04:39] <valorie> I've been getting multiple updates daily lately
 yes, updates down to the wire seem more prevelent this time around.
 2 installs on 2 different PC's went well.  I did not test OEM this time around.  Will test tomorrow unless someone beat me to it.  Nite all.
[05:05] <valorie> i"m testing oem right now
[05:06] <valorie> trying to find the bug number for clicking on links does nothing.....
[05:07] <valorie> LP#1681144 if anyone needs it
[05:08] <valorie> LP:#1681144 
[05:08] <valorie> huh
[07:17] <acheronuk> yes
[07:18] <acheronuk> why shouldn't it?
[07:23] <acheronuk> not everyone has a modern low form factor laptop without a cd drive or burner
[07:30] <valorie> I still use it rip CDs
[07:31] <valorie> and occasionally (at linuxfest for instance) to burn DVDs for people
[08:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2195: SUCCESS in 54 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2195/
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2195: SUCCESS in 1 min 17 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2195/
[08:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2195: SUCCESS in 4 min 19 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2195/
[11:06] <acheronuk> there is a new ubiquity coming to fix the reboot issue, so another respin looks very likely
[11:22] <BluesKaj> Howdy folks
[11:23] <mparillo> Howdy BluesKaj. A quarter-hour ago, we learned that new BB spins are likely.
[11:24] <BluesKaj> 'Morning mparillo, already  ?
[11:26] <mparillo> More like again. I entirely missed the spins that were tested whilst I slept.
[14:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2196: SUCCESS in 44 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2196/
[14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2196: SUCCESS in 1 min 15 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2196/
[14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2196: SUCCESS in 4 min 15 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2196/
[15:30] <mhall119> hey all, the Flatpak developers are gathering packaging guides for different languages and build systems to put on docs.flatpak.org, is there anyone here who would write one for the build systems Qt and KDE apps use?
 ping Aleix Pol about that
 he maintains our Flatpak build system stuff
 apol@kde.org
[15:38] <mhall119> thanks nggraham
 no problem
 Can anyone with a Bionic laptop (clean install) in front of them confirm that suspend on lid close works?
 If not, we will need to patch powerdevil for https://cgit.kde.org/powerdevil.git/commit/?id=be91abe7fc8cc731b57bec4cf2c004c07b0fd79b
 (Don't have mine available right now)
 @nggraham Not release-critical I assume?
 Worst case scenario, it can wait until I SRU the next Plasma 5.12 point release. … (I put an emphasis on me doing the work because if I recall correctly @acheronuk doesn't want to do it. :P)
 if it is indeed present, I would call it release-critical; there'll be no power management for laptops. You'll shut the lid and nothing will happen, and they won't suspend before they run out of battery power
 @nggraham, Then let's get this confirmed if present as soon as possible so I can yell loudly.
 indeed
 I found one report; need to confirm: https://www.reddit.com/r/kde/comments/8es08k/how_do_i_suspend_my_laptop_on_lid_close/dxy2yq6/
 @nggraham Just talked with Release Team... Does this /need/ to be in the ISO or can it land as a 0 day update?
 slangasek> tsimonq2: if 0 day SRU is even an option for whatever it is, then that's your only option … slangasek> tsimonq2: anything that doesn't scream "this needs to be in the ISO" doesn't need to be in the ISO
 could it be a 0-day update with an iso re-spin on that day?
 (lots of people never update...)
 @nggraham, It's an LTS, so while you won't get an ISO spin on the thing called "18.04 final", it will land in the point release.
 @nggraham, Not if they keep the checkbox checked for "Download updates during the installation"
 ah right
 ok, let's shoot for a 0-day at this point
 I don't object to it being a 0 day SRU, but if you think it NEEDS to be in the ISO and can confirm it, hop in #ubuntu-release and scream loudly.
 @nggraham, Ok.
 @tsimonq2, And that goes for every bug at this point.
 @nggraham Then it's settled.
 0 day SRU it is.
 👍
 Thanks as always!
 No problem.
 I'll give you something to test tonight at 7:30ish PM Central.
 ok, thanks!
 Np
 Nate, I have clean BB install from month+ ago.  Sleep on lid closed works perfectly.  I have fresh installs at home, but I won't be home for another 6 hours.  I can also assist with testing at that time.
 thank you very much for testing
[19:23] <acheronuk> zero day sounds wiser to me at this point
[19:48] <valorie> I'll check on my testing laptop right now
[19:54] <valorie> works perfectly on an install from last night
[19:55] <acheronuk> clean install?
[19:55] <valorie> on my little Dell/intel
[19:55] <valorie> yes
[19:55] <valorie> probably the oem test I did last night
 fantastic, maybe it's not an issue then...
[19:57] <valorie> it isn't suspend by default; it is "do nothing" by default
[19:57] <acheronuk> the commit says config is not created on a clean install, but your experience suggests that is either not always the case, or in some circumstances the problem resolves itself
[19:57] <valorie> well, I went into systemsettings and set it to suspend
 @valorie, it should be suspend by default on lid close
[19:58] <valorie> like I said, default is "do nothing" when lid is closed
[19:58] <valorie> it is not
 if you're not seeing that, then that's the bug
 ok, so you just hit the bug :(
[19:58] <valorie> ok, then I confirm the bug
 darn
 thanks a lot for testing!
[19:59] <valorie> do we have a BR yet?
[19:59] <acheronuk> IMO do nothing by default is correct. I see no reason why laptop should assume you closing the lid means you want to suspend
[19:59] <valorie> or should I file one
[19:59] <acheronuk> that should be an option you enable
[19:59] <valorie> I agree
[19:59] <valorie> in general, I only turn that on sometimes
 suspend on lid close is like the standard behavior since forever, and matches the user expectation
[19:59] <valorie> and off at Akademy
 not having this behavior is a bug that was just fixed
[19:59] <valorie> :-)
[20:00] <acheronuk> not my expectation
[20:00] <acheronuk> :P
 people who don't like it can turn it off, but it's *supposed* to be the default
[20:00] <valorie> imo it has changed back and for a few times
[20:00] <valorie> so once it bites me, I change it
[20:01] <acheronuk> bigger issue on that sounds like the default power button actions to me
[20:01] <valorie> yes, it was set to "do nothing" which is bizarre
[20:01] <acheronuk> "eading to it not suspending on lid close, not handling power buttons etc etc"
[20:01] <acheronuk> *leading
[20:01] <valorie> otoh, it worked when I pushed it
[20:03] <valorie> acheronuk: I think I disagree with you on what the default should be
[20:04] <valorie> I would say that 99% of people expect suspend when the lid is closed
[20:04] <valorie> and maybe half care that they can change that in Plasma
[20:05]  * valorie files a bug
 @nggraham Riddell added that patch to Neon user edition powerdevil this morning, and now a user reports this … https://paste.kde.org/py7uwhhpo
 I will NOT let that fix into Kubuntu until it has been tested
[20:06] <mmazur^> They do, though possibly only because laptops have mechanical parts. With a no-fan/no-hdd laptop, it sort of doesn't matter if the thing falls asleep a minute after it's closed… I guess.
 even though that may not be the cause of that issue
 not sure that's related, but fair enough
 @nggraham, I suspect it is not either, but right now I'm erring on the side of caution
[20:09]  * mmazur^ really likes the state of kde in bionic; every release some things work nicer
[20:09] <mmazur^> (except multi display with amdgpu, but that's because amdgpu still sucks)
[20:16] <valorie> hmmm, what do I file a bug against?
 powerdevil?
[20:17] <valorie> was upgrading my primary install etc.
[20:17] <valorie> ok
[20:18] <acheronuk> plasma 5.12 got to a .4 release without this being noticed, so *** shrug ***
 @DarinMiller are you able to test for the zero day if @tsimonq2 prepares it?
[20:24] <valorie> LP:#1766967
 more so we know it doesn't break existing installs
[20:26] <acheronuk> LP: #1766967
[20:26] <acheronuk> :P
[20:26] <valorie> oh, a space
[20:26] <valorie> sheesh
[20:27] <valorie> it's true, I never tested for that, or even noticed it
[20:27] <valorie> otoh my little lappy kept going dead and I didn't realize why
[20:27] <acheronuk> I'm not being smug, as it took me an embarrassingly long time to work out how to make that bug trigger always work! LOL
[20:28] <valorie> oh, you have the perfect right to be smug
[20:28] <valorie> lol
[20:28] <valorie> I would be feeling smug if I'd already mowed the lawn
[20:28] <valorie> but....
[20:28] <valorie> no
 @acheronuk, Yes, I can test assuming my current laptop meets your test requirements.
 Clarification on previous sleep when lid is closed.... I had to enable it myself.  Kubuntu has always been that way.
 Right. :)
 @nggraham so what would this fix change the default power button action to?
 not sure actually
 only sane defaults IMO would be "ask wat to do", with "nothing" a safe but silly fallback
 actually I do know: it shows the logout dialog with options for what to do
 @nggraham, Kool
 yes, after a momentary brain fart, I remembered that that is indeed what it does :)
 So how does one answer a screen prompt when the screen is closed?
 context?
 one opens the lid?
 From my understanding, the "closed lid" patch prompts the user what he wants to do when lid is closed.  If the lid is closed, he will not see it, battery goes dead, and the user is none the wiser.
 the patch fixes the issue that caused the lid closing event to not trigger suspend as is the intended upstream behavior
 Almost needs to be a pre-emptive configuration prompt on fresh install.
 the default behavior on lid close is *not* a UI prompt; that's the default behavior when you press the power button
 ohhhh, that makes way more sense.
[22:51] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Bionic Final] has been updated (20180425.1)
[22:51] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop i386 [Bionic Final] has been updated (20180425.1)
[22:57] <valorie> weeeeeeeeeeeeee
[22:58] <acheronuk> fingers crossed for last spin
[22:59] <valorie> knock on wood
[22:59] <acheronuk> tomorrow I will try to....
[23:00] <acheronuk> 1) test some isos
[23:00] <acheronuk> 2) update upgrade wiki page with nice pics
[23:01] <acheronuk> 3) draft relase announcement if no-one gets there 1st. please do if you feel like it!
 @MichaelTun is getting a video ready ;)
 👍😎
[23:05] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #1085: SUCCESS in 5 min 43 sec: https://kci.pangea.pub/job/mgmt_merger/1085/
[23:06] <valorie> I think I wrote one?
[23:09] <valorie> yep, there is a draft
[23:09] <valorie> feel free to fix links, etc.
[23:09] <valorie> mparillo: ^^^
[23:15] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ruqola build #192: STILL FAILING in 9 min 7 sec: https://kci.pangea.pub/job/bionic_unstable_ruqola/192/
[23:30] <valorie> and the lists written to again
[23:33] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kalzium build #85: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/bionic_stable_kalzium/85/
 Ok. goodnight all. I will be up my time in the morning to get things done I hope
 good night!
[23:41] <valorie> niters @nggraham
[23:52] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_cantor build #103: STILL UNSTABLE in 44 min: https://kci.pangea.pub/job/bionic_stable_cantor/103/
[23:57] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #131: STILL UNSTABLE in 49 min: https://kci.pangea.pub/job/bionic_unstable_kstars/131/
[23:57] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_libkgapi build #66: STILL UNSTABLE in 50 min: https://kci.pangea.pub/job/bionic_unstable_libkgapi/66/
[23:58] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_messagelib build #194: STILL FAILING in 50 min: https://kci.pangea.pub/job/bionic_unstable_messagelib/194/