New OS X Yosemite 10.10.4 installation: Inkscape 0.91 never launches

[playmeforafool]

I just got 2 new 13" MacBook Pro's that came with OS 10.10.4 pre-installed. I downloaded Inkscape 0.91 from the Inkscape site, as well as downloaded/installed XQuartz 2.7.7. Both of these new MBP's are exhibiting the same symptoms. When I launch Inkscape, it bounces in the dock for about 2 minutes. It eventually stops bouncing, but the application menu never appears in the menu bar and I have to force quit Inkscape (also, X11 never launches). Same problem even if I launch X11 manually beforehand. Inkscape works fine on my Mac Mini which has been progressively upgraded to 10.10.4, so I'm not sure why these 2 new "pristine" versions are having problems.

Below is what shows up in the system logs when I try to start Inkscape. I'll also attach the referenced crash report file.

-----------------------------8<---Cut-Here---8<-----------------------------
7/24/15 10:03:13.489 AM CoreServicesUIAgent[1786]: Error -60005 creating authorization
7/24/15 10:03:16.944 AM com.apple.xpc.launchd[1]: (com.apple.ReportCrash[1788]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
7/24/15 10:03:17.250 AM com.apple.xpc.launchd[1]: (com.apple.coreservices.uiagent[1786]) Service exited due to signal: Bus error: 10
7/24/15 10:03:17.281 AM ReportCrash[1788]: Saved crash report for CoreServicesUIAgent[1786] version 134.7 (134.7) to /Users/admin/Library/Logs/DiagnosticReports/CoreServicesUIAgent_2015-07-24-100317_CELLBIOWHD45602.crash
-----------------------------8<---Cut-Here---8<-----------------------------

[su_v (suv-lp)]

On 2015-07-24 17:32 (+0200), playmeforafool wrote:
> Inkscape works fine on my Mac Mini which has been progressively
> upgraded to 10.10.4, so I'm not sure why these 2 new "pristine"
> versions are having problems.

This, and the fact that similar questions started to get asked on the irc channel shortly after Apple released the latest OS X update for Yosemite (10.10.4), indicates to me that there had been internal changes by Apple in that specific OS X update (likely related to Gatekeeper (?)) which apparently prevent the unsigned Inkscape.app from launching (at least on some systems).

At this point I have no idea what might have changed, nor what a possible solution might be (for the existing Inkscape package, and for future releases) - I also don't have access to a system with OS X Yosemite installed (neither to one which was progressively updated to 10.10.4, nor to one with a newly installed system).

At what point and how did you attempt to bypass Gatekeeper for Inkscape.app on the two new Macs with Yosemite 10.10.4? The application is not signed, and in the past bypassing Gatekeeper per app (launched from the Finder via 'Open' in its context menu) or with Gatekeeper temporarily disabled in the System Preferences (allow from 'Anywhere') seemed to register and work just ok.

Gatekeeper information per app can be retrieved in the Terminal e.g. with this command:
$ spctl -a -vv /Applications/Inkscape.app

Just curious - at least two users on the irc channel confirmed that the following steps allowed to launch the app despite regular launching (double-click on the app in the Finder) did not (the instructions were only given for debugging purposes, and are _not_ meant as a solution for regular users). Would you mind testing this on one of the affected Yosemite systems?
1) In the Finder, browse to the folder where you installed Inkscape (usually /Applications)
2) select Inkscape, open the content menu and use 'Show Package Contents'
3) inside the app bundle, browse to 'Contents > MacOS'
4) double-click 'Inkscape' in that folder
The last step will open a non-interactive Terminal window displaying all console messages (it can be closed once Inkscape.app is quit). Note that if this is the first run of Inkscape.app by the current user, the initial launch can take several minutes until the caches for fontconfig are built. Subsequent launches are faster.

--
Internally, the steps to launch the main Inkscape process are rather convoluted (mostly for legacy reasons):
- Inkscape.app/Contents/MacOS/Inkscape - the app launcher (binary), registers Apple event handlers (for opening files with 'Open with', for drag&drop on the app icon), then launches a shell script:
- Inkscape.app/Contents/Resources/script - bash script, sets user env for config and cache, creates hidden folders in $HOME if not already present, checks whether to alert the user about initial building of font caches, runs an AppleScript-based dialog if this hasn't been shown yet, finally exec's yet another shell script:
- Inkscape.app/Contents/Resources/bin/inkscape - shell script, sets up the specific environment for Inkscape, and in the end exec's the actual binary:
- Inkscape.app/Cont...

[su_v (suv-lp)]

Setting bug status to 'Confirmed' for now based on similar questions about Inkscape failing to launch on OS X 10.10.4 in the #inkscape irc channel and on inkscapeforum.com.

[playmeforafool (playmeforafool)]

The very first time I launched Inkscape, it gave me the warning about not being trusted. I went to the "Security" System Preferences and it had the warning there. I said to go ahead and allow it.

$ spctl -a -vv /Applications/Inkscape.app
returns: /Applications/Inkscape.app: accepted

Also, following your steps 1-4 did allow Inkscape to start!

