

X11.plistĪnd then launch Inkscape.app to test whether it autolaunches XQuartz. newly installed fresh from the DMG into ~/Applications)Ĭ) quit XQuartz, and rename/move the preferences file for XQuartz:

Top hits for 'Warning: duplicate definition for key 'PATH' found in environment' again point to installs of OS X 10.10 Yosemite Beta.Ī) test with a new user account on the same machineī) test with an unmodified version of Inkscape.app apple.launchd" besides this question, and both cases report using X11 forwarding with XQuartz on a developer prerelease of OS X 10.10 Yosemite Beta: 'cannot open display' - That's likely what prevents Inkscape from launching, though I would not know why this happens.ĭoing a web search finds two other mentions of the substring "/private/ tmp/com. > (inkscape- bin:1091) : Gtk-WARNING **: cannot open display: /private/ tmp/com. Personally, I have never seen such a value for $DISPLAY for X11/XQuartz before - usually it's something like > * My $DISPLAY variable appears to be set correctly: Which version of XQuartz is installed now? Which version of XQuartz was installed before (when Inkscape launched ok)?
Xquartz inkscape wont open update#
Was this originally an update or just a reinstallation of XQuartz? Which version of OS X do you have installed? > For perhaps not very good reasons, I re-installed XQuartz on my system. > Inkscape no longer launching after XQuartz update Is this the issue? And if so, how might I go about fixing it? The first definition was '/usr/bin: /bin:/usr/ sbin:/sbin', the ignored definition is '/opt/local/ bin:/opt/ local/sbin: /sw/bin: /usr/local/ bin:/usr/ bin:/bin: /usr/sbin: /sbin:/ opt/X11/ bin'. * One interesting thing: The console generates three copies of this this note about paths, when launching via the "open -a Inkscape" command:Ħ/8/14 11:22:20.293 PM Inkscape: *** -: Warning: duplicate definition for key 'PATH' found in environment - subsequent definitions are ignored. * Trying to launch Inkscape from within an xterm behaves identically to using a regular terminal window. (inkscape- bin:1091) : Gtk-WARNING **: cannot open display: /private/ tmp/com. (process:1091): Gtk-WARNING **: Locale not supported by C library. * Trying to launch from the script fails in the same way, but gives a little more detail: Shows Inkscape briefly in the dock, but again fails to launch. * Trying to launch Inkscape from the terminal works the same as launching from the finder: So far as I have seen, only Inkscape is not launching correctly. Other X11 programs are also launching normally. If XQuartz is already open, this command opens another xterm window. * Other applications that use X11 appear to be working normally. * My $DISPLAY variable appears to be set correctly: net/inkscape/ +question/ 216559 ), obviously without success thus far. * I've tried the suggestions of many previous debugging threads here (e.g., https:/ /answers. * I have tried reinstalling XQuartz and Inkscape. * I have not changed OS version or Inkscape version (0.48.2) since everything was working.

Accordingly, I have not managed to find anything that appears to be relevant in the DiagnosticReports, logs, or console (with one exception, at the end of this list). * There is no crash, just a failure to launch. * The behavior is that the dock icon will highlight briefly, then go away, without opening XQuartz. After doing so, Inkscape will no longer launch. The only bug is that the developers have had years to start a native OS X port of Inkscape, and have not capitallized on it.For perhaps not very good reasons, I re-installed XQuartz on my system. Then start Inkscape, with an eye to the above paragraph on how it initially behaves. If you are getting an application not responding, then force quit Inkscape (option-command-Esc), and start XQuartz first. When you quit XQuartz, it takes down Inkscape - so be sure your documents are saved.ĭo you successfully have XQuartz installed? Do the above steps work for you now? I ignored the link advice about changing system preference security settings to just accommodate Inkscape. Subsequent launches of Inkscape will show its name on the menu bar, and then XQuartz will launch by itself in support of Inkscape, and finally Inkscape fully appears on screen. The preceding scenario only happens the first time to launch Inkscape. I clicked on the Open button, and it then appeared. Then I launched Inkscape, which took its sweet time, presented a barber-pole progress while OS X performed a third-party verification, and then it presented a dialog offering to Open it. When I initially ran Inkscape, I started XQuartz first. I forgot to mention to reboot after installing XQuartz.
