Mac OS X: Inkscape crashes after aqua version compiled?
Hello,
last two days I can no longer make my inkscape X11 run. I compiled an inkscape aqua, which runs quite nice, but now when launching inkscape X11 - bang! - I'm quite sure I hat some days with a co-existance of both versions - maybe it occurred since the update to macports 1.8.1 ?
Did inkscape aqua change preferences which make the X11 version crash now?
I do attach the crashreporter log and will be happy to proviede further information.
(Mac OS X 10.4.11, G4 PPC)
Greetings,
Wolf
On 2/10/09 08:43, Wolf Drechsel wrote:
last two days I can no longer make my inkscape X11 run. I compiled an inkscape aqua, which runs quite nice, but now when launching inkscape X11 - bang! - I'm quite sure I hat some days with a co-existance of both versions - maybe it occurred since the update to macports 1.8.1 ?
Did inkscape aqua change preferences which make the X11 version crash now?
I do attach the crashreporter log and will be happy to proviede further information.
(Mac OS X 10.4.11, G4 PPC)
You built both Inkscape versions yourself? From SVN? With separate MacPorts trees? Which Inkscape/X11 did run previously before compiling a new Macports tree and Inkscape/Aqua? (release or revision number) In case you built a Inkscape/X11 from SVN yourself - you are aware of the recent broken pango libraries on MacPorts? http://trac.macports.org/ticket/21679
From the crash report it looks like the cases on Leopard when Inkscape
hangs while creating/reading the font cache. Often it helps to clear the font cache (rm ~/.fontconfig/*) and restart Inkscape. But I don't know how exactly the fontcache works on Tiger with its ancient version of X11 (1.1.3 as far as I know).
~suv
You built both Inkscape versions yourself? From SVN? With separate MacPorts trees?
No! - I used the X11 version out of the box - and compiled the aqua myself.
I use the 0.46 X11 inkscape.app bundle - and the sources folder has the name inkscape-22205
From the crash report it looks like the cases on Leopard when Inkscape hangs while creating/reading the font cache. Often it helps to clear the font cache (rm ~/.fontconfig/*) and restart Inkscape. But I don't know how exactly the fontcache works on Tiger with its ancient version of X11 (1.1.3 as far as I know).
I did a rm ~/.fontconfig/* - but it didnt help.
Yours
Wolf
On 2/10/09 23:22, Wolf Drechsel wrote:
You built both Inkscape versions yourself? From SVN? With separate MacPorts trees?
No! - I used the X11 version out of the box - and compiled the aqua myself.
I use the 0.46 X11 inkscape.app bundle - and the sources folder has the name inkscape-22205
this is most likely bug #400165 "Binary Inkscape dist crashes when MacPorts is installed": https://bugs.launchpad.net/inkscape/+bug/400165
and here is a bug where the same happened on Tiger: https://bugs.launchpad.net/inkscape/+bug/183322 comments 7-14
The fix is to change the 'Contents/Resources/etc/fonts/fonts.conf' inside the Inkscape 0.46 package as described by Michael Wybrow in bug #400165 comment #4:
The problem is Inkscape trying to read incompatible fontcaches from Macports. The fix is to modify Inkscape.app/Contents/Resources/etc/fonts/fonts/conf to remove the following line: <cachedir>/opt/local/var/cache/fontconfig</cachedir>
hth, ~suv
Hello ~suv,
you made my day - early in the morning! - Your hint did it!
A little time I was afraid of now being tied to my home-brew forever…
Should this line be permanently be removed in any inkscape release?
Thanks a lot!
Wolf
this is most likely bug #400165 "Binary Inkscape dist crashes when MacPorts is installed": <https://bugs.launchpad.net/inkscape/+bug/ 400165>
and here is a bug where the same happened on Tiger: https://bugs.launchpad.net/inkscape/+bug/183322 comments 7-14
The fix is to change the 'Contents/Resources/etc/fonts/fonts.conf' inside the Inkscape 0.46 package as described by Michael Wybrow in bug #400165 comment #4:
The problem is Inkscape trying to read incompatible fontcaches from Macports. The fix is to modify Inkscape.app/Contents/Resources/etc/fonts/fonts/conf to remove the following line: <cachedir>/opt/local/var/cache/fontconfig</cachedir>
On 3/10/09 07:54, Wolf Drechsel wrote:
On 2/10/09 23:42, ~suv wrote:
this is most likely bug #400165 "Binary Inkscape dist crashes when MacPorts is installed": https://bugs.launchpad.net/inkscape/+bug/400165
and here is a bug where the same happened on Tiger: https://bugs.launchpad.net/inkscape/+bug/183322 comments 7-14
The fix is to change the 'Contents/Resources/etc/fonts/fonts.conf' inside the Inkscape 0.46 package as described by Michael Wybrow in bug #400165 comment #4:
The problem is Inkscape trying to read incompatible fontcaches from Macports. The fix is to modify Inkscape.app/Contents/Resources/etc/fonts/fonts/conf to remove the following line: <cachedir>/opt/local/var/cache/fontconfig</cachedir>
you made my day - early in the morning! - Your hint did it!
A little time I was afraid of now being tied to my home-brew forever…
Should this line be permanently be removed in any inkscape release?
as is noted in both bug reports the fix was committed (in rev. 21860). i.e. any binary package for Tiger >= 0.47pre2 includes it.
Currently there's only a 0.47pre1 Tiger available on sourcefourge.net - it will need to be 'patched' manually if running on a system with MacPorts installed. Any future prerelease and release packages (for Tiger and Leopard+) include the fixed font configuration file.
~suv
On 2/10/09 23:22, Wolf Drechsel wrote:
You built both Inkscape versions yourself? From SVN? With separate MacPorts trees?
No! - I used the X11 version out of the box - and compiled the aqua myself.
I use the 0.46 X11 inkscape.app bundle - and the sources folder has the name inkscape-22205
You know there's a Tiger build of Inkscape 0.47pre1 on sf.net? (still needs X11 of course ;-) http://sourceforge.net/projects/inkscape/files/inkscape/0.47pre1/
~suv
2009/10/2 Wolf Drechsel <drechsel@...2249...>:
I do attach the crashreporter log and will be happy to proviede further information.
Compile with debugging information, run 'gdb inkscape' and attach the backtrace, using the instructions from earlier :) The crashreporter log doesn't contain any useful information. Regards, Krzysztof
participants (3)
-
Krzysztof Kosiński -
Wolf Drechsel -
~suv