[Mac OS X] Cannot launch Inkscape 0.47pre1

[Jeffrey Pfau]

I recently downloaded Inkscape 0.47pre1, and after installing it, I was unable to launch it. It and kernel_task would consume most of my CPU until I killed Inkscape (a simple SIGINT works). Upon trying it in the command line to see if it was outputting any useful information, I was greeted with this message:

(process:7537): Gtk-WARNING **: Locale not supported by C library.
 Using the fallback 'C' locale.
Xlib: extension "RANDR" missing on display ":0.0".

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.

This happens every time I try to load Inkscape. It will not terminate until I issue a SIGINT. gdb seems to say that it's stuck in an event loop. I am on Mac OS X 10.5.7 (Intel) and am using XQuartz 2.3.3.2. Removing ~/.inkscape and ~/.inkscape-etc does nothing, except that ~/.inkscape-etc will get recreated when I launch it again.

[su_v (suv-lp)]

1) Could you attach the gdb backtrace and the crash report?
2)' ~/.inkscape' is the configuration directory for Inkscape 0.46, 0.47pre stores its preferences in '~/.config/inkscape'. To reset the preferences you need to rename/remove '~/.config/inkscape/preferences.xml'.
3) Did previous versions (development snapshots, prerelease builds) launch without issues? Any new fonts installed since? Other changes in your system? Did you try to clear the fontcache (quit X11.app, rm ~/.fontconfig/*, restart Inkscape)?
4) Could you test the most recent 0.47pre1-2? There was a conflict where Inkscape is trying to read incompatible fontcaches from Macports - this has been fixed with 0.47-pre1-2 (see bug #400165).

[Jeffrey Pfau (jpfau)]

0.47pre1-2 fixes the crash. I had looked for a newer version of Inkscape in the snapshots page, but didn't see one there. I also tried to build it from latest SVN source, but autogen.sh wouldn't work. Judging from the circumstances, I'd say it probably was bug #400165, but whatever it was, it's fixed now.

[su_v (suv-lp)]

Do you have any files installed in '/opt/local/var/cache/fontconfig'?
If so, please mark this report as duplicate of bug #400165.