track calligraphic path crash on Mac X 1.6

[crickxson]

With a Wacom, on Mac X 1.6, was not able to make work more than a few path the tracking (with ctrl). I remember previous version without this problem

[su_v (suv-lp)]

possibly duplicate of
Bug #284546 “SVN, rev.19997: Crash on using calligraphy tracing tool with wacom tablet”
<https://bugs.launchpad.net/inkscape/+bug/284546>
related:
Bug #324673 “Calligraphy tool crashes app when guide path used”
<https://bugs.launchpad.net/inkscape/+bug/324673>

Could you provide more information about the crash?
Console messages:
1) open 'Applications > Utilities > Console', select 'All Messages' from the log list, clear the display
2) Restart Inkscape and reproduce the crash
3) Copy all console messages that are now displayed in the 'Console' window, paste them into a new TextEdit document (in 'Plain Text' format) and save it

Crash report:
4) in 'Console' display the log list again and go to
   'Logfiles > ~/Library/Logs > DiagnosticReports'
5) look for the related (latest) crash report for 'inkscape-bin', ctrl-click it and use 'Reveal in Finder' to locate it.

Attach both the saved console messages and the crash report to your next comment here.

[crickxson (crickxson)]

redoing the crash - doc 1/2 - thanks for caring!

[crickxson (crickxson)]

redoing the crash - doc 2/2 - thanks for caring!

[crickxson (crickxson)]

It's a duplicated of

Bug #284546 “SVN, rev.19997: Crash on using calligraphy tracing tool with wacom tablet”
<https://bugs.launchpad.net/inkscape/+bug/284546>

and

Bug #324673 “Calligraphy tool crashes app when guide path used”
<https://bugs.launchpad.net/inkscape/+bug/324673>

Sorry, i haven't found it

Thanks for all the work, it's one of the most beautiful and interesting feature of Inkscape!

[su_v (suv-lp)]

The crash report is not a current one (Date/Time: 2010-03-04 22:52:34.693 +0100) - if OS X saved a new one it would be the last in the list of 'inkscape-bin_2010-03-…' entries. But from the console messages it looks like this is a duplicate of earlier reported bug #284546.