Topics

Beware macOS V11.0.1


Guy
 

Cuppertino moved my MBP  and iMAC to macOS "Big Sur" v11.0.1 overnight. Whoopie!
0930 today was our countywide Fall SET. The entire family of Fldigi programs opened as great white blobs of non-functionality.
Obviously, things did not go well on this end.
 Looking forward to fix in Fldigi "The Next Generation". Anyone have an idea of a release date?
Until then it's back to the pc. Ugh!

73
Guy, WA3JZN


Vince N2JRS
 

I feel your pain. I use an application called SARTrak for public service events. The developer had a propensity for pushing updates at the most inopportune times. (Thankfully, the app is much more stable, and updates are much less more frequent.) The beauty of the updates is that you HAD to do the update or it wouldn’t work. And yes, the night before an event is when an update rolled out. Had to update all the laptops at 5AM. Good times.

 

Vince N2JRS

 

From: nbems@groups.io [mailto:nbems@groups.io] On Behalf Of Guy
Sent: Saturday, November 14, 2020 1:08 PM
To: nbems@groups.io
Subject: [nbems] Beware macOS V11.0.1

 

Cuppertino moved my MBP  and iMAC to macOS "Big Sur" v11.0.1 overnight. Whoopie!
0930 today was our countywide Fall SET. The entire family of Fldigi programs opened as great white blobs of non-functionality.
Obviously, things did not go well on this end.
 Looking forward to fix in Fldigi "The Next Generation". Anyone have an idea of a release date?
Until then it's back to the pc. Ugh!

73
Guy, WA3JZN


KL4YFD ham
 

Hi,

Wanted to reply publicly with updates to the macOS 11: "Big Sur" Fldigi issues.

Apple changed some underlying aspects of the Graphical Interface system, breaking basically all FLTK-based programs.
The FLTK team has been working hard though, and version 1.4 (in development) is now working on MacOS, even on the new M1 ARM-CPU systems.

The process of porting Fldigi and the NBEMS suite to FLTK 1.4 for MacOS 11+ is well underway.
Dave has posted testing-binaries for MacOS Big Sur at:
(testing only: not for real-world use yet)

If anyone is willing to run these test binaries, even on Older MacOS, this could give helpful info for developers.
Please send any reports about the test-binaries to:  <w1hkj@...>

Happy Holidays everyone,
John Phelps
KL4YFD


On Sat, Nov 14, 2020 at 10:07 AM Guy <wa3jzn@...> wrote:
Cuppertino moved my MBP  and iMAC to macOS "Big Sur" v11.0.1 overnight. Whoopie!
0930 today was our countywide Fall SET. The entire family of Fldigi programs opened as great white blobs of non-functionality.
Obviously, things did not go well on this end.
 Looking forward to fix in Fldigi "The Next Generation". Anyone have an idea of a release date?
Until then it's back to the pc. Ugh!

73
Guy, WA3JZN


Dave
 

A further update.  The dmg's posted at http://www.w1hkj.com/bigsur/ have been linked to the latest development version of FLTK 1.3.5.x available on the FLTK git repository.  These work as well as the volatile (under development) 1.4.x branch of the git repository.  You can use either the 1.3.5 or 1.4.x branch on the FLTK git repository if you are targeting BigSur (Buggy Sir).  The same binary should work on all x86_64 macOS versions.

Dave

On 11/25/20 12:11 PM, KL4YFD ham wrote:
Hi,

Wanted to reply publicly with updates to the macOS 11: "Big Sur" Fldigi issues.

Apple changed some underlying aspects of the Graphical Interface system, breaking basically all FLTK-based programs.
The FLTK team has been working hard though, and version 1.4 (in development) is now working on MacOS, even on the new M1 ARM-CPU systems.

The process of porting Fldigi and the NBEMS suite to FLTK 1.4 for MacOS 11+ is well underway.
Dave has posted testing-binaries for MacOS Big Sur at:
(testing only: not for real-world use yet)

If anyone is willing to run these test binaries, even on Older MacOS, this could give helpful info for developers.
Please send any reports about the test-binaries to:  <w1hkj@...>

Happy Holidays everyone,
John Phelps
KL4YFD


