Bug #11626
closedCHIRP Warning 'Cannot set locale to language "".'at startup, if language is not set. MacOS 10.13.
0%
Description
If language selection is left at 'Ä€utomatic from system', there is 'Cannot set locale to language "".' warning at startup.
If language is set to something other, for example 'English (United States) - English', the warning does not appear.
It is reproducible by switching back and fort between 'Automatic..'and any language.
It is present in releases as far back as June 2024.
Mac OS 10.13 High Sierra, MacBook Pro 2011, Intel.
Also reproducible on non-supported 10.10.5 (Yosemite). It runs and downloads from radio, but crashes on drop-down menus.
P.S. Kudos to those who made the Mac version to work on 10.13! Not all of us are on the latest and greatest.
Files
Updated by Dan Smith about 1 month ago
- Status changed from New to Rejected
CHIRP is actually not expected to work on anything older than Big Sur. I'm shocked it works at all on anything as old as you're indicating here. Were it trivial to fix, I might try, but I believe this is just a fundamental lack of support in libraries we rely on (wx) that need a newer version of the OS. On my system here, 'en' is not a valid locale name from the base OS, yet that's what your system is reporting. I'm sure that has to do with changes that have been made since 10.13.
So, if it works enough to use by setting the language manually, consider yourself lucky, but it's not "supposed to work" on something that old. I will soon have to move the support envelope even later than Big Sur as Apple stops allowing me to notarize the build from such an old and unsupported system.
Updated by Justin Case about 1 month ago
Dan Smith wrote in #note-1:
CHIRP is actually not expected to work on anything older than Big Sur.
How come? Python binary inside the app has minimum system requirements = 10.9. All your libwx_osx_cocoau_etc = 10.10. chirpwx itself is 10.13, but that's easily changable in MachOView to 10.10 and it runs. I've checked dependencies and everything seems to be OK. No 'missing symbols' errors in terminal so far. Crash on a drop-down menus is probably wx related. I've seen that in others apps in the past - it was wxUILocale something.. Fixed it by RETing that procedure.
IMHO, pushing modern Mac systems down on users will only alienate them.
If you want me to beta test on older systems, let me know.