 @mparillo, I am hoping the next iso with ubiquity fixes in a few hrs might be ok
 ISO seems fixed
[10:50] <mparillo> TY. zsync'd. Seemed to boot fine in a VM. Selected install now. It did not guess my region, nor my time zone. I was able to click on the map for the time zone and the drop-down for the region, but the timezone did not populate in the drop-down
[10:51] <mparillo> Otherwise took defaults (full install, wipe the disk, etc.) Clicking the links still does nothing.
[10:57] <mparillo> And re-booting gives me Plasma 5.20.90, with no immediate breakage.
[10:58] <RikMills> cool. or at least we can get functional now
[11:01] <mparillo> ISTR there was a need to ship Oxygen sounds with the ISO so that sounds would work. But an unanticipated benefit for me is that my beloved Oxygen yellow cursor theme is on the ISO
[11:04] <mparillo> Ugh. I picked Toronto instead of NY for the time (they are pretty close on the World Map, and as I said, I got no feedback in the time zone drop-down in Ubiquity., and they generally go on and off summer time within weeks of one another). So I fixed it in System Settings. Question: Is it possible that I now have a different time zone in KDE System Settings and in my kernel?
[11:07] <mparillo> It seemed to update /etc/timezone.
 https://twitter.com/kdecommunity/status/1353998615732215808
[12:15] <BluesKaj> Hi folks
[21:54] <santa_> hi everyone
[21:54] <santa_> RikMills: the kalzium FTBFS in my server was a broken chroot, kitinerary still needs an upload
 oh, right
 done
[22:00] <santa_> thank you very much
[22:01] <santa_> btw, since a long time ago, I have a particular package (I don't remember which) which doesn't get properly uninstalled in a chroot
[22:02] <santa_> I bet that's what caused the kalzium "FTBFS"
[22:02] <santa_> * I don't remember which one
[22:06] <RikMills> santa_: and kitinerary FTBFS
[22:07] <RikMills> https://bugs.debian.org/980599
[22:56] <santa_> RikMills: I think it's not the same FTBFS
[22:58] <RikMills> santa_: yes, I think the libphonenumber uploader in the meantime screwed thing 10 times worse trying to fix previous issue
[23:06] <santa_> RikMills: now, this is the one from debian! https://launchpad.net/ubuntu/+source/kitinerary/
[23:06] <santa_> it's another one!
[23:06]  * santa_ facepalms
[23:07] <santa_> we are now getting the OTHER one from debian
[23:07] <RikMills> yes, as the even more broken -4 upload of libphonenumber synced
[23:09] <santa_> no no no
[23:09] <santa_> we have in ubuntu the 3.12.4-1ubuntu1
[23:10] <santa_> the one that - allegedly - fixes this new FTBFS is 3.12.4-4
[23:10] <RikMills> https://launchpad.net/ubuntu/+source/libphonenumber/8.12.16-4
[23:10] <santa_> ah, no no no
[23:11] <santa_> this new FTBFS, if I'm not mistaken is Powered By™ protobuf
[23:14]  * RikMills shrugs
[23:15] <santa_> hmm nope
[23:15] <santa_> dammit I'm confused
[23:15] <santa_> in any case we have a protobuf different than debian's
[23:16] <RikMills> but the same fail
[23:19] <RikMills> oh well, kitinerary is not exactly crucial in the short term. not going to worry much on it at this stage
[23:28] <santa_> RikMills: libphonenumber needs to be rebuilt in ubuntu against latest protobuf
[23:29] <RikMills> it is in main, so I can't
[23:29] <santa_> we have to ping LocutusOfBorg then
[23:32]  * RikMills asks
[23:38] <santa_> I've just pinged him in -release
[23:40] <RikMills> ok