The problem definitely seems to be an X11 issue rather than Inkscape. I set up a new user and 0.46 runs just fine using Inkscape and X11 from the same Applications directory, so the problem must be in my normal user settings or files somewhere. I found the following for anyone having problems with X11 startup at: http://lists.apple.com/archives/X11-users/2007/Nov/msg00498.html and specifically a short routine to check all the user controlled set up files (.rc, .profile etc) for incorrect DISPLAY settings:

$ grep DISPLAY ~/.*rc ~/.login ~/.*profile ~/.MacOSX/environment.plist 2>/dev/null $ grep -r DISPLAY /opt/local/etc /sw/etc /etc 2>/dev/null

In my case this came up with the ~/.profile file that included a line :

export DISPLAY=:0.0

and when I ran

"echo $DISPLAY" the result was

:0.0

Apparently this is a bad thing and what causes the problem - a common issue, and the offending line in ~/.profile should be deleted

Then after running Inkscape you will find that running

"echo $DISPLAY" will produce

/tmp/launch-LGD5sz/:0

or something similar in format.

So now 0.46 runs in the new user and 045.1 starts reliably in my old user - still no 0.46 in the old user yet -- need to keep hunting for the culprit! Any ideas?

Stu

On Feb 24, 2008, at 7:05 PM, jiho wrote:

Hi again,

On 2008-February-24 , at 22:40 , Stuart Edwards wrote:
On Feb 24, 2008, at 12:27 PM, jiho wrote:
2/24/08 10:22:31 AM [0x0-0x2e02e].org.inkscape.Inkscape[685]
(inkscape-
bin:686): Gtk-WARNING **: Locale not supported by C library.
2/24/08 10:22:31 AM [0x0-0x2e02e].org.inkscape.Inkscape[685] Using
the fallback 'C' locale.

This is OK.
Not getting this now with xquartz

2/24/08 10:22:32 AM [0x0-0x2e02e].org.inkscape.Inkscape[685] **
(inkscape-bin:686): WARNING **: Unknown verb name: FullScreen

This is just a warning but we are having it a lot. This is related to
the new version of X11 but I don't know where it comes from on
Inkscape's side.
Nor this

