[11:09] <blaze[m]> In my case Plasma Wayland session doesn't even start. Computer just freezes and I have to restart it
[11:09] <blaze[m]> Sigh
[11:10] <blaze[m]> With every Plasma release it just gets worse and worse
[11:10] <blaze[m]> :D
[11:35] <yofel> well, as long as your release upgrade at least went fine... Mine exploded into stars thanks to someone putting impossible upgrade requirements into virtualbox
[11:37] <yofel> still trying to figure out what all got missed
[11:40] <blaze[m]> Right, I had that issue with virtualbox too
[11:42] <blaze[m]> I had to remove everything virtualbox-related with dpkg and then complete my upgrade
[11:44] <yofel> well, a reboot is enough to get the virtualbox package install to succeed afterwards. But that then removed kubuntu-desktop because keeping amarok installed was more important to apt than uprading breeze.. and I'm not sure if something else got missed as well
[11:46] <yofel> ok, with the correct breeze version I have a background image on the login screen again
[11:48] <yofel> FWIW, the team did a good job on the plasma part otherwise. No visible issues other than what got caused by vritualbox
[11:48] <yofel> sadly 19.10 fixes none of the issues 19.04 brough me. But none of those are KDE releated
[12:00] <RikMills> yofel: ouch. have forwarded that to last person to do vbox uploads
[12:01] <RikMills> yofel: on bytemark, when it looked like we might lose linode, I started trying to get LXD containers set up there. not needed now I guess, so please undo if needed
[12:06] <yofel> it shouldn't break anything so I would leave it there for now. We might need that at some point after all
[12:18] <yofel> as for virtualbox: it's only kind of a packaging issue.. the dependencies don't match the requirements of virtualbox. And virtualbox from eoan does not support the kernel from disco. But that's what DKMS will try to build a kernel for during the upgrade, meaning the kernel requirement of the new virtualbox are impossible for the release upgrade
[12:18] <yofel> not sure how you would fix that other than downgrading virtualbox...
[12:28] <RikMills> yofel: ah, there was exactly the same sort of issue building some Eoan nvidia kernel modules with the disco kernel. that was reported and fixed, but guess vbox slipped under the radar :/ 
[13:35] <BluesKaj> Hi folks
[13:56] <Mamarok> upgraded to 5.17 this morning, works great :-) Just one knit-pick: why on earth does it override my default Desktop view with Folder View?  Shouldn't touch the previous settings IMHO
 Mamarok: I was not aware that happens. Please report it to KDE if you think that is out of order. It is certaily nothing Kubuntu has done on purpose.
[13:58] <Mamarok> Just did tell Kai, we are showcasing Plasma 5.17 at Linuxday.at in DOrnbirn today :-)
 Nice. Kai is super at investigating things like this
[14:04] <Mamarok> indeed, great guy to work with, and also great booth guy, he loves to explain to people visitng the booth
[15:15] <yofel> now lets try to get jenkins up to date..
[16:23] <RikMills> yofel: told to point you to https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1848006
[16:28] <yofel> ok then. Maybe that got out a tad too late for me
[16:30] <RikMills> That is what Gianfranco Costamagna <locutusofborg> thinks
[16:35] <yofel> yeah, looks like I forgot to reboot before the upgrade
[16:37] <RikMills> yeahm though it is arguable there should be measures in place to prevent trying to build on incompatible kernels. maybe somthing to address
[17:00] <yofel> thinking about it, on another system do-release-upgrade refused to upgrade before I rebooted, so I wonder what happend there
[17:27] <yofel> why is the old CI server still a thing...
[17:28] <yofel> sitter: ^
[17:29] <yofel> are you using river for something? otherwise that's just eating money
[18:52] <clivejo> Hi yofel, RE: river,  There was discussions at one point to rebuild a new NG CI system in python and I asked Clemen's if that was okay.  He said it was fine to do that.  
[18:53] <yofel> ah ok, thanks. I stopped jenkins on it so the bot doesn't hijack the nick, I'll leave it alone otherwise then
[18:53] <clivejo> sorry if that has already been discussed, Rik forwarded me on part of the conversation on Telegram
[18:54] <clivejo> I have no idea on the state of play on the new NG CI, I believe santa and tsimonq were working on that
[18:54] <yofel> RikMills: kci master is now running 18.04 and jenkins + plugins are updated. The ruby-runtime plugin fails to load now though, lets see if I can fix that
[18:54] <clivejo> but Clemen's was happy for them to use it as a test machine
[18:55] <clivejo> but that was while I was still on the team, might be best if someone touches base and confirms that
[18:57] <clivejo> Rik has the keys to rive, I believe
[18:58] <clivejo> I think he might be out partying
[18:59] <RikMills> clivejo: not quite, but I have maybe had more Jack Daniels than is recommended for tweaking servers
[19:00] <clivejo> some say it helps :P
[19:01] <RikMills> I think I am on the wrong side of the balmer curve ;)
[19:01] <RikMills> *peak
[19:02] <clivejo> BTW anyone got wayland working on NVidia?
[19:02] <clivejo> well plasma-wayland
[19:03] <RikMills> nope. it hates my card, even on latest plasma
[19:03] <clivejo> even on 5.17?
[19:03] <clivejo> darn, was hoping it would work!
[19:04] <blaze> Even amd doesn't work anymore, at least for me
[19:04] <RikMills> yesyes
[19:04] <clivejo> oh, that's odd
[19:04] <blaze> maybe I'm too lucky
[19:04] <clivejo> works great for me, just not NVidia :(
[19:06] <clivejo> anyone happen to know where the new redshift/night mode settings are in 5.17?
[19:07] <blaze> display and monitor
 wayland on NVidia works on my hybird laptop, but locks up my desktop.
 I was curious how if others experienced the same, seems so...
[19:09] <clivejo> Hi DarinMiller, I haven't tried it yet under 5.17
[19:10] <clivejo> we disable Wayland by default currently, so have to manually install the files I need
 Hi clivejo.  wayland requires manual install on kubuntu also.  Still not quite ready for prime time, but inching ever closer.
[19:15] <clivejo> ah cool, haven't used Kubuntu in a wee while, so out of the loop so to speak!
 :)
