[00:16] -lugito:#lubuntu-devel- [rMANUAL96e6ab58e84a: Fix indent] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL96e6ab58e84a
 FYI I am seeing the 1845424 timezone bug on the VM and BM installs, isotracker updated
 @franksmcb can you post your install log to the bug please? You should be able to find it in /var/log/installer/debug
 Will do.
 Thanks, I appreciate it.
 @kc2bez [Thanks, I appreciate it.], Done
 Thanks for all the help @franksmcb !
[01:43] <guiverc> fyi: vlc still doesn't start in live testing; I hoped it would with "fix committed" marked (25-sept) for eoan - lp 1842382
[01:44] <kc2bez> guiverc: have you seen bug 1845424 ?
[01:45] <kc2bez> I ask because you are in a different time zone than me. I am unfortunately in America New York (the default)
[01:46] <guiverc> i don't use QEMU/KVM so no; I did an install ~2 days ago on bios hardware without issue & it recognized my location
[01:46] <kc2bez> Good to know. 
[01:47] <kc2bez> I think there was a report on hardware as well though. 
[01:47] <guiverc> I'll have another quick look now.. 
[01:48] <kc2bez> I appreciate it. 
 Yeah the log's I sent where from bare metal
[01:53] <guiverc> kc2bez, it detects me as melbourne, au where i am   (the only thing I did pre-starting-install is adjust display to portrait-left)
[01:55] <kc2bez> Thanks guiverc and @franksmcb
[01:56]  * kc2bez sighs
[01:56] <kc2bez> inconsistent results are difficult to troubleshoot. 
 I've got the 1842382 live usb VLC bug as well. I can provide any logs you need for that
[02:01] <guiverc> thanks @franksmcb, I don't think required; it was chased down to a specific kernel patch, I was hopeful of fix alas not today :(
[02:06] <guiverc> kc2bez, install completed; all good with correct timzone, vlc starts post-install 
[02:07] <kc2bez> Thanks guiverc
 I can confirm that VLC works post-install