On Sat, Nov 14, 2020 at 10:07 AM Guy <wa3jzn@...> wrote:
Cuppertino moved my MBP  and iMAC to macOS "Big Sur" v11.0.1 overnight. Whoopie!
0930 today was our countywide Fall SET. The entire family of Fldigi programs opened as great white blobs of non-functionality.
Obviously, things did not go well on this end.
 Looking forward to fix in Fldigi "The Next Generation". Anyone have an idea of a release date?
Until then it's back to the pc. Ugh!

73
Guy, WA3JZN


 

Hi Dave, et al -

Wanter to give FLDIGI a try on my mew Mac mini M1, but it was not pretty. Did some Googling and found that there are changes in the works for FLDIGI and FLRIG to work on this Big Sur and M1 machine. I went to the above dmg posted web site and downloaded both apps. And they failed just as with v4.1.14 that I'd been using prior to getting this new Mini.

Have never done any stuff with source repositories and such, so I'm not sure where to go next. Are there any "beta" versions available for testing? Or should I just forget about it for now?

Jim / W6JHB


Dave
 

My pockets are not deep enough to put a new M1 based Apple in the computer line up.  Resolution to the problem will have to wait until one of the other developers (or a volunteer) is able to successfully build and test on the M1 architecture.

Dave

On 1/7/21 12:24 PM, Jim / W6JHB via groups.io wrote:
Hi Dave, et al -

Wanter to give FLDIGI a try on my mew Mac mini M1, but it was not pretty. Did some Googling and found that there are changes in the works for FLDIGI and FLRIG to work on this Big Sur and M1 machine. I went to the above dmg posted web site and downloaded both apps. And they failed just as with v4.1.14 that I'd been using prior to getting this new Mini.

Have never done any stuff with source repositories and such, so I'm not sure where to go next. Are there any "beta" versions available for testing? Or should I just forget about it for now?

Jim / W6JHB


 

Understood on that! I had to sell off a bunch of other stuff to get this one approved by the board chairman, and even then there was a lot of groveling… :-)
 
I certainly have the time to give it a shot as a builder / tester if there are any high-level procedures on doing the build. I’ve built WSJT-X about a hundred times on a Raspberry Pi a few years ago, so I’m not completely unfamiliar with the process. Lemme know.
 
Jim


Dave
 

An anonymous donor has purchased a miniMac/M1 for my use.  I expect it to arrive mid January.  I'll let the groups know if and when I am successful in build fldigi etc on the M1 architecture.

73, David, W1HKJ

On 1/7/21 2:54 PM, Jim / W6JHB via groups.io wrote:
Understood on that! I had to sell off a bunch of other stuff to get this one approved by the board chairman, and even then there was a lot of groveling… :-)
 
I certainly have the time to give it a shot as a builder / tester if there are any high-level procedures on doing the build. I’ve built WSJT-X about a hundred times on a Raspberry Pi a few years ago, so I’m not completely unfamiliar with the process. Lemme know.
 
Jim


Dan McGrath
 

That is Wonderful news! Good Luck David… 73 N2YLK

On Jan 7, 2021, at 4:50 PM, Dave <w1hkj@...> wrote:

An anonymous donor has purchased a miniMac/M1 for my use.  I expect it to arrive mid January.  I'll let the groups know if and when I am successful in build fldigi etc on the M1 architecture.

73, David, W1HKJ

On 1/7/21 2:54 PM, Jim / W6JHB via groups.io wrote:
Understood on that! I had to sell off a bunch of other stuff to get this one approved by the board chairman, and even then there was a lot of groveling… :-)
 
I certainly have the time to give it a shot as a builder / tester if there are any high-level procedures on doing the build. I’ve built WSJT-X about a hundred times on a Raspberry Pi a few years ago, so I’m not completely unfamiliar with the process. Lemme know.
 
Jim



ptbtx
 

Just a status report when trying the latest: I'm on an Intel Mac, v11.1 aka Big Sur.  I tried the howto at http://www.w1hkj.com/bigsur/ but the icon has a slash through it and the app starts with this message, "You can’t open the application “fldigi-4.1.17.08.app” because this application is not supported on this Mac."


 

What??? 

I, along with others are running FLDIGI etc. on v11.1 Big Sur and it works fine. If you have the Silicon / M1 processor, like I have in my Mac mini, following Dave’s install instructions work perfectly.


Jim Bennett
Folsom, CA

K7TXA (ex W6JHB as of 1/22/2021)




On Jan 29, 2021, at 10:36 AM, ptbtx via groups.io <ptbtx@...> wrote:

