Concur with Greg’s observations. George J Molnar, KF2T Virginia, USA
George J Molnar Arlington, Virginia > On Oct 4, 2019, at 10:08 AM, Greg Vatt <[email protected]> wrote: > > Bill, > > Here is the crash report of WSJT-X v2.1 using the last developer beta before > MacOS Catalina is released today. Thread 12 Crashed: which shows it is still > a Qt issue. > > This beta is supposed to be the same as the full release but I am waiting to > update later today with the public release of Catalina and see if this is > fixed. (Still using MacOS 10.14.6 on my other computer connected for Ham use > and WSJT-X v2.1 works fine here.) > > Greg, NC7B > > > Thread 12 Crashed: > 0 org.qt-project.QtCore 0x00000001088b4ce9 QLocale::QLocale() + > 25 > 1 org.qt-project.QtCore 0x0000000108909395 > QDateTimeParser::parseSection(QDateTime const&, int, QString&, int&, int, > QDateTimeParser::State&, int*) const + 1237 > 2 org.qt-project.QtCore 0x000000010890b340 > QDateTimeParser::parse(QString&, int&, QDateTime const&, bool) const + 512 > 3 org.qt-project.QtCore 0x000000010890de14 > QDateTimeParser::fromString(QString const&, QDate*, QTime*) const + 148 > 4 org.qt-project.QtCore 0x00000001088a10de > QDate::fromString(QString const&, QString const&) + 94 > 5 org.k1jt.wsjtx 0x00000001039156a6 > LotWUsers::impl::load_dictionary(QString const&) + 230 > 6 org.k1jt.wsjtx 0x000000010391725c > std::__1::__async_assoc_state<QHash<QString, QDate>, > std::__1::__async_func<QHash<QString, QDate> (LotWUsers::impl::*)(QString > const&), LotWUsers::impl*, QString> >::__execute() + 60 > 7 org.k1jt.wsjtx 0x000000010391758e void* > std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, > std::__1::default_delete<std::__1::__thread_struct> >, void > (std::__1::__async_assoc_state<QHash<QString, QDate>, > std::__1::__async_func<QHash<QString, QDate> (LotWUsers::impl::*)(QString > const&), LotWUsers::impl*, QString> >::*)(), > std::__1::__async_assoc_state<QHash<QString, QDate>, > std::__1::__async_func<QHash<QString, QDate> (LotWUsers::impl::*)(QString > const&), LotWUsers::impl*, QString> >*> >(void*) + 62 > 8 libsystem_pthread.dylib 0x00007fff69e65d76 _pthread_start + 125 > 9 libsystem_pthread.dylib 0x00007fff69e625d7 thread_start + 15 > > > > Full Crash report: > > > <MacOS_Catalina19A582a.txt> > > >> On Oct 4, 2019, at 3:47 AM, Bill Somerville <[email protected]> wrote: >> >>> On 04/10/2019 11:34, Gary Rogers wrote: >>> Question for Bill: Mac OS Catalina will be released to the public today. >>> Will WSJT-X version 2.1.0 be impacted if Mac users upgrade to Catalina? >>> Thanks Gary KO3F >> >> Hi Gary, >> >> the only testing has been done with beta releases of macOS 10.15 (Catalina), >> there were problems that caused WSJT-X to fail but those problems appeared >> to be operating system issues rather than WSJT-X issues, so they may have >> been fixed for the public release of macOS 10.15. >> >> As there are known issues with WSJT-X v2.1.0 on macOS that will not be fixed >> until the next release I would not recommend attempting to run WSJT-X v2.1.0 >> on any macOS version at present. Anyone willing to try WSJT-X v2.0.1 on >> macOS 10.15 would be welcome, but no guarantees of success are offered just >> yet. I will try and get a VM updated to 10.15 once it is available and do >> some testing myself. >> >> 73 >> Bill >> G4WJS. >> >> >> >> _______________________________________________ >> wsjt-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