[02:12] -lugito:#lubuntu-devel- [T120: Lubuntu 19.10 Beta Release] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T120#2394
[03:07] <wxl[m]> @freenode_guiverc:matrix.org: is there a reason you marked what sound like successful tests as failed? http://iso.qa.ubuntu.com/qatracker/milestones/406/builds/200084/testcases/1303/results
[03:07] <guiverc> wxl[m], only b/c of vlc not starting on 'live'  - no other reason
[03:08] <wxl[m]> @franksmcb thanks for the help
[03:08] <guiverc> if you want it changed, I can...
[03:08] <wxl[m]> @freenode_guiverc:matrix.org: you're a little more conservative than I in regards to judging test success 😉
[03:09] <wxl[m]> Err more liberal
[03:09] <wxl[m]> I only look at the testcase itself 
[03:10] <guiverc> "Use and execute the default applications found..." - vlc won't run
[03:10] <guiverc> "All applications should function without error"
[03:11] <guiverc> the GnuPG one also fails, but I won't fail for that..
[03:11] <wxl> touché!
[03:12] <wxl> i should send a patch to allow for additional columns to distinguish different types of success
[03:21] <guiverc> changed the hp8200 with many bugs to pass; so only crapbook with single vlc issue now is fail 
[03:31] <wxl> from what i can tell the qtpass bug is likely fixed with https://github.com/IJHack/QtPass/commit/7f8136e4f08baea281cef62393ff75616ce09c74 and https://github.com/IJHack/QtPass/commit/827a7104cebace94802dc479e2f3ae7564a99469 whcih are in 1.3.0 https://github.com/IJHack/QtPass/releases/tag/v1.3.0 which is in bullseye https://packages.debian.org/source/bullseye/qtpass so someone should get that synced
[04:39] -lugito:#lubuntu-devel- [rMANUAL5d232d934457: Add start of system tray for screengrab] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL5d232d934457
[04:43] -lugito:#lubuntu-devel- [rMANUAL8c2c11b00f79: Add show screengrab from tray icon] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL8c2c11b00f79
[04:47] -lugito:#lubuntu-devel- [rMANUALe29468fd02ba: Add new icon from systray] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALe29468fd02ba
[04:49] -lugito:#lubuntu-devel- [rMANUAL3a736dcda598: Fix capitilization] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL3a736dcda598
[04:51] -lugito:#lubuntu-devel- [rMANUAL8882369ef724: Add save from tray icon click] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL8882369ef724
[04:56] -lugito:#lubuntu-devel- [rMANUAL01bb6fe70fac: Add copy to clipboard from systray] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL01bb6fe70fac
[05:00] -lugito:#lubuntu-devel- [rMANUAL63179f467776: Add options from system tray] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL63179f467776
[05:02] -lugito:#lubuntu-devel- [rMANUALbba0bcba0310: Add quit ScreenGrab from systray] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALbba0bcba0310
 @HMollerCl [I think we can get people in the Spanish channel to help with iso testing @N0um3 …], Is a good idea ;)
 @kc2bez tested the timezone issue, ha a 24sept downloaded iso, same issue so it's before that.
 buuuuuut
 got ntp.ubuntu.com timeout
 strange
 if I try to connect in my browser also gives tomieot, but maybe is my proxy
 *timeout
 what do you get when you go to https://ipapi.co/json ?
 that works
 (Photo, 1280x960) https://i.imgur.com/PTr1wfa.jpg calamares log
 wait, I forgot to configure the proxy
 configure the proxy in /etc/environment and can ping ipapi.co (firefox use their own proxy config) but still have wrong timezone.
 i... don't think NTP respects proxies...
 it probably doesn't since it is UDP
 ^ this
 @HMollerCl your clock won't update because UDP doesn't respect proxies
 so you either have to update manually
 or run an NTP server from behind the proxy that *has* NTP access to an NTP server
 so you'll probably have to set the time manually
 ok, thanks
 Check out https://phab.lubuntu.me/w/release-team/iso-building/
 I just wrote it
 It covers the basics of how the ISOs are built
 The goal is to eventually add on more
 If someone could read through it and ask questions, that'd be awesome.
 There might be a fair bit of tsimonq2isms :)
 Could you add some infos about the bootloaders? BIOS and EFI configuration?
 @aptghetto [Could you add some infos about the bootloaders? BIOS and EFI configuration?], I'm not personally familiar with how that is done in the ISO building process
 However, you're welcome to ask Adam and get back to us :)
 Adam or Steve, I think.
 I found an "OEM install (for manufacturers)" in the uefi boot menu. But I guess, this does not work with calamares?
 @aptghetto [I found an "OEM install (for manufacturers)" in the uefi boot menu. But I guess, …], Right
 It shouldn't be there at all
 Check the changelog for debian-cd, either me or wxl made that change for BIOS
[16:52] <wxl> @HMollerCl @kc2bez for what it's worth i get nyc though i'm not in that time zone. is it restricted to vms for some reason? maybe given the ntp thing calamares is a red herring?
 But I'm not sure ntp is the problem. Time is not the same as timezone
[17:02] <kc2bez> Right. ntp doesn't set the cala timezone that comes from geoip.
[17:06] <kc2bez> proper ntp could be a valid issue for other Internet things however such as verifying valid ssl certificates and whatnot.
 `timedatectl`
 @kc2bez https://ipapi.co/json is what is used?
[17:08] <kc2bez> correct @HMollerCl
 And uses geoclue?
 I guess, we need `sudo calamares -d > cala.log` on a system, where it does not work
 Do we have geoclue in live?
