CHIRP

Note the previous daily build, chirp-daily-20170126, runs on both computers.

If you open Terminal.app and run @/opt/kk7ds/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python /Applications/Chirp.app/Contents/Resources/chirp/chirpw@ do you get a crash as well / what output do you get?

Changed the command slightly since I don't have the daily builds in the Applications directory. But, that opens with some minor resource errors.

$ /opt/kk7ds/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python ./Contents/Resources/chirp/chirpw
WARNING: Icon not found
./Contents/Resources/chirp/chirpw:132: PangoWarning: couldn't load font ".SF NS Text 12", falling back to "Sans 12", expect ugly output.
a.show()
./Contents/Resources/chirp/chirpw:132: PangoWarning: error opening config file '../Resources/etc/pango/pangorc': No such file or directory

a.show()
./Contents/Resources/chirp/chirpw:132: PangoWarning: couldn't load font ".SF NS Text Not-Rotated 12", falling back to "Sans Not-Rotated 12", expect ugly output.
a.show()

Oddly... Just to apply your test exactly, I placed chirp in my Applications directory and changed the name to "chirp.app" Guess what, that launches from the finder.

If this helps, I usually just unzip the daily builds and run them with their default name. Eg. chirp-daily-20170207 and my report above compared the current and last daily builds under that condition.

So, it seems to be a path problem.

Richard Perlman wrote:

If this helps, I usually just unzip the daily builds and run them with their default name. Eg. chirp-daily-20170207 and my report above compared the current and last daily builds under that condition. And, not from the Applications directory.