ChimeraX MacOS does not launch

[kelvin.lau@…]

Hi,

I am using the latest version of ChimeraX 0.8 on MacOS 10.14.2 and I have run into a problem where clicking on the Application icon appears to launch ChimeraX (one can see the dot beside the icon in the doc) but then it stops loading. There are no visual prompts, no windows are opened and there is no error message.

If I go directly into the ChimeraX package and run the executable, a Terminal window appears and ChimeraX runs fine.

Is this something due to ChimeraX or my Mac’s settings?

Deleting ChimeraX and replacing it with a fresh copy has no effect.

Best,

Kelvin

[Conrad Huang]

Hi, Kelvin.

I tried the latest daily build (dated 2019-02-04) and it started on Mojave (10.14.2), but it did take quite a while to verify. While waiting, the ChimeraX icon is bouncing on the dock. ChimeraX also seems to work for a couple other users running Mojave.

After you install ChimeraX, do you immediately double-click on the icon, or do you run it from the command line first? If the latter, it may result in some files getting created that cause the app signature to appear invalid.

And one last "desperate measure" that you can try: delete the Library/Application Support/ChimeraX folder from your home directory. It /shouldn't/ make any difference, but it also shouldn't hurt anything other than lose some old settings.

Let me know if any of these help at all.

Conrad

[kelvin.lau@…]

Dear Conrad,

1) I can confirm that if I use the daily build, it now works. (I overwrote the 0.8 with the newest build from the website) When I start the application, I get a prompt to verify its identity, and then it launches properly.

2) If I did not use the daily build and I overwrite an "old" version 0.8 with a "new" one, it still does not work. See the attached movie for how the icon behaves.

Best Regards,

Kelvin

Screen Recording 2019-02-05 at 11.56.35.mov​

[kelvin.lau@…]

Added by email2trac

[Conrad Huang]

That is very odd. I'm not really sure why it does absolutely nothing. Can you fire up the Console app (from /Applications) and see if there are messages about start-up failures under "system.log"?

[kelvin.lau@…]

I found a bunch of error messages

Feb  5 11:54:45 SV-01M-035 ChimeraX[6801]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debug
Feb  5 11:54:45 SV-01M-035 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.oneshot.0x1000000f.ChimeraX[6801]): Service exited with abnormal code: 1
Feb  5 11:55:29 SV-01M-035 ChimeraX[6820]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debug
Feb  5 11:55:29 SV-01M-035 com.apple.xpc.launchd[1] (edu.ucsf.cgl.ChimeraX.10624[6820]): Service exited with abnormal code: 1
Feb  5 11:56:24 SV-01M-035 ChimeraX[6853]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debug
Feb  5 11:56:25 SV-01M-035 com.apple.xpc.launchd[1] (edu.ucsf.cgl.ChimeraX.10624[6853]): Service exited with abnormal code: 1
Feb  5 11:56:56 SV-01M-035 ChimeraX[6862]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debug
Feb  5 11:56:56 SV-01M-035 com.apple.xpc.launchd[1] (edu.ucsf.cgl.ChimeraX.10624[6862]): Service exited with abnormal code: 1
Feb  5 11:57:01 SV-01M-035 ChimeraX[6864]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debug
Feb  5 11:57:01 SV-01M-035 com.apple.xpc.launchd[1] (edu.ucsf.cgl.ChimeraX.10624[6864]): Service exited with abnormal code: 1
Feb  5 12:01:12 SV-01M-035 ChimeraX[6934]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debug

[Conrad Huang]

Google search results suggest that the problem arose with a Mojave release/update and it affected quite a few apps. Answer from most vendors is "fixed in the next update", so we're going to go with that too. At least the daily build is a viable workaround. (No code was specifically to fix the problem, so I'm guessing that simply rebuilding the application with updated developer tools resolved the issue.)