[17:11] <kc2bez> in `cala -d` the debug output should show the global store values for geoip.
[17:12] <kc2bez> we don't use geoclue for anything in Lubuntu to my knowledge
 In https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1845424 I see `2019-09-26 - 23:42:17 [2]: WARNING: Invalid YAML data for GeoIPJSON`, which might be related to the problem. But I couldn't reproduce it here on an UEFI vm (with an older eoan-iso).
 @kc2bez [<kc2bez> we don't use geoclue for anything in Lubuntu to my knowledge], Yes, but actually no
 It's seeded
[17:13] <kc2bez> Same for me @aptghetto
 Something pulls from it
 It just doesn't work
[17:13] <kc2bez> That is what I thought @tsimonq2
[17:19] <wxl> @aptghetto i couldn't reproduce that either, even though i have the issue with the wrongt ime zone
[17:21] <wxl> the thing is i don't see a clear error message
 journalctl or calamares?
[17:22] <wxl> cala
[17:23] <wxl> well, besides that warning, but i'm not sure that's it
 inthe live I have from 24sept timedatectl gives me wrong timezone
[17:47] <wxl> that is undoubtably due to timedatectl
[17:48] <wxl> perhaps your proxy is blocking the port
[17:48] <wxl> udp 123
 not sure, I have a VM in the same computer in which timedatectl works
 and in the one that timcextl works i can ping
 wxl: you have wrong timezone but timedatectl works?
 anyway timedatectl gives mt UTC 0 but cala NY.
[18:00] <wxl> lemme check timedatectl
 @aptghetto [I guess, we need sudo calamares -d > cala.log on a system, where it does not wor …], did this. GeoIP give CL as an answer, but still timezone is NY.
 I'm noyt sure this worked before.
 in bionic I mean
 here is cala.log https://paste.ubuntu.com/p/5kffPm7dyk/
 line 109 is geoip
 cala figured out your location and gave you the right language so at least that part is working right.
 the language I set on boot
 on boot I set to (spanish) in cala I change to mx.
 I follow you now.
 tested on bionic
 in bionic works
 mmmm
 GeoIP reporting "America/Santiago"
 that's what bionic says instead of GeoIP result for welcome= "CL"
 @HMollerCl do you mean Disco or 19.04 ?
 disco
 but apparently prior release, it is from march19
 back up to speed now.
 there has been a lot of changes since then for sure
 I'm tryinhg to pastebinit disco log
 has difference in geopip
 geoip was handled differently by cala then. we had to adjust the settings to match.
 here is cala disco log https://paste.ubuntu.com/p/sBQptxYt9T/
 which says:  … 15:38:33 [6]: Fetching GeoIP data from "https://ipapi.co/json"  … 15:38:33 [8]: getting smart status failed for  "/dev/sda" :  Operation not supported … 15:38:33 [6]: GeoIP reporting "America/Santiago"
 eoan log doesn't mention ipapi.co
 geoip in eoan returns country, but in disco timezone
 CL vs "America/Santiago"
 There were changes in locale.conf for T107
[18:59] <kc2bez> https://phab.lubuntu.me/rCALASETTINGScd7fa92d15410c58e80490028a508114d5ca9aec
 https://phab.lubuntu.me/w/release-team/process/
 I'll update this as time goes on
 For right now it's simply going to include the releasey things as I do them
 If any of you are doing tasks related to the release, please add it to the wiki page
 (Photo, 1280x1051) https://i.imgur.com/Z86pUFa.jpg if you add -d after calamares in the exec line of the calamares desktop file it will launch calamares in debug mode. On the bottom left you see show debug information, click that. In the new window that pops up click locale. It should look something like the attached.
 @HMollerCl ^
 @tsimonq2 [If any of you are doing tasks related to the release, please add it to the wiki …], @N0um3n0 :)
 Ok
 @kc2bez [<reply to image>], I created the logs with - d will see that debug info
[19:15] -lugito:#lubuntu-devel- [T120: Lubuntu 19.10 Beta Release] tsimonq2 (Simon Quigley) commented on the task: https://phab.lubuntu.me/T120#2396
 Going AFK for a little while yet
 When I get back, my plan is to upload the update notifier and the default settings
 And then work on polishing the docs a bit
 If there's anything more pressing, please ping
 Not ignoring the work with Cala, but I'm leaving it to you guys cause you seem to have a handle on it :)
 Thanks for your work everyone
 @tsimonq2 [Not ignoring the work with Cala, but I'm leaving it to you guys cause you seem t …], Working on it. It isn't a show stopper but will keep plugging away.
 Sounds good, let me know if you need my help
 @tsimonq2 [When I get back, my plan is to upload the update notifier and the default settin …], You mean artwork right? or was there something in default settings too?
 @kc2bez [You mean artwork right? or was there something in default settings too?], Oh, right.
 That :)
 No worries, just wanted to make sure.
 The glasses don‘t work?
 @aptghetto [The glasses don‘t work?], HAHAHAHAHAHAHAHA
 Shut up XD
 XD
 (Photo, 800x600) https://i.imgur.com/cIrx0Ig.jpg although log says geoip: "CL"
 @kc2bez
 CL is used for the welcome module
 (Photo, 800x600) https://i.imgur.com/HPvfbWL.jpg this has both info