Just a status report when trying the latest: I'm on an Intel Mac, v11.1 aka Big Sur.  I tried the howto at http://www.w1hkj.com/bigsur/ but the icon has a slash through it and the app starts with this message, "You can’t open the application “fldigi-4.1.17.08.app” because this application is not supported on this Mac."


ptbtx
 

Here's the front part of the dump after the crash when it starts up:

Process:               fldigi [42121]
Path:                  /Applications/fldigi-4.1.17.app/Contents/MacOS/fldigi
Identifier:            com.w1hkj.fldigi
Version:               4.1..17 (4.1..17)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           fldigi [42121]
User ID:               501
 
Date/Time:             2021-01-29 18:06:02.138 -0600
OS Version:            macOS 11.1 (20C69)
Report Version:        12
Anonymous UUID:        A7625124-8667-308D-A9AF-55BAE2EB88C3
 
Sleep/Wake UUID:       FEAB153A-CBBB-4E4B-964C-90638854EFB2
 
Time Awake Since Boot: 49000 seconds
Time Since Wake:       390 seconds
 
System Integrity Protection: enabled
 
Crashed Thread:        0  Dispatch queue: com.apple.main-thread
 
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0xffffffffffffffe8
Exception Note:        EXC_CORPSE_NOTIFY
 
Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [42121]
 
VM Regions Near 0xffffffffffffffe8:
--> VM_ALLOCATE              7ffffff3a000-7ffffff3b000 [    4K] r-x/r-x SM=ALI  
    
 
Application Specific Information:
dyld: launch, running initializers
/Applications/fldigi-4.1.17.app/Contents/MacOS/fldigi
 
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libstdc++.6.dylib             0x00007fff78ac2c2f std::string::length() const + 7
1   com.w1hkj.fldigi               0x0000000107f7c2c7 cMorse::init() + 47
2   com.w1hkj.fldigi               0x0000000107f7bdc6 cMorse::cMorse() + 44
3   com.w1hkj.fldigi               0x0000000107f8aa36 _GLOBAL__I_ICOMwpm + 86
4   dyld                           0x000000010f7e9079 ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 559
5   dyld                           0x000000010f7e9478 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 40
6   dyld                           0x000000010f7e3d1a ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, char const*, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 492
7   dyld                           0x000000010f7e1b82 ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 188
8   dyld                           0x000000010f7e1c22 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 82
9   dyld                           0x000000010f7ce62f dyld::initializeMainExecutable() + 199
10  dyld                           0x000000010f7d49a4 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 8288
11  dyld                           0x000000010f7cd22b dyldbootstrap::start(dyld3::MachOLoaded const*, int, char const**, dyld3::MachOLoaded const*, unsigned long*) + 457
12  dyld                           0x000000010f7cd025 _dyld_start + 37
 
Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x00000000000002a0  rcx: 0x00007fff88985238  rdx: 0x0000000000000000
  rdi: 0x00000001088eeb00  rsi: 0x0000000000000000  rbp: 0x00007ffee7d38510  rsp: 0x00007ffee7d38510
   r8: 0x000000000007c15c   r9: 0xffffffff00000000  r10: 0x00007ffee7d3ccd8  r11: 0x00007fff78ac2c28
  r12: 0x00007ffee7d388e8  r13: 0x000000010f8716c0  r14: 0x0000000108b63e98  r15: 0x0000000107f8a9e0
  rip: 0x00007fff78ac2c2f  rfl: 0x0000000000010206  cr2: 0xffffffffffffffe8
  
Logical CPU:     1
Error Code:      0x00000004 (no mapping for user data read)
Trap Number:     14
 


ptbtx
 

That's with 17 not 17.08.  


Dave
 

Are you executing on an Intel or M1 ?

David


ptbtx
 

Intel


Dave
 

Please try deleting these two files and then starting fldigi from a CLI

~/.fldigi/fldigi.prefs
~/.fldiig/fldigi_def.xml

David

On 1/29/21 10:03 PM, ptbtx via groups.io wrote:
Intel


ptbtx
 

Those files aren't there.  In fact there is no ~/.fldigi.


ptbtx
 

I see 18 is now available.  That installed and ran fine.  And that directory is now there.


Dave
 

Good.  You might want to join the linuxham groups.io forum.  It's members are primarily on Linux / OS-X.

David

On 1/30/21 12:07 AM, ptbtx via groups.io wrote:
I see 18 is now available.  That installed and ran fine.  And that directory is now there.