On 14/11/10 14:40, Harald Hanche-Olsen wrote: > + ~suv <suv...@users.sourceforge.net>: > >> The following bugs also affect Inkscape (0.48.0 and trunk) if installed >> with MacPorts using GTK+ 2.22: >> [...] >> >> Bug #651678 “crashes with assertion failure on startup”: >> <https://bugs.launchpad.net/inkscape/+bug/651678> >> >> The second one happens as soon as there are entries in >> '~/.recently-used.xbel'. Workaround (so far): install 'gnome-icon-theme' >> and add this line to ~/.gtkrc-2.0: >> >> gtk-icon-theme-name = "gnome" > > Yes, that does work. Not that it helps me, for now I get instead a > crash as soon as I try to change a line thickness: > > Program received signal EXC_BAD_ACCESS, Could not access memory. > Reason: KERN_INVALID_ADDRESS at address: 0x00000000056bd978 > 0x00000001003d2dc9 in sp_stroke_style_line_update ()
That's the issue Jonathan initially asked about, see Bug #629363 in Inkscape: “inkscape 0.48 crashes in sp_stroke_style_line_update() when drawing with opened "Fill and Stroke" dialog” <https://bugs.launchpad.net/inkscape/+bug/629363> I can't reproduce the crash with Inkscape 0.48.0 installed with an up-to-date Macports tree (using gtk2 2.22), nor with Inkscape 0.48+devel built using the same dependencies, on Mac OS X 10.5.8 (i386) in 32bit. The issue seems related to building inkscape or one of the dependencies on 64bit operating systems, also described in Bug #672111 in Inkscape: “Operations in Fill/Stroke dialog results in SEGV (on a 64bit Mac)”: <https://bugs.launchpad.net/inkscape/+bug/672111>: "(…) problem is in handling of 64bit address in Inkscape or Glib." No workaround or fix available at the moment. ~suv _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