[19:42] <wxl> so when i boot the iso, `timedatectl` is on utc
[19:43] <wxl> and indeed timezone is set to utc
[19:43] <wxl> so that may make sense
[19:45] <wxl> locale module gets New_York
[19:46] <wxl> and then suddenly my timezone is set to it
[19:46] <wxl> even though i didn't do anything in cala
[19:47] <wxl> ipapi.co/json returns Los_Angeles
[19:50] <wxl> ah
[19:50] <wxl> ha
[19:50] <wxl> default /etc/calamares/modules/locale.cnof has New_York
[19:51] <wxl> guess where that comes from?
 ^ That has been there all along though, looking at the cpp manual
 It should be the default if it can't figure it out (ie no internet)
[19:52] <wxl> https://phab.lubuntu.me/rCALASETTINGSe7f71611133ac3c780f828b9fb561c2ed276f595
[19:53] <wxl> well to be fair, we should set it to UTC to be consistent with the ISO
 Fair point. Still not sure why it didn't change to LA in your case.
 yes, in my case stays in NY forever...
[20:01] <wxl> uh
[20:01] <wxl> weird
[20:02] <wxl> i removed the values in the conf file, set timezone (global) to utc, ran cala and it's all of a sudden setting America/New_York
[20:02] <wxl> s|utc|Europe/London| whatever
[20:02] <wxl> ^^^ all while no internet
 is there a way to launch geoip from commandline?
[20:03] <wxl> you mean ipapi?
 curl
 or wget maybe
[20:04] <wxl> for ipapi at least
 geoip-bin
[20:06] <wxl> ok, internet + london timezone + london conf = london for location
 naa, it's only for country, which is good in my case
 perhaps my yaml  formating is off there in the locale.conf
[20:07] <wxl> internet + Pacific/Pago_Pago + london conf = london for location
[20:09] <wxl> no internet + Pacific/Pago_Pago + london conf = london for location
[20:09] <wxl> oh wait let me recheck that
[20:10] <wxl> yep that's right
[20:11] <wxl> no internet + Pacific/Pago_Pago + no setting in conf = ny for location
 what happens if you switch out the current geoip for this: https://github.com/calamares/calamares/blob/master/src/modules/locale/locale.conf#L94
