Bug #4503
closedMacOS crash on launch
0%
Description
OS-X 10.12.2 daily build chirp-daily-20170111 crashes immediately after launch and logs
Feb 7 17:50:47 ham-shack-mac-2 com.apple.xpc.launchd1: Service exited with abnormal code: 126
to system.log
Observed on a mid-2010 MacBook pro and a late-2015 iMac
Updated by Richard Perlman over 7 years ago
Note the previous daily build, chirp-daily-20170126, runs on both computers.
Updated by Tim Smith over 7 years ago
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?
Updated by Richard Perlman over 7 years ago
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()
Updated by Richard Perlman over 7 years ago
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.
Updated by Richard Perlman over 7 years ago
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.
Updated by Tim Smith over 7 years ago
- Status changed from New to Rejected
I think this is a duplicate of #4479 so let's move discussion there; I'm starting to think that the problem is the symlink that the @Contents/MacOS/chirp@ script tries to create on first launch.