 @The_LoudSpeaker [should we also have a default lxqt related theme in libreoffice for future relea …], we have
 I mean, we changed the default
 (Photo, 445x358) https://i.imgur.com/ERPgqCx.jpg I don't remember how we do it but we did in old phab,
 (Photo, 445x358) https://i.imgur.com/l6W1jhK.jpg
 maybe @wxl23 xl or @tsimonq2 remember ...
[00:32] <wxl> in default settings?
 I look at it and didn't found something I think is for it.
 was old task 96, we couldn't recover it.
 found it! it was seed https://phab.lubuntu.me/rSEEDe36f3c2f194882802b1d904983f0edfb1d5a8303
 Oh wow! Cosmic. What a blast from the past.
[18:42] <wxl> has anyone tried a focal→groovy upgrade recently? there's a bug saying qps fails to upgrade which i am highly suspect of
 wxl: i'm clearing out disk space to make space for more stuff on my system, I can do a test upgrade in KVM
 gotta clean up 250GB of space tho xD
 I am updating a 20.04 vm now. I can give it a go too.
 I updated a couplwe of weeks ago, and had no problem.
 (electron tray icons work now)
[18:53] <wxl> @HMollerCl you think you can change dpkg/apt logs and see which qps you changed from/to? 
 I'll try
 @wxl23 I did … grep -ri 'qps' … in /var/log/apt and fonf nothing, any other idea?
[19:13] <wxl> @HMollerCl likely not that simple as older ones are gzipped. you should see if the ones from a couple weeks ago haven't been recycled by now
[19:18] <wxl> oh nevermind i just realized @leokolb already tested upgrades (see the testing checklist) on the 8th
 Mine is doing its thing in the background. More tests can't hurt.