[20:11] <wxl> internet + Pacific/Pago_Pago + no setting in conf = ny for location
[20:12] <wxl> so it seems to always go by the conf file or what i presume is a hardcoded ny
 @kc2bez [what happens if you switch out the current geoip for this: https://github.com/ca …], you mean this? https://geoip.kde.org/v1/calamares
 it gavez only timezone
 right, I meant in the locale.conf file
 sorry, I don't quite understand. The url only gives the timezone, while ipapi gives much more info
 maybe the ipapi info isn't well parsed?
 oo, now i get it, you want to cjhange ity
 where is the locale.conf file?
[20:16] <wxl> we have to use the old method though
[20:16] <wxl> no geoip section
 I found it in the cpp manual.
 I think it got missed in the version we have
 https://github.com/calamares/calamares/commit/0ee8427d5a310a568263f1493d573b888b28661a#diff-442c579d2a67e00679f9a3c905fb0cfe
[20:17] <wxl> internet + Pacific/Pago_Pago + london conf (with the kde geoip) = london for location
[20:17] <wxl> not i'm using london and pago pago because they're nowhere near America/Los_angeles
 I don't know where pago pago actually is but it sounds cool ;)
 it's a pagoda?
[20:19] <wxl> so i tried setting the selector explicitly to "time_zone" and that didn't help
 change locale.conf url, still gives ny
[20:20] <wxl> someone should compile upstream master and see what happens
 There is a new version upstream FWIW
 Also, if my manual reading is correct, the locale.conf file would need to be formatted the old way like this: https://paste.ubuntu.com/p/SYwzvxtxbt/
 the link /etc/localtime how is created?
 There are 2 modules in cala. This one https://github.com/calamares/calamares/tree/master/src/modules/localecfg and this one https://github.com/calamares/calamares/tree/master/src/modules/locale
 oh wait
 you said localtime not locale
 nvm me
 changed locale.conf to old way, still NY
 I think wxl is on to something we need to verify with the latest master.
 Or at least the next release.
 I need to head home though, I will continue there.
[20:42] <wxl> btw i set geoipUrl: "https://geoip.kde.org/v1/calamares" and geoipSelector: "time_zone"
[20:43] <wxl> the other values can stay the same
[20:44] <wxl> when we upgrade to that new version we really should go for the geoip hierarchy rather than the individual geoipThing values. though they're still supported, they're legacy and they could be dropped at any time
 oo, didn't notice had to change timezon to time_zone
[20:45] <wxl> yeah or you could use "" since it only returns one selector
 mm
 but sill Ny
[20:46] <wxl> yep
[20:46] <wxl> something's broken
 "" because time_zone is default
[20:46] <wxl> what we can say:
[20:46] <wxl>  * it's unchanged by local time zone
 https://github.com/calamares/calamares/blob/master/src/modules/locale/locale.conf#L97
[20:47] <wxl>  * it's unchanged by internet or not
[20:47] <wxl>  * it can be changed through hardcoding in the conf file
[20:48] <wxl>  * no values in the conf file result to hardcoded defaults (ny)
 mmm, any way to launch calamares in an installed system? to test it
 trying but complainig on settings.conf missing
[20:48] <wxl> you could install calamares and calamares-settings-lubuntu i imagine
[20:48] <wxl> the latter there
 ok, did it, (complain that are no partitions) and in NY … so, it is not running geoip
[20:50] <wxl> or it's just broken
 aaa, but maybe didn't updated, becasue it says: 17:49:21 [6]: GeoIP reporting "America/Santiago"
[20:51] <wxl> ah ha
 that' on eoan
 sooo, should be only a problem in live
[20:54] <wxl> oh wait
[20:54] <wxl> you're saying it sets it all right?????
 yes
 in my installed eoan
[20:54] <wxl> so when you go to location you see america/santiago???
 at least in the log
 can't go into my location because it complains of not having partition
[20:55] <wxl> huh???? XD
 "there are no partitions to install on"
[20:55] <wxl> maybe cuz it's mounted
 I'm running calamares on an installed machine
[20:55] <wxl> is this a vm?
 yes
[20:55] <wxl> add another empty drive and try again
[20:55] <wxl> i don't see "geoip" in the logs in live
[20:56] <wxl> so it's as if it's returning NOTHING
 but, since I'm running calamares -d it gaves me the debug info
 and there I se geoip reporting "America/Santiago"
 and that info isn't giving in live
 *given
[20:57] <wxl> there's only a success message :( https://github.com/calamares/calamares/blob/ec073ee188c40b7430955fb4fc4213a75480b2d9/src/libcalamares/geoip/Interface.cpp#L45
 https://paste.ubuntu.com/p/5kffPm7dyk/ this is live log
[20:59] <wxl> there's a warning for invalid yaml https://github.com/calamares/calamares/blob/ec073ee188c40b7430955fb4fc4213a75480b2d9/src/libcalamares/geoip/GeoIPJSON.cpp#L82
 this is "installed" log https://paste.ubuntu.com/p/5kffPm7dyk/
[21:00] <wxl> also warnings for wrong styles https://github.com/calamares/calamares/blob/ec073ee188c40b7430955fb4fc4213a75480b2d9/src/libcalamares/geoip/Handler.cpp#L73
 In my case bith versions of calamares and calamares-settings are ok
[21:00] <wxl> hmmmmmmmmmmm
 * are the same
[21:00] <wxl> what about an ssl problem!
 could be
[21:00] <wxl> given the time is necessarily wrong on the iso!
 will check with lynx
 (firefox uses his one proxy)
 @wxl [<wxl> given the time is necessarily wrong on the iso!], but versions are the same
[21:02] <wxl> no they're not
[21:03] <wxl> bah no
 ??
[21:03] <wxl> it didn't fix it
[21:04] <wxl> so you notice that delay loading calamares? it's on location
 being behind a proxy sucks now
 can't made apt changelog on live although I set proxy in environment
 meybe need some restart??
[21:05] <wxl> https://github.com/calamares/calamares/issues/1240
[21:06] <wxl> we do have the internet check
 yes
[21:08] <wxl> hm they're using xml
 but I insist it works ok in installed version
 have you tried?
[21:10] <wxl> that's insane
 install calamares and calamares-settings-lubuntu
 then run calamares -d
[21:15] -lugito:#lubuntu-devel- [rMANUAL06bdf393a9ef: Reword Ignore] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL06bdf393a9ef
[21:15] <wxl> lubuntu
[21:15] <wxl> hahahhaah oops
[21:23] <wxl> doesn't work for me in installed
 not in the log?
[21:23] <wxl> did you change the conf file?
 no
[21:24] <wxl> yeah there's no mention of "geoip" in the log and i can see in the debug information that ny was used
 it has the new style
 mmm I tried in another isntalled version which is 24sept iso. Didn't work either
[21:25] <wxl> yes i see that
 SO, it works on my installed version which is disco and is upgraded trhough changing sources
 but has same calamares version......
[21:26] <wxl> hm
[21:26] <wxl> we also have the geoip section in welcome.cnof, too
 wait!
 did you run sudo calamares -d?
[21:28] <wxl> yep
 aaa, same issu
 don't worry
 in my case geoip from welcome works
 so, I wonder if there are some calamares left in /home which aren't touch with upgrades...
 there is a file /e
[21:31] <wxl> it looks like getting country in welcome leads to setting locale (in my case, en) and presumedly that leads to language assumptions
 which in my working installation points to america/santiago, in the not working to ny
 in your case?
 https://wiki.debian.org/TimeZoneChanges
[21:38] <wxl>  /e ?
 nope /e /etc/localtime
[21:38] <wxl> /e/etc/localtime?
[21:38] <wxl> j/k XD
 not /e
[21:39] <wxl> /not/e/etc/localtime? X''''''''''D
 jajaja
 this is what my working installation (that comes from disco) says:
 17:37:30 [6]: GeneralRequirements output:  …      enoughStorage :   false  …      enoughRam :   true  …      hasPower :   true  …      hasInternet :   true  …      isRoot :   false  … 17:37:30 [6]: Added 5 requirement results  … 17:37:30 [6]: All requirements have been checked.  … 17:37:30 [6]:  ..  requirement 0 "partitions" is not
[21:40] <wxl> well currently (though likely because of running calamares) everything is ny
 I wonder how is set..
 jaja
 I change /etcl/localtime to ny then run calamares in my working machine and /etc/localtime goes to santiago
 why is it working!!!!!
[21:47] <wxl> i'm exhausted from it
 got to the parking lot and had to go back in. I had to go fix 2 servers. heading home for real now.
[21:51] <wxl> ugh that is always the way
 I'm exhausted
 bye
[22:01] <kc2bez> thanks for all the help @HMollerCl
[22:02] <kc2bez> home now. 
[22:02] <kc2bez> zsync ing the daily
 If you have an old installation (disco) upgrade to eoan, it install calamares and run it with - d in my case that gave me geoip output
[22:07] <kc2bez> does it upgrade settings too?
[22:08] <kc2bez> we would have had cala 3.2.4 in Disco and we are at 3.2.12 in eoan
 Yes
 At least the ones that are in /etc/calamares/modules
[22:11] <kc2bez> ok
[22:11] <kc2bez> that is strange that it works differently
 Although that should be in calamares-settings-lubuntu
 What could be is that we had more modules before
 Or more packages
 Or some settings in /home which aren't touched
 what is the problem with geoip?
[22:21] <kc2bez> in Calamares it doesn't seem to detect the proper timezone
 for me in kvm ——> US
 baremetal ———-> correct
 weird but we have reports that some of them fail too.
 @kc2bez [weird but we have reports that some of them fail too.], I will look at it again, thanks.