[19:17] <RikMills> yeah, keeping it as an 'you can install that session if you want to test, but it is not supported'
[19:18] <RikMills> having it there by default on sddm login options implies to too may that it should work
[19:18] <clivejo> RikMills: do you remove the session file in packaging?
[19:20] <santa_> hello everyone
[19:20] <RikMills> clivejo: seperated into: https://packages.ubuntu.com/eoan/plasma-workspace-wayland
[19:20] <RikMills> which is not installed by default
[19:20] <santa_> clivejo: nice to see you again :)
[19:20] <RikMills> santa_: hi!
[19:22] <santa_> clivejo: I had to pause my research on a new CI implementation a while ago, but I hope to resume it when KA is a bit more mature to handle that
[19:23] <santa_> RikMills: hi, if you want to discuss a few things about the packaging I'm available tonight
[19:24] <santa_> speaking of which, I have updated groomlake's tritemio to handle focal, first test rebuild in progress: http://tritemio-groomlake.duckdns.org/build-status/buildstatus_ubuntu-exp3/ubuntu-exp3_status_frameworks.html 
[19:26] <RikMills> santa_: well, as previously said, I have had more than a few Jack Daniels, so not sure how much my technical comprehension is up to that
[19:27] <santa_> RikMills: oh ok, I haven't seen that, let's have that talk tomorrow whenever you are in shape ;)
[19:27] <RikMills> I will mention a few things though, which I bet you have seen in debian
[19:28] <santa_> ok, go ahead please
[19:28] <RikMills> 1) Pio has been removing crappy testsuites so we can follow suit when 19.10 queue is unblocked
[19:29] <santa_> Pino
[19:29] <RikMills> *Pino
[19:30] <RikMills> 2) PIM is having symbols removed, and moving to a virtual ABI provides way of ensuring ABI deps are required internally and on other packages
[19:31] <santa_> ok
[19:31] <santa_> anything else?
[19:31] <RikMills> seems sensible to follow? I would say so, even if you disagree, as not a fun delta to maintain
[19:32] <RikMills> santa_: those were the main things
[19:32] <santa_> I'm fine to follow debian in autopkgtest removal
[19:32] <santa_> ack, I plan the next few days if possible:
[19:33] <santa_> - prepare tritemio's area51 for focal and do test rebuilds
[19:34] <santa_> - remove some of the branch checking from KA as we discussed some weeks ago in order to prepare the first 2.3 beta
[19:34] <santa_> - think about debian merges
[19:34] <santa_> and that's it, I think these are the main thing on my "agenda"
[19:34] <RikMills> seems good
[19:34] <santa_> * the main things
[19:35] <RikMills> 1st thing I will do is drop the tests debian did, then any subsequent stiff we do (FW etc) will trigger less to annoy the release team (Laney)
[19:35] <santa_> that's cool
[19:35] <RikMills> s/stiff/stuff
[19:36] <RikMills> ok. we are on same page then
[19:36] <santa_> :)
[19:36]  * RikMills pours another JD
[19:37]  * RikMills hands one to clivejo and anyone else who wants
[19:44] <clivejo> sorry, had to go to the shop before it closed!
[19:44] <clivejo> yeah, sure
[19:46] <clivejo> do you'll still use BBB?
 nice to see you clive!
 we've not had a meeting there for awhile, but they have it available to us
[20:18] <clivejo> Hi @Valoriez
[20:18] <clivejo> has anyone logged into it recently?