[19:19] <wxl> sure
 @kc2bez [Mine is doing its thing in the background. More tests can't hurt.], I can test this again on different machines..early AM
 Still getting the TimeZone bug (LP#1898501) on the daily installs.
 @franksmcb [Still getting the TimeZone bug (LP#1898501) on the daily installs.], Yeah, that one is weird. Not sure I have a solution since it seems to happen on 20.04 too.
[19:41] <wxl> i wonder if it isn't an issue with the api changing in a breaking way
[19:41] <wxl> i believe we have to set the key we're using
 Possibly the output format changed for `timezone` from here https://ipapi.co/json
[19:51] <wxl> well we're supposed to use country in welcome
 Yes, that too.
[19:52] <wxl> the locale module uses the time zone
 Right.
[19:54] <wxl> why are we using ipapi and not e.g. https://geoip.kde.org/v1/calamares?
[19:54] <wxl> or https://geoip.kde.org/v1/ubiquity
[19:54] <wxl> these are what upstream is using
 I think this applies https://phab.lubuntu.me/macro/view/4/
 But in consultation with [ade] the examples in the the config are just examples.
[19:57] <tsimonq2> <lubot "<kc2bez> I think this applies ht"> XD
[19:57] <wxl> ah they're not testing them eh
 I do know there was an issue with the kde thing a bit ago so no guarantees on that working.
[19:59] <wxl> check this out: it appears that there may be an issue https://github.com/calamares/calamares/issues/1240
[19:59] <wxl> the theorized fix is in 3.2.31 which we ain't got yet https://github.com/calamares/calamares/commit/0a1dc77f9be6b4c696e05fe218f7ff525d5bc702
 Oh weird. 1240 got closed a year ago.
[20:01] <wxl> right
[20:01] <wxl> also interesting, look at the last session.log on the bug https://launchpadlibrarian.net/501661670/session.log
[20:02] <wxl> 2020-10-12 - 01:58:24 [2]: virtual QString CalamaresUtils::GeoIP::GeoIPJSON::rawReply(const QByteArray&) WARNING:Invalid YAML data for GeoIPJSON
[20:02] <wxl> THAT is weird
[20:02] <wxl> 2020-10-12 - 01:58:24 [6]: setGeoIP(Config*, const QVariantMap&)::<lambda()> GeoIP result for welcome= "" 
[20:02] <wxl> 2020-10-12 - 01:58:24 [6]: void setCountry(Config*, const QString&, CalamaresUtils::GeoIP::Handler*) Unusable country code "" 
[20:02] <wxl> that's definitely not right
[20:02] <wxl> and there's only one set of the results, meaning that it tried to get the country (welcome) but not the timezone (locale)
 Yeah for sure.
 It puts the welcome stuff into the global store I think.
[20:03] <wxl> so i would suggest we grab 3.2.31 and/or master and run it through in debug mode and see what we're getting
 We should have it in CI. I can test it from there. I am the worst person to test though since I am in NY XD
[20:05] <wxl> use a vpn :)
 I have to VPN somewhere to fake my location.
 :D
[20:05] <wxl> riseupvpn has no node in ny that i know of fwiw
[20:05] <wxl> also it might be interesting to test different formats. xml, csv, yaml, and jsonp are all options
[20:06] <wxl> (that's the "style" configuration key)
 Good point. It might read a different format better.
[20:07] <wxl> it looks like only json or xml are acceptable by calamares
 right. I can try xml
[20:19] <wxl> for anyone that was bothering with the upgrades, nevermind. they somehow had a version of a core qt library that is higher than anything in the repos.
 wild.
 I broke my VM. Turns out you need disk space to do an upgrade. SMH
 I was wondering why it was taking so long.
[20:41] <wxl> wow, weird, go figure XD
 @wxl [<wxl> for anyone that was bothering with the upgrades, nevermind. they somehow h …], ok was 1/2 way through,,good to check anyways:)
[20:57] <wxl> @leokolb indeed. i'm glad you're doing upgrade testing regularly. this is often something that's an after thought when testing
[22:34] -queuebot:#lubuntu-devel- Unapproved: calamares-settings-ubuntu (groovy-proposed/universe) [1:20.10.9 => 1:20.10.10] (lubuntu, ubuntustudio)
[22:38] <Eickmeyer[m]> ^ forgot to upload before the beta. I'm a bot. >.<
 FYI I've added calamares from the unstable-ci PPA and still have the timezone issues during installation.
 @franksmcb [FYI I've added calamares from the unstable-ci PPA and still have the timezone is …], Do you still have the log file handy? If so can you provide a paste?  Thanks for checking Bill
 Give me a few and I will
 Awesome thanks.
[23:18] <wxl> @franksmcb if you still have that up and running we could suggest a couple variables to twiddle which might make a difference (see earlier discussion re: formats and/or perhaps different geoip services)
 i've got a live system up and running wxl right now
 @wxl [<wxl> @leokolb indeed. i'm glad you're doing upgrade testing regularly. this is …], upgrade via term -ok - graphical running - good night
 @Leokolb [upgrade via term -ok - graphical running - good night], Thanks!
[23:41] <wxl> @franksmcb sorry for the delay
[23:42] <wxl> so if i remember correctly at /etc/calamares/lubuntu/modules there should be a bunch of conf files
[23:43] <wxl> try changing the "style" key under the "geoip" section to "xml" and also change the "json" in the "url" key to "xml" in both welcome.conf and locale.conf and see if that helps
 I'll give those a shot wxl and let you know
[23:46] <wxl> you can also try using "https://geoip.kde.org/v1/calamares" as a url for locale with "style" "json" and/or "https://geoip.kde.org/v1/ubiquity" with "style" "xml" for either of the modules but the "selector" on that one would need to be "CountyCode" for welcome and "TimeZone" for locale
[23:47] <wxl> regardless of the results, grep the log file for "GeoIP" as there really should be two sets of results, one for the country code (e.g. "US") and one for the time zone (e.g. "America/Los_Angeles"). if there is only one, it would be good to know which one and it would be good to know if there are any errors
[23:47] <wxl> thanks in advance!