2/24/08 10:22:34 AM [0x0-0x2e02e].org.inkscape.Inkscape[685]
(inkscape-
[...]
(inkscape-
bin:686): Pango-WARNING **: Error loading GSUB table 85

These are regular warnings too.
ok, but they are gone too.

Glad to know these warnings are gone. But actually this makes me think there's an other problem. Indeed, they should be there actually... read on.

This may shed some light on the X11 problem

The X11 problem is the following: on Panther+Tiger X11 must be started
to run X11 applications so we started it manually in Inkscape
launcher, on Leopard, X11 is automatically launched when an
applications queries the DISPLAY variable (and X11 thing). So we just
had to surround the code which started X11 in the launcher by an if
condition ( if version is < 10.5 then start X11, else just skip it ).
This has been included in all recent devel versions of Inkscape (all
those compiled on Leopard at least) and has been "backported" to
0.45.1. So all those should work on Leopard.
So this definitely doesn't seem to be happening with Leopard or 0.45.1 (see below)

It does work and has worked on several systems already so that makes me think the problem is elsewhere.

[...]
- get the latest X11 from Xquartz (*much* better than the default one
on Leopard, and kind of official

http://trac.macosforge.org/projects/xquartz/wiki/X112.1.4
done - unfortunately the net result is no change as far as 0.46 is concerned. I downloaded 0.45.1 and it opens briefly, triggers X11 which opens and then Inkscape is gone. There are no Inkscape related console messages.

What log are you watching? By default when you open Console.app on Leopard you're on a sort of table view in which messages come in from several places. Just switch to LOG FILES > System log in the side bar. Here's what I get when I start Inkscape devel (latest on modevia), with X11 not yet running, on OS X 10.5.2, Xquartz 2.1.4. I've inserted markers where appropriate:

>>>>>> Monday, 2008 February 25 00:07:09,652Europe/Paris ----> Starting Inkscape
Feb 25 00:07:13 jiho-ibook [0x0-0x388388].org.inkscape.Inkscape[15189]: (inkscape-bin:15190): Gtk-WARNING **: Locale not supported by C library.
Feb 25 00:07:13 jiho-ibook [0x0-0x388388].org.inkscape.Inkscape[15189]: Using the fallback 'C' locale.
Feb 25 00:07:13 jiho-ibook org.x.X11[15224]: xauth: creating new authority file /Users/jiho/.serverauth.15224
Feb 25 00:07:13 jiho-ibook org.x.X11[15224]: xinit: Detected Xquartz startup, setting file=X, argv[0]=/Applications/Utilities/X11.app/Contents/MacOS/X11
Feb 25 00:07:13 jiho-ibook org.x.X11[15224]: XQuartz starting:
Feb 25 00:07:13 jiho-ibook org.x.X11[15224]: X.org Release 7.2
Feb 25 00:07:13 jiho-ibook org.x.X11[15224]: X.Org X Server 1.3.0-apple10
Feb 25 00:07:13 jiho-ibook org.x.X11[15224]: Build Date: 20080213
Feb 25 00:07:13 jiho-ibook org.x.X11[15224]: TransformProcessType: Success
Feb 25 00:07:13 jiho-ibook org.x.X11[15224]: Xquartz: run by launchd for fd 0
>>>>>> Monday, 2008 February 25 00:07:23,286Europe/Paris ---> Inkscape window appears
Feb 25 00:07:14 jiho-ibook [0x0-0x388388].org.inkscape.Inkscape[15189]: (inkscape-bin:15190): Pango-WARNING **: Error loading GDEF table 28333
Feb 25 00:07:14 jiho-ibook [0x0-0x388388].org.inkscape.Inkscape[15189]: (inkscape-bin:15190): Pango-WARNING **: Error loading GSUB table 28333
Feb 25 00:07:14 jiho-ibook [0x0-0x388388].org.inkscape.Inkscape[15189]: (inkscape-bin:15190): Pango-WARNING **: Error loading GPOS table 28333
Feb 25 00:07:17 jiho-ibook [0x0-0x388388].org.inkscape.Inkscape[15189]: (inkscape-bin:15190): Pango-WARNING **: Error loading GDEF table 28333
Feb 25 00:07:17 jiho-ibook [0x0-0x388388].org.inkscape.Inkscape[15189]: (inkscape-bin:15190): Pango-WARNING **: Error loading GSUB table 28333
Feb 25 00:07:17 jiho-ibook [0x0-0x388388].org.inkscape.Inkscape[15189]: (inkscape-bin:15190): Pango-WARNING **: Error loading GPOS table 28333
Feb 25 00:07:34 jiho-ibook org.x.X11[15224]: rlCopy.c:59: null pointer
>>>>>> Monday, 2008 February 25 00:08:07,286Europe/Paris ---> Quitting X11
Feb 25 00:08:23: --- last message repeated 1 time ---
Feb 25 00:08:11 jiho-ibook org.x.X11[15224]: Quitting XQuartz...
Feb 25 00:08:11 jiho-ibook org.x.X11[15224]: xinit: connection to X server lost.

The locale issue has been here for ever, I guess it's something in our starting script but it is harmless.
Then come messages from Xquartz
The Pango errors take some tim to appear and are, in my experience, associated at least in part with the use of Lucida Grande as Inkscape's UI font. Once again, the font is still displayed fine. This is harmless
Then again messages from Xquartz when quitting.

So basically, if you get any of these messages, don't worry, it's the normal behavior (not perfect but it works).

We'll try something else now: do you have any custom templates or the like in ~/.inkscape? Could you try moving away those and your preferences. In aTerminal:
mkdir -p inkscape-bkp
mv ~/.inkscape* inkscape-bkp
Then start Inkscape. To put them back in place:
mv inkscape-bkp/.ink* ~
rmdir inkscape-bkp
If this is indeed the problem, please try to find which file causes it (by moving back only part of your customizations. Are comfortable enough with a terminal?) and then submit a bug report with it on Launchpad.

From: rygle <pittos@...1208...>
Jiho (and others),

If any of these issues are common enough, can you please contribute some
wisdom to the http://wiki.inkscape.org/wiki/index.php/InstallHelp
InstallHelp section on the wiki?

I'm not a Mac user, but after some frustration helping my brother install
decided I could make a meaningful contribution for Mac users that could help
them navigate the X11 version nightmare. But this stuff I have no idea
about.

Well I would if I could. These different versions of X11 are a mess. The bug reports open on this are usually still lacking information while precise steps were given. I've never had a single problem with it so I don't have first hand experience. The information currently in the wiki is excellent IMHO. You did a great job. And if everyone followed these I think we would have had much less bug reports in the Panther-Tiger transition. As for Leopard, I personally use Xquartz but would not recommend it to people unless they have problems (like Stuart here). As usual: "Don't fix what ain't broken". The update Apple shipped with 10.5.2 should have improved the matter enough anyway.

Cheers,

JiHO
---
http://jo.irisson.free.fr/