internal error window on launch

[gury julien]

Last login: Sun Jan 22 17:40:06 on ttys000
/Applications/Inkscape.app/Contents/MacOS/Inkscape ; exit;
new-host:~ julien$ /Applications/Inkscape.app/Contents/MacOS/Inkscape ; exit;
Warning: AppleCollationOrder setting not found, using AppleLocale.
Setting Language: fr_FR.UTF-8
Xlib: extension "RANDR" missing on display "/tmp/launch-gdFdYh/org.x:0".
/Users/julien/.inkscape-etc/gtkrc:56: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/Users/julien/.inkscape-etc/gtkrc:57: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/Users/julien/.inkscape-etc/gtkrc:58: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.

(inkscape-bin:4538): Gtk-WARNING **: Could not find the icon 'object-visible'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
 http://icon-theme.freedesktop.org/releases

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.
logout

[Opération terminée]

[su_v (suv-lp)]

1) Please provide information about the version of Mac OS X you are using, as well as which version of Inkscape you have installed (if possible, name of the DMG)
2) Please attach the crash report created by the system: you can find it in 'Home > Library > Logs > DiagnosticReports' for 'inkscape-bin' (the file name of the crash report includes a date and time stamp).
3) Please clarify: "internal error window on boot" - do you really mean 'boot' (starting the computer) or rather 'launch' (launching the inkscape application)?

Probably a duplicate of
Bug #623640 “inkscape 0.48 crashes on startup in colorprofile_get_system_profile_handle()”
<https://bugs.launchpad.net/inkscape/+bug/623640>
but additional information (crash report) is needed to further investigate the issue.

[su_v (suv-lp)]

Forgot to mention: the warnings in the console log shown in the bug description are harmless and do not cause Inkscape to crash, nor are they related to Inkscape crashing. The relevant information is in the backtrace of the crash report.

[gury julien (urbandtribe)]

yes i have make a mistake it's when it lauch not when the computer boot sorry i'm french so i doesn't speak very well in english i'm on mac osx Mac OS X 10.6.8 and this is with inkscape 0.48.2-1-SNOWLEOPARD that there is a problem it seems to be like the probleme that you say to me but i admit i a very newbies in this sort of things regards julien

Process: inkscape-bin [1678]
Path: /Applications/Inkscape.app/Contents/Resources/bin/inkscape-bin
Identifier: inkscape-bin
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: bash [1675]

Date/Time: 2012-01-22 16:46:53.300 +0100
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x92afddc8 _UTF8_mbsnrtowcs + 62
1 libSystem.B.dylib 0x92b35c90 mbsrtowcs_l + 100
2 libSystem.B.dylib 0x92b3378a __collate_mbstowcs + 149
3 libSystem.B.dylib 0x92aa28ee strcoll_l + 121
4 libSystem.B.dylib 0x92aa286f strcoll + 61
5 libglib-2.0.0.dylib 0x0211231c g_utf8_collate + 124
6 inkscape-bin 0x0001a1e2 findThings() + 274
7 inkscape-bin 0x0001b5b3 Inkscape::colorprofile_get_system_profile_handle() + 611
8 inkscape-bin 0x0001bc86 Inkscape::colorprofile_get_display_transform() + 1382
9 inkscape-bin 0x0027258a sp_canvas_paint_rect_internal(PaintRectSetup const*, NRRectL) + 2202
10 inkscape-bin 0x00272468 sp_canvas_paint_rect_internal(PaintRectSetup const*, NRRectL) + 1912
11 inkscape-bin 0x002778b5 sp_canvas_paint_rect(SPCanvas*, int, int, int, int) + 437
12 inkscape-bin 0x00277d2b do_update(SPCanvas*) + 939
13 inkscape-bin 0x00277ec9 idle_handler(void*) + 73
14 libglib-2.0.0.dylib 0x020de4bd g_main_context_dispatch + 573
15 libglib-2.0.0.dylib 0x020e234b g_main_context_iterate + 1179
16 libglib-2.0.0.dylib 0x020e2627 g_main_loop_run + 439
17 libgtk-x11-2.0.0.dylib 0x01514f91 gtk_main + 177
18 libgtkmm-2.4.1.dylib 0x00f1859b Gtk::Main::run() + 27
19 inkscape-bin 0x000051aa sp_main_gui(int, char const**) + 1146
20 inkscape-bin 0x001fc712 Inkscape::NSApplication::Application::run() + 178
21 inkscape-bin 0x00003b51 main + 353
22 inkscape-bin 0x00003366 start + 54

Thread 1:
0 libSystem.B.dylib 0x92a48aa2 __semwait_signal + 10
1 libSystem.B.dylib 0x92a4875e _pthread_cond_wait + 1191
2 libSystem.B.dylib 0x92a482b1 pthread_cond_timedwait$UNIX2003 + 72
3 libgthread-2.0.0.dylib 0x020ab5eb g_cond_timed_wait_posix_impl + 107
4 libglib-2.0.0.dylib 0x020b2f21 g_async_queue_pop_intern_unlocked + 225
5 libglib-2.0.0.dylib 0x020b31a4 g_async_queue_timed_pop + 52
6 libglib-2.0.0.dylib ...

[su_v (suv-lp)]

Based on the backtrace from the crash report, it's the same issue as reported in bug #623640

Here are two workarounds confirmed by other users:
1) use a temporary installed Inkscape 0.47:
«A workaround to use 0.48 is to download an older version of Inkscape, go into preferences and check "Retrieve profile from display". Close Inskape. Now start 0.48 and it don't crash on startup.»
Inkscape 0.47 can be downloaded from here:
<http://sourceforge.net/projects/inkscape/files/inkscape/0.47/Inkscape-0.47-1.LEOPARD%2B.dmg/download>

2) open Inkscape using 'Open with…' command of existing SVG file:
«instead of regression to 0.47 just launch inkscape selecting an svg file and use the "open with" command, the program opens, and you change the "Preferences/Color management/Retrieve profile from display" as needed.»

(See attached screenshot for the related preference pane and profile setting in French).

[su_v (suv-lp)]

Please report back whether one of the workaround allowed you to successfully launch Inkscape 0.48.2 (after changing the setting for the display profile), so that this report can be linked as duplicate to bug #623640.

[gury julien (urbandtribe)]

ok big thank's to you i use the 0.47 and it works courage for the bug fix

[su_v (suv-lp)]

Thank you for the feedback and confirmation that the workaround did indeed work around the issue :)

Linking as duplicate to bug #623640. Please add a comment here and revert the duplicate status if you don't agree or have new information indicating that the issues are different after all.