[playmeforafool (playmeforafool)]

I tried changing setting in the "Security & Privacy" System Preferences:

  "Allow apps downloaded from" to "Anywhere" (It was set to "Mac App Store and Identified Developers").

And now Inkscape launches perfectly fine.

I then changed the setting back to "Mac App Store and Identified Developers" and also still launches perfectly fine!

I wanted to know if it was the act of getting Inkscape to start by running it using the 4 steps you gave above, or whether it was the act of setting the security preference to "Anywhere" and back again, so I got out the 2nd MBP. I had to re-download Inkscape because I had deleted it from the system. As I did yesterday, I copied it to /Applications. The first time I launched Inkscape it gave the warning about "unidentified developer", so I went to the "Security & Privacy" preference and clicked on "Open anyway" (I didn't change the settings, it was still set to the default "Mac App Store & identified developers". I then tried to start Inkscape, and had the same symptoms -- Inkscape icon bouncing in the Dock for about 2 minutes, then having to force quit it. I went back to the "Security & Privacy" and changed it to allow from "Anywhere". Inkscape launched fine! Went back and changed the setting to "Mac App Store and Identified Developers" and it still launches fine. It must be something buggy with that "Open anyway" option.

[su_v (suv-lp)]

Thank you for further investigating this issue, and sharing your solution here (as well as in the related forum topic) - this is much appreciated!

Overall, the problem looks like some sort of a regression (or incompatibility) possibly introduced with Apple's latest security update. [*]

Changing bug status to 'Triaged' for now - this will keep the report listed in launchpad's search results (and helps others finding it instead of filing duplicate reports). Unless further details indicate that changes to Inkscape's current packaging for OS X (apart from code signing) could work around the apparently changed and inconsistent behavior of current Gatekeeper settings, the report could be closed in case Apple includes a fix later on, or further tracked along with the request for code signing (bug #1363305).

--
[*] yes, ideally the 'Inkscape' project ought to provide a signed application for OS X - that's certainly an item for the roadmap, and tracked in bug #1363305 (currently, none of the active developers and packagers with access to OS X do have a paid membership in the Apple Developer Program (required to get a code signing certificate accepted by Gatekeeper), and the packaging routines for OS X are not yet set up for optional code signing either).

[frederic (f-caunes)]

Thanks same bug exactly

Your process works :
1) In the Finder, browse to the folder where you installed Inkscape (usually /Applications)
2) select Inkscape, open the content menu and use 'Show Package Contents'
3) inside the app bundle, browse to 'Contents > MacOS'
4) double-click 'Inkscape' in that folder

[su_v (suv-lp)]

On 2015-09-29 12:36 (+0200), frederic wrote:
> Your process works :
> 1) 1) In the Finder, browse to the folder (...)

@frederic - this is _NOT_ the recommended solution, and won't help in the long run.

Please follow these steps:
1. From System Preferences, open "Security & Privacy".
2. At the bottom of the General pane, change "Allow apps downloaded from:" to "Anywhere".
3. Start Inkscape.
4. After Inkscape has launched, go back to "Security & Privacy" and revert the setting to "Mac App Store and identified developers".

[Ravil (sh0ckfile)]

You can approve it manually via terminal:

spctl --add --label "ApprovedApps" /Application/Inkscape.app
spctl --enable --label "ApprovedApps"

[Juha Mäkeläinen (jpek)]

I have Mac OSX 10.9.5 and had the same problem.

I was trying to update my previous, working Inkscape (0.6?) to this 0.91, but starting of the program fails as described above.

The solutions given by frederic and ~suv 2015-09-29 work.

[LaDonna (morrow3615)]

I am running OS X Yosemite 10.10.5 I have loaded xQuartz (the most recent version), restarted.
Downloaded the most recent version on Inkscape (the most stable version)
Copied it to the Applications folder
Changed Security to Allow All
Tried to start Inkscape and get the following message:
Inkscape encountered an internal error and will close now.

I have tried all of the suggestions I have found with no luck.

I have attached a crash report if this helps.

[su_v (suv-lp)]

@LaDonna - please file a new bug report, and attach the actual crash report (not the console messages which say that the report was saved) to the new bug report [1]. We can't tell based on the attachment in comment #11 why inkscape-bin crashed (this report here - bug #1478053 - is about a crash of a system component when attempting to launch Inkscape the first time without disabling Gatekeeper, not about a crash of inkscape-bin itself).

[1] Based on the console messages in the RTF file, please attach these files (Crash reports) to the new bug report:
/Users/ladonnamorrow/Library/Logs/DiagnosticReports/inkscape-bin_2015-11-13-165547_LaDonnas-MacBook-Pro.crash
/Users/ladonnamorrow/Library/Logs/DiagnosticReports/inkscape-bin_2015-11-13-165715_LaDonnas-MacBook-Pro.crash

[Qantas94Heavy (qantas94heavy)]

Closing given native macOS Inkscape 1.0 makes this report obsolete. If there are issue with the native release, please check here to see if it has been reported: https://inkscape.org/inbox. Thank you!

Closed by: https://gitlab.com/Qantas94Heavy