Inkscape has been unusable for me on the mac since mid-September due to it crashing, usually within the first one or two actions after startup. I haven't complained yet because I don't use inkscape all that often; and when have needed it, I have been able to use it on a linux machine at work; and finally, I haven't had the time to investigate enough to produce a bug report of sufficient quality to be of any use.
Maybe I should blow away all of inkscape's direct and indirect dependencies and rebuild, but that is a huge number of ports. I might as well blow away my entire ports tree and rebuild it. All I can offer is an excerpt from a recent crashlog: Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0x00007fff84f403d6 __kill + 10 1 libSystem.B.dylib 0x00007fff84fe0913 __abort + 103 2 libSystem.B.dylib 0x00007fff84fe0981 abort_report_np + 0 3 libglib-2.0.0.dylib 0x0000000102505bf8 g_assertion_message + 328 4 libglib-2.0.0.dylib 0x0000000102506142 g_assertion_message_expr + 82 5 libgtk-x11-2.0.0.dylib 0x0000000101a3a947 get_icon_fallback + 103 6 libgtk-x11-2.0.0.dylib 0x0000000101a352d7 idle_populate_func + 839 7 libgdk-x11-2.0.0.dylib 0x0000000101db8c19 gdk_threads_dispatch + 89 8 libglib-2.0.0.dylib 0x00000001024e0919 g_main_context_dispatch + 553 9 libglib-2.0.0.dylib 0x00000001024e3fb1 g_main_context_iterate + 961 10 libglib-2.0.0.dylib 0x00000001024e42c5 g_main_loop_run + 485 11 libgtk-x11-2.0.0.dylib 0x00000001019dfd90 gtk_main + 176 12 inkscape 0x00000001000303a0 sp_main_gui(int, char const**) + 1280 13 inkscape 0x000000010002fa1e main + 1230 14 inkscape 0x000000010002eec8 start + 52 It might be interesting to know if others see the same in their crashlogs. Look for them in ~/Library/Logs/CrashReporter/, with names like inkscape_<date>_<machine>.crash - Harald _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
